Speed limit information for most of Queensland's roads. Includes state and locally controlled roads. Point-in-time data as per date of collection in dataset.

This map provides information on speed limits that are posted on state-maintained roadways in Virginia. Cities and towns set their own speed limits and these are not available to show on the map. Zoom in on the map to display the speed limits. Speed limits exist for all roads however; where this information is not available for mapping, they are not displayed. Most roads where speed limits are not shown are either rural, secondary roads (routes numbered 600 or greater) where a statutory 55 mph speed limit typically applies, or subdivision streets where a statutory 25 mph speed limit usually applies. These statutory speed limits are often are not posted on these roads. Click on any roadway to display the speed limit information.

It contains the full detail layer of the extents for certified speed limit records from 26 May 2022 onwards, and their associated attribute data.Previously, 68 different road controlling authorities (RCAs) published this information in multiple formats.You can use the data for:time-based analysisanalysis against other datasets, for example addressesbuilding additional datasets.The data is extracted from the NSLR on a nightly basis.New emergency speed limits are updated in this dataset shortly after being created in the NSLR.Note: speed limit record geometries (shapefiles) will overlap. This will be in addition to overpasses, underpasses, intersections, bus lanes, opposing speed differences and multiple speeds in the same direction. For example, if you have an overpass one speed limit will be given for the top level (bridge) and the second overlapping geometry for the bottom level (I.e. road under bridge).Permanent speed limit: A speed limit that’s in force except when a seasonal, variable, temporary - emergency or other temporary speed limit is in force.Variable speed limit: A speed limit that changes under certain conditions (excluding seasonal), for example due to the presence of a school where the speed limit is different at certain times of the day depending on the school activity.Seasonal speed limit: A speed limit that applies on a seasonal basis, for example during a holiday period. Seasonal speed limits can be one-off or recurring.Emergency speed limit: A speed limit put in place due to an emergency, for example an earthquake, tsunami or epidemic.The principles for how the speed limits interact with each other are as follows.Permanent and variable speed limits cannot overlap one another.A seasonal speed limit can overlap permanent and variable speed limits.A seasonal speed limit can overlap another seasonal speed limit, as long as the speed limit is not active at the same time as the record it is overlapping (i.e.one seasonal speed limit cannot overlap another seasonal speed limit).An emergency record can overlap a seasonal record but cannot overlap another emergency record.Temporary speed limits, other than emergency, are not included in this dataset.Members of the public can search for speed limits on New Zealand roads, obtain details of specific speed limits and obtain certified copies of speed limits through the NSLR web application. NSLR web browser applicationData reuse caveatsAs per license.Data quality statementRCAs signed off that the data in the NSLR is a true and accurate reflection of their bylaw. There is a high level of confidence in data quality, and we welcome user feedback.Data quality caveatsThe data has been migrated as provided by respective RCAs according to their current bylaw. There are errors as a result of having to migrate the legal speed limits as per the bylaw rather than what is signed on the ground. Many (but not all) of these were identified and RCAs can apply for Director’s approval to fix them.There is two known issues with the display of this data in Open Data, these are display issues within the Open Data application and do not impact the data when downloaded or used via API:Where there is no date 'December 31, 1969' is shown.Where there is no text 'null' is shown

This dynamic map service provodes a a linear representation of speed limit changes based on signs in the field or speed zones established by an Official Order.

Esri ArcGIS Online (AGOL) Hosted, View Feature Layer which provides access to the MDOT SHA Roadway Posted Speed Limit Signs data product.MDOT SHA Roadway Posted Speed Limit Signs data consists of point geometric features which represent the geographic locations of posted speed limit signs along MDOT SHA-maintained roadways throughout the State of Maryland. This layer is a hosted, view layer showing only Posted Speed Limit signage from the comprehensive MDOT SHA Roadway Sign Inventory. Roadway signs that share a sign support structure will be represented as stacked geometry.MDOT SHA Roadway Sign Inventory data is owned by the MDOT SHA Office of Traffic & Safety (OOTS). This data is currently updated on an annual basis. This is the latest version of the data, which was last updated in November 2019 (11/04/2019).MDOT SHA Roadway Sign Inventory data is published on ArcGIS Online for Maryland as a publicly available Hosted Feature Layer with Non-Restricted Access. Download / Export of the data is available in a variety of formats.For additional information, contact MDOT SHA OIT Enterprise Information Services:GIS@mdot.maryland.gov

