This is an update of a simplified version of the TripGo API, where we've incorporated feedback from developers, added a clearer structure to the endpoints, aligned varies data models with those from schema.org and FIWARE, and moved to Open API 3.0 format (mostly so we can use oneOf).
The documentation for how "mode identifiers" are structures, point to the TripGo developer page – it would make sense to move this repo, e.g., the Wiki or a Markdown file.
Same applies to the placeholders in what we call "segment templates". This should either also be moved here or the /routing/grouped/ endpoint could be considered out of scope for this API as it's not strictly speaking necessary, and more of a nice-to-have.
For polylines and polygons we're using Google's encoded polyline format. This could be moved to GeoJSON.
Addresses #1:
This is an update of a simplified version of the TripGo API, where we've incorporated feedback from developers, added a clearer structure to the endpoints, aligned varies data models with those from schema.org and FIWARE, and moved to Open API 3.0 format (mostly so we can use
oneOf).Full set of changes is in the commit logs and our internal review comments can be found at https://github.com/skedgo/maas-apis/pull/1.
A few remarks:
/routing/grouped/endpoint could be considered out of scope for this API as it's not strictly speaking necessary, and more of a nice-to-have.