Closed jeffharrison closed 3 years ago
jeffharrison
commented
3 years ago April 27, 2021 Routes SWG Mtg discussed.
Consensus is to include Mode but "do not fix any values" and register values of Mode in OGC Naming Authority.
SWG recommends establishing Mode values on the OGC Naming Authority. But first consider whether we want other registers in OGC-NA for Routing API, before passing motion. Also review existing Transportation taxonomies and ontologies.
jeffharrison
commented
3 years ago May 11, 2021 Routes SWG Mtg discussed.
One approach is to just create a new Conformance Class in Core, each server can offer Modes option, and declare the Modes it supports. Servers should be allowed to ignore Mode parameters.
SWG members do not want to restrict to registered values of Mode in OGC Naming Authority.
Discussion - If Mode is already listed in OGC Naming Authority recommend using registered values.
Clemens P offered to write a Pull Request for discussion at next SWG meeting.
In OGC API - Routes consider support for specifying 'Mode' of transport (on-road, bicycle, etc.) in requests.
Mode is a restriction based on the type of transport desired when computing the route. For instance: Mode may be “On Road”, Mode may be “Off Road”, Mode may be “Air Route”, etc.
SWG recommends that clients be able to support one or more Modes in an API request.
Note: Need to include wording on dependencies between the 'Mode' and the routing algorithms, engines, data sets. Clarify how the API handles as needed.