VITAL SIGNS INDICATOR Daily Miles Traveled (T15)

FULL MEASURE NAME Per-capita vehicle miles traveled

LAST UPDATED July 2017

DESCRIPTION Daily miles traveled, commonly referred to as vehicle miles traveled (VMT), reflects the total and per-person number of miles traveled in personal vehicles on a typical weekday. The dataset includes metropolitan area, regional and county tables for per-capita vehicle miles traveled.

DATA SOURCE Federal Highway Administration: Highway Statistics Series 2015 Table HM-71; limited to urbanized areas https://www.fhwa.dot.gov/policyinformation/statistics.cfm

U.S. Census Bureau: Summary File 1 2010 http://factfinder2.census.gov

CONTACT INFORMATION vitalsigns.info@mtc.ca.gov

METHODOLOGY NOTES (across all datasets for this indicator) "Vehicle miles traveled reflects the mileage accrued within the county and not necessarily the residents of that county; even though most trips are due to local residents, additional VMT can be accrued by through-trips. City data was thus discarded due to this limitation and the analysis only examine county and regional data, where through-trips are generally less common.

The metropolitan area comparison was performed by summing all of the urbanized areas within each metropolitan area (9-nine region for the San Francisco Bay Area and the primary MSA for all others). For the metro analysis, no VMT data is available outside of other urbanized areas; it is only available for intraregional analysis purposes.

VMT per capita is calculated by dividing VMT by an estimate of the traveling population. The traveling population does not include people living in institutionalized facilities, which are defined by the Census. Because institutionalized population is not estimated each year, the proportion of people living in institutionalized facilities from the 2010 Census was applied to the total population estimates for all years."

Rhode Island was the state in the United States with the highest share of rural highway miles in poor condition in 2023. Nevertheless, nearly 37 percent of the highways in Puerto Rico, although not a state, had pavement in poor condition. On the other hand, Georgia, Florida, and Nevada had the best rural highways in the United States.

Miles of public roads by the roadway's functional system and whether rural or urban for the 50 states, DC, and Puerto Rico (from 1996) from FHWA Highway Statistics table HM-60. (Note: In 2009, the Urban functional class of Collectors became Major Collectors and Minor Collectors.)

Annual estimated length of lane miles by federal-aid system and rural /urban for the 50 States, DC, and Puerto Rico from the Highway Statistics table HM-48.

Annual length of U.S. public roads in miles by functional system for each of the 50 states, DC, and Puerto Rico from the Highway Statistics table HM-20. (Note: In 2009, the Urban functional class of Collectors became Major Collectors and Minor Collectors.)

A performance index has been prepared to highlight the total number of categories in which each state showed improvement. The darker the shade of green, the more categories of improvement. The light and dark green labels show the total disbursements per mile ($M) per state.Most states (37 of 50) improved or maintained their performance in five or more categories. Most states (38 of 50) also spent less than the national average, per mile of responsibility. Interestingly, those states that spent the most money did not make the most improvement, and states with relatively few resources also made progress. For instance, California spent about twice as much as the average state (per mile of responsibility), but its performance improved in just two of the seven measures (deficient bridges and fatality rate). Hawaii and New York also spent between 2 and 2.5 times the national average but improved in just three of seven measures. Conversely, 10 states (led by North Dakota, Virginia and Missouri) spent less than the national average per mile of responsibility but improved on all seven measures, and only one state (Florida) improved on all seven measures and spent more than the national average.

