Public comment requested: OGC API - Routes - Part 1: Core Standard and OGC Route Exchange Model Standard

Status: 
Please note:  This Request is scheduled to close on 9 May 2022.
Open Date: 
Thursday, 2022-04-07
Closing Date: 
Monday, 2022-05-09

The Open Geospatial Consortium (OGC) seeks public comment on the candidate OGC API - Routes - Part 1: Core Standard and related candidate OGC Route Exchange Model Standard. The candidate OGC API - Routes Standard specifies the fundamental API building blocks for interacting with on-road route resources, and uses the Route Exchange Model to represent routes. 

Using geospatial information to plan routes for travel and logistics is among the most common uses of geospatial and location-based technologies, with countless routes being generated daily by smartphone users, logistics companies, and others. In support of this, road network data, routing & navigation algorithms, and route calculation services are now available from many different providers and sources. While this diversity in the marketplace is generally beneficial to consumers of route information, it makes accessing, integrating, overlaying, or comparing routes from different routing services overly complex.

The candidate OGC API - Routes - Part 1: Core Standard enables a simple method for an application to query any number of routing and/or data providers, even across multiple modes of transport, and present the resulting routes to the user in a single place. The capability for a client to request and retrieve routes from a routing API provider and share routes between applications will improve interoperability for many users, communities, and enterprises.

The candidate OGC API - Routes - Part 1: Core Standard provides the methods and apparatus for the execution of basic commands to retrieve, update, share, and delete routes, and will interface with other geospatial resources that use OGC APIs. Implementations of this candidate API standard leverage the OpenAPI specification for describing the resources and capabilities they offer. Complementing the API standard, the candidate Route Exchange Model standard provides a standardized method to share routes, regardless of the underlying proprietary data, routing engine software, or algorithms.

  • For providers of routes, the API building blocks and the Route Exchange Model provide a simple model to publish and offer those routes as resources for use by other systems.
  • For developers building infrastructures, the API building blocks provide an abstraction layer to leverage existing routing engines and algorithms using modern APIs - saving development and deployment time and costs.
  • For users, applications, and enterprises, the capability to get routes across a common API, regardless of the underlying routing data, engines, or algorithms, represents a significant step forward in geospatial interoperability.

OGC recognizes that in addition to on-road routing there are many environments for implementing open routing, including off-road, air, sea, Smart Cities, and many others, which may be addressed as future work. In addition, some communities may require specialized parameters in their Routing API. Accordingly, any on-road routing API will accept two waypoints: the start and end position. APIs are, however, free to support additional waypoints between the start and end positions, and be extensible to support parameters required by diverse implementation communities. This too could be addressed as future work or extensions.

Comment: 

Comments on the standard can be submitted via the OGC Routing SWG GitHub Repository.

Subscribe: 

Comments and development can be tracked via the OGC Routing SWG GitHub Repository.