Transportation · head-to-head
Transport for Denver, US vs Transport for Lisbon, Portugal
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.
EMEL (Lisbon's municipal mobility and parking operator) publishes its open data through the city's Lisboa Aberta CKAN portal rather than a dedicated live API — the old emel.city-platform.com/opendata/ address now 302-redirects to an unrelated EMEL page. Datasets cover on-street and off-street parking locations and occupancy, GIRA bike-share, regulated parking zones, road tunnels, and street furniture, served keyless as CSV, SHP, and JSON via CKAN's standard action API.
| Transport for Denver, US | Transport for Lisbon, Portugal | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | free |
| Formats | GTFS, GTFS-RT | JSON, CSV, SHP |
| CORS | no | no |
| HTTPS | Yes | Yes |
Transport for Lisbon, Portugal supports 3 response formats, while Transport for Denver, US offers fewer — pick Transport for Lisbon, Portugal for more integration flexibility.