***As of November 2023, this map has been updated to use a new format. For details, please see here.*** For up to date data starting in 2018, please go to the new dataset at: https://data.sfgov.org/d/wg3w-h783

As of May 2018, the feed from the legacy mainframe CABLE was discontinued. It was extremely prone to issues and caused many delays in data accessibility. The new dataset linked above comes from the Crime Data Warehouse, a more reliable data system maintained by the Police Department.

This data will undergo a minor update to conform more closely to the schema of the new dataset. We will post a change notice when that work is planned. This change will not include adding new fields or backfilling data. It is provided as is. We are keeping data from the two systems separate to make it transparent to data users that there were fundamental changes.

A. SUMMARY
Fire Calls-For-Service includes all fire units' responses to 911 calls from the city's Computer-Aided Dispatch (“CAD”) system. This includes responses to Medical Incidents requiring EMS staff. Each record includes the call number, incident number, address, unit identifier, call type, and disposition. All relevant time intervals are also included. Because this dataset is based on responses, and since most calls involve multiple units, there are multiple records for each call number. Addresses are associated with an intersection or call box, not a specific address.

B. HOW THE DATASET IS CREATED
This dataset is an extract from the Department of Emergency Management’s computer-aided dispatch system. The dataset is enhanced with fire-department specific information before being uploaded to the open data portal.

C. UPDATE PROCESS
This dataset updates daily via automated data pipeline.

D. HOW TO USE THIS DATASET
This dataset is based on responses, and since most calls involve multiple units, there are multiple records for each call number. The most common call types are Medical Incidents, Alarms, Structure Fires, and Traffic Collisions.

E. RELATED DATASETS
Fire Incidents

Mechanical street sweeping and street cleaning schedule managed by San Francisco Public Works

A. SUMMARY
Source of data for the Shelter Reservation Waitlist. Please view the below website for more information on the shelter reservation system:
- Shelter Reservation Website

For more information on Housing Assistance, please view the website below:
- Referrals and Housing Assistance

B. HOW TO USE THIS DATASET
Your waitlist ID is your eight-digit birthdate (MMDDYYYY) and your initials. For example, if your name is Michael Jackson and you were born on August 29, 1958, your waitlist ID is 08291958MJ.

It may take 24 hours for your name to show up on the list after you register.

If you are at the top of the waitlist there will be a note in the row with your Waitlist ID. Since some beds are gender-specific, it might be your turn even if your name does not appear in the first few rows. Make sure you search your waitlist ID to see if there are instructions to call in. Learn how to claim your bed on the FAQs page.

If you haven’t already registered, get instructions about how to sign up online or by phone. You can only have one entry in the waitlist at one time.

"A. SUMMARY Parking regulations by blockface for the City of San Francisco. Includes the following regulations: Residential Parking Permits, Time limits, Government Permit, No overnight, Oversized Vehicle. Does not include non metered color curb or curb cuts.
Update as of 1/1/2018: started recording No parking any time (regulations like ""TOW AWAY NO PARKING""), Limited No Parking (tow-away or no parking for certain periods of the day),

B. METHODOLOGY Mix of manual updates and data compilation.

C. UPDATE FREQUENCY Updated as MTA Board resolutions are passed that impact parking regulations.

D. OTHER CRITICAL INFO This dataset has not been comprehesively updated or vetted for accuracy. Dataset does not include color curb regulations such as loading zones or blue zones. Does not include detailed information for metered parking such as cap color or operating hours, which is contained in a separate relational database maintained by SFpark. No parking any time blockfaces were verified using Google Streetview, and only for Mission Bay blockfaces (Feburary 2017). "

A. SUMMARY
This dataset stores upcoming and current streets closure affected by shared spaces, some special events, and a portion of construction permitted by San Francisco Municipal Transportation Agency (SFMTA). This dataset doesn’t include street closure managed by other city department such as Public Works or the Police Department.

B. HOW THE DATASET IS CREATED
Exported from the Street Closure Saleforce database which is maintained by the SFMTA ISCOTT unit, and converted to geometry of streets and intersections based on closed street extent description.

C. UPDATE PROCESS
Database is updated constantly. This report is issued daily.

D. HOW TO USE THIS DATASET
Please be aware this dataset only contains temporary street closures 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).