The Road Segment table describes the administration and ownership of the segment of road. It contains tabular polyline data showing the log miles/measures, road name, functional class, government control, and U.S. Routes. Road names are derived from visual surveys by field crew or official GIS maps. Functional class is set by the Federal Highway Administration (FHWA). All other categories are determined by state and local agencies. This dataset is updated weekly. County – County in Tennessee where associated features and attributes are located.Route Number – Route in Tennessee with corresponding attributes.Special Case – Route designator for non-standard routes such as By-Pass.00 None01 Spur - S02 Alternate - A03 State Connector - C04 Bypass - BP05 Business Route - BR06 Northbound - N07 Southbound - S08 Eastbound - E09 Westbound - WCounty Sequence – This number indicates the sequential number of times a route enters and leaves the county, begins with zero (0).Beginning Log Mile (BLM) – The beginning log mile (measure) for the route segment.Ending Log Mile (ELM) - The ending log mile (measure) for the route segment.Functional Classification – These codes, set by the FHWA, provide a statewide highway functional classification in rural and urban areas to determine functional usage of the existing roads and streets.01 Rural Interstate02 Rural Other Principal Arterial03 Rural Freeway or Expressway06 Rural Minor Arterial07 Rural Major Collector08 Rural Minor Collector09 Rural Local11 Urban Interstate12 Urban Freeway or Expressway14 Urban Other Principal Arterial16 Urban Minor Arterial17 Urban Collector19 Urban LocalGovernment Control – These codes determine ownership and maintenance responsibility.01 State Highway Agency02 County04 Municipal11 State Park12 Local Park21 Other State Agency25 Other Local Agency26 Private27 Railroad40 Other Public60 Other Federal Agency63 US Fish and Wildlife64 US Forest Service66 National Park Service67 TVA68 Bureau of Land Management70 Corps of Engineers (Civil)72 Air Force73 Navy or Marines74 Army80 OtherUS Route Number – US Route Number assigned to roadway segment.

description: This dataset is a single centerline highway network representation of the 10,000 miles Kansas State Highway System (Interstate, U.S., and Kansas routes). The state highway system is a portion of KDOT's All Roads Network. The All Roads network, which includes both and state system and non-state system single centerline road networks, is mutually exclusive, and can be combined into one layer. Network graphics are not true representations of scaled mileages for road segments. Mileages are adjusted, via an attribute table, to allow for traveled distance which considers changes in elevation.; abstract: This dataset is a single centerline highway network representation of the 10,000 miles Kansas State Highway System (Interstate, U.S., and Kansas routes). The state highway system is a portion of KDOT's All Roads Network. The All Roads network, which includes both and state system and non-state system single centerline road networks, is mutually exclusive, and can be combined into one layer. Network graphics are not true representations of scaled mileages for road segments. Mileages are adjusted, via an attribute table, to allow for traveled distance which considers changes in elevation.

Select summary highway statistics, 1980 - 2017, mileage, lane-miles, vehicle miles traveled, and fatalities by state and functional system.

Daily Miles Traveled (T14)

FULL MEASURE NAME
Total vehicle miles traveled

LAST UPDATED
August 2022

DESCRIPTION
Daily miles traveled, commonly referred to as vehicle miles traveled (VMT), reflects the total and per-person number of miles traveled in personal vehicles on a typical weekday. The dataset includes metropolitan area, regional and county tables for total vehicle miles traveled.

DATA SOURCE
California Department of Transportation: California Public Road Data/Highway Performance Monitoring System - http://www.dot.ca.gov/hq/tsip/hpms/datalibrary.php
2001-2020

Federal Highway Administration: Highway Statistics - https://www.fhwa.dot.gov/policyinformation/statistics/2020/hm71.cfm
2020

California Department of Finance: E-4 Historical Population Estimates for Cities, Counties, and the State - https://dof.ca.gov/forecasting/demographics/estimates/
2001-2020

US Census Population and Housing Unit Estimates - https://www.census.gov/programs-surveys/popest.html
2020

CONTACT INFORMATION
vitalsigns.info@mtc.ca.gov

METHODOLOGY NOTES (across all datasets for this indicator)
Vehicle miles traveled (VMT) reflects the mileage accrued within the county and not necessarily the residents of that county; even though most trips are due to local residents, additional VMT can be accrued by through-trips. City data was thus discarded due to this limitation and the analysis only examines county and regional data, where through-trips are generally less common.

