The National Highway System consists of a network of roads important to the economy, defense and mobility. On October 1, 2012 the existing National Highway System (NHS) was expanded to include all existing Principal Arterials (i.e. Functional Classifications 1, 2 and 3) to the new Enhanced NHS. Under MAP-21, the Enhanced NHS is composed of rural and urban roads nationwide serving major population centers, international border crossings, intermodal transportation facilities, and major travel destinations.The NHS includes:The Interstate System. Other Principal arterials and border crossings on those routes (including other urban and rural principal arterial routes, and border crossings on those routes, that were not included on the NHS before the date of enactment of the MAP-21).Intermodal connectors -- highways that provide motor vehicle access between the NHS and major intermodal transportation facilities. STRAHNET -- the network of highways important to U.S. strategic defense. STRAHNET connectors to major military installations.

Vector polygon map data of mile markers from the state of California containing 157892 features.

Mile marker GIS data consists of points along a linear feature, such as roads or railways. They serve as reference points to measure distances along these features. Mile markers are often labeled with numbers indicating their distance from a starting point, such as a highway's origin or a railway station.

These markers are invaluable for navigation, route planning, emergency response, and data collection. For example, they help drivers and emergency services identify their location precisely on a road. In transportation planning, mile markers aid in analyzing traffic patterns, determining optimal routes, and estimating travel times. Additionally, they facilitate maintenance activities by providing clear reference points for inspecting and repairing infrastructure.

This data is available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

Under the Moving Ahead for Progress in the 21st Century Act (MAP-21), the Enhanced National Highway System (NHS) encompasses a comprehensive network of rural and urban roads across the United States. This network is pivotal in connecting major population centers, international border crossings, intermodal transportation facilities, and key travel destinations. The NHS comprises several critical components:

1. The Interstate System: This forms the backbone of the NHS, facilitating long-distance travel and commerce.
2. Principal Arterials and Border Crossings: In addition to the Interstate System, the NHS includes other principal arterial routes—both urban and rural. This category has been expanded under MAP-21 to include additional principal arterials and border crossings not previously part of the NHS.
3. Intermodal Connectors: These are crucial highways that provide direct motor vehicle access from the NHS to major intermodal transportation facilities, ensuring seamless transition between different modes of transportation.
4. STRAHNET (Strategic Highway Network): A network of highways that are vital for U.S. strategic defense purposes.
5. STRAHNET Connectors: These are specific routes providing access to major military installations, further emphasizing the strategic importance of the NHS. Overall, MAP-21's enhancement of the NHS reflects a comprehensive approach to national transportation planning, integrating various elements crucial for efficient and strategic movement within the United States.

This dataset only includes the California National Highway System along with its geographical features.

StateHighways are state highways based upon the Caltrans Linear Referencing System. Each record in this layer represents a highway segment where the county, route, postmile prefix, and postmile suffix are the same. Each segment has a begin and end postmile. This geometry is based upon the extraction from TSN on 8 June 2025. Route geometry updates based upon this extraction include routes 3, 36, 38, 49, 89, 139, 174, and 221. All updates received an update date of 6/8/2025 except for route 221 which received a date of 7/1/2025.

Context

Used for a uni project.

Content

A road network of California. Intersections and endpoints are represented by nodes and the roads connecting these intersections or road endpoints are represented by undirected edges.

Acknowledgements

retrieved from: https://snap.stanford.edu/data/roadNet-CA.html J. Leskovec, K. Lang, A. Dasgupta, M. Mahoney. Community Structure in Large Networks: Natural Cluster Sizes and the Absence of Large Well-Defined Clusters. Internet Mathematics 6(1) 29--123, 2009.

