The data set includes specifications about street signs in the City of Champaign. The data set covers signs owned by the city, IDOT, Champaign township, small selection of private street name signs and MTD.

Please click here to view the Data Dictionary, a description of the fields in this table.Feature layer depicting street signs within the City of Scottsdale.

Includes signs installed and maintained by the Seattle Department of Transportation within the public right of way. | Attribute Information: https://www.seattle.gov/Documents/Departments/SDOT/GIS/Street_Signs_OD.pdf | Data Confidence: Medium | Data Confidence Source: 2015 SDOT Asset Management, Status and Condition Report | Update Cycle: Weekly| Contact Email: DOT_IT_GIS@seattle.gov --- Signs by Category (Common SDOT queries of signs and data downloads) | Regulatory Sign Data: CATEGORY LIKE 'REG%'| No Parking Sign Data: CATEGORY IN ('PNP', 'PNS','PPEAK')| Parking Regulatory Sign Data: CATEGORY IN ('P1530','P1H','PPP','PR','PRZ','PTIML','PINST','PCARPL')| Parking Zones Sign Data: CATEGORY IN ('PBLO','PBZ','PCVL','PDIS','PLU','PPL','PSCH','PTRKL','PZONE')| Street Name Sign Data: CATEGORY = 'SNS'| Pay Station Sign Data:CATEGORY = 'PS'| Guide-Bike/Ped Sign Data: CATEGORY = 'GBP'| Guide Sign Data: CATEGORY = 'GUIDE'| Warning Crosswalk Sign Data: CATEGORY = 'WARNCW'| Information Sign Data: CATEGORY = 'INFOR'

Point geometry with attributes displaying the location of Manual on Uniform Traffic Control Devices (MUTCD) street sign locations in East Baton Rouge Parish, Louisiana. The data is derived from a 2012 field survey conducted by Fugro as part of a contract with the Louisiana Department of Transportation and Development. Metadata

The City of Seattle Transportation GIS Datasets | https://data-seattlecitygis.opendata.arcgis.com/datasets?t=transportation | Lifecycle status: Production | Purpose: to enable open access to SDOT GIS data. This website includes over 60 transportation-related GIS datasets from categories such as parking, transit, pedestrian, bicycle, and roadway assets. | PDDL: https://opendatacommons.org/licenses/pddl/ | The City of Seattle makes no representation or warranty as to its accuracy. The City of Seattle has created this service for our GIS Open Data website. We do reserve the right to alter, suspend, re-host, or retire this service at any time and without notice. | Datasets: 2007 Traffic Flow Counts, 2008 Traffic Flow Counts, 2009 Traffic Flow Counts, 2010 Traffic Flow Counts, 2011 Traffic Flow Counts, 2012 Traffic Flow Counts, 2013 Traffic Flow Counts, 2014 Traffic Flow Counts, 2015 Traffic Flow Counts, 2016 Traffic Flow Counts, 2017 Traffic Flow Counts, 2018 Traffic Flow Counts, Areaways, Bike Racks, Blockface, Bridges, Channelization File Geodatabase, Collisions, Crash Cushions, Curb Ramps, dotMaps Active Projects, Dynamic Message Signs, Existing Bike Facilities, Freight Network, Greater Downtown Alleys, Guardrails, High Impact Areas, Intersections, Marked Crosswalks, One-Way Streets, Paid Area Curbspaces, Pavement Moratoriums, Pay Stations, Peak Hour Parking Restrictions, Planned Bike Facilities, Public Garages or Parking Lots, Radar Speed Signs, Restricted Parking Zone (RPZ) Program, Retaining Walls, SDOT Capital Projects Input, Seattle On Street Paid Parking-Daytime Rates, Seattle On Street Paid Parking-Evening Rates, Seattle On Street Paid Parking-Morning Rates, Seattle Streets, SidewalkObservations, Sidewalks, Snow Ice Routes, Stairways, Street Design Concept Plans, Street Ends (Shoreline), Street Furnishings, Street Signs, Street Use Permits Use Addresses, Streetcar Lines, Streetcar Stations, Traffic Beacons, Traffic Cameras, Traffic Circles, Traffic Detectors, Traffic Lanes, Traffic Signals, Transit Classification, Trees.

