Name: Safety Pedestrian Segment
Display Field: ROUTE_NAME_PRIMARY
Type: Feature Layer
Geometry Type: esriGeometryPolyline
Is View: true
Is Updatable View: true
Source Schema Changes Allowed: true
Sources
Description: <div style="text-align:Left;"><div><div><p><span style="font-weight:bold;">General Description of Systemic Safety Analysis</span></p><p><span>The systemic safety approach “involves widely implemented improvements based on high-risk roadway features correlated with specific severe crash types. The approach provides a more comprehensive method for safety planning and implementation that supplements and complements traditional site analysis.” The systemic approach gives agencies another tool to address safety by allowing them to consider the risk of a site instead of its crash history. The general attributes of a systemic safety analysis include:</span></p><p><span style="font-weight:bold;">Identifying focus crash types and risk factors</span></p><ul><li><p><span>Agencies need to identify a crash type to focus on, based on either statewide data or on an area identified in prior planning activities such as the </span><span>State Strategic Highway Safety Plan (SHSP)</span><span>. Often the crashes associated with a focused crash types are randomly distributed across a network with few locations experiencing a cluster of crashes. For this analysis the focus was on bicyclist and pedestrian involved crashes.</span></p></li><li><p><span style="font-weight:bold;">Defining risk factors</span></p></li><li><p><span>After identifying a focus crash type, agencies associate those crashes with roadway or intersection characteristics. This association helps identify roadway characteristics that are correlated with a higher frequency or rate of that crash type. These characteristics, also known as risk factors, can be used to identify and prioritize similar locations where no crash history currently exists. </span></p></li><li><p><span style="font-weight:bold;">Screening and prioritizing the network</span></p></li><li><p><span>Risk factors (or roadway characteristics) are typically scored and weighted by agencies. This process of prioritizing characteristics allows agencies to take that information in combination and find areas within their roadway network that have higher concentrations of risk factors.</span></p></li><li><p><span>The resulting analysis identified roadways and intersections that have the greatest risk, regardless of existing crash history at those locations. Agencies can use this information to help select appropriate countermeasures and prioritize projects. </span></p></li></ul><p><span style="font-weight:bold;">Data Used in this analysis</span></p><ul><li><p><span style="font-weight:bold;">Crash Data</span></p></li></ul><ul><li><p><span>Ten years of crash data from 2009-2018 was used in this analysis. Only non-motorists crashes involving pedestrians, skaters, those using a personal conveyance, wheelchair occupants, bicyclists, and bicycle passengers were included in the analysis. Data as accessed July 8th, 2019. </span></p></li></ul><ul><li><p><span style="font-weight:bold;">Roadway data and Jurisdictional data</span></p></li></ul><ul><li><p><span>Roadway data was extracted from the Road Asset Management System (RAMS). The analysis included all paved roads within the state. Attributes included in the dynamic segmentation included number of lanes, average annual daily traffic (AADT), route name, shoulder width, shoulder type, shoulder rumble, speed limit, parking type, and median type. Jurisdictional data was also spatially joined to all the segments in the analysis including city, county, Regional Planning Agency (RPA), and Metropolitan Planning Organization (MPO). Roadways with minimum speed limits were eliminated from this analysis because pedestrian and bicyclist are prohibited from using facilities with minimum speed limits. The most recent access of this data was from September 20th, 2019. </span></p></li></ul><p style="margin:0 0 14 0;"><span style="font-weight:bold;">Feature Class Description</span></p><p style="margin:0 0 14 0;"><span>The roadway segment data contained in this feature class includes all of the paved roadways within the state of Iowa. Each segment has been analyzed according to the general process described above and for this particular feature class the focus was on pedestrians. The primary output of this analysis was a composite score from 0-100 for each roadway segment. This score indicates the relative risk of the segment as it relates to the attributes used in this analysis. The lower the composite score the higher the risk. Higher composite score rankings suggest less risk at those sites. For rural pedestrian segments the minimum composite score was 24, the max was 100, and the average was 79.2. For the urban pedestrian score the minimum composite score was 17.5, the maximum 95, and the average was 60.3.</span></p><p><span></span></p></div></div></div>
Copyright Text: Iowa Department of Transportation - Systems Planning Bureau
Min. Scale: 1000000
Max. Scale: 0
Default Visibility: true
Max Record Count: 2000
Supported query Formats: JSON, geoJSON, PBF
Use Standardized Queries: True
Extent:
XMin: -10757094.9899925
YMin: 4922054.2046775
XMax: -10036667.4266375
YMax: 5388546.4324325
Spatial Reference: 102100 (3857)
Drawing Info:
{"renderer":{"type":"simple","symbol":{"type":"esriSLS","style":"esriSLSSolid","color":[0,92,230,255],"width":1}},"scaleSymbols":true,"transparency":0,"labelingInfo":null}
HasZ: true
HasM: true
Has Attachments: false
Has Geometry Properties: true
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Object ID Field: OBJECTID
Unique ID Field:
IsSystemMaintained : True
Global ID Field: GLOBALID
Type ID Field:
Fields:
- OBJECTID (type: esriFieldTypeOID, alias: OBJECTID, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false)
- ROUTEID (type: esriFieldTypeString, alias: ROUTE ID, SQL Type: sqlTypeOther, length: 15, nullable: true, editable: true)
- ROUTE_NAME_PRIMARY (type: esriFieldTypeString, alias: PRIMARY ROUTE NAME, SQL Type: sqlTypeOther, length: 254, nullable: true, editable: true)
- ROUTE_NAME_COUNTY (type: esriFieldTypeString, alias: COUNTY ROUTE NAME, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
- ROUTE_NAME_SECONDARY (type: esriFieldTypeString, alias: SECONDARY ROUTE NAME, SQL Type: sqlTypeOther, length: 254, nullable: true, editable: true)
- ROUTE_NAME_LOCAL (type: esriFieldTypeString, alias: LOCAL ROUTE NAME, SQL Type: sqlTypeOther, length: 254, nullable: true, editable: true)
- OWNER_CODE (type: esriFieldTypeInteger, alias: ROADWAY OWNERSHIP, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [1: STATE HIGHWAY AGENCY], [2: COUNTY HIGHWAY AGENCY], [3: TOWN OR TOWNSHIP HIGHWAY AGENCY], ... 25 more ...)
- INCORPORATED (type: esriFieldTypeInteger, alias: WITHIN INCORPORATED BOUNDARY, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [0: Yes], [1: No])
- CITY_NUMBER (type: esriFieldTypeInteger, alias: City Number, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [22: Adair], [837: Bridgewater], [1152: Casey], ... 948 more ...)
- COUNTY_NUMBER (type: esriFieldTypeInteger, alias: County Number, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [1: Adair], [2: Adams], [3: Allamakee], ... 96 more ...)
- MPO_NUMBER (type: esriFieldTypeInteger, alias: MPO Number, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [0: N/A], [1: Ames Area Metropolitan Planning Organization (AAMPO)], [2: Corridor Metropolitan Planning Organization (CMPO)], ... 7 more ...)
- RPA_NUMBER (type: esriFieldTypeInteger, alias: RPA Number, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [1: Upper Explorerland Regional Planning Commission (UERPC)], [2: North Iowa Area Council of Governments (NIACOG)], [3: Northwest Iowa Planning and Development Commision (NWIPDC)], ... 15 more ...)
- RIGHT_SHOULDER_TYPE (type: esriFieldTypeInteger, alias: SHOULDER TYPE, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [1: 1 - EARTH], [2: 2 - GRAVEL], [6: 6 - PAVED], ... 3 more ...)
- RIGHT_SHOULDER_WIDTH (type: esriFieldTypeInteger, alias: SHOULDER WIDTH, SQL Type: sqlTypeOther, nullable: true, editable: true)
- RIGHT_SHOULDER_RUMBLE (type: esriFieldTypeInteger, alias: SHOULDER RUMBLE, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [0: Yes], [1: No])
- MEDIAN_TYPE (type: esriFieldTypeInteger, alias: MEDIAN TYPE, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [1: 1 - HARD SURFACE WITHOUT BARRIER (RAISED MEDIAN)], [2: 2 - GRASS SURFACE WITHOUT BARRIER], [3: 3 - HARD SURFACE WITH BARRIER], ... 2 more ...)
- PARKING_TYPE (type: esriFieldTypeInteger, alias: PARKING TYPE, SQL Type: sqlTypeOther, nullable: true, editable: true, Coded Values: [1: NO PARKING IS POSTED], [2: PARALLEL ONE SIDE - NO PARKING OTHER SIDE], [3: PARALLEL ONE SIDE - DIAGONAL OTHER SIDE], ... 6 more ...)
- NUMBER_LANES (type: esriFieldTypeInteger, alias: NUMBER OF LANES, SQL Type: sqlTypeOther, nullable: true, editable: true)
- SPEED_LIMIT (type: esriFieldTypeInteger, alias: SPEED LIMIT, SQL Type: sqlTypeOther, nullable: true, editable: true)
- AADT (type: esriFieldTypeInteger, alias: AADT, SQL Type: sqlTypeOther, nullable: true, editable: true)
- UPS_COMP_SCORE (type: esriFieldTypeDouble, alias: URBAN PEDESTRIAN COMPOSITE SCORE, SQL Type: sqlTypeOther, nullable: true, editable: true)
- RPS_COMP_SCORE (type: esriFieldTypeDouble, alias: Rural Pedestrian Composite Score, SQL Type: sqlTypeOther, nullable: true, editable: true)
- REST_UPDATED (type: esriFieldTypeDate, alias: Rest Service Last Updated (UTC), SQL Type: sqlTypeOther, length: 8, nullable: true, editable: false)
- REST_UTC_OFFSET (type: esriFieldTypeString, alias: REST UTC Offset, SQL Type: sqlTypeOther, length: 6, nullable: true, editable: true)
- LENGTH_MILE (type: esriFieldTypeDouble, alias: Length (Mile - State Plane), SQL Type: sqlTypeOther, nullable: true, editable: true)
- GLOBALID (type: esriFieldTypeGlobalID, alias: GLOBALID, SQL Type: sqlTypeOther, length: 38, nullable: false, editable: false)
- Shape__Length (type: esriFieldTypeDouble, alias: Shape__Length, SQL Type: sqlTypeDouble, nullable: true, editable: false)
Templates:
Name: Safety Pedestrian Segment
Description:
Drawing Tool: esriFeatureEditToolLine
Prototype:
Is Data Versioned: false
Has Contingent Values: false
Supports Rollback On Failure Parameter: true
Last Edit Date: 11/3/2020 8:04:15 PM
Schema Last Edit Date: 11/3/2020 8:03:27 PM
Data Last Edit Date: 11/3/2020 8:03:27 PM
Supported Operations:
Query
Query Pivot
Query Top Features
Query Analytic
Query Bins
Generate Renderer
Validate SQL
Get Estimates
ConvertFormat