Transportation · head-to-head
Transport for Denver, US vs Transport for Grenoble, France
RTD Denver's original gtfs-developer-guide.shtml page is gone after a full site rebuild (now 404s); the transit agency's open-data offering now lives under open-records/open-spatial-information, split into static GTFS zip downloads (bus, light rail, commuter rail, plus the regional Bustang service) and three GTFS-Realtime protocol-buffer feeds (vehicle positions, trip updates, alerts). No API key is required, only acceptance of a redistribution license agreement.
Open-data API behind Grenoble metro area's "M" mobility site (SMMAG), covering the transit network's stops, lines, real-time schedules (via an embedded OpenTripPlanner instance), and shared-mobility points like Métrovélo bike lockers and Citélib car-share stations. Every endpoint is keyless and returns JSON by default, with CSV/XLS exports offered for point-type datasets.
| Transport for Denver, US | Transport for Grenoble, France | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | free |
| Formats | GTFS, GTFS-RT | JSON, GeoJSON, CSV, XLS |
| CORS | no | yes |
| HTTPS | Yes | Yes |
Transport for Grenoble, France supports CORS, while Transport for Denver, US doesn't — pick Transport for Grenoble, France for direct browser calls.