This feature class consists of approximately 195,000 features representing over 70,000 miles of Interstate, Primary, Secondary and Urban roads throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Source System of Record for road inventory, Roadway Inventory Management System (RIMS). Geometry and Attribution: The Linear Referencing System (LRS) data contained within this feature class provides dissolved route segmentation (i.e. routes are not segmented when they intersect other routes), thus rendering one table record per route. Multi-part geometry is created where routes are noncontiguous (e.g. a valid physical gap exists because another route is the master). The feature class only depicts master routes, those are routes built in the prime direction and on divided roadways where the non-prime direction is the master. Each road centerline record has a master route record assigned. Measures: The linear reference is based on Official State Mileage (OSM) as derived from reference points at Roadway Inventory Management System (RIMS) roadway intersections (i.e. nodes/junctions). Purpose: This linear referenced data layer represents roadways that are maintained by the Virginia Department of Transportation and provides the underlying spatially enabled geometric network to which all "events" (e.g. potholes, pavement type, vehicle accidents, traffic counts, culverts, etc...) can be located. Note: The overlap and non-prime measures are for reference only and have not been fully validated for accuracy or completeness.

This layer visualizes over 60,000 commercial flight paths. The data was obtained from openflights.org, and was last updated in June 2014. The site states, "The third-party that OpenFlights uses for route data ceased providing updates in June 2014. The current data is of historical value only. As of June 2014, the OpenFlights/Airline Route Mapper Route Database contains 67,663 routes between 3,321 airports on 548 airlines spanning the globe. Creating and maintaining this database has required and continues to require an immense amount of work. We need your support to keep this database up-to-date."To donate, visit the site and click the PayPal link.Routes were created using the XY-to-line tool in ArcGIS Pro, inspired by Kenneth Field's work, and following a modified methodology from Michael Markieta (www.spatialanalysis.ca/2011/global-connectivity-mapping-out-flight-routes).Some cleanup was required in the original data, including adding missing location data for several airports and some missing IATA codes. Before performing the point to line conversion, the key to preserving attributes in the original data is a combination of the INDEX and MATCH functions in Microsoft Excel. Example function: =INDEX(Airlines!$B$2:$B$6200,MATCH(Routes!$A2,Airlines!$D$2:Airlines!$D$6200,0))                                                

This feature class contains locations and attributes of all DC Snow Routes for snow removal crew. This specific data set was created to increase routing efficiency and improve operational planning and execution. This data set was also created for the specific purpose of printing maps of each of the 69 snow routes on a letter-sized sheet of paper for use by the snow removal crew assigned to individual routes.

This line layer was created from the GTFS data feeds from the Washington D.C. Metropolitan Area Transportation Authority (WMATA) to represent the new WMATA bus transit routes for the Better Bus Network Redesign(BBNR). Lines in this layer represent individual bus routes; they were generalized from the GTFS format where lines depicted individual services. On June 29, 2025, WMATA implemented a brand new Metrobus Network – known as Better Bus. Read more about this update from BBNR info page. Each line represents the route that a specific bus follows during its daily service. The unique field, shape_id, is derived from the GTFS to identify the route, while route_id (route_shortname), direction, and variation fields use familiar letter or number designations for buses, with distinct IDs for each route. This layer was developed as part of the WMATA Better Bus Network Redesign and will be updated as necessary to reflect changes in the transit system. Learn more about GTFS feeds at wmata.com/about/developers.The District Department of Transportation (DDOT) has added DC attribution for Roadway Blocks and Roadway Subblocks to the Metro Bus Stop dataset. Use BLOCKKEY, SUBBLOCKKEY, and ROUTEID to relate back to DC government data. Learn more about DDOT's roadway centerline data at opendata.dc.gov/pages/roadway-centerlines.

This dataset provides information on fixed-route transit route lines for the State of Washington as of 8/14/23. Stop data was extracted from General Transit Feed Specification (GTFS) data. Because GTFS data is typically created and managed by each individual transit agency, WSDOT cannot guarantee the accuracy of these data.Most data points are provided direct from GTFS feeds according to the specification at https://gtfs.org/. The route_id field has been prepended with a code for each agency to ensure every route has a distinct route_id.Please send comments and questions to gtfs@wsdot.wa.gov

Transit Routes are line features which represent current Durham Region Transit (DRT) routes. This dataset is created based on Region of Durham Road Network data and follows roads centrelines.

Pierce Transit bus route polylines throughout the Public Transportation Benefit Area (PTBA) and surrounding area. Created from GTFS route digitization, minor location modification to align with street network, and addition of appropriate website hyperlink. Any data download constitutes acceptance of the Terms of Use.

This dataset can be used to assess the approximate location of "Fiber-To-The-Home" (FTTH) internet service along Vermont roadways.

The data set was built using the VT Data - E911 Road Centerlines and service availability information voluntarily shared by fiber providers in Vermont. Routes represented here are a subset of the total E911 Roadway Centerline line segments. Here is the REST endpoint.

Data is collected and collated from Vermont's fiber providers by PSD-Telecom. Each year, PSD-T requests data from internet service providers regarding the service routes for that organization. The State of Vermont cannot make any claims as to the accuracy or completeness of the data provided to the state by providers. The data is combination of provider-shared route maps and address-level service data. In each case, E911 road centerline data near those lines or points are selected to create this dataset.

Data from these sources was accessed and collected in the summer of 2024. Projects of new construction begun at or around that time may not be available on this map.

Please note, in some cases there may be discontinuous line segments in the dataset. Due to the process by which this dataset is made and the information from providers, there may be some stand-alone roadway sections. This route data does not indicate service availability.