The Open Data Hub has numerous data relating to roads and speed, whether it be the Sydney Region Carriageway, the Tolls on our NSW roads, or the speed zones and speed camera locations.

Below you will find a full list of available data sets;

• NorthConnex
• Sydney Region Carriageway
• Road Segment Data from Data.NSW
• NSW Speed Cameras
• Speed Zones
• NSW Toll Road Data
• NSW Rest Areas
• Toll Calculator API
• Toll Calculator
• Historic Roads Travel Time Data (TTDS)
• NSW Roads Traffic Volume Counts API
• Data on the speeding fines issued by the speeding cameras and NSW Police
• Data on the speeding fines by the offender's postcode
• Traffic Lights Location
• Penalty Offences
• NSW Clearways
• Live Traffic Site Status
• Live Traffic Hazards
• Live Traffic Cameras

Roadway Posted Speed Limit Signs data consists of point feature geometry which represents the geographic location of posted speed limit signs along public roadways in the State of Maryland. PLEASE NOTE: This layer is now deprecated as of September, 2020 and will be removed in September 2021.Data has been replaced with the following https://maryland.maps.arcgis.com/home/item.html?id=7549d74e31df427a82a64ab5a19d74e3#overviewRoadway Posted Speed Limit Signs data is developed as part of the Highway Performance Monitoring System (HPMS) which maintains and reports transportation related information to the Federal Highway Administration (FHWA) on an annual basis. HPMS is maintained by the Maryland Department of Transportation State Highway Administration (MDOT SHA), under the Office of Planning and Preliminary Engineering (OPPE) Data Services Division (DSD). This data is used by various business units throughout MDOT, as well as many other Federal, State and local government agencies. Roadway Posted Speed Limit Signs data is key to understanding the location of posted speed limit signs throughout the State of Maryland. Roadway Posted Speed Limit Signs data is updated and published on an annual basis for the prior year. This data is for the year 2017.For additional information, contact the MDOT SHA Geospatial Technologies Email: GIS@mdot.state.md.us For additional information related to the Maryland Department of Transportation (MDOT) Website: https://www.mdot.maryland.gov/ For additional information related to the Maryland Department of Transportation State Highway Administration (MDOT SHA) Website: https://roads.maryland.gov/Home.aspx Data Legal Disclaimer: The Maryland Department of Transportation State Highway Administration (MDOT SHA) makes no warranty, expressed or implied, as to the use or appropriateness of geospatial data, and there are no warranties of merchantability or fitness for a particular purpose or use. The information contained in geospatial data is from publicly available sources, but no representation is made as to the accuracy or completeness of geospatial data. MDOT SHA shall not be subject to liability for human error, error due to software conversion, defect, or failure of machines, or any material used in the connection with the machines, including tapes, disks, CD-ROMs or DVD-ROMs and energy. MDOT SHA shall not be liable for any lost profits, consequential damages, or claims against MDOT SHA by third parties.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Link:https://geodata.md.gov/imap/rest/services/Transportation/MD_RoadwayPostedSpeedLimits/FeatureServer/0

