Free layers of USPS carrier route centroids for the United States are available for use with GIS mapping software, databases, and web applications.

The National Transit Map - Routes dataset was compiled on December 02, 2024 from the Bureau of Transportation Statistics (BTS) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The National Transit Map (NTM) is a nationwide catalog of fixed-guideway and fixed-route transit service in America. It is compiled using General Transit Feed Specification (GTFS) Schedule data. The NTM Routes dataset shows transit routes, which is a group of trips that are displayed to riders as a single service. To display the route alignment and trips for each route, this dataset combines the following GTFS files: routes.txt, trips.txt, and shapes.txt. The GTFS Schedule documentation is available at, https://gtfs.org/schedule/. To improve the spatial accuracy of the NTM Routes, the Bureau of Transportation Statistics (BTS) adjusts transit routes using context from the submitted GTFS source data and/or from other publicly available information about the transit service. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529048

The Amtrak Routes dataset is as of January 05, 2024 from the Federal Railroad Administration (FRA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). This dataset is a single line representation of unique routes that are generated from the North American Railroad Network (Amtrak). It contains information on ownership, trackage rights, type, passenger, STRACNET, and geographic reference of the Amtrak system at 1:24,000 or better and the dataset covers all 50 states and the District of Columbia.

This API provides information about the operators which are contracted to Transport for NSW. It provides the route and service by Operator. This data is also considered a master (reference) list of transport routes and lines. The data is based on the Transport for NSW Contract Management Route Services and includes route lookup, operator contact details, operator Twitter handles, colours and icons.

You can connect to the actual flight routes around the world with your API key at any time with very fast response times. It is possible to view all routes at the same time via a single API key. For your convenience, we have also developed many different filters so that you can pull the exact data you are looking for. This way, you may get data of the routes of a specific airline, routes from or to a specific airport (both IATA and ICAO codes work), or may get an individual flight based on its flight number.

A common use of the air routes API is to develop software in the aviation industry. While Aviation Edge’s focus is to collect and maintaining aviation data, you are free to develop countless applications, tools, and platforms by using our data.

The details included in the routes data are: Departure data: IATA code, ICAO code, terminal, and time. Arrival data: IATA code, ICAO code, terminal, and time. Airline: IATA code of airline. Flight: Flight number. Aircraft: Registration number of the aircraft.

Here's an example response from the API: [ { "departureIata": "OTP", "departureIcao": "LROP", "departureTerminal": 2, "departureTime": "09:15:00", "arrivalIata": "TRN", "arrivalIcao": "LIMF", "arrivalTerminal": 1, "arrivalTime": "10:45:00", "airlineIata": "0B", "airlineIcao": "BMS", "flightNumber": "101", "codeshares": null, "regNumber": "YR-BAP" } ]

Developer information: 1) Available Endpoints &departureIata= &departureIcao= &airlineIata= &airlineIcao= &flightNumber=

2) Output Airports, Airlines or Flights routes output: GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&departureIata=OTP GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&departureIcao=LROP GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&airlineIata=0B GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&airlineIcao=BMS GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&flightNumber=101 For information about a specific route (example). GET http://aviation-edge.com/v2/public/routes?key=[API_KEY]&departureIata=OTP&airlineIata=0B&flightNumber=101

This data set contains a digital representation of US route features for New Hampshire. For additional information, see the Metadata Lite record

This dataset is a list of MTA bus routes that intersect with the CBD, and how each route relates to the CBD (whether it crosses the CBD or is entirely in the CBD). It is meant to be a dimension table that can easily be used with other bus route-level datasets so that data users can easily distinguish between routes serving the CBD and routes that do not.

ROUTE 500® était la base de données routières décrivant 500 000 km de routes du réseau classé (autoroutes, nationales, départementales) et des éléments d'habillage à des échelles nationales et régionales. Depuis l’édition 2019, ROUTE 500® correspond au réseau routier de la BD CARTO®. ROUTE 500® permet de situer toute information thématique, d'analyser des données statistiques et de gérer des déplacements routiers.

A map showing the location of LADOT DASH and Commuter Express Routes and Stops.

The FDOT LRS Routes with Measures feature class is a weekly snapshot of the official FDOT LRS. It provides a spatial representation of roadways in RCI. In addition, the polyline-M geometry supports creation of numerous spatial datasets from FDOT data sources like RCI and TCI. It is updated through the LRS package process between the Districts and Central Office staff. It is maintained as a versioned feature class in the Transportation Data & Analytics (TDA)'s spatial database. Weekly snapshots are created every Saturday morning from the DEFAULT version and published for download by FDOT and TDA customers and partners. This dataset is maintained by the Transportation Data & Analytics office (TDA). The source spatial data for this hosted feature layer was created on: 02/22/2025.For more details please review the FDOT RCI Handbook Download Data: Enter Guest as Username to download the source shapefile from here: https://ftp.fdot.gov/file/d/FTP/FDOT/co/planning/transtat/gis/shapefiles/basemap_route_road.zip

New York City has over 1,000 miles of truck routes. These data sets contain the centerlines of through and local truck routes, and were created from LION, the City's base map of streets. Note: This is historical data, for the most up to date New York City Truck Routes data, please visit: https://data.cityofnewyork.us/Transportation/New-York-City-Truck-Routes/jjja-shxy

