search

opengeospatial / ogcapi-routes

public repo for OGC API - Routes Standards Working Group
Other
10 stars 3 forks source link

Relationship between Route Exchange Model and OGC API - EDR #34

Open ghobona opened 2 years ago

ghobona commented 2 years ago

In Testbed-17, the REM is used to represent flight routes. One of the use cases for OGC API - EDR is retrieval of trajectories. Several of the implementers of OGC API - EDR are meteorological agencies that support and work closely with the aviation industry. So the relationship of the REM to OGC API - EDR needs to be clarified.

ghobona commented 2 years ago

Cc: @cportele @jeffharrison @chris-little @solson-nws

ghobona commented 2 years ago

Note that the relationship between the OGC API - EDR and Moving Features standards is documented at https://docs.ogc.org/is/19-086r4/19-086r4.html#toc74

skyNacho commented 2 years ago

Actually, the current draft of REM does not support flight routes. The implementation in Testbed 17 was using JSON-FG to test the concept of extending REM in order to support flight routes. But it is just a proof of concept that was presented at the Routing SWG but any further extension to current REM draft was postponed.

On the other hand, in the September OGC Meeting, at the Routes SWG session, Kyoungsook Kim started an interesting discussion on the possible overlap and complementarity between Moving Features and Routes standards.

cportele commented 2 years ago

To add to @skyNacho's comment: For the REM / MF-JSON relationship there is already an issue: #33.

cportele commented 1 year ago

Meeting 2022-09-20: Similar to #33, address both issues together.

chris-little commented 1 year ago

@cportele In the OGC Portal, I saw a GTM meeting today (2022-09-20) but nothing on Thursday 2022-09-22. except the Met Ocean DWG. I can set up an EDR API SWG.

cportele commented 1 year ago

@chris-little - I typed the wrong date. As you pointed out, the meeting was on the 20th. This was to record what we discussed/decided in the meeting, not to plan another meeting. I fixed this. Sorry for any confusion...