Description: | A. PURPOSE | Blockface geography for the City of San Francisco (coincident with curb lines), useful as a base for parking regulations and other feature attributes.| B. METHODOLOGY | Dataset created by multiple analysts over several years; various methodologies employed including manual drawing and use of offset tool and street centerline shapefile.| C. UPDATE FREQUENCY | Updated frequently as this dataset is currently in development, as of June 2015.| D. OTHER CRITICAL INFO | Attributes are in progress and unverified, except for SFPARK_ID.Some blockfaces are drawn only for portions of a given street length, as they were originally intended to show length of street where parking regulations were in effect. Currently being revised (June 2015). | E. ATTRIBUTES |SFPARK_ID: Blockface ID generated for the meter database (or "parking space inventory"), corresponds to meter post ID, block ID and parking management district IDs
Copyright Text: | A. CUSTODIAN | Manzell Blakeley, manzell.blakeley@sfmta.com, Parking Group, SFMTA
| B. CREATED | 2008, Eric Ganther (former SFpark staff member)
| C. VERSIONS |
20150619, Steph A. Nelson, MTA spatial data store prep (imported and added metadata)
Description: | A. METHODOLOGY | Data is collected from project managers and SFMTA.com project page editors through the Interactive Project Map Collector Tool.| B. UPDATE FREQUENCY | The data is updated on an as needed basis. Project geographies should be updated by project managers and project pge editors whenever project extents change.| C. OTHER CRITICAL INFO | Please note there is a 250ft buffer for projects to more accurately represent the supervisor districts and neighborhoods that could potentially be affected by a project.| D. ATTRIBUTES |OBJECTID: Auto-populated field generated when a new attribute is added to the feature class;PROJECTNODE: The project node ID is the unique page identifier behind each public-facing url for pages on SFMTA.com;PROJECTNAME: Auto-populated field that grabs the appropriate project name based on the PROJECTNODE entered with the map attribute; CIP ID (if applicable): The CIP ID assigned to projects. If the field says NEW the project has not yet been assigned a CIP ID, please reach out to Capital Finance staff; CIP Title: The CIP Title assigned to projects. If the field says NEW the project has not yet been assigned a CIP Title, please reach out to Capital Finance staff; PROJECTPAGE: Auto-populated field that grabs the appropriate page url based on the PROJECTNODE entered with the map attribute;Project Teaser: Auto-populated field that grabs Project Teaser info from SFMTA.com project page;Project Phase: Auto-populated field that grabs Project Phase info from SFMTA.com project page; Project Type: Auto-populated field that grabs Project Type/Mode info from SFMTA.com project page; WEBPAGEPUBLISHED: Auto-populated field that denotes whether the map attribute has a published webpage; Supervisor Name: Auto-populated field with the name of the district supervisor(s) based on project extent; Supervisor District: Auto-populated field with the number of the supervisorial district(s) based on project extent;Neighborhood: Auto-populated field with the name of the neighborhood based on project extent;Project Page Map Option: Auto-populated field showing which map tab option on SFMTA.com is selected by project page editors; GEOEVENT_LASTUPDATE: ; CREATED_DATE: Auto-populated field with creation time stamp;CREATED_USER: Auto-populated field with the GIS login assigned to various workgroups;LAST_EDITED_DATE: Auto-populated field with edit time stamp;LAST_EDITED_USER: Auto-populated field with the GIS login assigned to various workgroups;SHAPE: Auto-populated field based on how the project feature is drawn; Partner Agencies: Auto-populated field that grabs Partner Agency info from SFMTA.com project page;SHAPE.LEN: ;
Copyright Text: | A. CUSTODIAN | Tori Winters, SFMTA Planning, tori.winters@sfmta.com
| B. CREATED | 20171110, Steph A. Nelson
| C. VERSIONS |
20180613, Tori Winters, Metadata added, edited CIP data to transition data collected from development to maintenance
Description: | A. METHODOLOGY | Data is collected from project managers and SFMTA.com project page editors through the Interactive Project Map Collector Tool.| B. UPDATE FREQUENCY | The data is updated on an as needed basis. Project geographies should be updated by project managers and project pge editors whenever project extents change.| C. OTHER CRITICAL INFO | Please note there is a 250ft buffer for projects to more accurately represent the supervisor districts and neighborhoods that could potentially be affected by a project.| D. ATTRIBUTES |OBJECTID: Auto-populated field generated when a new attribute is added to the feature class;PROJECTNODE: The project node ID is the unique page identifier behind each public-facing url for pages on SFMTA.com;PROJECTNAME: Auto-populated field that grabs the appropriate project name based on the PROJECTNODE entered with the map attribute; CIP ID (if applicable): The CIP ID assigned to projects. If the field says NEW the project has not yet been assigned a CIP ID, please reach out to Capital Finance staff; CIP Title: The CIP Title assigned to projects. If the field says NEW the project has not yet been assigned a CIP Title, please reach out to Capital Finance staff; PROJECTPAGE: Auto-populated field that grabs the appropriate page url based on the PROJECTNODE entered with the map attribute;Project Teaser: Auto-populated field that grabs Project Teaser info from SFMTA.com project page;Project Phase: Auto-populated field that grabs Project Phase info from SFMTA.com project page; Project Type: Auto-populated field that grabs Project Type/Mode info from SFMTA.com project page; WEBPAGEPUBLISHED: Auto-populated field that denotes whether the map attribute has a published webpage; Supervisor Name: Auto-populated field with the name of the district supervisor(s) based on project extent; Supervisor District: Auto-populated field with the number of the supervisorial district(s) based on project extent;Neighborhood: Auto-populated field with the name of the neighborhood based on project extent;Project Page Map Option: Auto-populated field showing which map tab option on SFMTA.com is selected by project page editors; GEOEVENT_LASTUPDATE: ; CREATED_DATE: Auto-populated field with creation time stamp;CREATED_USER: Auto-populated field with the GIS login assigned to various workgroups;LAST_EDITED_DATE: Auto-populated field with edit time stamp;LAST_EDITED_USER: Auto-populated field with the GIS login assigned to various workgroups;SHAPE: Auto-populated field based on how the project feature is drawn; Partner Agencies: Auto-populated field that grabs Partner Agency info from SFMTA.com project page;SHAPE.LEN: ;
Copyright Text: | A. CUSTODIAN | Tori Winters, SFMTA Planning, tori.winters@sfmta.com
| B. CREATED | 20171110, Steph A. Nelson
| C. VERSIONS |
20180613, Tori Winters, Metadata added, edited CIP data to transition data collected from development to maintenance
Description: | A. METHODOLOGY | Data is collected from project managers and SFMTA.com project page editors through the Interactive Project Map Collector Tool.| B. UPDATE FREQUENCY | The data is updated on an as needed basis. Project geographies should be updated by project managers and project pge editors whenever project extents change.| C. OTHER CRITICAL INFO | Please note there is a 250ft buffer for projects to more accurately represent the supervisor districts and neighborhoods that could potentially be affected by a project.| D. ATTRIBUTES |OBJECTID: Auto-populated field generated when a new attribute is added to the feature class;PROJECTNODE: The project node ID is the unique page identifier behind each public-facing url for pages on SFMTA.com;PROJECTNAME: Auto-populated field that grabs the appropriate project name based on the PROJECTNODE entered with the map attribute; CIP ID (if applicable): The CIP ID assigned to projects. If the field says NEW the project has not yet been assigned a CIP ID, please reach out to Capital Finance staff; CIP Title: The CIP Title assigned to projects. If the field says NEW the project has not yet been assigned a CIP Title, please reach out to Capital Finance staff; PROJECTPAGE: Auto-populated field that grabs the appropriate page url based on the PROJECTNODE entered with the map attribute;Project Teaser: Auto-populated field that grabs Project Teaser info from SFMTA.com project page;Project Phase: Auto-populated field that grabs Project Phase info from SFMTA.com project page; Project Type: Auto-populated field that grabs Project Type/Mode info from SFMTA.com project page; WEBPAGEPUBLISHED: Auto-populated field that denotes whether the map attribute has a published webpage; Supervisor Name: Auto-populated field with the name of the district supervisor(s) based on project extent; Supervisor District: Auto-populated field with the number of the supervisorial district(s) based on project extent;Neighborhood: Auto-populated field with the name of the neighborhood based on project extent;Project Page Map Option: Auto-populated field showing which map tab option on SFMTA.com is selected by project page editors; GEOEVENT_LASTUPDATE: ; CREATED_DATE: Auto-populated field with creation time stamp;CREATED_USER: Auto-populated field with the GIS login assigned to various workgroups;LAST_EDITED_DATE: Auto-populated field with edit time stamp;LAST_EDITED_USER: Auto-populated field with the GIS login assigned to various workgroups;SHAPE: Auto-populated field based on how the project feature is drawn; Partner Agencies: Auto-populated field that grabs Partner Agency info from SFMTA.com project page;SHAPE.LEN: ;
Copyright Text: | A. CUSTODIAN | Tori Winters, SFMTA Planning, tori.winters@sfmta.com
| B. CREATED | 20171110, Steph A. Nelson
| C. VERSIONS |
20180613, Tori Winters, Metadata added, edited CIP data to transition data collected from development to maintenance
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. PURPOSE | Provide spatial route data for all routes.| B. METHODOLOGY | Route data is exported from the Trapeze scheduling system and filtered only for full length patterns, and manually edited in this database to reflect core service changes during shelter in place.| C. UPDATE FREQUENCY | Pending edits -- this is currently just a copy of the full simple routes feature class. Updated by “Sign-up”, when transit system changes are put into effect. Updates range from every 3-6 months. | D. OTHER CRITICAL INFO || Pending edits -- this is currently just a copy of the full simple routes feature class. Inbound and Outbound route lines are included and represented with separate polylines for each route. Route numbers 59, 60, 61 are all Cable Car routes. | E. ATTRIBUTES |PATTERN: Pattern designation. A pattern represents one of the variations of a route. For example, the 38-Geary outbound may terminate at Fort Miley, 48thAve, or 32ndAve. See the following pattern code document for full description of pattern codes: \\mtanas\sfmtagis\03_Geodata\Additional Documentation\Route Patterns Naming Conventions.docx;PATTERNID: Pattern unique ID;ROUTE_NAME: Public-facing route number;DIRECTION: “I” = Inbound, “O” = Outbound;PATTERN_TYPE: See pattern code document;SUB_TYPE: See pattern code document;PATTERN_VERSION: See pattern code document;LINEABBR: Line code in Trapeze;SIGNID: Signup unique ID - See https://transtat.sfmta.com/#/views/SignupsPlatformRevenueHoursandMiles/SignupPeriodsfor definition of signup periods;SERVICE_CA: As part of Muni Forward, SFMTA proposed a new framework that reorganizes Muni service into transit categories.
Copyright Text: | A. CUSTODIAN | Leslie Bienenfeld, Leslie.Bienenfeld@sfmta.com, SFMTA
| B. CREATED | 20160408
| C. VERSIONS |
20160610,
20160408
Description: | A. METHODOLOGY | Converted fromthe city’s centerline shapefilefilefound on the DataSF website. Brianremoved 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: Centerline network number;Classcode: Facility code;f_node_cnn: CNN of the from street node;f_st: From street;oneway: One-way or two-way street;st_type: Type of street;street: Name of the street;streetname: Name of street;t_node_cnn: CNN of the to street node;nhood: Neighborhood;t_st: To street;slw_st: 1 indicates the segment is on the slow street network. If a segment is 0, it means it was planned but removed from the program. Please query the data for Slw_st = 1 to see all planned and implemented Slow Streets;length: length of section;extents: extents of the slow street corridor;status: planned or implemented
Copyright Text: | A. CUSTODIAN | Brian Liang, brian.liang@sfmta.com | B. CREATED | 2020, SFMTA
| C. VERSIONS | 202004, imported to Spatial Data Store from G Drive
20200419, Brian Liang, revised Phase 2 streets
20200411, Brian Liang added Phase 2 streets
202004, Brian Liang, created using the city’s centerline shapefile
Description: | A. METHODOLOGY | Exported from the Special Events/Shared Spaces Saleforce database maintained by the SFMTA ISCOTT unit and the Special Traffic Permit (STP) Access database, and converted to geometry of streets and intersections based on closed street extent description. | B. UPDATE FREQUENCY | Database is updated weekly.| C. OTHER CRITICAL INFO | | D. ATTRIBUTES |CASE_NUM: case numberCASE_NAME: case nameTYPE: closure type - Shared Space, Special Event or STP (special traffic permit)STATUS: case statusSTART_DATE: closure start dateSTART_TIME: closure start timeSTART_DT: closure start datetimeEND_DATE: closure end dataEND_TIME: closure end timeEND_DT: closure end datetimeLOC_DESC: closure locationdescriptionDT_DESC: closure date/time descriptionCNN: CNN of street impacted by closure. CNN is San Francisco’s street centerline network unique ID.STREET: street impacted by closureFROM_ST: crossed street 1 of the street impacted by closureTO_ST: crossed street 2 of the street impacted by closureDOW: day of weekDIRECTION: direction of street being closedVEH_IMP: vehicle impact
Copyright Text: | A. CUSTODIAN | Muyi Zhou, muyi.zhou@sfmta.com, SFMTA, Sustainable Streets, Data Analytics
| B. CREATED | 20200701, Muyi Zhou created the first version | C. VERSIONS |
20200701, Muyi Zhou, created with program applications
Description: | A. METHODOLOGY | Exported from the Special Events/Shared Spaces Saleforce database maintained by the SFMTA ISCOTT unit and the Special Traffic Permit (STP) Access database, and converted to geometry of streets and intersections based on closed street extent description. | B. UPDATE FREQUENCY | Database is updated weekly.| C. OTHER CRITICAL INFO | | D. ATTRIBUTES |CASE_NUM: case numberCASE_NAME: case nameTYPE: closure type - Shared Space, Special Event or STPSTATUS: case statusSTART_DATE: closure start dateSTART_TIME: closure start timeSTART_DT: closure start datetimeEND_DATE: closure end dataEND_TIME: closure end timeEND_DT: closure end datetimeLOC_DESC: closure location descriptionDT_DESC: closure date/time descriptionCNN: CNN of street impacted by closure. CNN is San Francisco’s street centerline network unique ID.STREET: crossed street 1 of intersection impacted by road closureX_STREET: crossed street 2 of intersection impacted by road closureIS_OPEN: if intersection is open to trafficDOW: day of weekDIRECTION: direction of street being closedVEH_IMP: vehicle impact
Copyright Text: | A. CUSTODIAN | Muyi Zhou, muyi.zhou@sfmta.com, SFMTA, Sustainable Streets, Data Analytics
| B. CREATED | 20200701, Muyi Zhou created the first version | C. VERSIONS |
20200701, Muyi Zhou, created with program applications
Description: | A. METHODOLOGY | The powered scooter neighborhoods are designated and maintained by the Powered Scooter Program of SFMTA.| B. UPDATE FREQUENCY | Dataset is updated daily.| C. OTHER CRITICAL INFO | | D. ATTRIBUTES |Name: Name of geography;Description: Detailed description of geography;geography_type: Type of geography, e.g. municipal_boundary or council_district or custom text; geography_id: Unique ID of geography;geography_json: The GeoJSON that defines the geographical coordinates;effective_date: The date in timestamp at which a Geography is considered "live". Must be at or after published_date;published_date: The date in timestamp that the geography was published, i.e. made immutable;retire_date: The date in timestamp that the geography is slated to retire. Once the retire date is passed, new policies can no longer reference it and old policies referencing it should be updated. Retired geographies should continue to be returned in the geographies list. Must be after effective_date;prev_geographies: Unique IDs of prior geographies replaced by this one
Copyright Text: | A. CUSTODIAN | Alex Demisch, alex.demisch@sfmta.com, SFMTA, Sustainable Streets Data Analytics
| B. CREATED | 20220512, Muyi Zhou created the first version | C. VERSIONS |
20220512, Muyi Zhou, created with program applications
Description: This dataset tracks the status of midblock traffic calming devices from data collection to project completion. Use the definition query CURRENT_STATUS = Complete to find completed devices. Another usual query is PROGRAM = App-Based to find all application-based traffic calming locations.Attributes:- CNN: Corresponding centerline network node- STREETNAME: Primary street- FROM_ST: Beginning project bound- TO_ST: Ending project bound- PROJECT_LOCATION: Concatenated location- NEIGHBORHOOD: Neighborhood in which TC device is located- DISTRICT: Supervisorial district in which TC device is located- TC_MEASURE: Type of traffic calming device installed at location- UNITS: Number of devices installed at location- INSTALL_MO: Month of installation- INSTALL_YR: Year of installation- SOURCE: Data source for locations, device types, and current status- FISCAL_YR: Fiscal year included if a location is part of a fiscal year program cycle (ie. App-Based program)- PROGRAM: Specifies if a TC location is part of a specific program (ie. NTIP, CRT, or neighborhood proactive)- CURRENT_ST: Current status (Options include: Complete, Collect traffic data for each block, pending construction, etc.)- CURRENT_TI: Timeline for current step, if available- NEXT_ST: Next step in traffic calming process- NEXT_ST_TI: Timeline for next step, if available
Copyright Text: A. CUSTODIAN | Mike Jacobson; michael.jacobson@sfmta.com; SFMTA Livable Streets
| B. CREATED | 20191220; Jenn Chan; jennifer.chan@sfmta.com; SFMTA Livable Streets
| C. VERSIONS |
20191220, Jenn Chan, clean up for MTA spatial datastore
20220407, Mike Jacobson, updated with completed traffic calming devices installed through Q1 2022
20220614, Mike Jacobson, updated with completed traffic calming devices installed through May 2022
20221010, Mike Jacobson, updated to include pending devices locations in addition to completed traffic calmind devices. Data current through Q3 2022
Description: This dataset tracks the status of midblock traffic calming devices from data collection to project completion. Use the definition query CURRENT_STATUS = Complete to find completed devices. Another usual query is PROGRAM = App-Based to find all application-based traffic calming locations.Attributes:- CNN: Corresponding centerline network node- STREETNAME: Primary street- FROM_ST: Intersecting street- PROJECT_LO: Intersection location- NEIGHBORHOOD: Neighborhood TC device is located in- DISTRICT: Supervisorial district TC device is located in- TC_MEASURE: Type of traffic calming device- UNITS: Number of devices installed at the location- INSTALL_MO: Month the device was installed- INSTALL_YR: Year the device was installed- SOURCE: Data source for update- FISCAL YEAR: If applicable, the fiscal year program in which the TC location was part (ie. FY for App-Based program- PROGRAM: If applicable, particular program- CURRENT_ST: Current status of location (ie. Complete, pending, etc.)- CURRENT_TI: Anticipated timeline for current step- NEXT_STEP: Next step in traffic calming process- NEXT_STEP_TI: Anticipated timeline for next step
Copyright Text: | A. CUSTODIAN | Mike Jacobson; michael.jacobson@sfmta.com; SFMTA Livable Streets
| B. CREATED | 20190614; Jenn Chan; jennifer.chan@sfmta.com; SFMTA Livable Streets
| C. VERSIONS |
20190614, Jenn Chan, clean up for MTA spatial datastore
20220407, Mike Jacobson, updated with completed traffic calming devices installed through Q1 2022
20221010, Mike Jacobson, updated with new fields and traffic calming devices installed and planned through Q3 2022
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 2015LAST_REPAINT: The most recent year a continental crosswalk was repainted or refreshedCONTINENTAL: "YES" if the intersection has continental crosswalks; "UNDETERMINED" if it is unknown if there are continental crosswalksLONGITUDE: LongitudeLATITUDE: Latitude
Copyright Text: | A. CUSTODIAN | Vicente Romero; Vicente.Romero@sfmta.com; SFMTA Livable Streets
| B. CREATED | 20200103; Mike Jacobson; Mike.Jacobson@sfmta.com; SFMTA Livable Streets
| C. VERSIONS | 20240215, Vicente Romero, added new continental crosswalk locations
20230801, Vicente Romero, added new continental crosswalk locations
20200103 Mike Jacobson, publishing all geodata to date (2,917 nodes)
Description: | A. 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.| B. UPDATE FREQUENCY | Unknown. | C. 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.| D. 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.