View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000540 | file | General | public | 2024-07-08 22:18 | 2024-11-10 17:02 |
| Reporter | manfredsc | Assigned To | christos | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | HEAD | ||||
| Summary | 0000540: New IANA entry for BUFR | ||||
| Description | There is now an official entry for BUFR at IANA: https://www.iana.org/assignments/media-types/application/bufr BUFR is a meteorological data format for storing point or time series data. IANA has now assigned a mime format for it (https://www.iana.org/assignments/media-types/application/bufr): application/bufr;edition=3 application/bufr;edition=4 The original name [Binary Universal Form for the Representation of meteorological data (BUFR)] is too long for the magic format, so one has to shorten it, e.g. Binary Universal Form data (BUFR) I suggest adding the following definition to the "meteorological" section: # https://en.wikipedia.org/wiki/BUFR, https://www.iana.org/assignments/media-types/application/bufr 0 string BUFR >7 byte =3 Binary Universal Form data (BUFR) Edition 3 !:mime application/bufr !:ext bufr >7 byte =4 Binary Universal Form data (BUFR) Edition 4 !:mime application/bufr !:ext bufr | ||||
| Tags | No tags attached. | ||||
|
|
PS1: files are often prepended by a so called "TELEX header", so the "BUFR" magic is not at the file start: #> od -t x1 -c example.bufr 0000000 49 53 4e 44 30 31 20 45 44 5a 57 20 30 38 31 37 I S N D 0 1 E D Z W 0 8 1 7 0000020 30 30 0d 0d 0a 42 55 46 52 00 15 02 04 00 00 16 0 0 \r \r \n B U F R \0 025 002 004 \0 \0 026 ... The header is usually 21 bytes long and ends with "\r\r\n", so the magic starts at byte 22. Not sure how to deal with this optional header (which does not help with identifying the file). PS2: the bytes 5-7 encode the message length (in the above example it would be 5378), byte 8 is the edition number. I guess it is not worth decoding and displaying the message length by the "file" command. |
|
|
Added, thanks |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-07-08 22:18 | manfredsc | New Issue | |
| 2024-07-08 23:17 | manfredsc | Note Added: 0004064 | |
| 2024-11-10 17:02 | christos | Assigned To | => christos |
| 2024-11-10 17:02 | christos | Status | new => assigned |
| 2024-11-10 17:02 | christos | Status | assigned => resolved |
| 2024-11-10 17:02 | christos | Resolution | open => fixed |
| 2024-11-10 17:02 | christos | Fixed in Version | => HEAD |
| 2024-11-10 17:02 | christos | Note Added: 0004098 |
