Oslo meeting June 12: Comments on JSON structure and ORD functions #2
Description
Here are some of the questions or comments raised in the Oslo meeting on June 12th. These can be splittend to different issues, if needed to have actions:
- JSON -structure e.g. location of composite, radar metadata and links
- In collection data queries: location end point in ORD collections didn't return anything, if kept without filtering term. The number of files is so big that there needs to be a something to limit the amount of queried data.
- In the collection there are over 3000 parameters: how the discovery metadata can be related to these.
- ACRR is in abbreviation, this is not descriptive outside the radar field. ODIM standard is used at the moment until CF-convention also includes the needed parameters. This is OPERA work to have the ODIM needed parameters to be included in FM301 and therefore also to CF-conventions.
- KNMI demonstrated the use of authorized API in fetching the data. Discussion on how to deal this with MeteoGate as well. Could MeteoGate have a proxy key? Then the rate limits would be set to all users using this proxy key, which would not be good. MeteoAlarm uses "short-term" existing keys to their S3 bucket. This might be solution also for ORD national products.
- Does the JSON-structure include the period of how long the national product is available in their platform. It is in the comment field.