Web map displaying street lights and Manual of Uniform Traffic Control Devices (MUTCD) in East Baton Rouge Parish, Louisiana. The source data was collected by Fugro in 2012.

This dataset will be moving! The City is working on a new Open Data Portal for GIS data. This dataset will soon be available at https://data-seattlecitygis.opendata.arcgis.com/. We apologize for any inconvenience, but this new platform will allow us to regularly update our data and provided better tools for our spatial data. https://gisrevprxy.seattle.gov/arcgis/rest/services/SDOT_EXT/DSG_datasharing/MapServer/26

Traffic sign inventory.

Esri AGOL Hosted View Feature Layer which provides access to the MDOT SHA Scenic Byways Sign Inventory.MDOT SHA Scenic Byways Sign Inventory data consists of point geometric features which represent the geographic locations of scenic byways signs along MDOT SHA-maintained roadways throughout the State of Maryland. 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).Last Updated: 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 Geospatial Technologies:Email: GIS@mdot.maryland.gov

Esri AGOL Hosted Feature Layer view which provides access to the MDOT SHA Roadway Sign Inventory (Lane Reduction Signage) data. This is a subset of the MDOT SHA Roadway Sign Inventory.MDOT SHA Roadway Sign Inventory data consists of point geometric features which represent the geographic locations of signs along MDOT SHA maintained roadways throughout the State of Maryland. 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).Last Updated: 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 Geospatial Technologies:GIS@mdot.maryland.gov

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

This Functional Classification dataset was exported from Caltrans Linear Reference System (LRS) on July 3rd, 2024. The LRS serves as the framework upon which the Highway Performance Monitoring System (HPMS) and other business data are managed.

Road Centerline GIS Data exported from the CIty's GIS. See summary description (txt) file for information about intended use, projection, currency, attributes, etc.

This map data layer represents the centerline of roadways for the City of Bloomington, Indiana. It includes source data from the City of Bloomington and Monroe County to create a countywide network. It includes public roads, named private roads, major multi-use trails, and proposed roadways to be constructed. Centerlines outside the City's mapped area may not be positioned accurately.

Traffic signs are placed to provide roadway users information. They include things such as stop, yield, street names and specialty signs, such as adopt-a-road signs.

Overview

This dataset contains all DOMI Street Closure Permit data in the Computronix (CX) system from the date of its adoption (in May 2020) until the present. The data in each record can be used to determine when street closures are occurring, who is requesting these closures, why the closure is being requested, and for mapping the closures themselves. It is updated hourly (as of March 2024).

Preprocessing/Formatting

It is important to distinguish between a permit, a permit's street closure(s), and the roadway segments that are referenced to that closure(s).

• The CX system identifies a street in segments of roadway. (As an example, the CX system could divide Maple Street into multiple segments.)

• A single street closure may span multiple segments of a street.

• The street closure permit refers to all the component line segments.

• A permit may have multiple streets which are closed. Street closure permits often reference many segments of roadway.

The roadway_id field is a unique GIS line segment representing the aforementioned segments of road. The roadway_id values are assigned internally by the CX system and are unlikely to be known by the permit applicant. A section of roadway may have multiple permits issued over its lifespan. Therefore, a given roadway_id value may appear in multiple permits.

The field closure_id represents a unique ID for each closure, and permit_id uniquely identifies each permit. This is in contrast to the aforementioned roadway_id field which, again, is a unique ID only for the roadway segments.

City teams that use this data requested that each segment of each street closure permit be represented as a unique row in the dataset. Thus, a street closure permit that refers to three segments of roadway would be represented as three rows in the table. Aside from the roadway_id field, most other data from that permit pertains equally to those three rows. Thus, the values in most fields of the three records are identical.