The metropolitan area comparison was performed by summing all of the urbanized areas for which the majority of its population falls within a given metropolitan area (9-county region for the San Francisco Bay Area and the primary metropolitan statistical area (MSA) for all others). For the metro analysis, no VMT data is available in rural areas; it is only available for intraregional analysis purposes. VMT per capita is calculated by dividing VMT by an estimate of the traveling population.

The Kansas State System represents the "State roads" and "state highways": Per Kansas Statutes, Chapter 68: "State roads" and "state highways" means all roads designated as a part of the state highway system by the secretary of transportation. This dataset is a single centerline highway network representation of the 10,000 miles Kansas State Highway System (Interstate, U.S., and Kansas routes). The state highway system is a portion of KDOT's All Roads Network. The All Roads network, which includes both and state system and non-state system single centerline road networks, is mutually exclusive, and can be combined into one layer.Network graphics are not true representations of scaled mileages for road segments. Mileages are adjusted, via an attribute table, to allow for traveled distance which considers changes in elevation.More information about the Kansas Department of Transportation (KDOT) can be found at the following URL: ksdot.org.

Road centerlines digitized and maintained by Grant County GIS office.ROADNAMEThe name of the road, without road type or road direction. In capital letters.ROADTYPEThe type of road. Drive, Street, Avenue, Court, Ramp, Road, Driveway, etc.ROADPOSTDIRThe direction of the road. NW, NE, SW, SE.See Grant County Code Title 10 - ROADS, HIGHWAYS AND BRIDGES >> Chapter 10.16 - DESIGNATION AND CLASSIFICATION OF COUNTY ROADS >>10.16.010, which in part states: Roads running easterly and westerly, located northerly or southerly of base line, which is the township line between Townships 18 and 19 North, to be numbered beginning with road number one being the road on Section line one mile northerly of, or southerly of, base line, as the case may be; thence one number per section line road numbered consecutively.Roads running northerly or southerly, located easterly of or westerly of meridian line, which is the range line between Ranges 26 and 27 E.W.M., to be designated by letter, the road located on section line one mile easterly of or westerly of said meridian line, as the case may be, being designated by the letter "A"; thence one letter per each section line road lettered consecutively.Intermediate roads running in a cardinal direction within sections shall be designated by the next lower number or letter, followed by the distance in tenths of a mile; for example, a road five and one-half miles north of base line in northwest quadrant would be Road 5.5 N.W.The above described plan divides the county into four quadrants; southwest, northwest, southeast, and northeast. Roads will, in addition to the above described number or letter, carry the appropriate suffix, SW, NW, SE or NE.Diagonal roads or winding roads shall be designated by name, as authorized by the board of county commissioners.ALTROADNAMEA local name or alternative name for the road.FEDROUTEThe Interstate or US Route numberSTROUTEThe State Route numberCTYROUTEA Yes entry indicates it is a County-maintained road. County maintenance responsibility changes often. The data is only as good as the last update from the Public Works Department.FULLNAMEThe full name of the road, including the Road Name, Road Type, and Post Direction. In title case capitalization.ROUTETYPEThe type of transportation route. Interstate, US, State, County, City, Rural, Access, DrivewayCityNameThe Grant County city the road is associated with.

