toscana-regionale - GTFS transit data for Italy

Active
Open-Data-Regione-Toscana Italy September 11, 2026 — October 1, 2026

About This Feed

toscana-regionale is the GTFS feed Open-Data-Regione-Toscana publishes for Italy: 955 routes, 31,888 stops, 43 transit agencies. BusMaps provides the original source through the API. Corrected and validated builds are not available in the API and require the data request form.

Valid from September 11, 2026 to October 1, 2026.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 955 routes and 31,888 stops: stops near a point, departures, trips, timetables and source GTFS files. The requests below use the coordinates of this feed.

  • Stops within a radius of a coordinate.

    GET /v1/stopsInRadius?location=43.6054,10.9873&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

    GET /v1/nextDepartures?location=43.6054,10.9873&radius=500&results=30
  • Itineraries between two points on this network.

    GET /v1/routes?origin=43.6054,10.9873&destination=43.8241,11.3373
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • The original source feed, source validation report, and provider links. Processed data is not returned.

    GET /v1/getGtfsFeedsDownloads?feedName=toscana-regionale
  • Claude, ChatGPT or any MCP client asks this network questions in plain language.

    https://mcp.busmaps.com/mcp

Base URL https://capi.busmaps.com:8443. Send the key in the capi-key header. Route ids come from the responses above.

955
Routes
31,888
Stops
43
Agencies

GTFS Data Products

Request enhanced data access

The API provides source files only. Submit the data request form to discuss enhanced or custom data, coverage, and delivery terms.

Open the data request form →

Enhanced & Validated Recommended

Updated 2026-09-11

Cleaned, corrected, and validated against GTFS specifications. View corrections.

ZIP GTFS Feed - Corrected & Enriched
64.66 MB
Access: Submit the data request form The license for this work is not specified Content Hash: 6b70d62676215dfa
ZIP Validation Report
0.02 MB
0 Errors
76 Warnings
668 Info
Top Issues
mixed case recommended field 70
stop has too many matches for shape 5
feed expiration date30 days 1
GeoJSON GeoJSON Data
1.08 MB

Original Source

Obtained 2026-09-11

Unmodified GTFS data from official sources. May contain errors or inconsistencies.

ZIP GTFS Source Data
204.38 MB
Available through API The license for this work is not specified Content Hash: 135388790033f901
ZIP Validation Report
0.14 MB
Available through API
18 Errors
917,767 Warnings
6,266 Info
Top Issues
decreasing or equal stop time distance 14
equal shape distance diff coordinates 4
equal shape distance same coordinates 717,323

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
extraurbanogrosseto 61 (6.39%)
extraurbanofirenze 54 (5.65%)
extraurbanopisa 37 (3.87%)
extraurbanolivorno 30 (3.14%)
extraurbanolucca 29 (3.04%)
extraurbanoarezzo 27 (2.83%)
emg-extraurbano-massa-carrara 20 (2.09%)
emg-extraurbano-pisa 20 (2.09%)
servizi-area-poggibonsi 15 (1.57%)
urbanolucca 14 (1.47%)
autolinee-mugello-valdisieve 13 (1.36%)
urbanorosignanomari 12 (1.26%)
urbanocarrara 11 (1.15%)
emg-extraurbano-lucca 10 (1.05%)
urbanomassa 10 (1.05%)
urbanopiombino 10 (1.05%)
urbanoprato 10 (1.05%)
lineeregionali 9 (0.94%)
urbanocollevaldelsa 9 (0.94%)
urbanoportoferraio 9 (0.94%)
extraurbanoprato 7 (0.73%)
trenitalia-italy 7 (0.73%)
debole-extraurbano-livorno 6 (0.63%)
urbanocecina 6 (0.63%)
urbanomassaecarrara 5 (0.52%)
urbanoviareggio 5 (0.52%)
atc-la-spezia 1 (0.1%)
colbusnonscolastico 1 (0.1%)
debole-extraurbano-prato 1 (0.1%)
emg-extraurbano-monte-sansavino 1 (0.1%)
s-atscolastico 1 (0.1%)
servizi-sostitutivi-ferro 1 (0.1%)
gommagtfsbo 17 (0.05%)

Frequently Asked Questions

What is GTFS data?

GTFS, the General Transit Feed Specification, is the open format transit agencies use to publish schedules, stops and route shapes. Trip planners, routing engines and analytics tools read it directly.

What is the difference between enhanced and source data?

Source data is the original GTFS feed obtained from the transit agency or official provider. The enhanced version has been processed to fix errors, remove inconsistencies, and ensure compliance with GTFS specifications. API plans include source data only. Enhanced data requires a separate request through the data request form. Request access through the form →

Can I use this data in my application?

Source-data use depends on the licence set by the publisher; check it before integration. Enhanced and custom data is supplied under terms agreed for your coverage, delivery, and intended use.

How do I validate a GTFS feed?

Every feed here ships with a validation report of errors and warnings. For an independent check, run the MobilityData GTFS Validator. The enhanced feed has the critical issues resolved.

All data comes from public sources. If a file was posted in error, carries a wrong licence or lacks attribution, we will fix it.

Contact us →