Each row has the fields segment_num and total_segments which detail the relationship of each record, and its corresponding permit, according to street segment. The above example produced three records for a single permit. In this case, total_segments would equal 3 for each record. Each of those records would have a unique value between 1 and 3.

The geometry field consists of string values of lat/long coordinates, which can be used to map the street segments.

All string text (most fields) were converted to UPPERCASE data. Most of the data are manually entered and often contain non-uniform formatting. While several solutions for cleaning the data exist, text were transformed to UPPERCASE to provide some degree of regularization. Beyond that, it is recommended that the user carefully think through cleaning any unstructured data, as there are many nuances to consider. Future improvements to this ETL pipeline may approach this problem with a more sophisticated technique.

Known Uses

These data are used by DOMI to track the status of street closures (and associated permits).

Further Documentation and Resources

An archived dataset containing historical street closure records (from before May of 2020) for the City of Pittsburgh may be found here: https://data.wprdc.org/dataset/right-of-way-permits

Public Works roadway, paving plan, status, work order information and asset history, street lights, by owner and type, and other infrastructure information. Version 2.0

Geospatial data about City of Detroit, Michigan Traffic Signs. Export to CAD, GIS, PDF, CSV and access via API.

Road edges are defined as the edge of the improved surface including the improved shoulder but do not include the unimproved shoulder, only the travel part of the road. The road network is compiled to include all open intersections. Features do not overlap sidewalks, but have the sidewalk area cut out of the road polygons. Overlapping features are acceptable if one of the features is hidden. Road: A generally named thoroughfare, that is usually paved and can be public or private. Unimproved thoroughfares are excluded. Road polygons are formed by a combination of road edge, curb, sidewalk, street intersection closure line, and map sheet edge. Paved Median Island: Perimeter of non-traffic paved areas that separate traffic lanes in opposing directions. Unpaved Median Island: Perimeter of non-traffic grassy, unpaved areas that separate traffic lanes in opposing directions. Paved Traffic Island: Perimeter of non-traffic concrete areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Unpaved Traffic Island: Perimeter of non-traffic unpaved, grassy areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Alley: Perimeter of alleys first plotted photogrammetrically from other indicators such as building footprints, fence lines, curb lines, walls, paved or unpaved drives, and map sheet edge. Alley polygons are closed along the lines where they intersect with road polygons. Paved Drive: A paved driveway for a building or entranceway for a parking lot. Driveways are neither streets nor alleys, but provide access to public facilities, such as a drive to a monument, museum, hotel, large estate, sports field or golf course, grounds of the U.S. Capitol, etc. If a driveway is less than 200 feet and leads to a parking lot, the entire paved area is captured as Parking Lot. Driveways are photogrammetrically compiled as polygons and not compiled from individual vectors on different levels. Parking Lot: Generally paved surfaces used for cars to park on. Paved drives usually form entrances to these features, if the drive is more than 200 feet. If the driveway is less than 200 feet leading into the parking lot, the entire paved area is captured as Parking Lot. Parking lots sharing a common boundary with linear features must have the common segment captured once, but coded as both polygon and line. Small parking areas, where individuals park their cars in the middle of a block off a public alley, are not captured as parking lots. These are either public space (e.g., alleys) or private space where owners permit parking to occur. Intersection: A location where more than one road comes together. For standard cross streets, intersection polygons are bounded by curbs and four closure lines at street intersection crosswalks (outer line) or placed arbitrarily where crosswalks could logically be placed. For "T" intersections, the polygons are bounded by curbs and three such closure lines. Complex intersections can have more closure lines. Entire traffic circles are coded as intersections. Hidden Road: A section of a road that passes underneath a bridge or overpass and is not visible in an aerial photograph, but the location can be interpreted based on the road on either side of the bridge. Hidden Median: A road median that exists underneath a bridge or overpass and is not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge.

Roads data are intended to be used for a variety of mapping, resource management, planning, and analysis applications.

Amherst Street Centerlines