The USGS, in cooperation with the U.S. Bureau of Land Management (BLM), created a series of geospatial products of the Scotts Creek Watershed in Lake County, California, using National Agriculture Imagery Program (NAIP) imagery from 2022 and Open Street Map (OSM) from 2019. The imagery was downloaded from United States Department of Agriculture (USDA) - Natural Resources Conservation Service (NRCS) Geospatial Data Gateway (https://datagateway.nrcs.usda.gov/) and Geofabrik GmbH - Open Street Map (https://www.geofabrik.de/geofabrik/openstreetmap.html), respectively. An updated trail map for the Upper Scotts Creek Watershed, including the BLM Recreational Area, was created to estimate trail densities in the watershed. A preview image of the roads and trail maps is attached to this data release (see UpperScottsCreek_Roads_and_Trails_Map_2022_USGS2022_CC0.png).

This data set of line features represent Riverside County's recorded street centerlines.This data set was designed to carry out functions of the Transportation department and is not a true street network layer. Centerlines do not have complete "connectivity" due to the fact that this layer is primarily roads that have been recorded but does not necessarily contain all roads. OBJECTID - Internal feature number. STNAME - Recorded name of the centerline. TYPE - Used to classify roads, primarily by surface type. Description of the codes found in the attribute "TYPE" TYPE DESCRIPTION C01 Federal Aid Interstate C02 State Highways C03 F.A.U. Maintained C04 F.A.S. Maintained C05 Paved Surface Maintained C06 Paved Surface (Traveled) C07 Graveled Surface Maintained C08 Graveled Surface (Traveled) C09 Dirt Surface Maintained C10 Dirt Surface (Traveled) C11 Accepted For Public Use C12 Non-County/Accepted for P.U. C13 Non-County road C14 Vacated C15 Abandon C16 Maintained F.A.U./Non-County C17 Maintained F.A.S./Non-County C18 Maintained Paved/Accepted C19 Maintained Paved/Non-County C20 Maintained Paved/Vacated C21 Maintained Gravel/Accepted C22 Maintained Gravel/Non-County C23 Maintained Gravel/Vacated C24 Maintained Dirt/Accepted C25 Maintained Dirt/Non-County C26 Maintained Dirt/Vacated C27 Accepted/Vacated C28 Maintained Under Contract C29 City Road C30 Paved Maintained/Dirt Maintained C31 Dedicated and Accepted/CFD Maintained W01 Maintained for City W02 Maintained for City/Non-County W03 Maintained for City/Non-County (Reversed) W04 Maintained for City/Accepted W05 F.A.U. Maintained/Maintained for City W06 Dirt Surface Maintained/Maintained for City W07 Paved Surface Maintained/Maintained for City W08 Graveled Surface Maintained/Maintained for City Z01 Traffic Division Modeling Connectivity Use Only (The "W" series within the TYPE field were initially created for the City of Wildomar, but have had their application expanded to include any Centerline where the County maintains the road for a City - typically for a limited period after a City's incorporation. The "W" will continue as a convention to make it easy to distinguish such roads from roads normally maintained by the County, even though it is understood that the "W" will lose its initial association with the City of Wildomar over time.). GENPLANTYPE - General Plan Classification of the Road. Not corrected for the RCLIS 2003 updated at thsi time. Description of the codes found in the attribute "GENPLANTYPE" GENPLANTYPE SYMBOL DESCRIPTION 01 101 FREEWAY 02 201 EXPRESSWAY 03 301 URBAN ARTERIAL 04 304 URBAN ARTERIAL (PROPOSED) 05 401 ARTERIAL 06 404 ARTERIAL (PROPOSED) 07 501 MOUNTAIN ARTERIAL 08 504 MOUNTAIN ARTERIAL (PROPOSED) 09 13 MAJOR 10 16 MAJOR (PROPOSED) 11 21 SECONDARY 12 24 SECONDARY (PROPOSED) 13 801 SPECIFIC PLAN ROAD 14 804 SPECIFIC PLAN ROAD (PROPOSED) 15 25 SCENIC ROUTE 16 28 SCENIC ROUTE (PROPOSED) 17 0 COLLECTOR(PROPOSED) indicates that the road is part of the "General PLan Alignment" but does not currently exist as a legal centerline. This type of centerline will be stored in the CENTERLINEREF data set. DIRECTION - Represents the direction of traffic flow. Presently not supported. NAMEID - Numerical representation of the recorded street name. Unique STNAME and NAMEID values are tracked in the STNMS table. RDNUMBER - Used by the Transportation Department to identify county maintained roads. Used for accounting purposes. SEGNUMBER - Used in combination with the RDNUMBER to uniquely identify an individual centerline, segment, or length. No longer supported. FLAG - Indicates whether or not an arc will be used in a street network data set. Presently not used because there is no street network data set. L_F_ADD - The starting address for the left side of the street. L_T_ADD - The ending address for the left side of the street. R_F_ADD - The starting address for the right side of the street. R_T_ADD - The ending address for the right side of the street. PRE_DIR - The street direction prefix. Example: 'E' for east. STREET_NAME - The base legal street name of the centerline. Example: "MAIN". STREET_TYPE - The Street Name Type abbreviation. Example: 'ST' for street. Valid values for the STREET_TYPE field are: ' ' - ' ' (No Type is a space) AVE - AVENUE BLVD - BOULEVARD CIR - CIRCLE CT - COURT CV - COVE DR - DRIVE EXPY - EXPRESSWAY FWY - FREEWAY HWY - HIGHWAY LN - LANE LOOP - LOOP PATH - PATH PKWY - PARKWAY PL - PLACE PT - POINT RD - ROAD SQ - SQUARE ST- STREET TER - TERRACE TRL - TRAIL WALK - WALK WAY - WAY SUF_DIR - The street direction suffix. Example: "N' for north. TRACT - The tract map number in which the centerline can be found. MODIFIED - Modified Date CREATED - Created Date SOURCE_NOTES - References to legal documentation related to the Centerline found during research, including such things as recordation histroy, name change history, and acceptance for or termination of maintenance information, FULL_NAME - Name used to construct ROUTE_NAME field values. Used to detect changes in the STNAME value. AREA_PLAN_ABBREVIATION - Abbreviated Area Plan Name used to create ROUTE_NAME Valid values for AREA_PLAN_ABBREVIATION are: DESCN - Desert Center ECDES - East County/Desert ECVAP - Eastern Coachella Valley Plan ELSIN - Lake Elsinore EVALE - Eastvale HIGHG - Highgrove HVWIN - Harvest Valley/Winchester JURUP - Jurupa LAKEV - Lakeview/Nuevo LMATH - Lake Mathews MARCH - March MEADV - Mead Valley PASS - Pass Area PVERD - Palo Verde Valley RECHE - Reche Canyon REMAP - REMAP (Riverside Extended Mountain Area Plan) RIVER - Riverside/Corona/Norco SANJA - San Jacinto Valley SBCO - San Bernardino County SUNCI - Sun City/Menifee Valley SWAP - Southwest Area Plan TEMES - Temescal Valley WCVAP - Western Coachella Valley Area Plan SUBROUTE - Optional Identifier used to build ROUTE_NAME to separate branches or distiguish discontinuous portions of a street within an area plan that are unlikely to ever form a continuous route. ROUTE_NAME - Primary field used to construct a Linear Referencing derivative of the Centerlines layer. THis values is a component of ROUTE_ALT1 and ROUTE_ALT2 and is overriden by those fields when they have values. ROUTE_DIR1 - Used with ROUTE_NAME to build values for ROUTE_ALT1 when there is a value assigned. ROUTE_ALT1 - First Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Norh or East. ROUTE_DIR2 - Used with ROUTE_NAME to build values for ROUTE_ALT2 when there is a value assigned. ROUTE_ALT2 - Second Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Souh or West. BUILD_PRIORITY - Used to create Linear Referenced Routes. Sets the corner from which to build routes. Valuid values for BUILD_PRIORITY are: UL - Upper Left (Default) LL - Lower Left UR - Upper Right LR - Lower Right LINE_LINK - Geometric ID of Centerline arc. Made up of the From X/Y coordinate, the To X/Y coordinate and the Length. Used to detect geometric changes to an existing Centerline. CL_ID - Duplicate of OBJECTID. USed for detecting newly added segments to the network each week or to relate and join exported versions of CENTERLINES back to the original CENTERLINE feature class.FROM_X_COORDINATE, FROM_Y_COORDINATE, TO_X_COORDINATE and TO_Y_COORDINATE: The coordinate data for the end points of the line in numeric format.ROUTE_ORIENTED: Indicates if the line is drawn in the direction that corresponds to the Routes created based on the ROUTE_NAME fields.TRAVEL_DIRECTIONS: Indicates whether the road can be driven and in what directions. Values include "Both Ways", "From-To", "To-From" and "No Ways".CA_ROAD_SYSTEM_PAGE: The map page location of the California Roadway System (CRS) Maps containing the Centerline: See http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/CA_ROAD_SYSTEM_INDEX: The map index grid location of the California Roadway System (CRS) Maps containing the Centerline: See http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/CA_FUNCTIONAL_CLASS: The California Functional Classification of the Roadway per the CRS maps. Only classifications between 1 and 5 may qualify for state and federal funds. Classifications include:1 - Interstate2 - Other Freeway or Expressway3 - Other Principal Arterial4 - Minor Arterial5 - Major Collector6 - Minor Collector7 - LocalFEDERAL_ROUTE and FEDERAL_ROUTE_TYPE: The number of the Federal Interstate or U.S. Highway and the operational type of the facility, where applicable.STATE_ROUTE and STATE_ROUTE_TYPE: The number of the State Route or Highway and the operational type of the facility, where applicable.COUNTY_ROUTE: The number of a County Route.CITY_LEFT or CITY_RIGHT: The City or Community name to the left or right of the Centerline. Used for address geolocators.STATE: CA for Califonia. For geolocators that use the State field.ZIP_LEFT or ZIP_RIGHT: The ZIP code to the left or right of the Centerline. Used for address geolocators.FULL_NAME_MIXED_CASE: The full street name in mixed Upper and Lower case letters, sometimes also called Title case. May be used for labeling and geolocators.

