Suggestion to split otpGraphQl into two types

[GerdC]

History
at the beginning of 2024, EnTur's OTP GraphQL implementation was merged into the OTP main stream.

With that, the two incompatible GraphQL APIs got different official names:

• GTFS GraphQL API: https://docs.opentripplanner.org/en/latest/apis/GTFS-GraphQL-API/
• Transmodel GraphQL API: https://docs.opentripplanner.org/en/latest/apis/TransmodelApi/

Suggestion
As both OTP GraphQL APIs are incompatible and have official distinct names
I'd suggest to split

type value otpGraphQl

into maybe

otpGTFSGraphQl
otpTransmodelGraphQl

or whatever you like more.

[derhuerst]

Right now, do all OTP instances expose both GraphQL APIs, i.e. does every endpoint expose both "sub-endpoints"?

[GerdC]

My experiments as a consumer appear to suggest that each instance is configured to exposes exactly one of both.

Entur gets its data in NeTEx format and exposes routing as Transmodel.

Most others get their data as GTFS and expose routing with GTFS vocabulary (example: Digitransit instances).

Makes sense to me not to have to map the vocabulary and semantic between Transmodel and GTFS, but I'm not a routing server guy.

[GerdC]

both can be enabled and are enabled by default: https://developer.entur.org/pages-journeyplanner-journeyplanner

Entur exposes only one (Transmodel):
"Entur Journey Planner v3: „All data is presented as a Transmodel-based GraphQL-API“ and „There is only one endpoint“ documented here https://developer.entur.org/pages-journeyplanner-journeyplanner

Helsinki: "OpenTripPlanner has multiple APIs but currently we only expose the GTFS GraphQL API version 1. Even though the version is called 1, it's a newer version of the GraphQL API we had available in our /routing/v1 API." se https://digitransit.fi/en/developers/architecture/x-apis/1-routing-api/