The FDOT U.S. Highways feature class provides spatial information on Florida U.S. Highways. The interstate and US route numbers are assigned by the Federal American Association of State Highway and Transportation Officials (AASHTO) usually following recommendations by the each state department. Both interstate and US routes are coded under the USROUTE characteristic. This information is required for roadways functionally classified as principal, minor arterials that have US route designations, and all Active Exclusive roads that are associated with Interstate and the US route. This dataset is maintained by the Transportation Data & Analytics office (TDA). The source spatial data for this hosted feature layer was created on: 10/25/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/us_roads.zip

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: 11/01/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

Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the transitland feed registry (formerly from GTFS Data Exchange). Routes are developed from the GTFS data available through the transitland feed registry (https://transit.land/feed-registry/) or transitfeed (http://transitfeeds.com) depending on which is most current (formerly from the GTFS Data Exchange). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.

A line feature class of Miami-Dade County Bus Routes.Updated: Weekly-Thu The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

Created at request of City of Columbia Utilities for the public to look up the days their recycling will be picked up.City of Columbia Utilities, Public Information Specialist, M. Nestor is the point of contact and creates the calendar images bi monthly to be manually added to this application.Notes: Currently the application requires manually updating the calendar image used in the popups for the application. Images are created and provided by Matt Nestor bi-monthly. Images are uploaded to ArcGIS Online as a hosted item. Please review Recycling Route App Notes for documentation on this work flow. Web Map URL:https://gocolumbiamo.maps.arcgis.com/apps/mapviewer/index.html?webmap=0f1d3817cd4345f88b6cc06a8f53776b Hosted Feature Layer:https://gocolumbiamo.maps.arcgis.com/home/item.html?id=a78718144c2444599daea94dde555cdd Image URLhttps://gocolumbiamo.maps.arcgis.com/home/item.html?id=60472f47114343d48306d88b5bbe2087

Votran Bus Routes downloaded 02/2023 and created using ESRI Streets and the GTFS tool in ArcGIS Prohttps://www.transit.land/feeds/f-djn-votran/

Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the transitland feed registry (formerly from GTFS Data Exchange). Routes are developed from the GTFS data available through the transitland feed registry (https://transit.land/feed-registry/), formerly from the GTFS Data Exchange. GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.Please note that this data was reprojected for use in the San Diego Ocean Planning Partnership, a collaborative pilot project between the California State Lands Commission and the Port of San Diego. For more information about the Partnership, please visit: https://www.sdoceanplanning.org/

It is derived from the Connecticut Route Segments layer, which is based on spatial information from the U.S. Bureau of Census that was published for Connecticut by the University of Connecticut, Center for Geographic Information and Analysis. The spatial information (line feature geometry) from the U.S. Bueau of Census was compiled for the year 2000 and used to create a continuous line feature for each interstate highway and route shown on the State Tourism Map 2002-2003 published by the Connecticut Department of Transportation. The Connecticut Routes layer does not include local roads, highway entrance and exit ramps, highway rest areas, exit numbers, house address, traffic direction, or traffic volume information. Features are linear and represent divided and undivided route centerlines mapped at 1:100,000 scale (1 inch = 1.578 mile).

This feature class consists of approximately 505,000 features representing over 70,000 miles of Interstate, Primary, Secondary and Urban roads throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Source System of Record for road inventory, Roadway Inventory Management System (RIMS).Geometry and Attribution: The Linear Referencing System (LRS) data contained within this feature class provides dissolved route segmentation (i.e. routes are not segmented when they intersect other routes), thus rendering one table record per route. In cases where routes are noncontiguous (e.g. a valid physical gap exists), multi-part geometry is created. The feature class also depicts overlapping routes (e.g. Interstate 64 and Interstate 95) as two separate collinear features, one on top of the other. Routes built in the prime and non-prime directions are included. Each road centerline record has a master route record assigned. This feature class is best suited for labeling roadways when overlap reference is needed.Measures: The linear reference is based on Official State Mileage (OSM) as derived from reference points at Roadway Inventory Management System (RIMS) roadway intersections (i.e. nodes/junctions). Purpose: This linear referenced data layer represents roadways that are maintained by the Virginia Department of Transportation and provides the underlying spatially enabled geometric network to which all "events" (e.g. potholes, pavement type, vehicle accidents, traffic counts, culverts, etc...) can be located.

This data contains Montgomery County Department of Transportation (MCDOT) Ride-On bus routes created from the system's GTFS file. Ride-On's GTFS file was downloaded on 12/02/2020 from https://www.montgomerycountymd.gov/DOT-Transit/GTFS/GTFSfiles.html. For more information, contact: GIS Manager Information Technology & Innovation (ITI) Montgomery County Planning Department, MNCPPC T: 301-650-5620

The polyline dataset currently represents 241 climbing routes at Devils Tower National Monument. It was created in ArcGIS Pro Scene 3.1, using an integrated approach combining literature review and collaboration with technical climbing staff. Routes were heads-up digitized over a 3D model of Devils Tower with derived triangulated irregular network (TIN) surfaces created from the DETO Unmanned Aircraft Systems (UAV) Digital Elevation Model (DEM). This dataset utilizes the updated NPS Core Spatial Data Standard Implementation Plan Template dated August 31, 2016. Description last updated January 2020. IRMA Reference

This layer, created from MBTA GTFS GTFS data, displays the routes and stops for MBTA GTFS. The colors of the routes are determined by the HEX values specified in the GTFS files. The popups indicate the name of the transit stop and route. There are numerous analysis options for you to run on this feature service. For example, you can use Data Enrichment to determine the number of households below poverty or the number of businesses within a certain walk or drive time to each stop.