GTFS Static schedule integration
Screen capture on an iPhone of Google Maps used for transit trip planning without realtime tracking (ie just based on the schedule). Orlando, Florida. LYNX and LYMMO bus routes.
GTFS Realtime integration with Live Trip Updates
Screen capture on an iPhone of Google Maps used for transit trip planning with real-time tracking. Tampa, Florida. HART bus routes.
Why Comprehensive Google Maps Integration Matters
- Potential riders don’t know your transit service exists. Without Google Maps integration, riders who use this trip planning tool don’t see your transit service as an option.
- Wait times for riders 50% longer without real-time info. Without Live Transit Updates for Google Maps, riders perceive their wait times to be 50% longer. Real-time info also reduces wait times for riders.
- 3rd most common internet activity is trip planning. Trip planning is the third most common internet activity for Americans behind only email and using search engines.
- 1 billion monthly active Google Maps users. Google Maps alone has 1 billion monthly active users around the world.
- Sharing transit data with software developers is an industry-wide standard. It has become standard practice for transit providers to integrate their static and real-time transit data onto Google Maps to ensure their services are accessible to Google Maps users.
- The GTFS data format enables Google Maps trip planning. Google Maps integration requires the General Transportation Feed Specification (GTFS) format – GTFS Static for schedule, route and fare information; and GTFS Realtime for real-time information.