1 / 11

IPET-DRMM

IPET-DRMM. WMO; Name of Department (ND). IPET-DRMM. Inter-Programme Expert Team on Data Representation Maintenance and Monitoring looks after traditional alphanumeric codes (SYNOP, TEMP, etc) Table Driven Code Forms (BUFR, GRIB, CREX) Met 1-5 July in Tokyo. Key Issues impacting ET-SUP.

meir
Download Presentation

IPET-DRMM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPET-DRMM WMO; Name of Department (ND)

  2. IPET-DRMM Inter-Programme Expert Team on Data Representation Maintenance and Monitoring looks after traditional alphanumeric codes (SYNOP, TEMP, etc) Table Driven Code Forms (BUFR, GRIB, CREX) Met 1-5 July in Tokyo

  3. Key Issues impacting ET-SUP • Traditional Alphanumeric Codes • Proliferation of unstructured information on instrumentation • Multiple (inconsistent) requests for representing wind profiler data • Standard approach to (radiosonde) wind at poles • JCOMM SHIP identifier masking

  4. Migration no more changes to codes (excludes OPMET) encourage AWS/sonde suppliers to provide TDCF as default BUFR encourage standard templates makes sure expected information present encourage manufacturers to send sample messages to IPET-DRMM for validation Traditional Alphanumeric Codes

  5. Proliferation of unstructured instrument information • BUFR code tables • limited size • prefer to use hierarchy • Wind profiler (IPET-DRMM-1: Doc 3.2(2)) • have proposals to add: • Doppler radar wind profiler • Doppler lidar wind profiler • Backscatter lidar (wind profiler) • Spaced antenna wind profiler • Want – contact to work with

  6. Proliferation of unstructured instrument information (2) • Balloons (IPET-DRMM-1: Doc 3.2(7)) • current balloon types • some – bursting height • some – materials • some – not clear • Want – contact to work with

  7. Multiple requests for representing wind profiler data Doc 3.(2) – Radar Wind Profiler template “A number of radar windprofiler networks exist worldwide, and the data are encoded in BUFR to be exchanged over the GTS. However, each of these networks uses a different implementation of the BUFR code.” • Lack of standard approach increases costs, and risks of error, for end users • Want – contact point to help standardize

  8. Standard approach to (radiosonde) wind at poles • Although not noted in the draft minutes of the meeting, there is a need to standardize on the difinition of wind components over the poles. • Is this an ET-SUP or CIMO issue?

  9. JCOMM ship identifier masking (info only) • JCOMM has a proposal to encrypt ship identifiers • use highly secure algorithm • management of software? • export controls? • need to distribute encryption/decryption keys • to all Members • key distribution challenge • high likelihood of compromise

  10. Summary • Traditional Alphanumeric Codes • Proliferation of unstructured information on instrumentation • Multiple (inconsistent) requests for representing wind profiler data • Standard approach to (radiosonde) wind at poles

  11. Thank you for your attention • This space can be used for • contact information

More Related