11/22/2024 – The 4 lanes of US 85 from south of the Little Missouri to south of Watford City was added, US 2 was realigned near RP 313, about 2 miles east of Petersburg. There have also been numerous intersections and ramps "trued up" for preparation of MIRE intersections. 1/27/2022 – Business 94 at Dickinson Interchange 64 – The NE & SE ramps were realigned due to 2021 construction. The 2 ramps and 94B were adjusted to a single intersection. Hwy 20 between reference points 87 and 90 was realigned due to a grade raise several years ago.3/1/21 - Realigned the following highways: Hwy 1804 - Mileposts 300–301, 303–305, and 317-317.979, Hwy 85 - Mileposts 123-130, Hwy 23A – Milepost 911 and Hwy 35 - Mileposts 0–12/3/2020 – Minot Bypass - Added the southbound route to Hwy 83B (Route ID = 10). This includes realignment of the south bound ramp at reference point 921.5. Also realigned two ramps at the I94 and University Drive interchange in Fargo.12/4/19 - NewTown Bypass – 1.3714 miles was added to Route ID 297. A new reference point was created at the intersection of Route ID 297 and Route ID 205 (Hwy 23) at 48.684 and at 925.629 (Hwy 23B). Reference points were also created at 926 and 927 on Route ID 297 (Hwy23B). The ramps at the Sheyenne Interchange in West Fargo were updated. The Route ID = 169. The 5 existing ramps were realigned and 3 other ramps were created.9/13/18 - Route ID 4/253 - US 2 Business in Williston, alignment change as it intersects US 2. Route ID 67 - 32nd Avenue interchange on I-29, addition of exit ramp for I-29 Southbound traffic. Route ID 205 - alignment change at the intersection of ND 23 and County Roads 55 and 103/21/17 - Route ID 68 Interchange 64.252 on I-29 in Fargo. This interchange is 13th Avenue and I-29 one leg of the ramp was realigned.1/25/17 - started to maintain roads in Esri's Road and Highways. The shapes now contain measures in miles along with the associated linear referencing/roads and highways fields. Changes also include adding ramps and mainline designations in RTE_SUFFIX field.9/22/16 - added Killdeer Bypass 1. ND 22 North Route ID = 272, Created a new alignment for ND 22 west of Killdeer that begins with intersection of ND 200 and travels northeasterly to a junction with ND 22B north of Killdeer. New reference points were created on the new alignment as follows: 105.710 intersection of ND 22 and ND 200, 106, 107, 108, 109, 109.518 intersection of ND 22 and ND 22B north of Killdeer.2. ND 22 Business (Killdeer) Route ID = 302, The existing ND 22 through Killdeer becomes ND 22 Business due to the completion of a bypass route constructed west of Killdeer. New reference points were created as follows: 940.466 this junction of ND 22, ND 200 and ND 22B. Current ND 22 reference points through Killdeer remain in place but the number changes as follows: 105.000 = 941.000, 106.000 = 942.000, 107.000 = 943.000, 108.000 = 944.000, 109.000 = 945.000. Reference point 945.518 intersection of ND 22B and ND 22 north of Killdeer was also created.3. ND 200 East Route ID = 200, A new reference point 93.247 was created for the intersection of ND 22 and ND 200 west of Killdeer.9/6/16 by bb - added Dickinson Bypass and associated Reference Points.3/1/16 by bb - realigned US 85 North Route ID = 261 to match 2015 NAIP. Added Ramps on 94 at Mile Marker 56.668.10/20/2015 by bb - 1. US 85 North Route ID = 261, Created new alignment for US 85 North that follows the permanent NW Bypass at Williston. New reference points were created as follows: 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 196.705 this is the junction of US 85 and US 2 north of Williston.2. US 85 South Route ID = 300, Created new alignment for US 85 South that completes the four lane project between Alexander and Williston. New reference points were created as follows: 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, and 183.743. This is the junction with the US 2 west of Williston. Created new alignment for US 85 that follows the permanent NW Bypass at Williston. New Reference points created as follows: 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 196.705 this is the junction of US 85 and US 2 north of Williston.3.US 2 East Route ID = 253, alignment change north of Williston at junction of US 85, also created new reference point 25.674 at the intersection of US 85 on north end of NW Permanent Bypass.4. US 2 West Route ID = 254, alignment change north of Williston at junction of US 85, also created new reference point 25.674 at the intersection of US 85 on north end of NW Permanent Bypass.5. ND 3 Route ID = 263, Realignment and grade raise south of Junction of ND 200 west of Hurdsfield has been corrected.5/14/15 by bb - US 281 slip ramp at Church’s Ferry has been removed during a reconstruction project. This segment of roadway was designated as Route ID 25, Interchange ID 175.379, reference points 3.000 and 4.500.2/6/15 by bb - An extension of ND 46 has been added to the State Highway system. The segment of roadway east of I-29 was removed from the State Highway system in 1977. As of May 2011, a document showing a maintenance agreement with a county, as required by State Law to transfer responsibility, has not been found. The Fargo District has been doing basic maintenance on this segment. The segment of road that begins at I-29 and extends to the east until the intersection CMC 0957 is added to the State Highway system. The addition will result in an increase of 0.4 miles. This addition has also created a new reference point 120.823 which is at the end of the highway, reference point 120.318 is moved to the center of the structure on I-29.11/18/14 by bb - added New Town Bypass11/3/14 by Gerald - extended US85 Southbound to Mile Marker 172US 85 South Route ID = 300, Created new alignment for US 85 South that follows the Watford City SW Bypass and the West Bypass at Alexander as well as the new alignment for the 4-lane project that continues to reference point 172.000 which is north of McKenzie County Highway 16. New reference points were created as follows: 139.082 beginning of highway south of Watford City, 140.831 junction with the US 85 Business in Watford City, 145.659 junction of US Business west of Watford City, 160.505 junction with US 85 Business south of Alexander, 163.506 junction of US 85 north of Alexander. Created all whole number reference points between 139.082 and reference point 172.000.10/29/14 by Gerald 1. ND 23 Business Route ID = 297, Changed existing ND 23 in Watford City from the previous Junction of US 85 to the Junction of ND 1806 to ND 23B also changed the reference points 0.000 = 900.000, 1.000 = 901.000, 1.350 = 901.350, 2.000 = 902.000, 3.000 = 903.000, 3.353 = 903.3532. ND 23 East Route ID = 205, Watford City SE Bypass from the previous Junction of US 85 continuing northeasterly to the current alignment of ND 23. New reference point 0.533 was created for the beginning of the route as well as reference point 3.701 which is the Junction with ND 1806 extension.3. ND 23 West Route ID = 299, Watford City SE Bypass from the previous Junction of US 85 continuing northeasterly to the current alignment of ND 23. New reference point 0.533 was created for the beginning of the route as well as reference point 3.751 which is the termination point of this route.4. ND 1806 Route ID = 271, Created an extension of ND 1806 from the Junction of ND 23 B north of Watford City to the Junction of the ND 23 along the new alignment. New reference point 311.577 was created for the intersection.5. US 85 North Route ID = 261, Created new alignment for US 85 North that follows the Watford City SW Bypass and the West Bypass at Alexander as well as the new alignment for the 4-lane project that continues to the Junction of US 2 at Williston. New reference points were created as follows: 140.831 junction with the US 85 Business in Watford City, 145.659 junction of US Business west of Watford City, 160.505 junction with US 85 Business south of Alexander, 163.506 junction of US 85 north of Alexander.6. US 85 South Route ID = 300, Created new alignment for US 85 South that follows the Watford City SW Bypass and the West Bypass at Alexander as well as the new alignment for the 4-lane project that continues to the Junction of ND 200 North of Alexander. New reference points were created as follows: 140.831 junction with the US 85 Business in Watford City, 145.659 junction of US Business west of Watford City, 160.505 junction with US 85 Business south of Alexander, 163.506 junction of US 85 north of Alexander. Created a new reference point 139.082 which is the beginning point for US 85 South along with all reference points between this point and the Junction of ND 200 North of Alexander.7. US 85 Business North Route ID = 298, The existing route US 85 through Watford City and Alexander becomes US 85 Business due to the completion of the Bypass routes. New reference points that were created are: 950.000 intersection with US 85, 950.555 intersection with ND 23, 951.000, 952.000, 952.486 intersection with ND 23 A, 952.707 intersection with ND 23 B, 953.000, 954.000, 955.000, 956.000, 956.233 intersection with US 85 west of Watford City, 970.079 intersection with US 85 south of Alexander, 971.000, 972.000, 973.000 intersection with US 85 north of Alexander.8. Several small alignment changes occurred due to construction projects: ND 8 Junction ND 50 to Bowbells. ND 22 slide repair through the badlands. ND 57 and ND 20 South of Devils Lake. ND 31 bridge replacement 13 miles north of South Dakota Border. ND 23A in Watford City, this highway had the wrong designation as ND 23B, this change corrected this error and is now correctly designated as ND 23A.9. Junction of ND 1804 and ND 58 near Trenton, the intersection of these two highways was realigned.10. US 2 alignment in Williston near 11th street to near 9th Ave NW.Changed all RTE_SIN codes to either I, U, or S.2/15/13 - changes made

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not bedivided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

