NTAD North American Rail Network Lines
- Coverage
- All 50 US states plus District of Columbia
Industry hub · Rail transportation data provider
Datadory covers rail transportation data provider with 15 datasets spanning NTAD North American Rail Network Lines , Data.gov US Rail Catalog and Eurostat Railway Freight Transport Statistics . Delivered daily, weekly, or hourly — your call.
Every catch in this slice, ranked by our quality rubric — depth of documentation, freshness, breadth. Pick one, sample it, ship it.
Plus 2 more in this slice — each with its field dictionary and sample rows on its own page.
Where rail transportation data provider data actually comes from.
Three to start with. The rest of the board is above.
OBJECTID · FRAARCID · FRFRANODE …+23 more
title · description · publisher.name …+7 more
unit · tra_cov · nst07 …+6 more
Time period · <operator name> (million) · [p] provisional marker …+3 more
GTFS standard files · NeTEx XML · GTFS-RT Trip Updates …+3 more
feed code DARWIN · feed code DTD · feed code KB_API …+3 more
nom_gare · code_uic_complet · total_voyageurs_2024 …+5 more
Code · CSI · Year …+3 more
Start with the unit of record, because this shelf refuses to flatten to one grain.
Questions about infrastructure resolve to polylines - 302,771 of them in the American network, millions of mapped elements globally.
Questions about journeys resolve to scheduled stops and their realised counterparts, stop-level in the Swiss and French collections, per-train station calls in Britain.
Questions about volume resolve to statistic rows: country-year and country-quarter tonnage, or a single national total per year at the macro level.
And questions about material condition resolve to photographs, point clouds and text rows.
Then weigh geography honestly.
Only the geometry layer spans borders cleanly - United States, Canada and Mexico in one file - and only the metadata catalogue reaches every member state at once.
The national shelves go deeper inside their fences: Britain for performance and finance, France for ridership, Germany for facilities, Switzerland for timetable archaeology, Brussels for freight comparisons.
Finally, match the clock to the question.
Live movement data exists for Great Britain today and tomorrow; timetable horizons roll months ahead; freight statistics land quarterly; accident history compounds across five decades; and the training corpora are fixed snapshots that will not correct themselves.
Any catch on this board, sampled against your own question. API, files, or your warehouse. Daily, weekly, or hourly..
Nothing in the tray. Hit “Sample it” on anything in the catalog.
0 datasets, real rows from each. We reply from a person, not a pipeline.
API number · Surface coordinates · Drilling start (approx.) …+47 more
UniqueCarrier / AirlineID · OriginAirportID / DestAirportID · Month / Class …+36 more
Record_ID · Change_Type · Covered_Recipient_Type …+36 more
MatchedObjectId · PositionID · PositionTitle …+62 more
X_Minimum · X_Maximum · Y_Minimum …+31 more
departure_airport · departure_iata · departure_icao …+30 more
0 datasets
Not on the board yet? Tell us. We'll source it.
Request a datasetDelivery: API, files, or your warehouse. Daily, weekly, or hourly.