1. Know what you own
List the data you hold: stops and stations, lines and timetables, fares, real-time information, shared vehicle availability or road data. Decide which datasets are in scope for your National Access Point. See static and dynamic data.
2. Choose the format
- Public transport timetables: NeTEx, or GTFS if your NAP accepts it.
- Real-time public transport: SIRI or GTFS Realtime.
- Shared mobility: GBFS.
- Road traffic: DATEX II.
Check which profile and version your NAP expects. See data formats.
3. Produce and validate
Most planning and operations systems can export timetable data. Validate the files before publishing: XML data against the schemas of the standard, and GTFS with a validator such as the one maintained by MobilityData. Fix errors at the source so the next export is correct too.
4. Describe it with metadata
Add title, description, owner, contact, area and modes covered, format and version, update frequency and licence. See metadata and licences.
5. Publish and announce
Publish the data, or a link or API endpoint, through the National Access Point. Make sure it can be reached without manual steps for the user, as far as your NAP rules allow.
6. Keep it up to date
- Update timetable data whenever the plan changes, and before it takes effect.
- Keep real-time feeds running and monitored.
- Keep identifiers stable so consumers can link datasets over time.
- Respond to questions and error reports from data users.
Common problems
- Wrong coordinates or missing accessibility information at stops.
- Calendar and time zone errors.
- Stop or trip identifiers that change on every export.
- Missing or unclear licence information.
Frequently asked questions
Where do I publish my data?
Through the National Access Point of your country. Check its own guidance for accounts, formats and metadata.
Do I have to give the data away for free?
Access conditions and licences are described in the metadata. Rules differ between datasets and countries, so check national requirements.