(Link to Metadata) Public-transportation route and stop layers derived from GTFS (General Transit Feed Specification) feeds. Includes data from multiple Vermont GTFS-feeds with the intention of providing statewide layers (covering the state where GTFS feeds are known and available). THIS DATASET IS A DERIVATIVE, NOT ORIGINAL/MASTER/OFFICIAL DATA. ITS ACCURACY ISN'T GUARANTEED. DISCREPANCIES CAN BE REPORTED TO CORRESPONDING TRANSIT AGENCIES. For more information on GTFS and GTFS feeds, GO TO https://vermont-gtfs.org/.

The original GTFS file can be downloaded at https://www.norta.com/RTA/media/GTFS/GTFS.zip.Shapefiles Included:Routes: Line geometry representing the transit routesStops: Point locations of transit stops, including attributesThe data provided is for informational purposes only and may be subject to change without notice. The New Orleans Regional Transit Authority (RTA) makes no guarantees, representations, or warranties regarding the accuracy, completeness, or currentness of the data. By accessing and using this data, the user acknowledges that the information is provided "as is" and agrees that RTA, its affiliates, employees, or agents shall not be held liable for any errors, omissions, or any actions taken based on the information provided.This dataset is not intended to be used as a legal document and should not be relied upon for critical decision-making processes without further verification. Any use of this data for commercial or non-commercial purposes is at the user’s risk, and users are responsible for compliance with any local, state, or federal regulations when using the data. By downloading or using this data, the user agrees to these terms.

The New York City Truck Route Network is a set of roads that commercial vehicles must use in New York City. NYC Truck Routes are also available in LION data. https://data.cityofnewyork.us/City-Government/LION/2v4z-66xt

Data has been obtained from the National Transportation Database and the National Transit Maphttps://geodata.bts.gov/datasets/80086198b67c456194b064ba21b82326_0/explore?location=38.641901%2C-121.401551%2C12.71https://www.transit.dot.gov/ntd/ntd-dataSACOG provides data as a public service. These data are provided "as-is." While every effort has been made to ensure the accuracy or correctness of these data, SACOG makes no warranty, expressed or implied, as to its accuracy or correctness and expressly disclaims liability for the accuracy thereof. In no event shall SACOG become liable to users of these data, or any other party, for any loss or damages, consequential or otherwise, including but not limited to time, money, or goodwill, arising from the use, operation or modification of the data. In using these data, users further agree to indemnify, defend, and hold harmless SACOG for any and all liability of any nature arising out of or resulting from the lack of accuracy or correctness of the data, or the use of the data. Users will not distribute these data to other potential users. Instead, they will refer those users to SACOG for an independent dataset and documentation. To assist SACOG in the maintenance of the data, users should provide SACOG's GIS staff information concerning errors or discrepancies found in using the data.

Displays the bicycle routes located in the Adelaide City Council area. Information provided includes the primary bicycle network, important secondary roads and secondary (alternate) routes. Co-ordinate System: Geographic Coordinate System: GCS_WGS_1984. Datum: D_WGS_1984. Prime Meridian: Greenwich. Angular Unit: Degree.

This dataset is GIS data representing waypoints and routes in the Mawson area, Antarctica. It includes routes in the Framnes Mountains and routes west and east of Mawson along the Mawson Coast. The waypoint and route data held by the Australian Antarctic Data Centre are routinely updated using feedback provided by the Australian Antarctic Division's Field Training Officers and Station Leaders with approval for changes given by the Australian Antarctic Division's Field Support Coordinator.

Update frequency: as needed

The Milwaukee Streetcar project’s 2.1 mile initial route (or hub) connects the Intermodal Station (AMTRAK and buses) and its 1.4 million annual users, the Third Ward (the fastest-growing neighborhood in Milwaukee), East Town (with the largest concentration of jobs in the state), and the lower east side (the highest-density residential neighborhood in Wisconsin).

Shapefile is projected in Wisconsin State Plane South NAD27 (WKID 32054)

Department of Conservation (DOC) - Recreation track lines (approx. centreline). Dataset shows tracks managed for walking and tramping. If you intend to walk a track, please confirm with your local office or the DOC website that the track isn't under a temporary or more permanent closure before embarking. Refreshed weekly and reflects the content on the website.*LICENCEThis work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.DISCLAIMER 1. DOC makes no express or implied warranties as to the accuracy or completeness of the data or information, nor its suitability for any purpose. Errors are inevitably part of any database, and can arise by a number of means, from errors during field data collection, to errors during data entry. 2. DOC makes no warranties or representations as to possible infringement upon copyrights or other intellectual property rights of others in the data or information. 3. DOC will not accept liability for any direct, indirect, special or consequential damages, losses or expenses howsoever arising and relating to use, or lack of use, of the data or information supplied.GUIDELINES FOR THE USE OF THE INFORMATION 4. Care should be taken in deriving conclusions from any data or information supplied. 5. Any use of the data or information supplied should state when the data or information was acquired and that it may now be out-of-date.COPYRIGHT OBLIGATIONS*** 6. All proprietary rights to the intellectual property in the data or information remain with the Crown as its sole property. 7. Modification of the data and information or the addition of the information does not confer copyright or any other form of property of the original material to a user. 8. All maps or reports that are derived from the data or information must acknowledge the Crown copyright, in the following way: Crown Copyright: Department of Conservation Te Papa Atawhai [year]. 9. This information resource may be passed onto another party, in either hard copy or electronic form. If a user does this, then it is recommended that they also supply this metadata record with the information resource.