This issues summarizes the outstanding tasks to move both the OGC Route Exchange Model and OGC API - Routes - Part 1: Core to the approval process. We will update the issue as we make progress.
Route Exchange Model (REM)
In review (open issues with a Pull Request)
61
33
34
49
60
To be drafted (open issues with a decision)
67
Add informative text that actions can be associated with waypoints. When there is a agreed model for actions, normative text could be added in a future revision.
Remove maxHeight and maxWeight from RouteOverview plus maxHeight, maxWeight and duration from RouteSegment. Add them in the respective conformance classes of the API.
58
Mention possibility to link to alternate representations (e.g. GTFS)
To be discussed
67
Remove also roadName, speedLimit and couple these to the modes in the API? For example, the two attributes could apply for motor vehicles.
Move to version 2
68
Timed actions could be associated either by introducing a waypoint with the action based on estimated trip time or by associating timed actions with the route (overview).
69
API
In review (open issues with a Pull Request)
none
To be drafted (open issues with a decision)
62
Move "preference" out of the Core requirements class into the Modes requirements class.
If the Modes requirements class is supported, a new operation is added that lists all available modes. A mode will specify the preferences for optimizing the route that are available for that mode. Information about the preferences and modes will be removed from the Conformance Declaration.
Modes and preferences will be described by objects. Pre-defined properties are title and description. The mode and preference objects can be extended with additional properties. For example, the UxS group can specify mode parameters that are specific to UxS vehicles.
The "preference" query parameter will be moved to the Modes requirements class.
63
Add operating areas as a new resource in a new requirements class.
64
Remove "Obstacles" requirements class from v1.0. The plan is to add a more general "Restrictions" requirements class in v1.1.
58
Mention possibility to support other route representations beside REM (e.g., GTFS).
44
Split into two parts, Part 1: Compute Routes and Part 2: Manage Routes. Add Route Creation to Part 2.
When creating a new route in Part 2 through a CREATE request, the route must include additional metadata describing the route (the parameters used to compute the route). This needs to be added to the REM.
Querying routes should support queryables to select a subset of the available routes.
To be discussed
64
@cportele to make a proposal
Other tasks
58
Compile OpenAPI definition after changes are complete
This issues summarizes the outstanding tasks to move both the OGC Route Exchange Model and OGC API - Routes - Part 1: Core to the approval process. We will update the issue as we make progress.
Route Exchange Model (REM)
In review (open issues with a Pull Request)
61
33
34
49
60
To be drafted (open issues with a decision)
67
maxHeightandmaxWeightfromRouteOverviewplusmaxHeight,maxWeightanddurationfromRouteSegment. Add them in the respective conformance classes of the API.58
To be discussed
67
roadName,speedLimitand couple these to the modes in the API? For example, the two attributes could apply for motor vehicles.Move to version 2
68
69
API
In review (open issues with a Pull Request)
none
To be drafted (open issues with a decision)
62
titleanddescription. The mode and preference objects can be extended with additional properties. For example, the UxS group can specify mode parameters that are specific to UxS vehicles.63
64
58
44
To be discussed
64
Other tasks
58