This dataset is intended for researchers, students, and policy makers for reference and mapping purposes, and may be used for basic applications such as viewing, querying, and map output production, or to provide a basemap to support graphical overlays and analysis with other spatial data.

Tunnels in the United States According to the HSIP Tiger Team Report, a tunnel is defined as a linear underground passageway open at both ends. This dataset is based on the U.S. Department of Transportation's National Bridge Inventory (NBI). Records in the NBI that are attributed as "Tunnels" were extracted by TGS and were located using a combination of ortho imagery, topographic DRGs, NAVTEQ streets, and NAVTEQ railroads. Two points were captured for each tunnel, one at each tunnel opening. A line was then created either by tracing the NAVTEQ street / railroad, or, if there was not a NAVTEQ street / railroad coincident with the tunnel, then by a straight line joining the two points. For some tunnels, the NBI contains two records, one for the road through the tunnel and one for the road on top of the tunnel (if any). In these cases, both have been captured in this dataset. Features in this dataset that are over tunnels have a [RECTYPE] of "1", while features that are in tunnels have a [RECTYPE] of "2". Presumably, this was done because both roads could be blocked if the tunnel was destroyed. In some cases, the NBI only represented a tunnel with a record of type = "1" (over). In these cases, the following rules were applied: 1) If there was no road running through the tunnel, the road on top of the tunnel was captured. For example, if a mine conveyor runs through the tunnel and a county highway runs on top of the tunnel, the county highway was captured. 2) If a road ran through the tunnel, then this road was captured and the [RECTYPE] was changed to "2". The "feature carried" and "feature intersected" fields were also changed to be consistent with the feature actually captured. According to the U.S. DOT: "Our reporting requirements do not extend to tunnels, therefore, any info we have should be considered incomplete."

