I noticed that our EDR API returns different responses for
POINT and MULTIPOINT queries, both are correct but other one is very inconvenient. We should put in the profile, correct CoverageJSON responses for each query.
Position point (POINT) query:
https://opendata.fmi.fi/edr/collections/ecmwf/position?f=CoverageJSON¶meter-name=Temperature&coords=POINT%28-50.666+-9.599%29&datetime=2025-11-02T21:00Z/2025-11-03T21:00Z
Notice how all time steps are in same coverage. (CORRECT)
Position query with MULTIPOINT works, but returns inconvenient CoverageJSON
https://opendata.fmi.fi/edr/collections/ecmwf/position?coords=MULTIPOINT%28%28-66.730+-22.069%29%2C%28-59.097+-0.359%29%29&f=CoverageJSON¶meter-name=Temperature&datetime=2025-11-02T21:00Z/2025-11-03T21:00Z
Notice how each point/time combination is a separate coverage (INCORRECT). Also this returns coverage, not PointSeries.
I have seen elsewhere also position query to return 1x1 size of grid, which is also technically correct, but different.
I propose that we to profile, domainType of CoverageJSON for different queries (position in this case) and how data is split to individual coverages. In this case each point would be separate Coverage with domainType PointSeries.
I noticed that our EDR API returns different responses for
POINT and MULTIPOINT queries, both are correct but other one is very inconvenient. We should put in the profile, correct CoverageJSON responses for each query.
Position point (POINT) query:
https://opendata.fmi.fi/edr/collections/ecmwf/position?f=CoverageJSON¶meter-name=Temperature&coords=POINT%28-50.666+-9.599%29&datetime=2025-11-02T21:00Z/2025-11-03T21:00Z
Notice how all time steps are in same coverage. (CORRECT)
Position query with MULTIPOINT works, but returns inconvenient CoverageJSON
https://opendata.fmi.fi/edr/collections/ecmwf/position?coords=MULTIPOINT%28%28-66.730+-22.069%29%2C%28-59.097+-0.359%29%29&f=CoverageJSON¶meter-name=Temperature&datetime=2025-11-02T21:00Z/2025-11-03T21:00Z
Notice how each point/time combination is a separate coverage (INCORRECT). Also this returns coverage, not PointSeries.
I have seen elsewhere also position query to return 1x1 size of grid, which is also technically correct, but different.
I propose that we to profile, domainType of CoverageJSON for different queries (position in this case) and how data is split to individual coverages. In this case each point would be separate Coverage with domainType PointSeries.