Back to the website
Reviewed · 16 July 2026

Data and sources

Where every emap data point comes from, the licence under which it is used and how often it is updated.

Public transport: lines, stops and timetables

SourceWhat it providesLicenceUpdates
Metro BilbaoLines, 42 stations and timetablesNAP · MITRAMS (RISP)Several times a year
EuskotrenLines, 73 stations and timetablesOpen Data Euskadi · MITRAMSSeveral times a year
Renfe Cercanías67 stations and timetablesNAP · MITRAMS (RISP)Several times a year
Bilbobus · City of Bilbao537 stops and linesCC BY 3.0 ESSeveral times a year
Bizkaibus2,270 stops and linesNAP · MITRAMS (RISP)Several times a year
dbus · TUVISA · Lurraldebus · Álava BusLines in Gipuzkoa and Álava; more than 3,400 stopsOpen Data Euskadi · CC BY 4.0Several times a year

Live: waiting times and signals

SourceWhat it providesLicenceUpdates
Bizkaia Transport Consortium (CTB)Metro and Bizkaibus waits, alerts and car park occupancyCTB open data · NAP15–90 s
Moveuskadi · Open Data EuskadiEuskotren, dbus and TUVISA waits; alertsCC BY 4.030 s
Basque GovernmentTraffic incidents and cameras; air qualityCC BY 4.05–15 min
Provincial Council of BizkaiaBeach status and facilitiesDFB open data10 min
BilboMad · PBSCPublic bikes and available docksProvider terms60 s

Prices and services

SourceWhat it providesLicenceUpdates
MITECOFuel prices at service stationsRISP · Law 37/2007~30 min
Open Charge Map · REVE networkElectric vehicle charging pointsCC BY 4.0Daily and on demand
Open-MeteoWeather forecasts and terrain elevationCC BY 4.0On demand

Base map, search and routing

SourceWhat it providesLicenceUpdates
OpenStreetMapStreets, cycle lanes and places such as fountains, toilets, car parks or peaksODbLWeekly refresh
OpenFreeMap · CARTOLight and dark base map renderingCC BY · ODbL dataContinuous
Photon · NominatimAddress and place searchODbLOn demand
OSRM · OpenTripPlannerCar, bike, walking and public transport routesOpen source · ODbL dataContinuous
DGTBilbao Low Emission ZoneCC BY 4.0Manual

How data is transformed

Sources are downloaded, normalised and packaged by an automated process. Every package is registered with a date and checksum. If a source fails, emap shows the last valid value with its date or says no data is available: it never invents it.