-
Transport
This dataset provides General Transit Feed Specification (GTFS) data for all the routes and route variants in the Dublin LUAS network. The dataset contains a zip file as per the GTFS specification. The data is valid for January 2013.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
-
These public transport operators' GTFS files are updated every time a service timetable is changed. If there was a previous version it will be over written. The validity period for each operator's Schedule is declared in the appropriate manner within in the individual GTFS files.
Contact Information
Open Data UnitDepartment of Public Expenditure Infrastructure Public Service Reform and Digitalisation,
St. Stephen’s Green House,
Earlsfort Terrace, D02 PH42 Dublin 2 Ireland.
Give us feedback
The Open Data Unit values your feedback, questions or comments. We are always delighted to hear from you.
Derilinx