This dataset comprises road centerlines for all roads in San Diego County. Road centerline information is collected from recorded documents (subdivision and parcel maps) and information provided by local jurisidictions (Cities in San Diego County, County of San Diego). Road names and address ranges are as designated by the official address coordinator for each jurisidcition. Jurisdictional information is created from spatial overlays with other data layers (e.g. Jurisdiction, Census Tract).The layer contains both public and private roads. Not all roads are shown on official, recorded documents. Centerlines may be included for dedicated public roads even if they have not been constructed. Public road names are the official names as maintained by the addressing authority for the jurisdiction in which the road is located. Official road names may not match the common or local name used to identify the road (e.g. State Route 94 is the official name of certain road segments commonly referred to as Campo Road).Private roads are either named or unnamed. Named private roads are as shown on official recorded documents or as directed by the addressing authority for the jurisdiction in which the road is located. Unnamed private roads are included where requested by the local jurisidiction or by SanGIS JPA members (primarily emergency response dispatch agencies). Roads are comprised of road segments that are individually identified by a unique, and persistent, ID (ROADSEGID). Roads segments are terminated where they intersect with each other, at jurisdictional boundaries (i.e. city limits), certain census tract and law beat boundaries, at locations where road names change, and at other locations as required by SanGIS JPA members. Each road segment terminates at an intersection point that can be found in the ROADS_INTERSECTION layer.Road centerlines do not necessarily follow the centerline of dedicated rights-of-way (ROW). Centerlines are adjusted as needed to fit the actual, constructed roadway. However, many road centerline segments are created intially based on record documents prior to construction and may not have been updated to meet as-built locations. Please notify SanGIS if the actual location differs from that shown. See the SanGIS website for contact information and reporting problems (http://www.sangis.org/contact/problem.html).Note, the road speeds in this layer are based on road segment class and were published as part of an agreement between San Diego Fire-Rescue, the San Diego County Sheriff's Department, and SanGIS. The average speed is based on heavy fire vehicles and may not represent the posted speed limit.

Geospatial data about North Carolina Interstate Speed Limits. Export to CAD, GIS, PDF, CSV and access via API.

Statewide Road Network including sealed and unsealed roads. The dataset represents navigable roads, including public and private access roads and tracks. A separate data layer stores 'unformed' DCDB centrelines which do not represent navigable roads. A limited number of associated features are stored separately as point features. Automatically updated when changes occur.

This datasets presents Legal Speed Limits on state and local roads. The speed limit is the maximum speed limit allowed under the provisions of the State Traffic Act and Regulations. Road speed limits are used to regulate the speed of road vehicles. Speed limits may define maximum (which may be variable), minimum or no speed limit and are normally indicated using a traffic sign. Speed limits are set by the Commissioner of Main Roads Western Australia (Regulation 297 of the Road Traffic Code 2000) and enforced by national or regional police and/or judicial bodies. This layer shows the location of legal speed limits on all public access roads found in the Integrated Road Information System (IRIS) and is provided for information only. This data presents the speed limits of roads in Western Australia as of August 2018. For more information please visit the MRWA Open Data Portal.

This dataset contains estimates of the average number of vehicles that used roads throughout the City of Detroit. Each record indicates the Annual Average Daily Traffic (AADT) and Commercial Annual Average Daily Traffic (CAADT) for a road segment, where the road segment is located, and other characteristics. This data is derived from Michigan Department of Transportation's (MDOT) Open Data Portal. SEMCOG was the source for speed limits and number of lanes.

The primary measure, Annual Average Daily Traffic (AADT), is the estimated mean daily traffic volume for all types of vehicles. Commercial Annual Average Daily Traffic (CAADT) is the estimated mean daily traffic volume for commercial vehicles, a subset of vehicles included in the AADT. The Route ID is an identifier for each road in Detroit (e.g., Woodward Ave). Routes are divided into segments by features such as cross streets, and Location ID's are used to uniquely identify those segments. Along with traffic volume, each record also states the number of lanes, the posted speed limit, and the type of road (e.g., Trunkline or Ramp) based on the Federal Highway Administration (FHWA) functional classification system.

According to MDOT's Traffic Monitoring Program a commercial vehicle would be anything Class 4 and up in the FHWA vehicle classification system. This includes vehicles such as buses, semi-trucks, and personal recreational vehicles (i.e., RVs or campers). Methods used to determine traffic volume vary by site, and may rely on continuous monitoring or estimates based on short-term studies. Approaches to vehicle classification similarly vary, depending on the equipment used at a site, and may consider factors such as vehicle weight and length between axles.

For more information, please visit MDOT Traffic Monitoring Program.

Legal Speed Limit (State and Local Roads)The maximum speed limit allowed under the provisions of the State Traffic Act and Regulations. Road speed limits are used to regulate the speed of road vehicles. Speed limits may define maximum (which may be variable), minimum or no speed limit and are normally indicated using a traffic sign. Speed limits are set by the Commissioner of Main Roads Western Australia (Regulation 297 of the Road Traffic Code 2000) and enforced by national or regional police and/or judicial bodies.This layer shows the location of legal speed limits on all public access roads found in the Integrated Road Information System (IRIS) and is provided for information only.Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes.Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material:- The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.Creative Commons CC BY 4.0 https://creativecommons.org/licenses/by/4.0/

This layer contains the traffic regulatory signs, such as speed limit, no left turns, weight restrictions and other signs for motorists on the streets of Los Angeles.

The ORN is a provincewide geographic database of over 250,000 kilometres of municipal roads, provincial highways, and resource and recreational roads. The ORN is the authoritative source of roads data for the Government of Ontario. Road names in the ORN are the official names provided by the authoritative jurisdiction for each road segment, such as a municipality or the Ontario Government. The list of authoritative sources used for the ORN is in the “Ontario Road Network - List of Partners” document in the Supporting Files section below. You can also find the authoritative jurisdiction for a specific road feature in the Jurisdiction table in ORN Road Net Element. ORN Road Net Element requires an advanced knowledge of GIS including LRS and complex table relationships. This dataset contains the following related tables: * official street name * alternate street name * address information * road classification * number of lanes * road surface * speed limit * structure * toll point * blocked passage * route name * route number * jurisdiction * source * underpass * junction

Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines support address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network. (From ESRI Local Government Model "RoadCenterline" Feature)**This dataset was significantly revised in August of 2014 to correct for street segments that were not properly split at intersections. There may be issues with using data based off of the original centerline file. ** The column Speed Limit was updated in November 2014 by the Transportation Intern and is believed to be accurate** The column One Way was updated in November of 2014 by core GIS and is believed to be accurate.[MAXIMOID] A unique id field used in a work order management software called Maximo by IBM. Maximo uses GIS CL data to assign locations to work orders using this field. This field is maintained by the Transportation GIS specialists and is auto incremented when new streets are digitized. For example, if the latest digitized street segment MAXIMOID = 999, the next digitized line will receive MAXIMOID = 1000, and so on. STREET NAMING IS BROKEN INTO THREE FIELDS FOR GEOCODING:PREFIX This field is attributed if a street name has a prefix such as W, N, E, or S.NAME Domain with all street names. The name of the street without prefix or suffix.ROAD_TYPE (Text,4) Describes the type of road aka suffix, if applicable. CAPCOG Addressing Guidelines Sec 504 U. states, “Every road shall have corresponding standard street suffix…” standard street suffix abbreviations comply with USPS Pub 28 Appendix C Street Abbreviations. Examples include, but are not limited to, Rd, Dr, St, Trl, Ln, Gln, Lp, CT. LEFT_LOW The minimum numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 101.LEFT_HIGH The largest numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 201.LOW The minimum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 100.HIGHThe maximum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 200.ALIAS Alternative names for roads if known. This field is useful for geocode re-matching. CLASSThe functional classification of the centerline. For example, Minor (Minor Arterial), Major (Major Arterial). THIS FIELD IS NOT CONSISTENTLY FILLED OUT, NEEDS AN AUDIT. FULLSTREET The full name of the street concatenating the [PREFIX], [NAME], and [SUFFIX] fields. For example, "W San Antonio St."ROWWIDTH Width of right-of-way along the CL segment. Data entry from Plat by Planning GIS Or from Engineering PICPs/ CIPs.NUMLANES Number of striped vehicular driving lanes, including turn lanes if present along majority of segment. Does not inlcude bicycle lanes. LANEMILES Describes the total length of lanes for that segment in miles. It is manually field calculated as follows (( [ShapeLength] / 5280) * [NUMLANES]) and maintained by Transportation GIS.SPEEDLIMIT Speed limit of CL segment if known. If not, assume 30 mph for local and minor arterial streets. If speed limit changes are enacted by city council they will be recorded in the Traffic Register dataset, and this field will be updating accordingly. Initial data entry made by CIP/Planning GIS and maintained by Transportation GIS.[YRBUILT] replaced by [DateBuilt] See below. Will be deleted. 4/21/2017LASTYRRECON (Text,10) Is the last four-digit year a major reconstruction occurred. Most streets have not been reconstructed since orignal construction, and will have values. The Transportation GIS Specialist will update this field. OWNER Describes the governing body or private entity that owns/maintains the CL. It is possible that some streets are owned by other entities but maintained by CoSM. Possible attributes include, CoSM, Hays Owned/City Maintained, TxDOT Owned/City Maintained, TxDOT, one of four counties (Hays, Caldwell, Guadalupe, and Comal), TxState, and Private.ST_FROM Centerline segments are split at their intersections with other CL segments. This field names the nearest cross-street in the From- direction. Should be edited when new CL segments that cause splits are added. ST_TO Centerline segments are split at their intersections with other CL segments. This field names the nearest cross-street in the To- direction. Should be edited when new CL segments that cause splits are added. PAV_WID Pavement width of street in feet from back-of-curb to back-of-curb. This data is entered from as-built by CIP GIS. In January 2017 Transportation Dept. field staff surveyed all streets and measured width from face-of-curb to face-of-curb where curb was present, and edge of pavement to edge of pavement where it was not. This data was used to field calculate pavement width where we had values. A value of 1 foot was added to the field calculation if curb and gutter or stand up curb were present (the face-of-curb to back-of-curb is 6 in, multiple that by 2 to find 1 foot). If no curb was present, the value enter in by the field staff was directly copied over. If values were already present, and entered from asbuilt, they were left alone. ONEWAY Field describes direction of travel along CL in relation to digitized direction. If a street allows bi-directional travel it is attributed "B", a street that is one-way in the From_To direction is attributed "F", a street that is one-way in the To_From direction is attributed "T", and a street that does not allow travel in any direction is attibuted "N". ROADLEVEL Field will be aliased to [MINUTES] and be used to calculate travel time along CL segments in minutes using shape length and [SPEEDLIMIT]. Field calculate using the following expression: [MINUTES] = ( ([SHAPE_LENGTH] / 5280) / ( [SPEEDLIMIT] / 60 ))ROWSTATUS Values include "Open" or "Closed". Describes whether a right-of-way is open or closed. If a street is constructed within ROW it is "Open". If a street has not yet been constructed, and there is ROW, it is "Cosed". UPDATE: This feature class only has CL geometries for "Open" rights-of-way. This field should be deleted or re-purposed. ASBUILT field used to hyper link as-built documents detailing construction of the CL. Field was added in Dec. 2016. DateBuilt Date field used to record month and year a road was constructed from Asbuilt. Data was collected previously without month information. Data without a known month is entered as "1/1/YYYY". When month and year are known enter as "M/1/YYYY". Month and Year from asbuilt. Added by Engineering/CIP. ACCEPTED Date field used to record the month, day, and year that a roadway was officially accepted by the City of San Marcos. Engineering signs off on acceptance letters and stores these documents. This field was added in May of 2018. Due to a lack of data, the date built field was copied into this field for older roadways. Going forward, all new roadways will have this date. . This field will typically be populated well after a road has been drawn into GIS. Entered by Engineering/CIP. ****In an effort to make summarizing the data more efficient in Operations Dashboard, a generic date of "1/1/1900" was assigned to all COSM owned or maintained roads that had NULL values. These were roads that either have not been accepted yet, or roads that were expcepted a long time ago and their accepted date is not known. WARRANTY_EXP Date field used to record the expiration date of a newly accepted roadway. Typically this is one year from acceptance date, but can be greater. This field was added in May of 2018, so only roadways that have been excepted since and older roadways with valid warranty dates within this time frame have been populated.

This dataset contains the current estimated speed for about 1250 segments covering 300 miles of arterial roads. For a more detailed description, go to: http://bit.ly/Q9AZAD.

The Chicago Traffic Tracker estimates traffic congestion on Chicago’s arterial streets (nonfreeway streets) in real-time by continuously monitoring and analyzing GPS traces received from Chicago Transit Authority (CTA) buses. Two types of congestion estimates are produced every ten minutes: 1) by Traffic Segments and 2) by Traffic Regions or Zones. Congestion estimate by traffic segments gives the observed speed typically for one-half mile of a street in one direction of traffic.

