A. SUMMARY This table includes all active and upcoming "street use" permits issued by the Department of Public Works for activities on the street surface (not underground). It lists permits that are currently active or have a start date within the next 14 days. B. HOW THE DATASET IS CREATED This dataset is the union of two other permit tables on the open data portal:

Note 1/17/2025: This dataset has been backfilled to include additional permit status and historical permit data. Please see Active Street-Use Permits if you are only interested in currently active permits. A. SUMMARY All street space permits received by SF Public Works. This includes permits in all statuses of review by Public Works, including those approved and issued as well as those pending review, closed or withdrawn. The dataset includes permits received since 1996. A street space permit grants permission to temporarily occupy a portion of a public roadway or sidewalk for building construction and other construction related work. Find out more about street space permits here. B. HOW THE DATASET IS CREATED The dataset is extracted by SF Public Works from its source system and transmitted directly to the Open Data Portal via an automated pipeline. C. UPDATE PROCESS The dataset is updated daily at 12am with a one day lag. D. HOW TO USE THIS DATASET This dataset can be used to identify the status of any street space permits received by SF Public Works since 1996. Some of the data fields are from early versions of Public Works current system and may not have been validated when first entered. Some fields such as the DBI Building Permit Application (“bpa” field) are entered by Public Works staff and are not validated against Building Permit Applications in DBI’s Permit Tracking System (PTS). A single permit may be repeated on multiple rows if it covers more than one street or location. You can use the permit_number field to identify the unique number of permits. The data_as_of field represents when the row was updated, and can be used for incremental loading of the data in conjunction with the unique_id. E. RELATED DATASETS

A. SUMMARY This dataset stores upcoming and current street closures occurring as a result of the Shared Spaces program, certain special events, and some construction work. This dataset only includes street closures permitted by the San Francisco Municipal Transportation Agency (SFMTA). It doesn’t include street closures managed by other City departments such as Public Works or the Police Department. B. HOW THE DATASET IS CREATED The data is exported from the Street Closure Salesforce database which is maintained by the SFMTA ISCOTT unit and converted to the geometry of streets and intersections based on closed street extent descriptions. C. UPDATE PROCESS Database is updated constantly. This report is issued daily. D. HOW TO USE THIS DATASET Please be aware that this dataset only contains temporary street closure events that are permitted “status = permitted” This dataset contains various types of street closures. If you are looking for a particular type please use the type field to select the appropriate closure type (Ex. type = Shared Space). E. RELATED DATASETS,

A. SUMMARY This dataset contains a list of intersections impacted by upcoming and current street closures occurring as a result of the Shared Spaces program, certain special events, and some construction work. This dataset only includes street closures permitted by the San Francisco Municipal Transportation Agency (SFMTA). It doesn’t include street closures managed by other City departments such as Public Works or the Police Department. B. HOW THE DATASET IS CREATED The data is exported from the Street Closure Salesforce database which is maintained by the SFMTA ISCOTT unit and converted to the geometry of streets and intersections based on closed street extent descriptions. C. UPDATE PROCESS Database is updated constantly. This report is issued daily. D. HOW TO USE THIS DATASET Please be aware that this dataset only contains temporary street closure events that are permitted (“status = permitted”). This dataset contains various types of street closures. If you are looking for a particular type please use the TYPE field to select the appropriate closure type (Ex. type = Shared Space). E. RELATED DATASETS,

A. SUMMARY In compliance with CA Government Code 6270.5 (passed via SB 272), the City must publish a catalog of enterprise systems that collect data about the public. There are certain exceptions to this detailed in the Government Code. The code is available here. B. HOW THE DATASET IS CREATED This dataset is collated through 2 ways: 1. Ongoing updates are made throughout the year to reflect new or retired systems, this process involves DataSF staff reconciling records at the request of departments 2. Annual bulk updates - departments review their inventories and identify changes and updates and submit those to DataSF for a once a year bulk update - not all departments will have changes or their changes will have been captured over the course of the prior year already as ongoing updates C. UPDATE PROCESS The dataset changes infrequently and is uploaded manually as needed by DataSF staff D. HOW TO USE THIS DATASET Companion dataset inventory dataset A companion dataset of inventoried and published datasets can be accessed online as well.

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 = Freeway 2 = Major street/Highway 3 = Arterial street 4 = Collector Street 5 = Residential Street 6 = Freeway Ramp 0 = Other (private streets, paper street, etc.) E. RELATED DATASETS

A. SUMMARY This dataset is list of all active Place of Entertainment permits granted by the San Francisco Entertainment Commission. B. HOW THE DATASET IS CREATED After a new permit applicant has completed the necessary processes and has been granted a Place of Entertainment permit by the San Francisco Entertainment Commission, the business and permit information is logged and tracked through this dataset. C. UPDATE PROCESS Newly granted permits are manually input by EC staff as they are received. This dataset is updated automatically by DataSF daily D. HOW TO USE THIS DATASET This dataset will be used to determine location of active Place of Entertainment permits.

A. SUMMARY A Taxi A-Card is a permit issued to taxi drivers operating in San Francisco. This dataset contains DMV, SFO and SFMTA status information for drivers’ A-cards. Taxi data providers can integrate this data to verify A-Card validity and ensure compliance. B. HOW THE DATASET IS CREATED This data is pulled from SFMTA Salesforce, which is integrated with SFO Ground Transportation Management System (GTMS). C. UPDATE PROCESS Full update of all driver records daily with the current status in Salesforce. D. HOW TO USE THIS DATASET When the A‑card expiration field is blank, it indicates that the driver’s A‑card has already expired.

,This dataset contains information on inspections for building permits in the Town of Cary. This is the list of all permit inspections since 2015 in our building permits system. It is loosely based on the BLDS (permitdata.org) specification. At this time there is not a clean mapping between the Town of Cary inspection types and the InspTypeMapped values provided in the specification. As a result, we have left the field blank. We have also provided additional fields that ensure rows in the dataset are unique. If you're looking for more information, please look to the Building Permits Online web page if the record(s) you are looking for are not in this dataset. This data is updated daily.,

A. SUMMARY This dataset provides review time metrics for the San Francisco Planning Department’s application review process. The following metrics are provided: total days to Planning approval, days to finish completeness review, days to first check plan letter, and days to complete resubmission review. Targets for each metric and outcomes relative to these targets are also included. These metrics allow for ongoing tracking for individual planning projects and for the calculation of summary statistics for Planning review timelines. There are both Project level metrics and project event level metrics in this table. You can see a dashboard which shows the City's current permit processing performance on sf.gov. B. HOW THE DATASET IS CREATED Planning application review is tracked within Planning’s Project and Permit Tracking System (PPTS). Planners enter review period start and end dates in PPTS when review milestones are reached. Review timeline data is extracted from PPTS and review timelines and outcomes are calculated and consolidated within this dataset. The dataset is generated by a data model that pulls from multiple raw Accela sources and joins them together. C. UPDATE PROCESS This dataset is updated daily overnight. D. HOW TO USE THIS DATASET Use this dataset to analyze project level timelines for planning projects or to calculate summary metrics related to the planning review and approval processes. The review metric type is defined in the ‘project stage’ column. Note that multiple rounds of completeness check review and resubmission review may occur for a single Planning project. The ‘potential error’ column flags records where data entry errors are likely present. Filter out rows where a value is entered in this column before building summary statistics. E. RELATED DATASETS