EFA (Elektronische Fahrplan-Auskunft) API endpoints not rendered correctly as they are XML data and part of a propriatory API rather then a dataset.

[lukmay]

Currently we promote the EFA (Elektronische Fahrplan-Auskunft) API endpoint proxies as six distinguished datasets on the data browser.
We decided to hide these datasets for now and start a discussion on how to better present these endpoints and provide all necessary information to potential data consumers.

To begin this process, we will document the datasets here as they currently are so we do not lose this information.

Datasets before hiding

The data browser shows nothing because it cannot render this type of data:

These are all the datasets and their descriptions:
All datasets have the source "STA" and the License "CC0"

• Public Transportation Route Planner
  • The main call allows you to perform a route calculation search from point A to point B.
  • API URL: https://mobility.api.opendatahub.com/v2/XML_TRIP_REQUEST2
• Real Time Public Transportation Timetable
  • "DEPARTURE MONITOR" returns the "Departure Monitor," which is the departure/arrival board for a specific stop.
  • API URL: https://mobility.api.opendatahub.com/v2/XML_DM_REQUEST
• Static Public Transportation Timetable
  • It's like a "Departure monitor," but it returns only the scheduled data, the information displayed at the stops.
  • API URL: https://mobility.api.opendatahub.com/v2/XML_STT_REQUEST
• Public Transportation Info
  • It returns the list of ongoing disruptions.
  • API URL: https://mobility.api.opendatahub.com/v2/XML_ADDINFO_REQUEST
• Public Transportation Stop Finder
  • "STOPFINDER REQUEST" call to resolve any text input by the user into a list of stops that contain that text.
  • API URL: https://mobility.api.opendatahub.com/v2/XML_STOPFINDER_REQUEST
• Public Transportation Stop Coordinates
  • It allows you to obtain the coordinates of a specific stop.
  • API URL: https://mobility.api.opendatahub.com/v2/XML_COORD_REQUEST