FAF domestic region level datasets and products provide information for states, state portions of large metropolitan areas, and remainders of states. Metropolitan areas consist of Metropolitan Statistical Areas or Consolidated Statistical Areas as defined by the Office of Management and Budget. When a metropolitan area is entirely within a state or when a state's portion of a multi-state metropolitan area is large enough to support the sampling procedures in the Commodity Flow Survey, the area becomes a separate FAF region. Small single-state metropolitan areas and small portions of a multi-state metropolitan area are part of the State or Remainder of State. FAF has two metropolitan areas that are each divided into three FAF regions, four that are each divided into two FAF regions, and several that have small pieces combined with States or Remainders of States.

© United States Department of Transportation, Federal Highway Administration. For more information, see the site http://www.ops.fhwa.dot.gov/freight/freight_analysis/faf/faf3/userguide/index.htm This layer is sourced from maps.bts.dot.gov.

The spatial component of the FAF network is derived from National Highway System Version 2009.11 and contains state primary and secondary roads, National Highway System (NHS), National Network (NN) and several intermodal connectors as appropriate for the freight network modeling. The network consists of over 447,808 miles of equivalent road mileage. The data set covers the 48 contiguous States plus the District of Columbia, Alaska, and Hawaii. The nominal scale of the data set is 1:100,000 with a maximal positional error of ±80 meters.

