Pricing overview

Transport for Bordeaux, France, offers its public transportation data under an open data model, meaning all datasets are freely accessible and available to the public. There are no direct costs associated with accessing or utilizing the data provided by Transport for Bordeaux, France (TBM). This approach is consistent with open data initiatives aimed at fostering innovation and transparency by making public sector information available for reuse.

The primary data sources include static General Transit Feed Specification (GTFS) data, which describes transit schedules, routes, stops, and other geographic information, and real-time GTFS-RT data, offering live updates on vehicle positions, service alerts, and trip updates. Both formats are industry standards, facilitating integration into various applications and analyses.

Developers, researchers, and urban planners can access these datasets without registration or payment directly through the Bordeaux Métropole open data portal. The absence of a tiered pricing structure simplifies access and encourages broad adoption for projects ranging from personal applications to academic research and commercial ventures built upon public transit information.

Plans and tiers

Unlike many commercial API providers or data platforms that employ usage-based pricing, subscription models, or tiered access, Transport for Bordeaux, France (TBM) does not operate with distinct plans or pricing tiers. All data is made available equally to all users, regardless of their intended use case or data consumption volume.

This model eliminates the need for developers to monitor API call limits, worry about exceeding quotas, or manage monthly subscriptions. The focus is on providing unrestricted access to public transit information to support a wide array of applications without financial barriers. The data portal serves as the single point of access, where users can download datasets or subscribe to RSS feeds for updates to the data.

The open data policy aligns with initiatives to promote smart cities and enhance civic engagement by enabling the public and private sectors to build services that leverage publicly funded infrastructure and data. This transparent approach avoids complex licensing agreements, further streamlining the process for developers to integrate TBM data into their platforms.

Free tier and limits

Transport for Bordeaux, France operates entirely as a free tier because all its data is openly accessible without any charge. There is no separate paid tier or premium service for accessing TBM public transport data. This includes both the static GTFS files and the real-time GTFS-RT feeds.

While technically free, users should be aware of practical limits inherent to any data provision system:

  • Data freshness: Real-time data feeds refresh at intervals determined by the transit authority, typically every few seconds or minutes, as outlined in the GTFS Realtime specification. Your application's performance will depend on how frequently you poll the endpoints.
  • Request volume: Although there are no explicit API call limits enforced by TBM for GTFS-RT feed downloads, excessive or abusive request patterns could theoretically lead to temporary IP blocking to maintain service stability for all users. Developers are expected to implement reasonable polling intervals to avoid overloading the server.
  • Data volume: The size of the GTFS and GTFS-RT files can be substantial, especially for large metropolitan areas. Users should have adequate bandwidth and storage to download and process these datasets. Practical limits on data volume are typically defined by the capacity of the hosting server and the user's internet connection.
  • Service Level Agreements (SLAs): As an open data service provided free of charge, there are typically no formal SLAs guaranteeing uptime, response times, or data accuracy. Users integrate the data with the understanding that service availability may vary, although TBM aims for high reliability as part of its public service commitment.

The intent is to provide robust access, but developers should design their applications to be resilient to potential variations in data availability or refresh rates, as is common with open data sources.

Real-world cost examples

Given that Transport for Bordeaux, France's data is entirely free and openly accessible, real-world cost examples primarily reflect the developer's operational expenses rather than direct data acquisition fees. There are no direct API costs, subscription fees, or per-request charges from TBM.

Example 1: A personal mobile application for real-time bus tracking

  • Data acquisition costs: €0
  • Infrastructure costs: A developer creates a mobile app that fetches TBM's GTFS-RT feed every 30 seconds to display real-time bus locations. The primary costs would involve hosting for the application's backend (if any), cloud services for mobile app distribution, and potentially a mapping API (e.g., Google Maps Platform, which has its own pricing structure for usage above free tiers).
  • Development costs: Time spent coding the application logic, UI design, and testing.
  • Estimated direct TBM data cost: €0 per month.