A. SUMMARY
This table contains all crashes resulting in an injury in the City of San Francisco. Fatality year-to-date crash data is obtained from the Office of the Chief Medical Examiner (OME) death records, and only includes those cases that meet the San Francisco Vision Zero Fatality Protocol maintained by the San Francisco Department of Public Health (SFDPH), San Francisco Police Department (SFPD), and San Francisco Municipal Transportation Agency (SFMTA). Injury crash data is obtained from SFPD’s Interim Collision System for 2018 through the current year-to-date, Crossroads Software Traffic Collision Database (CR) for years 2013-2017 and the Statewide Integrated Transportation Record System (SWITRS) maintained by the California Highway Patrol for all years prior to 2013. Only crashes with valid geographic information are mapped. All geocodable crash data is represented on the simplified San Francisco street centerline model maintained by the Department of Public Works (SFDPW). Collision injury data is queried and aggregated on a quarterly basis. Crashes occurring at complex intersections with multiple roadways are mapped onto a single point and injury and fatality crashes occurring on highways are excluded.

The crash, party, and victim tables have a relational structure. The traffic crashes table contains information on each crash, one record per crash. The party table contains information from all parties involved in the crashes, one record per party. Parties are individuals involved in a traffic crash including drivers, pedestrians, bicyclists, and parked vehicles. The victim table contains information about each party injured in the collision, including any passengers. Injury severity is included in the victim table.

For example, a crash occurs (1 record in the crash table) that involves a driver party and a pedestrian party (2 records in the party table). Only the pedestrian is injured and thus is the only victim (1 record in the victim table).

To learn more about the traffic injury datasets, see the TIMS documentation

B. HOW THE DATASET IS CREATED
Traffic crash injury data is collected from the California Highway Patrol 555 Crash Report as submitted by the police officer within 30 days after the crash occurred. All fields that match the SWITRS data schema are programmatically extracted, de-identified, geocoded, and loaded into TransBASE. See Section D below for details regarding TransBASE.

C. UPDATE PROCESS
After review by SFPD and SFDPH staff, the data is made publicly available approximately a month after the end of the previous quarter (May for Q1, August for Q2, November for Q3, and February for Q4).

D. HOW TO USE THIS DATASET
This data is being provided as public information as defined under San Francisco and California public records laws. SFDPH, SFMTA, and SFPD cannot limit or restrict the use of this data or its interpretation by other parties in any way. Where the data is communicated, distributed, reproduced, mapped, or used in any other way, the user should acknowledge TransBASE.sfgov.org as the source of the data, provide a reference to the original data source where also applicable, include the date the data was pulled, and note any caveats specified in the associated metadata documentation provided. However, users should not attribute their analysis or interpretation of this data to the City of San Francisco. While the data has been collected and/or produced for the use of the City of San Francisco, it cannot guarantee its accuracy or completeness. Accordingly, the City of San Francisco, including SFDPH, SFMTA, and SFPD make no representat

A. SUMMARY
San Francisco International Airport Report on Monthly Passenger Traffic Statistics by Airline.

B. HOW THE DATASET IS CREATED
Data is self-reported by airlines and is only available at a monthly level

C. UPDATE PROCESS
Data updated quarterly

D. HOW TO USE THIS DATASET
Airport data is seasonal in nature, therefore any comparative analyses should be done on a period-over-period basis (i.e. January 2010 vs. January 2009) as opposed to period-to-period (i.e. January 2010 vs. February 2010). It is also important to note that fact and attribute field relationships are not always 1-to-1. For example, Passenger Counts belonging to United Airlines will appear in multiple attribute fields and are additive, which provides flexibility for the user to derive categorical Passenger Counts as desired.

A. SUMMARY Location, cap color and other key attributes of parking meters in San Francisco. Does not include operating schedules or rate schedules.

B. METHODOLOGY Updated via the SFpark data warehouse (Parking Space Inventory) by meter shop staff, with manual updates sourced from SFMTA CAD drawings and MTAB resolutions.

C. UPDATE FREQUENCY Updated weekly.

D. OTHER CRITICAL INFO For active meters only, filter for "Active_Met" = 'M" or "T". Meter operating and rate schedules are more complex and available as separate tables. Key field for joining is the Parking Space ID field.