© ederal Highway Administration Office of Freight Management and Operations and the Battelle Memorial Institute, Columbus, OH

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not bedivided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

(Link to Metadata) EmergencyE911_RDS was originally derived from RDSnn (now called TransRoad_RDS). "Zero-length ranges" in the ROADS layer pertain to grand-fathered towns that have not yet provided the Enhanced 9-1-1 Board road segment range information. RDSnn was originally developed using a combination of paper and RC Kodak RF 5000 orthophotos (visual image interpretation and manual digitizing of centerlines). Road attributes (RTNO and CLASS) were taken from the official VT Agency of Transportation (VTrans) highway maps. New roads not appearing on the photos were digitized with locations approximated from the VTrans highway maps. State Forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 2500 or RF 1250 orthophotos and GPS, or other means for adding new roads and improving road locations. The Enhanced E911 program added new roads from GPS and orthos between 1996-1998. Also added road name and address geocoding. VCGI PROCESSING (Tiling and Added items); E911 provides the EmergencyE911_RDS data to VCGI in a statewide format. It lacks FIPS6 coding, making it difficult to extract data on the basis of town/county boundaries. As a result, VCGI has added FIPS6 to the attribute table. This field was originally populated by extracting MCODE value from RDNAME and relating to TBPOLY.PAT to bring over matching MCODE values. FIPS6 problems along the interstates and "Gores & Grants" in the Northeast Kingdom, were corrected. All features with an MCODE equal to 200 or 579 were assigned a FIPS6 equal to 0. The center point of these arcs were then intersected with BoundaryTown_TBHASH to assign a FIPS6 value. This information was then transfered back into the RDS.AAT file via a relate. A relate was established between the ROADNAMES.DBF file (road name lookup table) and the RDS.AAT file. The RDFLNAME attribute was populated by transfering the NAME value in the ROADNAMES.DBF table. The RDFLNAME item was then parsed into SUF.DIR, STREET.NAME, STREET.TYPE, and PRE.DIR, making addressing matching functions a little easier. See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. https://vcgi.vermont.gov/techres/?page=./white_papers/default_content.cfmField Descriptions:OBJECTID: Internal feature number, automatically generated by Esri software.SEGMENTID: Unique segment ID.ARCID: Arc identifier, unique statewide. The ARCID is a unique identifier for every ARC in the EmergencyE911_RDS data layer.PD: Prefix Direction, previously name PRE.DIR.PT: Prefix Type.SN: Street Name. Previously named STREET.ST: Street Type.SD: Suffix Direction, i.e., W for West, E for East, etc.GEONAMEID: Unique ID for each road name.PRIMARYNAME: Primary name.ALIAS1: Alternate road name 1.ALIAS2: Alternate road name 2.ALIAS3: Alternate road name 3.ALIAS4: Alternate road name 4.ALIAS5: Alternate road name 5.COMMENTS: Free text field for miscellaneous comments.ONEWAY: One-way street. Uses the Oneway domain*.NO_MSAG:MCODE: Municipal code.LESN: Left side of road Emergency Service Number.RESN: Right side of road Emergency Service Number.LTWN: Left side of road town.RTWN: Right side of road town.LLO_A: Low address for left side of road.RLO_A: Low address for right side of road.LHI_A: High address for left side of road.RHI_A: High address for right side of road.LZIP: Left side of road zip code.RZIP: Right side of road zip code.LLO_TRLO_TLHI_TRHI_TRTNAME: Route name.RTNUMBER: Route number.HWYSIGN: Highway sign.RPCCLASSAOTCLASS: Agency of Transportation class. Uses AOTClass domain**.ARCMILES: ESRI ArcGIS miles.AOTMILES: Agency of Transportation miles.AOTMILES_CALC:UPDACT:SCENICHWY: Scenic highway.SCENICBYWAY: Scenic byway.FORMER_RTNAME: Former route name.PROVISIONALYEAR: Provisional year.ANCIENTROADYEAR: Ancient road year.TRUCKROUTE: Truck route.CERTYEAR:MAPYEAR:UPDATEDATE: Update date.GPSUPDATE: Uses GPSUpdate domain***.GlobalID: GlobalID.STATE: State.GAP: Gap.GAPMILES: Gap miles.GAPSTREETID: Gap street ID.FIPS8:FAID_S:RTNUMBER_N:LCOUNTY:RCOUNTY:PRIMARYNAME1:SOURCEOFDATA: Source of data.COUNTRY: Country.PARITYLEFT:PARITYRIGHT:LFIPS:RFIPS:LSTATE:RSTATE:LESZ:RESZ:SPEED_SOURCE: Speed source.SPEEDLIMIT: Speed limit.MILES: Miles.MINUTES: Minutes.Shape: Feature geometry.Shape_Length: Length of feature in internal units. Automatically computed by Esri software.*Oneway Domain:N: NoY: Yes - Direction of arcX: Yes - Opposite direction of arc**AOTClass Domain:1: Town Highway Class 1 - undivided2: Town Highway Class 2 - undivided3: Town Highway Class 3 - undivided4: Town Highway Class 4 - undivided5: State Forest Highway6: National Forest Highway7: Legal Trail. Legal Trail Mileage Approved by Selectboard after the enactment of Act 178 (July 1, 2006). Due to the introduction of Act 178, the Mapping Unit needed to differentiate between officially accepted and designated legal trail versus trails that had traditionally been shown on the maps. Towns have until 2015 to map all Class 1-4 and Legal Trails, based on new changes in VSA Title 19.8: Private Road - No Show. Private road, but not for display on local maps. Some municipalities may prefer not to show certain private roads on their maps, but the roads may need to be maintained in the data for emergency response or other purposes.9: Private road, for display on local maps10: Driveway (put in driveway)11: Town Highway Class 1 - North Bound12: Town Highway Class 1 - South Bound13: Town Highway Class 1 - East Bound14: Town Highway Class 1 - West Bound15: Town Highway Class 1 - On/Off Ramp16: Town Highway Class 1 - Emergency U-Turn20: County Highway21: Town Highway Class 2 - North Bound22: Town Highway Class 2 - South Bound23: Town Highway Class 2 - East Bound24: Town Highway Class 2 - West Bound25: Town Highway Class 2 - On/Off Ramp30: State Highway31: State Highway - North Bound32: State Highway - South Bound33: State Highway - East Bound34: State Highway - West Bound35: State Highway - On/Off Ramp40: US Highway41: US Highway - North Bound42: US Highway - South Bound43: US Highway - East Bound44: US Highway - West Bound45: US Highway - On/Off Ramp46: US Highway - Emergency U-Turn47: US Highway - Rest Area50: Interstate Highway51: Interstate Highway - North Bound52: Interstate Highway - South Bound53: Interstate Highway - East Bound54: Interstate Highway - West Bound55: Interstate Highway - On/Off Ramp56: Interstate Highway - Emergency U-Turn57: Interstate Highway - Rest Area59: Interstate Highway - Other65: Ferry70: Unconfirmed Legal Trail71: Unidentified Corridor80: Proposed Highway Unknown Class81: Proposed Town Highway Class 182: Proposed Town Highway Class 283: Proposed Town Highway Class 384: Proposed State Highway85: Proposed US Highway86: Proposed Interstate Highway87: Proposed Interstate Highway - Ramp88: Proposed Non-Interstate Highway - Ramp89: Proposed Private Road91: New - Class Unknown92: Military - no public access93: Public - Class Unknown95: Class Under Review96: Discontinued Road97: Discontinued Now Private98: Not a Road99: Unknown***GPSUpdate Domain:Y: Yes - Needs GPS UpdateN: No - Does not need GPS UpdateG: GPS Update CompleteV: GPS Update Complete - New RoadX: Unresolved Segment

