As of November 2023, this map has been updated to use a new format. For details, please see here.
San Francisco ZIP Code Areas. Matched to city streets and lots by Department of Planning. These are generalized areal representations of United States Postal Service (USPS) ZIP Code service areas. Please note that actual USPS ZIP Codes identify the individual post office or metropolitan area delivery station associated with mailing addresses. USPS ZIP Codes are not areal features but a collection of mail delivery routes.

This coverage can be used for basic applications such as viewing, querying, and map output production, or to provide a basemap to support graphical overlays and analyses of geospatial data.

NEW!: Use the new Business Account Number lookup tool. SUMMARYThis dataset includes the locations of businesses that pay taxes to the City and County of San Francisco. Each registered business may have multiple locations and each location is a single row. The Treasurer & Tax Collector’s Office collects this data through business registration applications, account update/closure forms, and taxpayer filings. Business locations marked as “Administratively Closed” have not filed or communicated with TTX for 3 years, or were marked as closed following a notification from another City and County Department. The data is collected to help enforce the Business and Tax Regulations Code including, but not limited to: Article 6, Article 12, Article 12-A, and Article 12-A-1. http://sftreasurer.org/registration.HOW TO USE THIS DATASETSystem migration in 2014: When the City transitioned to a new system in 2014, only active business accounts were migrated. As a result, any businesses that had already closed by that point were not included in the current dataset.2018 account cleanup: In 2018, TTX did a major cleanup of dormant and unresponsive accounts and closed approximately 40,000 inactive businesses.To learn more about using this dataset watch this video.To update your listing or look up your BAN see this FAQ: Registered Business Locations ExplainerData pushed to ArcGIS Online on November 9, 2025 at 6:13 AM by SFGIS.Data from: https://data.sfgov.org/d/g8m3-pdisDescription of dataset columns:

 UniqueID
 Unique formula: @Value(ttxid)-@Value(certificate_number)


 Business Account Number
 Seven digit number assigned to registered business accounts


 Location Id
 Location identifier


 Ownership Name
 Business owner(s) name


 DBA Name
 Doing Business As Name or Location Name


 Street Address
 Business location street address


 City
 Business location city


 State
 Business location state


 Source Zipcode
 Business location zip code


 Business Start Date
 Start date of the business


 Business End Date
 End date of the business


 Location Start Date
 Start date at the location


 Location End Date
 End date at the location, if closed


 Administratively Closed
 Business locations marked as “Administratively Closed” have not filed or communicated with TTX for 3 years, or were marked as closed following a notification from another City and County Department.


 Mail Address
 Address for mailing


 Mail City
 Mailing address city



 Mail State
 Mailing address state



 Mail Zipcode
 Mailing address zipcode


 NAICS Code
 The North American Industry Classification System (NAICS) is a standard used by Federal statistical agencies for the purpose of collecting, analyzing and publishing statistical data related to the U.S. business economy. A subset of these are options on the business registration form used in the administration of the City and County's tax code. The registrant indicates the business activity on the City and County's tax registration forms.

See NAICS Codes tab in the attached data dictionary under About > Attachments.

 NAICS Code Description
 The Business Activity that the NAICS code maps on to ("Multiple" if there are multiple codes indicated for the business).


 NAICS Code Descriptions List
 A list of all NAICS code descriptions separated by semi-colon


 LIC Code
 The LIC code of the business, if multiple, separated by spaces


 LIC Code Description
 The LIC code description ("Multiple" if there are multiple codes for a business)


 LIC Code Descriptions List
 A list of all LIC code descriptions separated by semi-colon


 Parking Tax
 Whether or not this business pays the parking tax


 Transient Occupancy Tax
 Whether or not this business pays the transient occupancy tax


 Business Location
 The latitude and longitude of the business location for mapping purposes.


 Business Corridor
 The Business Corridor in which the the business location falls, if it is in one. Not all business locations are in a corridor.

Boundary reference: https://data.sfgov.org/d/h7xa-2xwk

 Neighborhoods - Analysis Boundaries
 The Analysis Neighborhood in which the business location falls. Not applicable outside of San Francisco.

