search

openmobilityfoundation / mobility-data-specification

A data standard to enable right-of-way regulation and two-way communication between mobility companies and local governments.
https://www.openmobilityfoundation.org/about-mds/
Other
676 stars 232 forks source link

Align with GBFS/TOMP geoJSON format #823

Open edwinvandenbelt opened 1 year ago

edwinvandenbelt commented 1 year ago

Is your feature request related to a problem? Please describe.

See https://github.com/TOMP-WG/TOMP-API/issues/485

It is not really a problem, but it's more about efficiency and ease of implementation. If the area endpoints in GBFS, MDS and TOMP could be alike (preferably geoJSON), the information could be published by the city, consumed by the TO (and shown in their app), published again by the TO (using GBFS/TOMP) and consumed directly by the MP (and again, shown in their app). The only thing that has to be taken into account, is that the rules that MDS (or maybe even CDS) use, are not all needed by the end users of the apps.

Describe the solution you'd like

the policy endpoint should produce geoJSON, that the Transport operators (TO) and the MaaS Service Providers can use in their apps (in a filtered way). In the current situation platforms that publish MDS (like Vianova) offer this service (transforming to geoJSON).

Is this a breaking change

Impacted Spec

Describe alternatives you've considered

Use the geography endpoint to produce a complete geoJSON and refer to rules in the policy endpoint.

schnuerle commented 1 month ago

The MDS Geography API has a GeoJSON formatted field in it when defining its geography.

https://github.com/openmobilityfoundation/mobility-data-specification/tree/main/geography#geography-fields

This can be grabbed and used as GeoJSON. I don't think we will get to a point where the whole endpoint will be GeoJSON as there are a lot of other fields and overhead needed for it to work in the greater MDS context.