Schema for {collectionId}/locations query response GeoJSON

[mrauhala]

• standard property names for GeoJSON (like wigos ids, name, available parameters and other metadata like links)
• id for different data types, like for observations wigos id, METARs and TAFs ICAO id and so on
• how and when to use other geometries than Points
• filtering of the locations query
• paging

This issue may need to be divided to multiple issues.

[havardf]

@mrauhala Are you thinking a specifc schema for the Observations data here? Or a general schema for any usage of the locations data query?

[mrauhala]

@mrauhala Are you thinking a specifc schema for the Observations data here? Or a general schema for any usage of the locations data query?

Most of it can probably be generic, but some of it have to be data specific like observations, radar, warnings and so on.

[geira]

A possible complication here is that we are sometimes required to issue aviation weather data for locations without registered ICAO codes, e.g. oil platforms or helicopter landing pads.

[havardf]

@geira ICAO codes falls outside the immediate concerns for RODEO, so I think we can postpone thinking about that.

@Teddy-1000 Could you help with this issue? E-SOH already have a schema for this, which is similar or maybe identical to https://github.com/opengeospatial/ogcapi-environmental-data-retrieval/blob/master/core/standard/openapi/schemas/edr-geojson/edrFeatureCollectionGeoJSON.yaml