Boundary reference: https://data.sfgov.org/d/p5b7-5n3h

 Supervisor District
 The Supervisor District in which the business location falls. Not applicable outside of San Francisco. Boundary reference: https://data.sfgov.org/d/xz9b-wyfc


 Community Benefit District
 The Community Benefit District in which the business location falls. Not applicable outside of San Francisco. Boundary reference: https://data.sfgov.org/d/c28a-f6gs


 data_as_of
 Timestamp the data was updated in the source system


 data_loaded_at
 Timestamp the data was loaded here (open data portal)


 SF Find Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'SF Find Neighborhoods' (6qbp-sg9q) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Police Districts
 This column was automatically created in order to record in what polygon from the dataset 'Current Police Districts' (qgnn-b9vv) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Supervisor Districts
 This column was automatically created in order to record in what polygon from the dataset 'Current Supervisor Districts' (26cr-cadq) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Analysis Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'Analysis Neighborhoods' (ajp5-b2md) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'Neighborhoods' (jwn9-ihcz) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.

Note: If no description was provided by DataSF, the cell is left blank. See the source data for more information.

SUMMARY The Air Pollutant Exposure Zone (APEZ) map identifies areas in San Francisco where air modeling indicates higher levels of air pollution. This map is required to be updated every 5 years, as established in San Francisco Health Code article 38. The 2025 Air Pollutant Exposure Zone map is an update to the 2020 map. Additional information may be found at Air Quality Review | SF Planning. The map can be viewed on the San Francisco Property Information Map. HOW THE DATASET IS CREATED The 2025 APEZ update modeled areas of the city where: particulate matter (PM2.5) is greater than or equal to 9 µg/m3 or where the risk of cancer from air pollutants is greater than or equal to 100 in a million; in health vulnerable ZIP codes (94102, 94103, 94110, 94124, and 94134), where the risk of cancer from air pollutants is greater than or equal to 90 in a million; locations within 500 feet of freeways; or locations within 1,000 feet of roadways with a daily average of 100,000 vehicles. To learn more, visit San Francisco Citywide Health Risk Assessment: Technical Support Documentation, Air Pollutant Exposure Zone Handout and Air Pollutant Exposure Zone Story Map. UPDATE PROCESS Updated every five years. HOW TO USE THIS DATASET The City uses this dataset as follows. San Francisco Health Code article 38 requires new developments or major renovations within the APEZ with sensitive receptors, like housing or preschools, to include a ventilation system that sufficiently removes fine particulate matter (minimum efficiency reporting volume [MERV] 13 or equivalent filtration). In addition, Environment Code Chapter 25 requires public agencies implementing projects within the APEZ to use the cleanest construction equipment available. The City’s environmental review under the California Environmental Quality Act (CEQA) uses the APEZ in its analysis to mandate the use of clean construction equipment, when applicable. To learn more, visit Air Quality Review | SF Planning.

This dataset includes all itemized monetary contributions ($100 or more) e-filed on Fair Political Practices Commission (FPPC) Form 460 Schedule "A" Monetary Contributions from 1998 to the present.The data is current as of the last modified date on this dataset.See the data key for column definitions: https://data.sfgov.org/Ethics/Campaign-Finance-Data-Key/wygs-cc76

A. SUMMARYThis data represents the boundaries of City-owned lands maintained in the City's Facility System of Record (FSR). Note: Not all lands are within the City and County proper. The City owns properties outside of its boundaries, including lands managed by SF Recreation and Parks, SF Public Utilities Commission, and other agencies. Certain lands are managed by following agencies which are not directly part of the City and County of San Francisco, but are included here for reference: San Francisco Housing Authority (SFHA), San Francisco Office of Community Investment and Infrastructure (OCII), and City College of San Francisco.B. HOW THE DATASET IS CREATEDThe Enterprise GIS program in the Department of Technology is the technical custodian of the FSR. This team creates and maintains this dataset in conjunction with the Real Estate Division and the Capital Planning Program of the City Administrator’s Office, who act as the primary business data stewards for this data. C. UPDATE PROCESSThere are a handful of events that may trigger changes to this dataset:1. The sale of a property2. The leasing of a property3. The purchase of a property4. The change in jurisdiction of a property (e.g. from MTA to DPW)5. The removal or improvement of the propertyEach of these changes triggers a workflow that updates the FSR. The Real Estate Division and Capital Planning make updates on an ongoing basis. The full dataset is reviewed quarterly to ensure nothing is missing or needs to be corrected. Updates to the data, once approved, are immediately reflected in the internal system and are updated here in the open dataset on a monthly basis.D. HOW TO USE THIS DATASETSee here for an interactive map of all the City lands in this dataset. To track the facilities on City lands, join this dataset to the City Facilities dataset using the land_id field. If you see an error in the data, you can submit a change request with the relevant information to dtis.helpdesk@sfgov.org. Please be as specific about the error as you can (including relevant land_id(s)). E. RELATED DATASETSCity FacilitiesData pushed to ArcGIS Online on November 1, 2025 at 6:00 AM by SFGIS.Data from: https://data.sfgov.org/d/gtnh-hgvsDescription of dataset columns:

 land_id
 Unique Identifier


 land_name
 Name of land. i.e., property owned by City and County of San Francisco


 dept_id
 Foreign key to Department table in Facility System of Record (FSR) database


 address
 Address of City Land


 city
 Address City


 zip
 Address ZIP Code


 category
 Category of department (useful for mapping purposes)


 department_name
 Name of Department with Jurisdiction


 shape
 Geometry of City Land encoded as multipolygon


 data_last_updated
 Timestamp when the record (row) was last updated in the source system


 data_as_of
 Timestamp when the record (row) was last refreshed in the source system


 data_loaded_at
 Timestamp when the record (row) was was last updated here (in the data portal)

Note: If no description was provided by DataSF, the cell is left blank. See the source data for more information.

Context

The Bay Area Bike Share enables quick, easy, and affordable bike trips around the San Francisco Bay Area. They make regular open data releases (this dataset is a transformed version of the data from this link), plus maintain a real-time API.

Content

station.csv - Contains data that represents a station where users can pickup or return bikes.

status.csv - data about the number of bikes and docks available for given station and minute.

trips.csv - Data about individual bike trips

weather.csv - Data about the weather on a specific day for certain zip codes

Acknowledgements

This dataset is a transformed version of the Bay area bike share data.

Inspiration

• How does weather impact bike trips?
• How do bike trip patterns vary by time of day and the day of the week?

Summary

Geojson files used to visualize geospatial layers relevant to identifying and assessing trucking fleet decarbonization opportunities with the MIT Climate & Sustainability Consortium's Geospatial Trucking Industry Decarbonization Explorer (Geo-TIDE) tool.

Relevant Links

Link to the online version of the tool (requires creation of a free user account).

Link to GitHub repo with source code to produce this dataset and deploy the Geo-TIDE tool locally.

Funding

This dataset was produced with support from the MIT Climate & Sustainability Consortium.

Original Data Sources

These geojson files draw from and synthesize a number of different datasets and tools. The original data sources and tools are described below:

Filename(s) Description of Original Data Source(s) Link(s) to Download Original Data License and Attribution for Original Data Source(s)

