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 2017 Vision Zero High Injury Network is derived from 2013-2015 severe and fatal injury data from Zuckerberg San Francisco General (ZSFG), San Francisco Police Department/Crossroads Software Traffic Collision Database (SFPD), and the Office of the Medical Examiner (OME). ZSFG patient records and SFPD victim records were probabilistically linked through the Transportation Injury Surveillance System (TISS – contact Leilani.Schwarcz@sfdph.orgfor more information) using LinkSolv Software. Injury severity for linked SFPD/ZSFG records was reclassified based on injury outcome as determined by ZSFG medical personnel (net 883 police reported severe injuries) consistent with the Vision Zero Severe Injury Protocol (2017) while unlinked SFPD victim records were not changed (104 police reported severe injuries). Severe injuries captured by ZSFG but not reported to SFPD were also included in this analysis (411 unreported/unlinked severe injury patient records). Fatality data came from OME records that meet San Francisco’s Vision Zero Fatality Protocol (96 fatalities).Only transportation-related injuries resulting in a severe injury or fatality were used in this analysis. Each street centerline segment block was converted into ~0.25 mile overlapping corridorized sections using ArcPy. These sections were intersected with the severe/fatal injury data. Only severe/fatal injuries with the same primary street as the corridorized section were counted for that section. The count of severe/fatal injuries was then normalized by the sections mileage to derive the number of severe/fatal injuries per mile. A threshold of ≥7 severe/fatal injuries per mile was used as the threshold to determine if a corridorized segment qualified for inclusion into the network. Sections of the 2015 Vision Zero High Injury Network that had ≥6 severe/fatal injuries or a fatality in the last 4 year (2013-2016) were included in the updated network as well.2017 VZ High Injury Network Injury Capture by Mode (2013-2015):PedestrianSevere/Fatal Injuries: 77.1% - 404/524 PedestrianAll Injuries: 63.0% - 1675/2659CyclistSevere/Fatal Injuries: 71.1% - 248/349CyclistAll Injuries: 62.8% - 1319/2101VehicleSevere/Fatal Injuries: 74.5% - 450/604:VehicleAll Injuries: 59.5% - 4536/7628All Modes Severe/Fatal Injuries: 74.6% - 1102/1477All Modes All Injuries: 60.8% - 7530/12388| B. UPDATE FREQUENCY |This dataset will be updated in 2019/20 using 2016-2018 injury when available from SFPD, ZSFG, and OME. This update schedule is tentative and pending approval from the SFDPH/SFMTA. Please contact Devan Morris (devan.morris@sfdph.org) for more information.| C. OTHER CRITICAL INFO |The network represents a snapshot in time (2013-2015) where severe and fatal injuries are most concentrated. It may not reflect current conditions or changes to the city’s transportation system. Although prior incidents are often indicative of future incidents the Vision Zero High Injury Network is not a prediction (probability) of future risk. The High Injury Network approach is in contrast to risk-based approaches, which focus on locations determined to be more dangerous with increased risk or danger often calculated by dividing the number of injuries or collisions by vehicle volumes to estimate risk of injury per vehicle. The High Injury Network instead informs agencies of the streets where injuries, particularly severe and fatal, are concentrated in San Francisco based on injury counts; it is not an assessment of whether a street or particular location is dangerous. The 2017 Vision Zero Network is derived from only the worst injury outcomes (severe/fatal injuries) and may not cover locations with high numbers of less severe injury collisions. Hospital and emergency medical service records from which unreported injury and reclassified injury collisions are derived are protected by the Health Insurance Portability and Accountability Act and have strict confidentiality and privacy requirements. As of June 2017 SFPDH is working in conjunction with SFPDH’s Office of Compliance and Privacy Affairs, ZSFG and the SFMTA to determine at what level of aggregation SFDPH can share the data to be compliant with HIPAA. Location specific counts of severe/fatal injuries have been intentionally excluded from this dataset and a full dataset is pending review.A complete methodology is available here: link forthcoming.| D. 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;geom_Length: Object length created by ArcGIS;prior_network: identifies if street segment was on the 2015 Vision Zero High Injury Network or is new;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;geom_Length: Object length created by ArcGIS;prior_network: identifies if street segment was on the 2015 Vision Zero High Injury Network or is new
Copyright Text: | A. CUSTODIAN | Devan Morris, devan.morris@sfdph.org, Population Health, San Francisco Department of Public Health;
Leilani Schwarcz, leilani.schwarcz@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 DATE |
20170629
| C. VERSIONS |
Original release - 20110601, Devan Morris/Megan Wier (Department of Public Health) – previous methodology (http://bit.ly/1QQxU79);
Latest release - 20170629, Devan Morris/Megan Wier (Department of Public Health).
Description: | A. METHODOLOGY | Chapter 4 Section 1 BSP establishes a three-tiered process for establishing street types. See the Better Streets Planfor descriptions of street typologies: www.sfbetterstreets.orgColumns match the standardized zoning shape file for the City of San Francisco available at:https://data.sfgov.org/d/mici-sct2One new column was added to the dataset called: BSPThis column represents a simplified version of the city’s zoning districts as described in chapter 4 of the Better Streets PlanFigure 4.1 in the BSP determines which zoning district should be allocated to each street type:Street TypeZoning District (Per SF Planning Code)COMMERCIALDowntownC-3, C-2 (C-3 adjacent), CCB (w/in Downtown Streetscape Plan)Throughway, NeighborhoodNC, C-2, NCT, CCB (not w/in Downtown Streetscape Plan), CVR, CRNC, MB Retail, MB HotelRESIDENTIALDowntownDTR, RC-3, RC-4Throughway, Neighborhood RHRH, RM, RTO, RED, MB ResidentialOTHERIndustrialC-M, M1, M2, PDR-1, PDR-1-B, PDR-1-G (except Transit-Oriented Retail SUD), PDR-2Mixed-useMUG, MUO, MUR, PDR-1-D, PDR-1-G (Transit-Oriented Retail SUD only), SLR, SLI, SPD, SSO, RSD, UMU, MB districts: Public Facilities, Commercial Industrial, Commercial Industrial/RetailSummary of BSP Column in zoning shapefileZoning TypeNotesDowntown CommercialDowntown Commercial ZonesDowntown ResidentialDowntown Residential ZonesHunters Point – Follow Up LaterHunter’s Point Shipyard Redevelopment Area. Parcels layer hasn’t been updated to reflect impending changes. Check Redevelopment PlanIndustrialIndustrial zonesMission Bay – Follow Up LaterMission Bay Redevelopment Area. Check Redevelopment PlanMixed UseMixed Use ZonesNeighborhood CommercialNeighborhood Commercial ZonesNeighborhood ResidentialNeighborhood Residential ZonesPublicPublicly owned land including Parks and Open SpacesShapefile: Streets_bsp_baseColumns match the standardized streets shape file for the City of San Francisco available at:https://data.sfgov.org/d/5rn4-fswjSeveral additional columns described below were added to the legacy SF streets shapefile.Primary Street Classification ColumnThe column called BSP_Classdefines each street in the city with a different street classification specified in the City’s Better Streets Plan.The BSP_Classcolumn can be used to display all streets with appropriate street types.Individual typology Classification ColumnsEach street typology is given its own unique column in addition to the BSP_Classcolumn. These columns can be used to display all of the streets that fall under one street typology. Individual street typologies are classified with a binary Y/N.Y(Yes) = Street segment is classified as the typology specified in the column nameN(no) = Street segment is not classified as the typology specified in the column nameA note on AlleysNote: Alleys are defined in the State of California legal codeas streets under 30’ or less. When attempting to apply this definition to alleys some streets inner-ring neighborhoods like SOMA, Hayes Valley and the Mission, didn’t show up. We then tried to apply a width of 40’ to alleys, but then numerous streets in neighborhoods like Twin Peaks and Bernal Heights lit up. For the purposes of this map, alleys are defined as: Streets that are 40’ wide or less in areas of the City with a secondary grid system. This allows wider streets in the inner-ring neighborhoods to be considered alleys, but doesn’t included large swathes of Twin Peaks and Bernal Heights where there is no 2ndary hierarchy to the street network.| B. UPDATE FREQUENCY | Not regularly updated.| C. OTHER CRITICAL INFO | Sourced from the City of SF Planning Department.| D. ATTRIBUTES |Summary of BSP-related Columns AddedColumn NameDescriptionNotesBSP_ClassDelineates the BASIC street class based on underlying zoning. Does not include special conditions except for Alleys & Paseos.Alley = Street has basic class of AlleyCommercial Throughway = Street has basic class of Commercial ThroughwayDowntown Commercial = Street has basic class of Downtown Commercial StreetDowntown Residential = Street has basic class of Downtown Residential StreetHWY = Street is a Highway, (not regulated by the BSP)HWY Ramp = Street is a Highway on or off ramp, (not regulated by the BSP)Industrial = Street has basic class of Industrial StreetMixed Use = Street has basic class of Mixed-use StreetNeighborhood Commercial = Street has basic class of Neighborhood Commercial StreetNeighborhood Residential = Street has basic class of Neighborhood Residential StreetPark Interior = Street has a basic class of Park Interior street. (Not identified in the BSP. BSP needs to be updated with addition of Park Interior Typology)Paseo = Street has basic class of PaseoResidential Throughway = Street has basic class of Residential ThroughwayTBD =Street is in a Redevelopment Plan area and will change when redevelopment plan is implemented. Check w/ redevelopment agency or relevant successor agencyUnaccepted/Paper Streets= Street is not accepted for maintenance by the City and County of San Francisco. May be several reasons such as: Unimproved ROW on a steep slope, privately owned street in an office park or mall, or street platted but not built underwaterThroughwayDelineates weather or not a street is a throughway. Does not distinguish between Residential Throughways and Commercial ThroughwaysY= ThroughwayN= Not a ThroughwaySpecialDelineates weather or not a street segment has a special condition.Used to display all streets with special conditionsAlley = Street has special condition of AlleyBoulevard = Street has special condition of BoulevardCeremonial = Street has special condition of Ceremonial StreetPark Edge = Street has special condition of Park Edge StreetParkway = Street has special condition of ParkwayPaseo = Street has special condition of PaseoN = Street segment does not have a special condition overlayAlleyDelineates weather or not a street segment is an AlleyY= AlleyN= Not an AlleyPark EdgeDelineates weather or not a street segment is a Park Edge StreetY= Park Edge StreetN= Not a Park Edge StreetCeremonialDelineates weather or not a street segment is a Ceremonial StreetY= Ceremonial StreetN= Not a Ceremonial StreetParkwayDelineates weather or not a street segment is a ParkwayY= ParkwayN= Not a ParkwayBoulevardDelineates weather or not a street segment is a BoulevardY= BoulevardN= Not a BoulevardThroughway2Delineates weather or not a street segment is a throughwayComm_Throughway= Commercial ThroughwayRes_Throughway= Residential ThroughwayNA= Not a ThroughwayPaseoPaseo (Pedestrian Only) StreetsY= Paseo N= Not a PaseoStrets_BSP.width_FTStreet width in 2’ incrementsUsed to determine alleys, may not be entirely accurateStNameLwrCStreet Names listed in lower case text with first letters capitalized
Copyright Text: | A. CUSTODIAN | Paul Chasan, paul.chasan@sfgov.org, Planning Department, City of San Francisco
| B. CREATED | February 26, 2013, paul.chasan@sfgov.org
| C. VERSIONS |
Description: | A. METHODOLOGY | Green Connections is a network that considers access to open space, stormwater capture, walking routes, bicycling routes, and wildlife. For more information about how the Green Connections Network was developed, please vist: http://208.121.200.84/ftp/files/Citywide/green_connections/GC_Final_Report-CH3_The_Green_Connections_Network.pdf| B. UPDATE FREQUENCY | N/A| C. OTHER CRITICAL INFO | Some portions of routes may not be ideal for bicycles due to conditions such as steep topography, stairs or trails. The proposed network falls mostly on public rights of way, but occasionally deviates onto public properties such as park lands.| D. ATTRIBUTES |CNN: San Francisco's street centerline network unique ID; STREET: Street name in upper case;ST_TYPE: Street type;GC_RT_NAME: Green Connections route name;GC_RT_NMBR: Green Connections route number
Copyright Text: | A. CUSTODIAN | Jen Wong, jennifer.wong@sfmta.com, Livable Streets, SSD, SFMTA
| B. CREATED | 20130807
| C. VERSIONS |
20160500 - downloaded from DataSF at https://data.sfgov.org/Energy-and-Environment/Green-Connections-Network/3n7h-3jam
Description: | A. METHODOLOGY | A python script runs every Friday night, utilizing a series of spatial joins to synthesize data from multiple feature classes. The script can be found here for reference: \\mtanas\sfmtagis\01_Projects\InformationTechnology\SpatialDataStore_Administration\05_ReferenceFiles\projects_post_processing_prep.pySpatial joins for Muni routes, service categories, bike facilities, and supervisor districts result in a comma separated list of all intersecting features for each respective attribute.| B. UPDATE FREQUENCY | Weekly. Python script runs every Friday night at 11pm.| C. OTHER CRITICAL INFO | Accuracy of this feature class depends upon the accuracy of all other feature classes that it pulls from. For sausage streets, streetblocks are drawn as separate features (one for each side of street), however, the attribtues pertain to the entire right of way from parcel to parcel, and do not have side of street precision.| D. ATTRIBUTES |CNN: Unique ID for a given streetblock. Source feature class = MTA.RightOfWay/MTA.DPW_row_streetblocks;Streetname: Name of the street. Source feature class = MTA.RightOfWay/MTA.DPW_row_streetblocks;Functional Class: Functional Classification per Highway. Source feature class = MTA.RightofWay/MTA.CALTRANS_BayArea_roads, pulling from field 'FC_DRAFT';BetterStreetsPlanClass: Class as determined by SF Planning's Better Streets Plan. Source feature class = MTA.Multimodal/MTA.PL_betterstreetsplan, pulling from field 'BSP_Class';RightofWayWidth: Unofficial width of the right of way, measured from parcel to parcel, utilizing nearest neighbor geoprocessing tool. Source feature class = MTA.RightofWay/MTA.row_streetblocks, pulling from field 'ROW_201507';SidewalkWidth: Width of the sidewalk based on an AECOM survey in 2012 (?). Source feature class = MTA.Pedestrian/MTA.sidewalk_widths, pulling from field 'SIDEWALK_F';NumberofLanes_AM: Number of lanes during morning hours. Source feature class = MTA.Traffic/MTA.CTA_trafficlanes, pulling from field 'LANE_AM';NumberofLanes_PM: Number of lanes during morning hours. Source feature class = MTA.Traffic/MTA.CTA_trafficlanes, pulling from field 'LANE_PM';NumberofLanes_OffPeak: Number of lanes during morning hours. Source feature class = MTA.Traffic/MTA.CTA_trafficlanes, pulling from field 'LANE_OP';SupervisorDistrict: Supervisor district that a given streetblock intersects. Can be multiple, in which case it will be a comma separated list of districts. Source feature class = MTA.Basemap/MTA.SFGIS_supervisordistricts, pulling from field 'SUPERVISORDISTRICT';Supervisor: Supervisor name corresponding to the distrct that a given streetblock intersects. Can be multiple, in which case it will be a comma separated list of last names. Source feature class = MTA.Basemap/MTA.SFGIS_supervisordistricts, pulling from field 'SUPERVISORNAME';VisionZeroHIN: Indicates whether the streetblock is in the Vision Zero High Injury Network. Source feature class = MTA.Multimodal/MTA.DPH_vz_hgh_injry_ntwrk;MuniRoute: Comma separated list of all Muni routes traversing a given streetblock. Source feature class = MTA.Transit/MTA.Muni_simpleroutes, pulling from field 'ROUTE_NAME';MuniServiceCategory: Comma separated list of service categories corresponding to the Muni routes traversing a given streetblock. Source feature class = MTA.Transit/MTA.Muni_simperoutes, pulling from field 'SERVICE_CA';EquityNeighborhood: Indicates whether the streetblock is in an equity neighborhood. Source feature class = MTA.Transit/MTA.equityneighborhood;TransitOnlyLane: Indicates whether the streetblock has a transit only lane, regardless of direction. Source feature class = MTA.Transit/MTA.transitonlylanes; TOL_RedLane: Indicates whether the transit only lane is also a red lane or not. Source feature class = MTA.Transit/MTA.transitonlylanes, pulling from field 'RedLane';TOL_TaxiAllowed: Indicates whether the transit only lane allows taxis as well. Source feature class = MTA.Transit/MTA.transitonlylanes, pulling from field 'TaxiAllowed';BikeFacility_Type: Comma separated list of all bike facility types on a given streetblock. Source feature class = MTA.Bicycle/MTA.bikewaynetwork, pulling from field = 'FACILITY_T';BikeFacility_Desc:Comma separated list of the correspdonding descriptions of bike facility types on a given streetblock. Source feature class = MTA.Bicycle/MTA.bikewaynetwork, pulling from field = 'SYMBOLOGY';BikeShareStation: Indicates whether there is a bike share station on a given streetblock. Source feature class = MTA.Bicycle/MTA.bikeshare_stations;CommercialPassengerLoading: Indicates whether there is metered commercial or passenger loading on a given streetblock. Source feature class = MTA.Parking/MTA.meters, pulling from field "CAP_COLOR" where "CAP_COLOR IN ('white','yellow'), and also from MTA.Parking/MTA.colorcurb where 'ZONE_TYPE' IN ('white','yellow');CommuterShuttle: Indicates whether there is a commuter shuttle stop on a given streetblock. Source feature class = MTA.Traffic/MTA.commutershuttle_stops;ParkingCensusCount: Number of surveyed parking spaces available on a given streetblock as of the last parking census completed in 2014. Includes both metered and non-metered spaces at that time. Source feature class = MTA.Parking/MTA.parkingcensus, pulling from field 'PKNG_SPLY';MeteredParking: Indicates whether there is metered parking on a given streetblock. Source feature class = MTA.Parking/MTA.meters;MotorcycleParking: Indicates whether there is motorcycle parking on a given streetblock. Source feature class = MTA.Parking/MTA.meters where 'CAP_COLOR' = 'black';RPPTimeLimitedParking: Indicates whether there are RPP time limited parking exemptions on a given streetblock. Source feature class = MTA.Parking/MTA.parkingregulations where 'RPPAREA1 IS NOT NULL';Speedlimit: Speed limit on a given streetblock. Source feature class = MTA.Traffic/MTA.speedlimits, pulling from field 'SPEEDLIMIT';VehicleRestrictions_Weight: Weight restrictions for a given streetblock. Source feature class = MTA.Traffic/MTA.vehiclerestrictions, pulling from field 'RSTR_WEIGHT';VehicleRestrictions_Other: Weight restrictions for a given streetblock. Source feature class = MTA.Traffic/MTA.vehiclerestrictions, pulling from field 'RSTR_OTHER';CREATED_USER: Automated record;CREATED_DATE: Automated record;LAST_EDITED_USER: Automated record;LAST_EDITED_DATE: Automated record;SHAPE: Automated record;SHAPE.AREA: Automated record;SHAPE.LEN: Automated record;
Copyright Text: | A. CUSTODIAN | Steph A. Nelson, GIS Administrator/Developer, steph.nelson@sfmta.com
| B. CREATED | 20171201
| C. VERSIONS | Updated weekly
Description: | A. METHODOLOGY | Initial data were gathered from the 2017 Short Range Transit Plan, Facility Condition Assessments prepared by EMG in 2016, the SF OpenData portal, and the 2013 "SFMTA Real Estate and Facilities Vision for the 21st Century," among other sources. Ongoing updates are derived from annual updates to the Capital Asset Inventory.| B. UPDATE FREQUENCY | Annual| C. OTHER CRITICAL INFO | N/A| D. ATTRIBUTES |Name: Name of facility;Address: Address of facility;Year_Const: Year facility constructed;Site_Area: Area of facility site, if unavailable = 0;Ftprt_Area: Area of combined building footprint(s) on the facility, if unavailable = 0;Gr_Fl_Area: Gross floor area of all buildings on the facility, if unavailable = 0;Function: Function(s) of facility;Lat: Latitude coordinates of facility centroid;Long: Longitude coordinates of facility centroid;Elev_Min: Minimum elevation above sea level of facility, if unavailable = 0;Elev_Max: Maximum elevation above sea level of facility, if unavailable = 0;Height_Min: Minimum building height of facility, if unavailable = 0;Height_Max: Maximum building height of facility, if unavailable = 0;Type: Facility type (substation or restroom);Subst_ID: Substation ID number;RR_ID: Restroom ID number;RR_Locatio: More details on restroom location to complement address data;RR_Hours: Hours of restroom operation;RR_Type: Restroom type (free, permanent, portable, etc.);
Copyright Text: | A. CUSTODIAN | Anna Harkman; anna.harkman@sfmta.com; Planning, SSD, SFMTA
| B. CREATED | 20161007, Derek Cheah
| C. VERSIONS |
20161007, Derek Cheah, initial version created