Traffic Segment level congestion is available for about 300 miles of principal arterials. Congestion by Traffic Region gives the average traffic condition for all arterial street segments within a region. A traffic region is comprised of two or three community areas with comparable traffic patterns. 29 regions are created to cover the entire city (except O’Hare airport area). This dataset contains the current estimated speed for about 1250 segments covering 300 miles of arterial roads. There is much volatility in traffic segment speed. However, the congestion estimates for the traffic regions remain consistent for relatively longer period. Most volatility in arterial speed comes from the very nature of the arterials themselves. Due to a myriad of factors, including but not limited to frequent intersections, traffic signals, transit movements, availability of alternative routes, crashes, short length of the segments, etc. speed on individual arterial segments can fluctuate from heavily congested to no congestion and back in a few minutes. The segment speed and traffic region congestion estimates together may give a better understanding of the actual traffic conditions.

This dataset contains estimates of the average number of vehicles that used roads throughout the City of Detroit. Each record indicates the Annual Average Daily Traffic (AADT) and Commercial Annual Average Daily Traffic (CAADT) for a road segment, where the road segment is located, and other characteristics. This data is derived from Michigan Department of Transportation's (MDOT) Open Data Portal. SEMCOG was the source for speed limits and number of lanes.

The primary measure, Annual Average Daily Traffic (AADT), is the estimated mean daily traffic volume for all types of vehicles. Commercial Annual Average Daily Traffic (CAADT) is the estimated mean daily traffic volume for commercial vehicles, a subset of vehicles included in the AADT. The Route ID is an identifier for each road in Detroit (e.g., Woodward Ave). Routes are divided into segments by features such as cross streets, and Location ID's are used to uniquely identify those segments. Along with traffic volume, each record also states the number of lanes, the posted speed limit, and the type of road (e.g., Trunkline or Ramp) based on the Federal Highway Administration (FHWA) functional classification system.

