Is your feature request related to a problem? Please describe.
Currently, neither gbfs/ endpoint (for GBFSv2) nor the manifest.json endpoint for GBFSv3 provide information, which systems are operated by which operator.
Goal / high level use-case
Mobility Apps usually group different systems by provider, e.g. to limit the number of options in preferences (see this discussion in the MobilityData GBFS slack).
Describe the solution you'd like
I suggest a new endpoint gbfs/operators.json which lists the operators (their id and name) and their published systems.
Describe alternatives you've considered
Alternatively,
manifest.json could be extended to provide operator(s) information.
the GraphQL API could be extended to provide links to the systems
Additional context
Example of a possible endpoint response:
Is your feature request related to a problem? Please describe. Currently, neither
gbfs/
endpoint (for GBFSv2) nor themanifest.json
endpoint for GBFSv3 provide information, which systems are operated by which operator.Goal / high level use-case Mobility Apps usually group different systems by provider, e.g. to limit the number of options in preferences (see this discussion in the MobilityData GBFS slack).
Describe the solution you'd like I suggest a new endpoint
gbfs/operators.json
which lists the operators (their id and name) and their published systems.Describe alternatives you've considered Alternatively,
manifest.json
could be extended to provide operator(s) information.Additional context Example of a possible endpoint response: