Description: | A. PURPOSE | To identify the location and clearance heights for large vehicle circulation in the City.| B. METHODOLOGY | Manual updates| C. UPDATE FREQUENCY | once or twice per year.| D. OTHER CRITICAL INFO | None| E. ATTRIBUTES |Type: Overpass, Pedestrian bridge, Tunnel, Railroad;Height: Clearance height of that location
Copyright Text: | A. CUSTODIAN | Tamam Abdallah, tamam.abdallah@sfmta.com, Transportation Engineering Traffic Operations Section, SFMTA
| B. CREATED | 20150502, unknown
| C. VERSIONS |
20150527, updated by Tamam Abdallah
Description: | A. PURPOSE | Statewide Integrated Traffic Records System (SWITRS) is a database that serves as a means to collect and process data gathered from a collision scene. http://iswitrs.chp.ca.gov/Reports/jsp/userLogin.jsp. SFPD (SF Police Department) also reports collision data, although the geocoding accuracy rate is lower for SFPD data.| B. METHODOLOGY | -- imported from SWITRS| C. UPDATE FREQUENCY | Quarterly, approximately. However, there is a one year lag with SWITRS data availability.| D. OTHER CRITICAL INFO | Geocoding accuracy rate for 2013-14 SFPD data was at 75%.| E. ATTRIBUTES | http://ds.civicknowledge.org.s3.amazonaws.com/iswitrs.chp.ca.gov/SWITRS%20Data%20Dictionary.pdf
Copyright Text: | A. CUSTODIAN | James Shahamiri, james.shahamiri@sfmta.com, Transportation Engineering, SFMTA.
| B. CREATED | 20150201
| C. VERSIONS |
201605, James Shahamiri, regular updates as data become available
20150201, James Shahamiri, regular updates as data become available
Description: | A. PURPOSE | Centerline shapefile of San Francisco's streets and number of lanes by time of day. | B. METHODOLOGY | This shapefile is derived from data initially provided by the San Francisco County Transportation Authority (SFCTA) in 2010 from their travel forecasting model (SF-CHAMP 4). In 2010-2011, the San Francisco Department of Public Health’s Program on Health, Equity and Sustainability (SFDPH-PHES) developed a methodology to convert the SFCTA travel forecasting model data outputs so they could be joined to the CNN (Centerline Network Number) street format (the unique identifier used for street segments in San Francisco), resulting in the data included in this shapefile. More detailed information regarding this approach is available upon request.| C. UPDATE FREQUENCY | Unknown. | D. OTHER CRITICAL INFO | Previously found at \\mtanas\T_E_DATA\GIS\SF Shapefiles\DPH Number Traffic Lanes\Streets_Vehicle_Traffic_TA_Lanes.shp. Some of the streets were originally coded in the SFCTA data as having “0” lanes, and remain as such. 1.6% of the zero-lane roads are in the Presidio neighborhood and 0.4% are in the new Mission Bay neighborhood. The remaining 1.5% of roads coded as having zero lanes appear to be sporadic around the city and based on visual inspection are largely a mix of parking lot, driveway, dead ends, alleys, private, and newly-constructed roads. All attributes are from the street centerlines feature class except those listed below.| E. ATTRIBUTES |Lane_AM: number of auto lanes during AM Peak hours;Lane_OP: number of auto lanes during non-peak hours;Lane_PM: number of auto lanes during PM peak hours.
Copyright Text: | A. CUSTODIAN | SFCTA
| B. CREATED | San Francisco County Transportation Authority (SFCTA), 2010. San Francisco Department of Public Health-Program on Health, Equity and Sustainability (SFDPH-PHES), 2011. | C. VERSIONS | 20160923, Steph A. Nelson imported into MTA spatial data store and re-formatted metadata.
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
Description: | A. PURPOSE | Indicates locations of one way streets.| B. METHODOLOGY | Extracted from street centerlines and modified.| C. UPDATE FREQUENCY | No current update schedule. In need of verification and updatees.| D. OTHER CRITICAL INFO | This feature class is not 100% accurate, and it is in need of verification and updates. It was previously found at \\mtanas\T_E_DATA\GIS\Traffic Shapefiles\One Way Streets\sfclines_Oneway.shp. All attributes appear to be pulled from street centerline data except for the ONEWAY field, which is identified below.| E. ATTRIBUTES |ONEWAY: Indicated by a -1 or a 1. Values do not consistently reflect directionality.
Copyright Text: | A. CUSTODIAN | Carleton Wong, carleton.wong@sfmta.com, Traffic Engineering, SFMTA
| B. CREATED | unknown
| C. VERSIONS |
20160923, Steph A. Nelson, MTA spatial data store (imported and added metadata)
Description: | A. PURPOSE | This dataset serves as an inventory of traffic signal and related equipment.| B. METHODOLOGY | N/A| C. UPDATE FREQUENCY | Signals Access database updated regularly (weekly, or quarterly) based on SRC work orders returned to date. GIS file updated quarterly. | D. OTHER CRITICAL INFO | Attribute data primarily maintained in the Access database. Spatial data exports are sourced from the Access database. To query for TSP (Transit Signal Prioritization), load this query into the "Definition Query" tab under Properties: \\mtanas\sfmtagis\04_GeoTools\Queries\TSP.exp| E. ATTRIBUTES |CNN: San Francisco’s street centerline network unique ID If there is more than one type of equipment at an intersection or mid-block segment, the unique ID will be based on the CNN plus 1 or 2;STREET1: Cross street #1;STREET2: Cross street #2;STREET3: Cross street #3;STREET4: Cross street #4;SUP_DIST: Supervisorial district(s);SIG_NUM: Maintenance field for Traffic Signal Shop;TYPE: Type of equipment present at this location--SIGNAL-Traffic signal,FLASHER- Traffic signal that is always on flashing mode,BEACON-Flashing yellow warning light,PENDING- Pending signal location, programmed and/or under construction,FUTURE- Candidate intersection for new signals contract, not yet funded,CALTRANS- Traffic Signal maintained and operated by the State,Others- DALY CITY, LIGHTED CROSSWALK, MESSAGE SIGN, LANE CONTROL, MASTER, NEW BEACON;IC_MAKE: Manufacturer of traffic signal controller;MODEL: Model of traffic signal controller;CABINET_SI: Size and type of traffic signal controller cabinet;SYSTEM_NUM: Number indicating to which system a signal belongs;MASTER: Identifies location of system master or TBC system reference intersection;BBS: Indicates presence of battery backup system (BBS);VEH_ACTUATED: Indicates presence and type of vehicle detection;PED_SIGNAL: Indicates presence of pedestrian signals--ALL- Pedestrian signals for all open crosswalks,SOME PHASES- pedestrian signals only across some crosswalks,NONE- no pedestrian signals for any crosswalks,PENDING- pending additional pedestrian signals to be installed as part of a signal project (upgrade, modification, or new signals) which is under design or construction and not yet completed;APS: Indicates presence and model of accessible pedestrian signal (APS) push buttons as well as which project the APS units were installed by;PED_ACTUATED: “YES” if intersection is pedestrian actuated either by conventional push buttons or by buttons integrated in APS units;MANUAL_CONTROL: Unknown field;TBC: Indicates presence and type of time based clock (TBC);INTERCONNECT: Type of traffic signal interconnect used for coordination;PREEMPT_PR: Indicates presence and order of priority of traffic signal preempts, including TSP (Transit Signal Prioritization);DETECTION: Type of detection used to activate traffic signal preempt;D_ATE2070: Date when traffic signal controller was upgraded to type 2070;PROJECT_NEW: Most recent project (new signals, modifications, or full upgrade) planned, pending, or under construction;PROJECT_OLD: Previous signal contract (new signals, modifications, or full upgrade) which has already been completed;YR_OF_CONTRACT: Approximate date of UPGRADED contract certification;LAST_UPGRADE: Year intersection was last upgraded (since 1990);NEW_SIGNALS: Field indicates project status for new signals project--FUTURE-Candidate intersection for new signals project, not yet funded,PENDING- Intersection under design or construction as part of new signals project, not yet completed,DONE- Construction at intersection as part of new signals project has been completed. Please note that only intersections included as part of contracts completed after 1990 are noted as “DONE”,NONE- No new signals project planned; MOD _PROJECT: Field indicates project status for signal modifications project--FUTURE- Candidate intersection for signal modifications project, not yet funded,PENDING- Intersection under design or construction as part of signal modifications project, not yet completed,DONE- Construction at intersection as part of signal modifications project has been completed. Please note that only intersections included as part of contracts completed after 1990 are noted as “DONE”,NONE- No signal modifications project planned;FULL_UPGRADE _PROJECT: Field indicates project status for full upgrade project--FUTURE- Candidate intersection for full upgrade project, not yet funded,PENDING- Intersection under design or construction as part of full upgrade project, not yet completed,DONE- Construction at intersection as part of full upgrade project has been completed. Please note that only intersections included as part of contracts completed after 1990 are noted as “DONE”, NONE- No full upgrade project planned; BEACON_FLASHER: Field indicates project status for installation of beacons and flashers--FUTURE- Candidate intersection for beacon and flashers contract, not yet funded,PENDING- Intersection under design or construction as part of beacon and flashers contract, not yet completed,DONE- Construction at intersection as part of beacon and flashers contract has been completed. Please note that only intersections included as part of contracts completed after 1990 are noted as “DONE”,NONE- No beacon and flashers contract planned;FUNDING: Source of funds used to pay for signal contract;RLCAM: “YES” if intersection has red light camera system;STARTYEAR: Year equipment (traffic signal) began operation if known;CALTRANS_ROUTE: Caltrans highway route number if applicable; CALTRANS: “X” if signals are maintained in full or in part by Caltrans;PERCENT_C: Percent of maintenance paid by Caltrans;SF: “X” if signals are maintained in part by City of San Francisco;PERCENT_SF: Percent of maintenance paid by City of San Francisco;PERCENT_PORT: Percent of maintenance paid by Port of San Francisco;LAMP_ASSGN: Maintenance field for Traffic Signal Shop;LAMP_SORT: Maintenance field for Traffic Signal Shop;SORT_ME: Maintenance field for Traffic Signal Shop
Copyright Text: | A. CUSTODIAN | Jarrett Hornbostel, jarrett.hornbostel@sfmta.com, SFMTA, Sustainable Streets, Transportation Engineering
| B. CREATED | Unknown
| C. VERSIONS |
20161222, Jarrett Hornbostel, quarterly update
201605, Jarrett Hornbostel, quarterly update, prep for MTA spatial data store
20150611, Jarrett Hornbostel, quarterly update, prep for MTA spatial data store
Description: | A. PURPOSE | Location of "old style" speed bumps.| B. METHODOLOGY | Manually updated.Search "Speed bump" through Work Order Database and confirm work completed date.| C. UPDATE FREQUENCY | As needed| D. OTHER CRITICAL INFO | N/A| E. ATTRIBUTES | STREETNAME: Street name;FROM_ST: One end of the block;TO_ST: One end of the block;CNN: San Francisco's street centerline network unique ID
Copyright Text: | A. CUSTODIAN | Jen Wong, jennifer.wong@sfmta.com, Livable Streets, SFMTA
| B. CREATED |
| C. VERSIONS |
20160429, Jen Wong, deleted extraneous fields
20150618, Jen Wong, MTA spatial data store prep
Description: | A. PURPOSE | Speed limits are indicated primarily for streets that have speeds higher than 25 MPH. 25 MPH is the de facto speed limit for residential and most commercial streets. Alleys narrower than 25 feet can have de facto speed limits of 15 MPH. | B. METHODOLOGY | individual speed limit shapefiles manually updated by Tamam Abdallah (15 mph speed limits, and the rest of the city). This merged, citywide speedlimits dataset (MTA.speedlimits) managed by Dan Howard.| C. UPDATE FREQUENCY | Updated as changes are legislated, a few times a year.| D. OTHER CRITICAL INFO | Prior datasets located here\\mtanas\T_E_DATA\GIS\Traffic Shapefiles\Speed Limits\15MPH\ALL15mphstreetsUpdated.shp\\mtanas\T_E_DATA\GIS\Traffic Shapefiles\Speed Limits\speedlimits.shp| E. ATTRIBUTES |SPEEDLIMIT: Max speed limit for that street segment (values of 0 -- default speed limit of 25 mph)
Copyright Text: | A. CUSTODIAN | Dan Howard (merged speed limits dataset), dan.howard@sfmta.com, Transportation Engineering, SFMTA and Tamam Abdallah (individual 15mph & other speed limits shapefiles), tamam.abdallah@sfmta.com, Transportation Engineering Traffic Operations, SFMTA
| B. CREATED | 1998
| C. VERSIONS |
20160728, Tamam Addallah, added changes to segments of Leavenworth St, Folsom St, San Jose Ave, and Geary Blvd.
20150602, Steph Nelson, added 15 mph streets from 'ALL15mphstreetsUpdated.shp' to streets with or '0' in the "SPEEDLIMIT" field when migrating into the MTA spatial data store.
20140225 'ALL15mphstreetsUpdated.shp', Tamam Abdallah, updated to reflect changes in speed limits
20141106, Tamam Addallah, updated to reflect changs in speed limits
Description: | A. PURPOSE | to identify the location of stop signs for operational and planning purposes.| B. METHODOLOGY | Manually updated as MTAB resolutions are passed.| C. UPDATE FREQUENCY | Updated several times a year.| D. OTHER CRITICAL INFO | Prior dataset located at \\mtanas\T_E_DATA\GIS\Traffic Shapefiles\STOP_signs\Stop Sign Map- 2011\stops_signs.shp| E. ATTRIBUTES |Streets: main Corridor; X_Street: Interecting Streets; St_Facing:NB,SB,EB,WB,;CNN: Center Line Network Node;Direction: NE,SW,SE,NW
Copyright Text: | A. CUSTODIAN | Tamam Abdallah, tamam.abdallah@sfmta.com, Transportation Engineering, SFMTA
| B. CREATED | 20090716
| C. VERSIONS |
20150618, Steph A. Nelson, MTA spatial data store prep (added metadata with Tamam guidance)
20150319, Tamam Abdallah, updated per MTAB resolutions
Description: | A. PURPOSE | Location and attributes of streets with weight and/or interurban bus restrictions.| B. METHODOLOGY | Manual updates to individual restriction shapefiles completed by Tamam Abdallah. Merging of all restriction shapefiles into this parent shapefile complete periodically by Dan Howard. | C. UPDATE FREQUENCY | Updated infrequently, twice a year at most.| D. OTHER CRITICAL INFO | prior location of shapefiles at \\mtanas\T_E_DATA\GIS\Traffic Shapefiles\Restricted Traffic Streets\SHP\interurban bus restriction.shp\\mtanas\T_E_DATA\GIS\Traffic Shapefiles\Restricted Traffic Streets\SHP\weight restriction over 3 tons TC 28.shp\\mtanas\T_E_DATA\GIS\Traffic Shapefiles\Restricted Traffic Streets\SHP\weight restriction over 9 tons (tc 282).shp| E. ATTRIBUTES |RSTR_WEIGHT: Type of weight restriction, if applicable;RSTR_OTHER: Other restrictions such as interurban bus restriction
Copyright Text: | A. CUSTODIAN | Tamam Abdallah, tamam.abdallah@sfmta.com, Transportation Engineering, SFMTA
| B. CREATED | 20150617, Steph A. Nelson, MTA spatial data store prep (merged and added metadata)
| C. VERSIONS |
20131218, Tamam Abdallah, updates per MTAB resolutions
Description: | A. METHODOLOGY | The location of taxi stand is by street name and number with geolocation in latitude and longitude. | B. UPDATE FREQUENCY | SFMTA is continuing to solicit suggestions on where passengers, drivers, and businesses would like new taxi stands to be installed. The map will be updated whenever there is a change of taxi stands. | C. OTHER CRITICAL INFO | The map also displays temporarily removed taxi stands, which were removed or relocated due to construction or other long-term impacts, of which SFMTA intends to reinstall. The layer is turn off as default, viewer can turn it on in layer.| D. ATTRIBUTES |Active Taxi Stands: Taxi stands are in active status and the layer is on as defaultTemporaily Removed Taxi Stands: Taxi stands are in Temporaily Removed status, which were removed or relocated due to construction or other long-term impacts, of which SFMTA intends to reinstall.
Copyright Text: | A. CUSTODIAN | Geodata custodian: Mona Chiu, mona.chiu@sfmta.com, Taxis and Accessible Services Division, SFMTA
| B. CREATED | 2020 01 24, Mona Chiu
| C. VERSIONS | 2020 01 29, Mona Chiu
Description: | A. METHODOLOGY | Exported from the Street Closure Saleforce database which is maintained by the SFMTA ISCOTT unit, and converted to geometry of streets and intersections based on closed street extent description. | B. UPDATE FREQUENCY | Database is updated constantly. This report is issued daily/weekly/thrice weekly. | C. OTHER CRITICAL INFO | | D. ATTRIBUTES |CNN: CNN of street impacted by closure. CNN is San Francisco’s street centerline network unique ID.Case_number: case numberCase_name: case nameType: closure typeStatus: case statusDT_opened: date/time of case openedPolicyDist: policy districtPubhear: public hearing dateContact_Na: contact nameContact_Em: contact emailLocation: closure locationStreet: street impacted by closureX_Street1: crossed street 1 for the entire closureX_Street2: crossed street 2 for the entire closure Street_name: street impacted by closureFrom_st: crossed street 1 for the street segment impacted by closureTo_st: crossed street 1 for the street segment impacted by closureStart_date: start date of closure in date/time format (local time)End_date: end date of closure in date/time format (local time)Start_UTC: start date of closure in date/time format (UTC time)End_UTC: end date of closure in date/time format (UTC time)Event_Date: event details of start/end date, day of week, frequency, ect.Descriptio: comments by applicant
Copyright Text: | A. CUSTODIAN | Nick Chapman, nick.chapman@sfmta.com, SFMTA, Sustainable Streets, Transportation Engineering
| B. CREATED | 20200701, Muyi Zhou created the first version | C. VERSIONS |
20200701, Muyi Zhou, created with program applications
Description: | A. METHODOLOGY | Exported from the Street Closure Saleforce database which is maintained by the SFMTA ISCOTT unit, and converted to geometry of streets and intersections based on closed street extent description. | B. UPDATE FREQUENCY | Database is updated constantly. This report is issued daily/weekly/thrice weekly. | C. OTHER CRITICAL INFO | | D. ATTRIBUTES || D. ATTRIBUTES |CNN: CNN of intersection impacted by closure. CNN is unique ID of San Francisco’s street centerlines/intersections .Case_number: case numberCase_name: case nameType: closure typeStatus: case statusDT_opened: date/time of case openedPolicyDist: policy districtPubhear: public hearing dateContact_Na: contact nameContact_Em: contact emailLocation: closure locationStreet: street impacted by closureX_Street1: crossed street 1 for the entire closureX_Street2: crossed street 2 for the entire closure Street_name: street impacted by closureFrom_st: intersected streetTo_st: kept blankStart_date: start date of closure in date/time format (local time)End_date: end date of closure in date/time format (local time)Start_UTC: start date of closure in date/time format (UTC time)End_UTC: end date of closure in date/time format (UTC time)Event_Date: event details of start/end date, day of week, frequency, ect.Descriptio: comments by applicant
Copyright Text: | A. CUSTODIAN | Nick Chapman, nick.chapman@sfmta.com, SFMTA, Sustainable Streets, Transportation Engineering
| B. CREATED | 20200701, Muyi Zhou created the first version | C. VERSIONS |
20200701, Muyi Zhou, created with program applications
Description: | A. METHODOLOGY | Sources include shops reports, Paint Shop database maintained by MTA Paint Shop, project delivery spread maintained by Damon Curtis| B. UPDATE FREQUENCY | Quarterly| C. OTHER CRITICAL INFO | N/A| D. ATTRIBUTES |CNN: San Francisco's street centerline network unique ID; STREET_NAM: Street name in upper case;FROM_ST: One end of the block;TC_MEASURE: Traffic calming device typeUNITS: Quantity of device type on street segmentINSTALL_MO: Month traffic calming device was installedINSTALL_YR: Year traffic calming device was installedSource: Data sourceFISCAL_YR: Fiscal year of project/program associated with the traffic calming devicePROGRAM: Project or program associated with the traffic calming deviceADDRESS: Nearest street address to traffic calming deviceLATITUDE: Latitude of traffic calming deviceLONGITUDE: Longitude of traffic calming deviceSPHERE: Sphere of influence used for mileage calculation in annual Vision Zero reporting
Copyright Text: | A. CUSTODIAN | Jenn Chan, jennifer.chan@sfmta.com, Livable Streets, SSD, SFMTA
| B. CREATED | 20190614
| C. VERSIONS |
20190614, Jenn Chan, clean up for MTA spatial datastore
Description: | A. METHODOLOGY | Converted from the city’s intersection nodes shapefile found on the DataSF website. Brian removed extraneous fields and added fields related to Slow Streets.| B. UPDATE FREQUENCY | As-needed.| C. OTHER CRITICAL INFO | The Slow Streets Program is part of the SFMTA’s response to COVID-19. The program is temporary and helps maintain social distance requirements for users on the streets. Slow Streets utilize temporary tools like cones and signage to divert traffic and remind vehicles to maintain a safe speed to accommodate for pedestrians and bicyclists who may be traveling to make essential trips.| D. ATTRIBUTES |CNN: San Francisco’s street centerlines network unique ID;From_CNN: From street node CNN;To_CNN: To street node CNN;Node_slwst: Indicates that the intersection is in the extents of the Slow Street. Value of 1 indicates a traffic diverter exists at the intersection;Phase: Phase of the Slow Streets program in which the Slow Street was part of;Barrier: Total # of traffic diverters at the intersection;Slw_st name: Name of the Slow Street;Streetname: Street name;From_st: Cross street name;Intersection_control: If it exists, intersection control device;Notes: Notes for the barrier;Int_nb: number of traffic diverters in the northbound direction (-1: new design, 1: type III barricade);Int_sb: number of traffic diverters in the southbound direction (-1: new design, 1: type III barricade);Int_wb: number of traffic diverters in the westbound direction (-1: new design, 1: type III barricade);Int_eb: number of traffic diverters in the eastbound direction (-1: new design, 1: type III barricade)
Copyright Text: A. CUSTODIAN | Brian Liang; Brian.Liang@sfmta.com; Livable Streets, Streets Division, SFMTA
B. CREATED | 20210205
C. VERSIONS |
20200205, Brian Liang, Slow Streets traffic diverter data created and consolidated from implementation work orders
Description: | A. METHODOLOGY | Locations of continental crosswalks collected at the intersection level. Pre-2015 data was collected in the summer of 2019 as a one-time effort to locate every intersection with continental crosswalks on the city's High Injury Network. Crosswalks painted post-2015 are collected as part of Vision Zero data reporting. Shops reports are used as the data source. Shops reports include data citywide. Crosswalks marked "UNDETERMINED" in the "CONTINENTAL" field may or may not have continental crosswalks and require additional scrutiny. These two data sources were joined with an intersection nodes layer to create the feature class.| B. UPDATE FREQUENCY | Quarterly| C. OTHER CRITICAL INFO | This dataset includes: (1) all continental crosswalks citywide that were installed after 1/1/2015, and (2) all continental crosswalks that were installed before 12/31/2014 on the High Injury Network. It does not include continental crosswalks off the High Injury Network that were painted before 2015.| D. ATTRIBUTES |CNN: Intersection CNNSTREET_NAME: Primary street nameCROSS_STREET: Secondary street nameREPORT: Date of corresponding shops report (if applicable); "12:00:00 AM" used if a source other than a shops report was used to identify the presence of continental crosswalksYR_INSTALL: Year the continental crosswalks were painted; "0" used if crosswalks were painted before 2015CONTINENTAL: "YES" if the intersection has continental crosswalks; "UNDETERMINED" if it is unknown if there are continental crosswalksLONGITUDE: LongitudeLATITUDE: Latitude
Copyright Text: | A. CUSTODIAN | Jennifer Chan, jennifer.chan@sfmta.com, Livable Streets, SFMTA
| B. CREATED | 20200103, Mike Jacobson l
| C. VERSIONS | 20200103 Mike Jacobson, publishing all geodata to date (2,917 nodes)
Description: | A. METHODOLOGY | Sources include shops reports, Paint Shop database maintained by MTA Paint Shop, project delivery spread maintained by Damon Curtis| B. UPDATE FREQUENCY | Quarterly| C. OTHER CRITICAL INFO | N/A| D. ATTRIBUTES |CNN: San Francisco's street centerline network unique ID; STREET_NAM: Street name in upper case;FROM_ST: One end of the block;TC_MEASURE: Traffic calming device typeUNITS: Quantity of device type on street segmentINSTALL_MO: Month traffic calming device was installedINSTALL_YR: Year traffic calming device was installedSource: Data sourceFISCAL_YR: Fiscal year of project/program associated with the traffic calming devicePROGRAM: Project or program associated with the traffic calming deviceADDRESS: Nearest street address to traffic calming deviceLATITUDE: Latitude of traffic calming deviceLONGITUDE: Longitude of traffic calming deviceSPHERE: Sphere of influence used for mileage calculation in annual Vision Zero reporting
Copyright Text: | A. CUSTODIAN | Jenn Chan, jennifer.chan@sfmta.com, Livable Streets, SSD, SFMTA
| B. CREATED | 20190614
| C. VERSIONS |
20190614, Jenn Chan, clean up for MTA spatial datastore
20220407, Mike Jacobson, updated with completed traffic calming devices installed through Q1 2022
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 7 0;"><SPAN>| A. METHODOLOGY | Sign shop assets are manually added and updated via the Sign Shop Web Map Editor: https://sfgov.maps.arcgis.com/apps/webappviewer/index.html?id=a28072f040a84754a56163003e2b1fc2 </SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>| B. UPDATE FREQUENCY | Multiple times per day, Monday through Friday 7am to 5pm</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN>| C. OTHER CRITICAL INFO | Delineators and bike racks use the "NUM_OF_ASSETS" field to indicate how many assets are represented by a single point. Use values of 5 and 10 where possible. New are located along the curb. Old assets will be gradually moved to the curb. The 'zero point' of the blockface (where measurements begin) needs further SFMTA internal discussion and alignment. Currently, the MTA.curb layer sourced from SFGIS in 2017/18 uses the intersection of property lines to splice the curb into blockfaces and curb returns. Traffic Engineering uses a different methodology reliant on the location of the crosswalk.</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN>| D. ATTRIBUTES |</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN>OBJECTID_1: System (ArcGIS) generated unique identifier;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>ASSET_ID: Unique ID generated by HxGN EAMS and synced back to ArcGIS via Logic Apps. Does not populate for 'cancelled' features;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_CODE: Alphanumeric value associated with unique combination of LEGEND and SIGN_SIZE. Uses domain EAMS_Signshop_SignCode. Domain created from table MTA.signshop_domain_signcode;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>LEGEND: Text that appears on the sign, or if not a sign, a brief description of asset type. Populated via Logic App which uses the MTA.signshop_contingent_reference table to look up the value based on the sign code;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_SIZE: Dimensions of the sign. Populated via Logic App which uses the MTA.signshop_contingent_reference table to look up the value based on the sign;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>STREET_ADDRESS_RANGE: Lowest to highest address number and name of street asset is located on. Null for intersection assets;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_SUPPORT: Type of structure sign is affixed to. Uses domain EAMS_Signshop_SignSupport. Domain created from table MTA.signshop_domain_signsupport;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>FROM_ST: For assets on blockfaces/street segments, street name of first intersecting street. Based on CNN street segments, is not directional. For 3+ way intersections, street name(s) of intersecting street(s);</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>TO_ST: For assets on blockfaces/street segments, street name of second intersecting street. Based on CNN street segments, is not directional. Null for intersection assets;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>INTERSECTION: Street names of two intersecting streets. Null for assets on street segment / blockface;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>CORNER_SIDE_FACING: Description of where asset is located in an intersection. Somewhat legacy field from previous tabular database architecture. Uses domain EAMS_Signshop_SideFacing. Domain created from table MTA.signshop_domain_sidefacing;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>ARROW_DIR: Direction of arrow for signs with arrows, such as ONE WAY. Uses domain EAMS_Signshop_ArrowDirection. Domain created from table MTA.signshop_domain_arrowdir;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>BAPA: Whether asset requires Breakaway Pole Assembly;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>BOOM_TRUCK: Whether the asset requires a boom truck to install;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>CLEARANCE_PERMIT: Whether the asset requires a clearance permit;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>NUM_OF_ASSETS: Number of assets, such as in the case of delineators and bike racks. Should use value of 5 or 10;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>CONDITION: Condition of the asset. Uses domain EAMS_Signshop_Condition. Domain created from table MTA.signshop_domain_condition;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>ORIG_INSTALL_DATE: Date of original installation;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>REPLACEMENT_DATE: Replacement date;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_SUPERVISOR: Which sign supervisor district the asset is in;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SF_SUP_DISTRICT: Which SF Supervisor district the asset is in;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SHEETING: Type of sheeting. Uses domain EAMS_Signshop_Sheeting. Domain created from table MTA.signshop_domain_sheeting;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>STATUS_CODE: Status of asset, such as Pending Installation, In Service, Retired, or Withdrawn. Uses domain EAMS_Signshop_SignStatus. Domain created from table MTA.signshop_domain_status;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>NEW_SIGN_CODE: Alphanumeric value for new sign codes. Manually entered by Sign Shop supervisors;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>NEW_SIGN_LEGEND: Text for new legends. Manually entered by Sign Shop Supervisors;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>NEW_SIGN_SIZE: Dimensions of sign for new sign codes. Uses domain EAMS_Signshop_NewSignSize. Domain created from table MTA.signshop_domain_signsize;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_CATEGORY: Name of category. Uses domain EAMS_Signshop_SignCategory. Domain created from table MTA.signshop_domain_category;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_CLASS: Name of sign class. Uses domain EAMS_Signshop_SignClass. Domain created from table MTA.signshop_domain_class;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>PURPOSE: For what purpose sign is for, according to planners. Uses domain EAMS_Signshop_Purpose. Domain created from table MTA.signshop_domain_purpose;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>GISOBJID: Unique ID generated by Logic App, set equal to OBJECTID_1, populated in HxGN EAMS then synced back to GIS. Does not populate for 'cancelled' features. Required field for HxGN EAMS;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>CANCEL: If asset created in error, user will populate this field with "cancel' to flag it for removal;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN /></P></DIV></DIV></DIV>
Copyright Text: | A. CUSTODIAN | Contact steph.nelson@sfmta.com, Spatial Data Store DBA
| B. CREATED | 20230703, Mallik Budhavarapu and Steph Nelson imported from Spears/SHOPS database
| C. VERSIONS | 20230703