© U.S. Department of Transportation's National Bridge Inventory This layer is a component of Road and Rail Tunnels.

This is a subset of the U.S. Department of Transportation's National Bridge Inventory that depicts tunnels associated with roads and rail lines.

© U.S. Department of Transportation's National Bridge Inventory

Adopted and Proposed Scenic Highways from the State of California Department of Transportation (Caltrans), specific to the UNINCORPORATED areas of Los Angeles County.SOURCE: Caltrans; https://dot.ca.gov/programs/design/lap-landscape-architecture-and-community-livability/lap-liv-i-scenic-highwaysUPDATED: 4/20/17 for a newly adopted scenic highway.NEED MORE FUNCTIONALITY? If you are looking for more layers or advanced tools and functionality, then try our suite of GIS Web Mapping Applications.

Notice - Replacement of the English and French Web services (WMS and ESRI REST) with a bilingual one. The NRN product is distributed in the form of thirteen provincial or territorial datasets and consists of two linear entities (Road Segment and Ferry Connection Segment) and three punctual entities (Junction, Blocked Passage, Toll Point) with which is associated a series of descriptive attributes such as, among others: First House Number, Last House Number, Street Name Body, Place Name, Functional Road Class, Pavement Status, Number Of Lanes, Structure Type, Route Number, Route Name, Exit Number. The development of the NRN was realized by means of individual meetings and national workshops with interested data providers from the federal, provincial, territorial and municipal governments. In 2005, the NRN edition 2.0 was alternately adopted by members from the Inter-Agency Committee on Geomatics (IACG) and the Canadian Council on Geomatics (CCOG). The NRN content largely conforms to the ISO 14825 from ISO/TC 204.