Example 2: Urban planning analysis for public transport efficiency

  • Data acquisition costs: €0
  • Infrastructure costs: A researcher downloads several months of static GTFS data and historical GTFS-RT data (if available and archived by the user) to analyze public transport ridership patterns and identify areas for service improvement. This might involve significant local storage, powerful computing resources for data processing, and specialized GIS software (e.g., ArcGIS, which offers various developer pricing tiers for its APIs and tools).
  • Development/Analysis costs: Analyst's salary, software licenses, computational time.
  • Estimated direct TBM data cost: €0 per project.

Example 3: Commercial service integrating multiple transit providers

  • Data acquisition costs: €0 (for TBM data)
  • Infrastructure costs: A startup builds a journey planner service that integrates TBM data with data from other transit agencies (some of which might have commercial API fees) and third-party map providers. The service requires robust cloud infrastructure (e.g., AWS, GCP, Azure) to handle user requests, process real-time data from multiple sources, and store aggregated information. Costs here would be driven by compute instances, database services, and network egress.
  • Development costs: Team salaries for ongoing development, maintenance, and support.
  • Estimated direct TBM data cost: €0 per month, contributing to the overall value proposition of the commercial service.

In all these scenarios, the value derived from TBM's open data is significant, enabling a range of applications without adding direct data access costs to the project budget.

How the pricing compares

Transport for Bordeaux, France's pricing model, characterized by entirely free and open data access, stands in contrast to various alternative data sources and API providers. The comparison highlights TBM's commitment to open data principles.

Provider/Data Source Pricing Model Key Differentiator / Limits Best For
Transport for Bordeaux, France (TBM) Free, Open Data All static and real-time GTFS/GTFS-RT data available without cost. No API keys or usage limits (practical limits apply). Local Bordeaux transit applications, academic research focusing on Bordeaux, open-source projects.
SNCF Open Data Free, Open Data Provides national rail data (schedules, disruptions) for France, primarily focusing on SNCF services. Similar open data philosophy but different scope. National train journey planners, rail network analysis across France.
RATP Dev Open Data Free, Open Data (for Île-de-France) Offers public transport data for Paris and the Île-de-France region. Follows a similar open data model to TBM but is geographically specific to Paris. Parisian metro, bus, and tram applications, regional travel in Île-de-France.
Citymapper API Tiered (Free to Enterprise) Commercial API offering multimodal routing and real-time data aggregation across many global cities. Provides a robust, managed service with SLAs. Free tier has strict request limits; higher tiers are paid. Commercial journey planning apps, cross-city transit solutions, developers needing strong support and aggregated data.
Google Maps Platform (Transit Layer) Pay-as-you-go (usage-based) Offers comprehensive mapping services including a transit layer showing real-time public transport. Usage is priced per request for various APIs (e.g., Directions API, Maps SDK for Android/iOS). Free credits available for initial usage. Applications requiring integrated mapping and transit data, highly scalable global solutions.
Twilio (SMS/Voice for transit alerts) Pay-per-use (volume-based) While not a data provider, Twilio's APIs are often used alongside transit data for real-time alerts or customer service. Costs are per message or call, scaled by volume. Developing communication features for transit applications (e.g., SMS alerts for delays).
Stripe (for ticketing/payments) Transaction fees Payment gateway often integrated into transit apps for buying tickets. Charges a percentage + fixed fee per transaction. Not a data provider but a common companion service. Integrating payment functionality into transit applications.

TBM's zero-cost model for data access is highly advantageous for developers focusing specifically on the Bordeaux region or those with limited budgets. It reduces the barrier to entry significantly compared to commercial alternatives like Citymapper or Google Maps Platform, where API calls incur charges after a certain free usage threshold.

However, commercial alternatives often provide broader geographical coverage, enhanced features such as multimodal routing across different providers, dedicated support, and higher service level guarantees. For projects requiring data beyond Bordeaux or demanding enterprise-grade SLAs, integrating with paid services may be necessary. For purely Bordeaux-focused projects, TBM offers a compelling and fiscally efficient solution.