Average weekday traffic counts (AWT) are collected at count stations throughout the city and represent the daily average for Monday-Friday traffic volume. Count stations in the eastern section of the city are collected in even numbered years, while those in the city's western section are collected in odd numbered years. Field descriptions/definitions for traffic count data as follows: ObjectID: GIS auto-generated unique identifiermslink: mslink of street segmentsegment_na: street segment nameSTATION: count station numberSOURCE: designates segment with counter or linkedSTATION: volume count station numberSOURCE: volume count station or linked segmentAWT_Count: most recent average weekday traffic countAWT_Yr: year of most recent countShape: GIS geometry typeYear_Txt: year of most recent count (text field)Shape.STLength(): GIS calculated segment length
This data set gives traffic flows for three locations throughout the city, broken out by hour, for a week of each month for a year. The data is mostly for the year 2017, but note that in some cases, 2016 numbers were used instead.
Bike counts are collected annually and represent the daily average for Monday-Friday bike volumes during the months of April-October. Field descriptions/definitions for bike count data as follows:ObjectID: GIS auto-generated unique identifierLocation: bike count locationSignal_Typ: type of traffic signal at count location, if applicableConnected: connection to city traffic signal network StationID: internal station IDCount_: most recent average weekday bike count Count_Yr: year of most recent countYear_Txt: year of most recent count (text field)Shape: GIS geometry type
This data set gives hourly pedestrian counts for six locations on upper State Street for the period between August 12, 2018, and August 31, 2020, as reported by the Traffic Engineering department’s pedestrian counters.
Fields
ObjectID: GIS auto-generated unique identifier
Angle: Sign rotation
Text: Traffic Engineering department shorthand for sign type
Text Long: Text on sign, where applicable
Installation Date: Initial date of install
Arrow Style: Used by Traffic Engineering for symbolization
Replacement Date: Date of sign replacement
Sign-ID: Unique identifier used for asset management purposes
Ownership: Sign ownership (Null implies City of Madison)
Maint By Agency: Maintenance agency
Muni: Municipal location of signShape: GIS geometry type
Intersection Control Inventory. City of Madison:City of Madison Traffic Engineering for arterial and collector intersections.Greater Madison MPO for local intersections. Not complete.Outside City of Madison:Greater Madison MPO for arterial and collector intersections. Local intersections not collected.Sources:Updated: 6/2022.2020 orthophotos, Google Street View.Traffic Control for Intersections with Arterial or Collector RoadwayInt_Class: Highest level of Roadway Functional Class (MPO) for intersection.A: ArterialC: CollectorL: LocalIntControl: Traffic Control at IntersectionSTA: Stop (All Way) . All approaches have a stop sign. STM: Stop (Multi) Locations that have more than 2 approaches with stops, but not all are stop controlled. 3-way stops are considered Multi.ST: Stop. One street has stop signs, while the other has no control. 3-way stops are considered Multi.YD: Yield. Any non-roundabout intersection with a yield sign.YDR: Yield (Round) . Roundabouts with yield signs.NO: No Control. No control identifiedU: Unknown. Unable to identifySL: Signal. Signal for any direction.
https://www.cityofmadison.com/policy/datahttps://www.cityofmadison.com/policy/data
Centerline file used for Bike LTS Network. Has existing streets and bike paths integrated.Clean topology. All connections are end point to end point.Bridges involving bike paths cleaned manually to accommodate bug in Network Analyst connectivity using elevation fields.The Bicycle Level of Traffic Stress (LTS) system rates or scores streets and paths by calculating an LTS score (1, 2, 3, or 4) for each street or multi-use path segment, intersection approach, and intersection crossing and then assigning the highest of the three scores to the segment. In those cases where the intersection LTS score is higher than the street segment score, the street segment encompassing the first block on either side of the intersection is given the higher intersection score. LTS scores for street segments are based on the posted speed limit, traffic volumes, number of travel lanes, and bicycle lane or bicycle/parking lane dimensions. Multi-use paths are classified as the lowest stress (LTS score of 1). Please refer to the Low-Stress Bicycle Network Report, and updated segment methodology for additional detail. Description of LTS Levels for Street SegmentsLTS 1: Paths and streets with 1 lane per direction, speed limits ≤ 20 mph, and low traffic volumes, or up to 25 mph with bike lanes.LTS 2: Streets with 1 lane per direction, speed limits ≤ 30 mph, and low traffic volumes and/or bike lanes.LTS 3: Streets with 1-2 lanes per direction, speed limits ≤ 35 mph, and moderate traffic volumes and/or bike lanes.LTS 4: Streets with 2+ lanes per direction, with high speed limits and/or high traffic volumes.The LTS score for an intersection approach is based on the intersection configuration. Specifically, the score is based on whether there is a right-turn only lane and, if so, whether there is a “pocket” bike lane to the left of the right-turn lane and other details related to the design of these lanes and the curb radius of the intersection. Description of LTS levels for Intersection ApproachesNo effect: Simple intersection with no right-turn lane, or a single right turn lane of less than 75 feet with slow turning speeds.LTS 2: Intersection with a single right-turn lane of less than 150 feet and a bike lane that continues straight.LTS 3: Intersection with a right-turn lane of 75-150 feet and no bike lane, a bike lane that shifts to the left across a right-turn lane with slow turning speeds, or a bike lane that continues straight alongside a turn lane of more than 150 feet.LTS 4: Other intersection configurations, including multiple right-turn lanes and/or higher turning speeds.The LTS score for an unsignalized intersection crossing is based on the number of travel lanes per direction on the intersecting street to be crossed, the presence of a median (for multi-lane streets), and the speed limit on the intersecting street. Description of LTS Levels for Intersection CrossingsUnsignalized CrossingsLTS 1: Intersecting street has only 1 lane per travel direction and speed limit ≤ 30 mph.LTS 2: Intersecting street has only 1 lane per travel direction and speed limit ≤ 35 mph or 2 lanes but speed limit ≤ 30 mph.LTS 3: Intersecting street has 1 lane per travel direction and a speed limit of 40+ mph, or 2 lanes and a speed limit of 35 mph.LTS 4: Intersecting street has 2 lanes per travel direction and 40+ mph speed limit, or 3+ lanes.In some cases, intersection crossing LTS is reduced below these levels if the intersecting street is one-way only or is equipped with a median refuge. Signalized CrossingsCrossing streets at signalized intersections does not present a significant barrier for bicyclists and thus does not affect the LTS score unless a right turn lane is present.LTS_F (LTS_F) Final Bike LTS (Level of Traffic Stress) score.
Intersections. City of Madison Area:City of Madison Traffic Engineering for arterial and collector intersections and most local.Greater Madison MPO for local intersections. Not complete.Outside City of Madison Area:Greater Madison MPO for arterial and collector intersections. Local intersections not collected.Updated 6/2022.2020 Orthophotos, Google Street ViewIntersection polygons mapped for Crash Analysis and Level of Traffic Stress (LTS) for Bicyclists for Intersections with Arterial or Collector Roadway Int_Class: Highest level of Roadway Functional Class (MPO) for intersection.A: ArterialC: CollectorL: LocalIntControl: Traffic Control at IntersectionSTA: Stop (All Way) . All approaches have a stop sign. STM: Stop (Multi) Locations that have more than 2 approaches with stops, but not all are stop controlled. 3-way stops are considered Multi.ST: Stop. One street has stop signs, while the other has no control. 3-way stops are considered Multi.YD: Yield. Any non-roundabout intersection with a yield sign.YDR: Yield (Round) . Roundabouts with yield signs.NO: No Control. No control identifiedU: Unknown. Unable to identifySL: Signal. Signal for any direction.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Average weekday traffic counts (AWT) are collected at count stations throughout the city and represent the daily average for Monday-Friday traffic volume. Count stations in the eastern section of the city are collected in even numbered years, while those in the city's western section are collected in odd numbered years. Field descriptions/definitions for traffic count data as follows: ObjectID: GIS auto-generated unique identifiermslink: mslink of street segmentsegment_na: street segment nameSTATION: count station numberSOURCE: designates segment with counter or linkedSTATION: volume count station numberSOURCE: volume count station or linked segmentAWT_Count: most recent average weekday traffic countAWT_Yr: year of most recent countShape: GIS geometry typeYear_Txt: year of most recent count (text field)Shape.STLength(): GIS calculated segment length