According to MDOT's Traffic Monitoring Program a commercial vehicle would be anything Class 4 and up in the FHWA vehicle classification system. This includes vehicles such as buses, semi-trucks, and personal recreational vehicles (i.e., RVs or campers). Methods used to determine traffic volume vary by site, and may rely on continuous monitoring or estimates based on short-term studies. Approaches to vehicle classification similarly vary, depending on the equipment used at a site, and may consider factors such as vehicle weight and length between axles.

For more information, please visit MDOT Traffic Monitoring Program.

This webmap shows average traffic speed of major roads in Hong Kong. It is made available by the Transport Department under the Government of Hong Kong Special Administrative Region (the “Government”) at https://DATA.GOV.HK/ (“DATA.GOV.HK”). The source data is in XML web service and been processed and converted into Esri File Geodatabase format and then uploaded to Esri’s ArcGIS Online platform for sharing and reference purpose. The objectives are to facilitate our Hong Kong ArcGIS Online users to use the data in a spatial ready format and save their data conversion effort.

This dataset contains estimates of the average number of vehicles that used roads throughout the City of Detroit in 2019. Each record indicates the Annual Average Daily Traffic (AADT) and Commercial Annual Average Daily Traffic (CAADT) for a road segment, where the road segment is located, and other characteristics. This data is derived from Michigan Department of Transportation's (MDOT) Open Data Portal. SEMCOG was the source for speed limits and number of lanes.The primary measure, Annual Average Daily Traffic (AADT), is the estimated mean daily traffic volume for all types of vehicles. Commercial Annual Average Daily Traffic (CAADT) is the estimated mean daily traffic volume for commercial vehicles, a subset of vehicles included in the AADT. The Route ID is an identifier for each road in Detroit (e.g., Woodward Ave). Routes are divided into segments by features such as cross streets, and Location ID's are used to uniquely identify those segments. Along with traffic volume, each record also states the number of lanes, the posted speed limit, and the type of road (e.g., Trunkline or Ramp) based on the Federal Highway Administration (FHWA) functional classification system.According to MDOT's Traffic Monitoring Program a commercial vehicle would be anything Class 4 and up in the FHWA vehicle classification system. This includes vehicles such as buses, semi-trucks, and personal recreational vehicles (i.e., RVs or campers). Methods used to determine traffic volume vary by site, and may rely on continuous monitoring or estimates based on short-term studies. Approaches to vehicle classification similarly vary, depending on the equipment used at a site, and may consider factors such as vehicle weight and length between axles.For more information, please visit MDOT Traffic Monitoring Program.