The spatial component of the FAF network is derived from National Highway System Version 2009.11 and contains state primary and secondary roads, National Highway System (NHS), National Network (NN) and several intermodal connectors as appropriate for the freight network modeling. The network consists of over 447,808 miles of equivalent road mileage. The data set covers the 48 contiguous States plus the District of Columbia, Alaska, and Hawaii. The nominal scale of the data set is 1:100,000 with a maximal positional error of ±80 meters.

© "Freight Analysis Framework Network Machine Readable Data Files" were prepared by the Federal Highway Administration Office of Freight Management and Operations, Washington DC, 2013 The freight assignment, capacity analysis and modeling portions of "FAF Network" are developed by Battelle Memorial Institute, Columbus, OH.

This layer is sourced from maps.bts.dot.gov.

MILE_MARKERS_SYSTEM1_INDOT_IN is a point shapefile that contains locations of all mile-markers on System 1 roads in Indiana, provided by personnel of Indiana Department of Transportation (INDOT), Business Information and Technology Systems, GIS Mapping. The source data provided by INDOT was an ESRI point feature class (in a file geodataase) named "DOTGIS_Ref_Post_Exor." MILE_MARKERS_SYSTEM1_INDOT_IN is attributed with route numbers, and mile-marker post numbers. On November 8, 2012 mile-markers for the extension of Interstate 69 (I-69) were added to these data. The term "System 1 Roads" refers to all roads found in the System 1 road network that include: interstates, U.S. highways, state routes, ramps, institutional roads (roads in state university properties, state hospitals, Indiana National Guard properties), and IDNR roads (roads contained within properties owned by IDRN and maintained by INDOT). The following is excerpted from the metadata provided by INDOT for the source shapefile STATEREFPOST.SHP: "StateRefPost.shp is a Point Layer, at one mile increments on all system one roads"

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.