faf5_freight_flows/*.geojson

trucking_energy_demand.geojson

highway_assignment_links_*.geojson

infrastructure_pooling_thought_experiment/*.geojson

Regional and highway-level freight flow data obtained from the Freight Analysis Framework Version 5. Shapefiles for FAF5 region boundaries and highway links are obtained from the National Transportation Atlas Database. Emissions attributes are evaluated by incorporating data from the 2002 Vehicle Inventory and Use Survey and the GREET lifecycle emissions tool maintained by Argonne National Lab.

Shapefile for FAF5 Regions

Shapefile for FAF5 Highway Network Links

FAF5 2022 Origin-Destination Freight Flow database

FAF5 2022 Highway Assignment Results

Attribution for Shapefiles: United States Department of Transportation Bureau of Transportation Statistics National Transportation Atlas Database (NTAD). Available at: https://geodata.bts.gov/search?collection=Dataset.

License for Shapefiles: This NTAD dataset is a work of the United States government as defined in 17 U.S.C. § 101 and as such are not protected by any U.S. copyrights. This work is available for unrestricted public use.

Attribution for Origin-Destination Freight Flow database: National Transportation Research Center in the Oak Ridge National Laboratory with funding from the Bureau of Transportation Statistics and the Federal Highway Administration. Freight Analysis Framework Version 5: Origin-Destination Data. Available from: https://faf.ornl.gov/faf5/Default.aspx. Obtained on Aug 5, 2024. In the public domain.

Attribution for the 2022 Vehicle Inventory and Use Survey Data: United States Department of Transportation Bureau of Transportation Statistics. Vehicle Inventory and Use Survey (VIUS) 2002 [supporting datasets]. 2024. https://doi.org/10.21949/1506070

Attribution for the GREET tool (original publication): Argonne National Laboratory Energy Systems Division Center for Transportation Research. GREET Life-cycle Model. 2014. Available from this link.

Attribution for the GREET tool (2022 updates): Wang, Michael, et al. Summary of Expansions and Updates in GREET® 2022. United States. https://doi.org/10.2172/1891644

grid_emission_intensity/*.geojson

Emission intensity data is obtained from the eGRID database maintained by the United States Environmental Protection Agency.

eGRID subregion boundaries are obtained as a shapefile from the eGRID Mapping Files database.

eGRID database

Shapefile with eGRID subregion boundaries

Attribution for eGRID data: United States Environmental Protection Agency: eGRID with 2022 data. Available from https://www.epa.gov/egrid/download-data. In the public domain.

Attribution for shapefile: United States Environmental Protection Agency: eGRID Mapping Files. Available from https://www.epa.gov/egrid/egrid-mapping-files. In the public domain.

US_elec.geojson

US_hy.geojson

US_lng.geojson

US_cng.geojson

US_lpg.geojson

Locations of direct current fast chargers and refueling stations for alternative fuels along U.S. highways. Obtained directly from the Station Data for Alternative Fuel Corridors in the Alternative Fuels Data Center maintained by the United States Department of Energy Office of Energy Efficiency and Renewable Energy.

US_elec.geojson

US_hy.geojson

US_lng.geojson

US_cng.geojson

US_lpg.geojson

Attribution: U.S. Department of Energy, Energy Efficiency and Renewable Energy. Alternative Fueling Station Corridors. 2024. Available from: https://afdc.energy.gov/corridors. In the public domain.

These data and software code ("Data") are provided by the National Renewable Energy Laboratory ("NREL"), which is operated by the Alliance for Sustainable Energy, LLC ("Alliance"), for the U.S. Department of Energy ("DOE"), and may be used for any purpose whatsoever.

daily_grid_emission_profiles/*.geojson

Hourly emission intensity data obtained from ElectricityMaps.

Original data can be downloaded as csv files from the ElectricityMaps United States of America database

Shapefile with region boundaries used by ElectricityMaps

License: Open Database License (ODbL). Details here: https://www.electricitymaps.com/data-portal

Attribution for csv files: Electricity Maps (2024). United States of America 2022-23 Hourly Carbon Intensity Data (Version January 17, 2024). Electricity Maps Data Portal. https://www.electricitymaps.com/data-portal.

Attribution for shapefile with region boundaries: ElectricityMaps contributors (2024). electricitymaps-contrib (Version v1.155.0) [Computer software]. https://github.com/electricitymaps/electricitymaps-contrib.

gen_cap_2022_state_merged.geojson

trucking_energy_demand.geojson

Grid electricity generation and net summer power capacity data is obtained from the state-level electricity database maintained by the United States Energy Information Administration.

U.S. state boundaries obtained from this United States Department of the Interior U.S. Geological Survey ScienceBase-Catalog.

Annual electricity generation by state

Net summer capacity by state

Shapefile with U.S. state boundaries

Attribution for electricity generation and capacity data: U.S. Energy Information Administration (Aug 2024). Available from: https://www.eia.gov/electricity/data/state/. In the public domain.

electricity_rates_by_state_merged.geojson

Commercial electricity prices are obtained from the Electricity database maintained by the United States Energy Information Administration.

Electricity rate by state

Attribution: U.S. Energy Information Administration (Aug 2024). Available from: https://www.eia.gov/electricity/data.php. In the public domain.

demand_charges_merged.geojson

demand_charges_by_state.geojson

Maximum historical demand charges for each state and zip code are derived from a dataset compiled by the National Renewable Energy Laboratory in this this Data Catalog.

Historical demand charge dataset

The original dataset is compiled by the National Renewable Energy Laboratory (NREL), the U.S. Department of Energy (DOE), and the Alliance for Sustainable Energy, LLC ('Alliance').

Attribution: McLaren, Joyce, Pieter Gagnon, Daniel Zimny-Schmitt, Michael DeMinco, and Eric Wilson. 2017. 'Maximum demand charge rates for commercial and industrial electricity tariffs in the United States.' NREL Data Catalog. Golden, CO: National Renewable Energy Laboratory. Last updated: July 24, 2024. DOI: 10.7799/1392982.

eastcoast.geojson

midwest.geojson

la_i710.geojson

h2la.geojson

bayarea.geojson

saltlake.geojson

northeast.geojson

Highway corridors and regions targeted for heavy duty vehicle infrastructure projects are derived from a public announcement on February 15, 2023 by the United States Department of Energy.

The shapefile with Bay area boundaries is obtained from this Berkeley Library dataset.

The shapefile with Utah county boundaries is obtained from this dataset from the Utah Geospatial Resource Center.

Shapefile for Bay Area country boundaries

Shapefile for counties in Utah

Attribution for public announcement: United States Department of Energy. Biden-Harris Administration Announces Funding for Zero-Emission Medium- and Heavy-Duty Vehicle Corridors, Expansion of EV Charging in Underserved Communities (2023). Available from https://www.energy.gov/articles/biden-harris-administration-announces-funding-zero-emission-medium-and-heavy-duty-vehicle.

Attribution for Bay area boundaries: San Francisco (Calif.). Department Of Telecommunications and Information Services. Bay Area Counties. 2006. In the public domain.

Attribution for Utah boundaries: Utah Geospatial Resource Center & Lieutenant Governor's Office. Utah County Boundaries (2023). Available from https://gis.utah.gov/products/sgid/boundaries/county/.

License for Utah boundaries: Creative Commons 4.0 International License.

incentives_and_regulations/*.geojson

State-level incentives and regulations targeting heavy duty vehicles are collected from the State Laws and Incentives database maintained by the United States Department of Energy's Alternative Fuels Data Center.

Data was collected manually from the State Laws and Incentives database.

Attribution: U.S. Department of Energy, Energy Efficiency and Renewable Energy, Alternative Fuels Data Center. State Laws and Incentives. Accessed on Aug 5, 2024 from: https://afdc.energy.gov/laws/state. In the public domain.

These data and software code ("Data") are provided by the National Renewable Energy Laboratory ("NREL"), which is operated by the Alliance for Sustainable Energy, LLC ("Alliance"), for the U.S. Department of Energy ("DOE"), and may be used for any purpose whatsoever.

costs_and_emissions/*.geojson

diesel_price_by_state.geojson

trucking_energy_demand.geojson

Lifecycle costs and emissions of electric and diesel trucking are evaluated by adapting the model developed by Moreno Sader et al., and calibrated to the Run on Less dataset for the Tesla Semi collected from the 2023 PepsiCo Semi pilot by the North American Council for Freight Efficiency.

In

List of dpw maintained street trees including: Planting date, species, and locationData pushed to ArcGIS Online on November 9, 2025 at 5:27 AM by SFGIS.Data from: https://data.sfgov.org/d/tkzw-k3nqDescription of dataset columns:

 TreeID
 Unique id of tree


 qLegalStatus
 Legal staus: Permitted or DPW maintained


 qSpecies
 Species of tree


 qAddress
 Address of Tree


 SiteOrder
 Order of tree at address where multiple trees are at same address. Trees are ordered in ascending address order


 qSiteInfo
 description of location of tree


 PlantType
 Landscaping or Tree


 qCaretaker
 Agency or person that is primary caregiver to tree. Owner of Tree


 qCareAssistant
 Agency or person that is secondary caregiver to tree


 PlantDate
 date tree was planted


 DBH
 depth, ,height


 PlotSize
 date tree was planted


 PermitNotes
 Tree permit number reference


 XCoord
 CA State Plane III


 YCoord
 CA State Plane III


 Latitude
 WGS84


 Longitude
 WGS84


 Location
 Location formatted for mapping


 Fire Prevention Districts
 NaN


 Police Districts
 NaN


 Supervisor Districts
 NaN


 Zip Codes
 NaN


 Neighborhoods (old)



 Analysis Neighborhoods
 NaN

Note: If no description was provided by DataSF, the cell is left blank. See the source data for more information.

A. SUMMARY A list of street centerlines, including both active and retired streets. These centerlines are identified by their Centerline Network Number ("CNN").B. HOW THE DATASET IS CREATED This data is extracted from the Department of Public Works Basemap. Supervisor District and Analysis Neighborhood are added during the loading process. These boundaries utilize the centroid (middle) of the line to determine the district or neighborhood.C. UPDATE PROCESS This dataset refreshes daily, though the data may not change every day.D. HOW TO USE THIS DATASET Note 1: The Class Code field is used for symbolization:1 = Freeway2 = Major street/Highway3 = Arterial street4 = Collector Street5 = Residential Street6 = Freeway Ramp0 = Other (private streets, paper street, etc.)E. RELATED DATASETS Understanding street-level dataData pushed to ArcGIS Online on November 10, 2025 at 3:25 AM by SFGIS.Data from: https://data.sfgov.org/d/3psu-pn9hDescription of dataset columns:

 cnn
 Centerline Network Number - unique identifier for dataset


 lf_fadd
 From address number on left side of street, the lowest number in the address range


 lf_toadd
 To address number on left side of street, the highest number in the address range


 rt_fadd
 From address number on right side of street, the lowest number in the address range


 rt_toadd
 To address number on right side of street, the highest number in the address range


 street
 Street name without street type


 st_type
 Street Type (AVE, ST, BLVD, et al.)


 f_st
 The street name of the segment intersects at its beginning.


 t_st
 The street name of the segment intersects at its end.


 f_node_cnn
 Centerline Network Number for the node/intersection that the street segment begins from.


 t_node_cnn
 Centerline Network Number for the node/intersection that the street segment ends on.


 accepted
 Accepted by City and County of San Francisco for maintenance.


 active
 Active street segment, i.e., not retired.


 classcode
 Classification code for street segment. Used for symbolization: 1 = Freeway 2 = Major street/Highway 3 = Arterial street 4 = Collector Street 5 = Residential Street 6 = Freeway Ramp 0 = Other (private streets, paper street, etc.)


 date_added
 Date added to dataset by Public Works.


 date_altered
 Date altered to dataset by Public Works.


 date_dropped
 Date dropped to dataset by Public Works.


 gds_chg_id_add
 The internal change transaction id when the segment was added.


 gds_chg_id_altered
 The internal change transaction id when the segment was altered.


 gds_chg_id_dropped
 The internal change transaction id when the segment was dropped/retired.


 jurisdiction
 Agency with jurisdiction over the segment, if any.


 layer
 Derived from the source AutoCAD drawing, this field indicates the category of segment. Definitions for each of the values: Freeways such as 80, 280 and 101. Paper, the centerline segment is present on Assessor and/or Public Works map, but is not an actual street in reality. Paper_fwys, the centerline segment is present on Assessor and/or Public Works map, but is not an actual street in reality, and is under or near a freeway. Paper_water, the centerline segment is present on Assessor and/or Public Works map, but is not an actual street in reality, and is under water in the Bay. PARKS, street segement maintained by Recreation and Park Department, e.g., in Golden Gate Park. Parks_NPS_FtMaso, street segement maintained by the National Park Service within Fort Mason. Parks_NPS_Presid, street segement maintained by the National Park Service within the Presidio. Private, street segment is not maintained by the City and is not on an Assessor or Public Works map. Private_parking, street segment is not maintained by the City and is not on an Assessor or Public Works map, and is a parking lot. PSEUDO, street segment created for use in addressing. Streets, standard street centerline segement. Streets_HuntersP, standard street centerline segement within the Hunters Point Shipyard area. Streets_Pedestri, standard street centerline segement, but pedestrian access only. Streets_TI, standard street centerline segement within Treasure Island. Streets_YBI, standard street centerline segement within Yerba Buena Island. UPROW, Unpaved Right of Way street centerline segment.


 nhood
 SFRealtor-defined neighborhood that the segment is primarily intersects


 oneway
 Indicates if street segment is a one way street: possible values are F (the segment is one way beginning at the "from" street) , T (the segment is one way beginning at the "to" street), or B (traffic is legal in "both" directions)


 street_gc
 Street name without street type, with the numbered streets with leading zeroes dropped to facilitate geocoding


 streetname
 Full street name and street type


 streetname_gc
 Full street name and street type, with the numbered streets with leading zeroes dropped to facilitate geocoding


 zip_code
 ZIP Code that street segment falls in.


 analysis_neighborhood
 current analysis neighborhood


 supervisor_district
 current supervisor district


 line
 Geometry


 data_as_of
 Timestamp the data was updated in the source system


 data_loaded_at
 Timestamp the data was loaded to the open data portal

Note: If no description was provided by DataSF, the cell is left blank. See the source data for more information.

The catch basin data is collected by SFDPW Hydraulics Engineering and SFPUC Wastewater Enterprise, Collection System Division engineers, drafters and operators. The data is collected from sewer reference and construction documents and field surveys. You can learn more about how the City's wastewater collection system works here: http://www.sfwater.org/index.aspx?page=399Data pushed to ArcGIS Online on November 10, 2025 at 3:20 AM by SFGIS.Data from: https://data.sfgov.org/d/jtgq-b7c5Description of dataset columns:

 DPW_Node_ID



 PUC_Maximo_Asset_ID
 NaN


 System_Use_Code
 NaN


 System_Use
 NaN


 Drain_Type
 NaN


 POINT_X
 NaN


 POINT_Y
 NaN


 PRIORITY_STATUS
 NaN


 Location



 analysis_neighborhood



 supervisor_district



 data_as_of
 Timestamp the data was updated in the source system


 data_loaded_at
 Timestamp the data was loaded to the open data portal


 Neighborhoods_from_fyvs_ahh9 2
 This column was automatically created in order to record in what polygon from the dataset 'Neighborhoods_from_fyvs_ahh9' (f58d-8dbm) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 (old) SF Find Neighborhoods 2
 This column was automatically created in order to record in what polygon from the dataset '(old) SF Find Neighborhoods' (vtsz-7cme) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Supervisorial_Districts_Waterline_data_from_7pkg_wer3 2
 This column was automatically created in order to record in what polygon from the dataset 'Supervisorial_Districts_Waterline_data_from_7pkg_wer3' (uruc-drv6) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Neighborhoods_from_6ia5_2f8k 2
 This column was automatically created in order to record in what polygon from the dataset 'Neighborhoods_from_6ia5_2f8k' (6qbp-sg9q) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Supervisor Districts 2
 This column was automatically created in order to record in what polygon from the dataset 'Supervisor Districts' (rxqg-mtj9) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Police Districts 2
 This column was automatically created in order to record in what polygon from the dataset 'Current Police Districts' (jx4q-fizf) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Neighborhoods - Analysis Boundaries 2
 This column was automatically created in order to record in what polygon from the dataset 'Neighborhoods - Analysis Boundaries' (ajp5-b2md) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Neighborhoods (old) 2
 This column was automatically created in order to record in what polygon from the dataset 'Neighborhoods (old)' (fyvs-ahh9) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Police Districts 2
 This column was automatically created in order to record in what polygon from the dataset 'Police Districts' (p5aj-wyqh) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Fire Prevention Districts 2
 This column was automatically created in order to record in what polygon from the dataset 'Fire Prevention Districts' (yftq-j783) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Zip Codes 2
 This column was automatically created in order to record in what polygon from the dataset 'Zip Codes' (bh8s-q3mv) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Neighborhoods
 This column was automatically created in order to record in what polygon from the dataset 'Neighborhoods' (jwn9-ihcz) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Police Districts 3
 This column was automatically created in order to record in what polygon from the dataset 'Current Police Districts' (qgnn-b9vv) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.


 Current Supervisor Districts
 This column was automatically created in order to record in what polygon from the dataset 'Current Supervisor Districts' (26cr-cadq) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.

Note: If no description was provided by DataSF, the cell is left blank. See the source data for more information.

This dataset includes all itemized monetary contributions ($100 or more) e-filed on Fair Political Practices Commission (FPPC) Form 460 Schedule "A" Monetary Contributions from 1998 to the present.The data is current as of the last modified date on this dataset.See the data key for column definitions: https://data.sfgov.org/Ethics/Campaign-Finance-Data-Key/wygs-cc76