Overview
If you are not the provider of the GTFS feeds for Google Maps, your integration is Stop-only. For this integration we need to understand how you identify the different train or bus stops.
General feed specifications
When starting the integration, we create a unique identifier for each
integration, for example: ch_google_test (country code, partner name,
integration) or eu_google (region code, partner name).
Partners can provide a zip file containing text files in CSV format that are applied globally or per integration:
Example 1:
- ch_google_test_stops.txt
- ch_google_test_markets.txt
Example 2:
- stops.txt (applied to all integrations)
- eu_google_integration1_markets.txt
- eu_google_integration2_markets.txt
Stop feed specification (required)
The stop file should contain the following columns:
| Field Name | Type (see GTFS) | Description |
|---|---|---|
stop_id |
ID (required) | The unique identifier that identifies a stop or station. Larger stations should only contain a single entry. This is used when making calls to your Partner Server API and in the ticketing deep links. |
stop_name |
Text (required) | A human readable name for debugging stop mapping, cache filling & price accuracy data. |
stop_lat |
Latitude (required) | Latitude of the stop. |
stop_lon |
Longitude (required) | Longitude of the stop. |
We will use an automated ingestion process where partners can continuously provide updated zip files when information contained therein changes. For example, a partner may expand the inventory provided by extending the list of stops. However, similar to GTFS, stop_ids should be stable.
Market set feed specification (optional)
With the mapped stops, we generate the market set for this integration (a list containing popular origin / destination pairs). From there, you have the option to reduce this set of markets by proving a market set feed.
The market set acts as an allowlist: If no market set is provided, all markets are enabled in the integration. If a market set is provided, any market that is not in the list is disabled.
The market set file should contain the following columns:
| Field Name | Type (see GTFS) | Description |
|---|---|---|
origin_stop_id |
ID (required) | The origin stop_id of the market. |
destination_stop_id |
ID (required) | The destination stop_id of the market. |
Partner Configuration
When using the stop-only integration, we require extra information for the static partner configuration as outlined in the Partner Configuration section.
Ticketing Deep Links
The format and parameters of a deep link are defined in Ticketing Links
Partner API parameters
The SegmentKeys parameters for the Partner API
(GetBulkTripOptionsRequest)
are based on the deep link specification. We use
SegmentKeys
including only from_ticketing_stop_time_id, to_ticketing_stop_time_id,
service_date, boarding_time and arrival_time, leaving ticketing_trip_id
empty. We will fully specify the route including all transfers by specifying
multiple SegmentKeys, one per segment.