search

opengeospatial / ogcapi-routes

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

Remove from Core: "Routing engine", "Routing algorithm" or "Source dataset" #23

Open cportele opened 3 years ago

cportele commented 3 years ago

See https://github.com/opengeospatial/ogcapi-routes/issues/19#issuecomment-816389532

My view is that the typical routing API will not offer the requirements classes "Routing engine", "Routing algorithm" or "Source dataset". This is just too complicated for most users. As a result, I think they should be dropped from Core and be specified in an extension for those special routing APIs that want to expose such information and offer choices.

jeffharrison commented 3 years ago

April 27, 2021 Routes SWG meeting discussed this Issue.

Consensus is to make Core as simple as possible. No objection to removing these as long as the Requirements Classes are included in an Extension. Clemens P assigned task to move proposal forward.

SWG also recommended that Elevation (Issue #19 ) be assessed for potential integration in same Extension.

cportele commented 3 years ago

See PR #24. I have also created a stub for the elevation model requirements class.