metropolitano - GTFS transit data for Chile

Active
Directorio-Transporte-Publico-Metropolitano Chile 4 de julio de 2026 — 31 de diciembre de 2026

About This Feed

metropolitano is the GTFS feed Directorio-Transporte-Publico-Metropolitano publishes for Chile: 427 routes, 12,306 stops, 4 transit agencies. BusMaps checks and corrects it every week and serves the result through the API and as GTFS files.

Valid from 4 de julio de 2026 to 31 de diciembre de 2026.

Checked and corrected automatically. How we do it →

One API for this feed

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

  • Stops within a radius of a coordinate.

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

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

    GET /v1/routes?origin=-33.4838,-70.6543&destination=-33.4366,-70.6115
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • GTFS files Free

    The corrected feed, the source feed, GeoJSON and the validation reports.

    GET /v1/getGtfsFeedsDownloads?feedName=metropolitano
  • 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.

Per-feed pages: 427 routes, 12,306 stops, 4 agencies

Public pages merge every feed. Sign in to browse this feed on its own, which helps when you integrate or debug it.

Entrar →

GTFS files of this feed

Two builds: the copy BusMaps corrected and validated, and the original from Directorio-Transporte-Publico-Metropolitano. The API returns either one for ?feedName=metropolitano. Documentation →

Enhanced & Validated Recommended

Updated 2026-08-21

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

ZIP GTFS Feed - Corrected & Enriched
11.84 MB
Available through API only The license for this work is not specified Content Hash: e28daafddac1abcb
ZIP Validation Report
0.01 MB
Available through API only
0Errors
24Warnings
0Info
Top Issues
stop too far from shape20
stops match shape out of order4
GeoJSON GeoJSON Data
0.35 MB
Available through API only

Original Source

Obtained 2026-07-02

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

ZIP GTFS Source Data
10.25 MB
Available through API only The license for this work is not specified Content Hash: 1d7aa130c0e1cd0a
ZIP Validation Report
0.03 MB
Available through API only
0Errors
851,176Warnings
5Info
Top Issues
missing timepoint value851,022
unused shape122
stop too far from shape25

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?

The source feed is what the agency published. The enhanced feed is the same data after BusMaps fixed the errors and inconsistencies and checked it against the GTFS specification. Use the enhanced feed in production.

Can I use this data in my application?

That depends on the licence the publisher set; you find it next to the files above. Most GTFS feeds allow free use with attribution. Check the licence before you integrate.

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, contact us and we will fix it.