ArcGIS REST Services Directory Login | Get Token
Home > services > Traffic > traffic (FeatureServer) > MTA.DPH_veh_hin_archive API Reference
JSON

Layer: MTA.DPH_veh_hin_archive (ID: 4)

View In:   ArcGIS Online Map Viewer

Name: MTA.DPH_veh_hin_archive

Display Field: STREET_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: | A. PURPOSE | This data was created by the San Francisco Department of Public Health to identify street segments and intersections in San Francisco that have a high number of vehicle fatalities and severe injuries. As of 2014, this network is being used to inform Vision Zero.| B. METHODOLOGY | The vehicle high injury corridors used data for 2008-2012 (the most recent annual data available) from the Statewide Integrated Traffic Records System (SWITRS), managed by the California Highway Patrol, for this analysis. This included a total of 16,271 vehicle injuries including 537 of which were severe and 75 fatalities. Of those injuries, 12,551 were determined to have happened on a city street (not a freeway) and geocodable to the nearest intersection including 440 severe (97 not geocoded to city street) and 50 fatalities (25 not geocoded to city street). Freeway injuries were determined using a combination of the primary street, police jurisdiction, and geocoded location. For this analysis, weighted severe and fatal injuries – a focus of Vision Zero prevention efforts and consistent with previous San Francisco studies , - by multiplying those counts times 3 while complaints of pain and visible injury were assigned a count of 1.ArcGIS mapping software was used to map vehicle injury counts to street segments by aggregating weighted injury counts at intersections (initially assigned to intersections based on primary and secondary streets in SWITRS) and then assigned them to their adjoining street segments. (Note that this approach results in injuries being counted on each of the streets that intersect at that intersection.) The total number of weighted collisions from all adjoining intersections was summed for each street segment.Potential high injury density corridors, which were defined by first identifying street segments with the top 30th percentile of injuries per mile selected and then assessing whether there was a linear pattern of higher injury counts proximate to those segments and following the street network to identify high injury corridors were identified. The strength of this corridor approach is that it can be used to inform targeted interventions to factors common along a corridor contributing to higher numbers of injuries, while accounting for some of the year-to-year random variability in injury occurrence at specific locations. The initial cut-point of the top 30th percentile of injuries per mile based on the distribution of the data was used.| C. UPDATE FREQUENCY | This dataset will be updated in 2015/16 using 2009-2013 injury when available from SWITRS. This update schedule is tentative and pending approval from the MTA/DPH. Please contact Devan Morris (devan.morris@sfdph.org) to inquire about the latest vehicle high injury network.| D. OTHER CRITICAL INFO | This is one of three networks that make up the Vision Zero High Injury Network. All injury data was geocoded to the nearest intersection for this analysis and available on www.transbasesf.org. A complete methodology will be available here in Summer 2015: http://bit.ly/1QQxU79.| E. ATTRIBUTES |OBJECTID: Unique record identifier;geom: PostGIS/ArcGIS geometry identifier;cnn_sgmt_pkey: This attribute is the same as Centerline Network Number Unique ID (CNN) found in other road network feature classes throughout the city;street_name: Street name excluding prefix and suffix;street_type: Street suffix;street_layer: SFDPW street classification;full_street_name: Full street name including suffix;class_code: Class code used for symbolizing;gis_length_miles: Street length representing duel carriage ways as one street segment instead of two;duel_car_way_yn: Street is represented as a duel carriage way;duel_car_way_id: Unique ID assigned for each side of a duel carriage way;corrected_length_miles: Street length representing duel carriage ways as one street segment instead of two;f_node_cnn_intrsctn_fkey: Unique intersection ID at start of street segment;t_node_cnn_intrsctn_fkey: Unique intersection ID at end of street segment;shape_length: Object length created by ArcGIS;sgmt_veh_hgh_injry_crrdr_pkey: Unique identifier used by TransBASE;vhic_code: Unique code created for each vehicle high injury corridor;vhic_name: Name of each vehicle high injury corridor;cross_street_1: Starting cross street for vehicle high injury corridor;cross_street_2: Ending cross street for vehicle high injury corridor;geom_Length: Object length created by ArcGIS

Copyright Text: | A. CUSTODIAN | Devan Morris, devan.morris@sfdph.org, Population Health, San Francisco Department of Public Health; Megan Wier, megan.wier@sfdph.org, Population Health, San Francisco Department of Public Health | B. CREATED | 20141114 | C. VERSIONS | 20141114, Devan Morris/Megan Wier (Department of Public Health), original release

Default Visibility: false

MaxRecordCount: 10000

MaxSelectionCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields: Templates:
Capabilities: Query

Sync Can Return Changes: false

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Edit Fields Info:
Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:

Supported Operations:   Query   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata   Update Metadata