This single line road network (SLRN) contains all road allowances within the county. Road allowances are classed by: provincial highways, county highways, county roads, rural roads, urban roads, county lanes, private lanes, unopened road allowances and closed roads. Official road names and alternate road names are included as well as civic address ranges for each road section. The data was originally created using 2002 orthoimagery and is continuously maintained using reference plans, registered plans and the most current orthoimagery.

This map represents roads that are Maintained by the County Department of Public Works Transportation division.

Road Centerlines for the City of Shasta Lake, CA. The road centerline file has been maintained as a major component of the Shasta County Integrated Public Safety System and has been updated to meet the needs of the public safety agencies for dispatch. Road centerline data is segmented at each intersecting feature along a route, which means multiple linear features may represent a single route. The road functional classifications assigned to the roadways are based on the California Department of Transportation (CalTrans) CA Road System (CRS) maps. The CRS maps can be viewed at this location: https://www.dot.ca.gov/hq/tsip/hseb/crs_maps/

The PUC data contains a [grade] attribute that allows for the isolation of at-grade crossings. There are 10,478 at-grade records in the most recent PUC file available. The PUC data also includes a crossing numbering system that should be maintained as part of the development of this feature to facilitate easy update and linkage to subsequent releases. There are over 14,000 open crossings included in the state inventory as of December 2020. The fields included in this table are copied directly from the CPUC data set without any changes. Version of 12/29/2020 - INCLUDES ONLY RECORDS WITH 'Crossing Status' = Open AND Latitude/Longitude coordinates are not blank.This list is provided as of October 28, 2020 for information only. The information may contain some inaccuracies. Comments may be sent to RCEB@cpuc.ca.gov with Subject: CPUC Rail Crossing List.

To identify the future regional roads of the Regional Official Plan. ROP Consolidation September 3, 2024.

Saskatchewan Highway Network map contains current Highway Network layer with highway classification based on varied criteria

This line feature class is the combined collection of the street centerlines created by various agencies in the San Luis Obispo county region and quality control checked by Contact One. The County of San Luis Obispo maintains these data as needed and at a minimum, monthly. Please report any errors to gis@co.slo.ca.us.category field domain valuesCode Description0 ALLEY1 CAMPGROUND 2 CEMETERY3 DRIVEWAY4 FREEWAY5 HIGHWAY6 MOBILE HOME PARK7 PARK ROAD8 PIER9 RAMP10 RETIRED11 ROAD12 TRAIL13 OTHER14 EMERGENCY ACCESS ROAD15 PAPER ROAD

This dataset represents the road network within the Regional Municipality of Waterloo and along its periphery. The network depicted includes private and public routes both paved and unpaved suitable for vehicular traffic.