- API data.sfgov.org | Last Updated 2019-09-06T03:15:39.000Z
All political contributions of $100 or more made or delivered by the lobbyist or the lobbyist's employer, or made by a client at the behest of the lobbyist or the lobbyist's employer during the reporting period to an officer of the City and County, a candidate for such office, a committee controlled by such officer or candidate, or a committee primarily formed to support or oppose such officer or candidate, or any committee primarily formed to support or oppose a ballot measure to be voted on only in San Francisco. This includes political contributions arranged by the lobbyist, or for which the lobbyist acted as an agent or intermediary.Political contributions are disclosed by lobbyists registered with the Ethics Commission on a monthly basis. This dataset updates automatically every night.
- API data.sfgov.org | Last Updated 2019-11-17T12:08:58.000Z
Fire Incidents includes a summary of each (non-medical) incident to which the SF Fire Department responded. Each incident record includes the call number, incident number, address, number and type of each unit responding, call type (as determined by dispatch), prime situation (field observation), actions taken, and property loss.
- API data.sfgov.org | Last Updated 2019-09-06T01:36:48.000Z
These geographic designations were created to define geographic areas within San Francisco that have a higher density of vulnerable populations. These geographic designations will be used for the Health Care Services Master Plan and DPH's Community Health Needs Assessment. aov_fin - 1 = YES aov_fin - 0 = NO AOV's were defined using 2012-2016 ACS data at the census tract level and the following criteria: 1) Top 1/3rd for < 200% poverty or < 400% poverty & top 1/3rd for persons of color OR 2) Top 1/3rd for < 200% poverty or < 400% poverty & top 1/3rd for youth or seniors (65+) OR 3) Top 1/3rd for < 200% poverty or < 400% poverty & top 1/3rd for 2 other categories (unemployment, high school or less, limited English proficiency persons, linguistically isolated households, or disability) Tracts that had unstable data for an indicator were automatically given zero credit for that indicator. That is why two language variables are included in the bonus group, because there tend to be a high number of tracts with unstable data for language variables.
- API data.sfgov.org | Last Updated 2019-11-16T01:55:50.000Z
Each City elective officer who approves a contract that has a total anticipated or actual value of $100,000 or more must file this form with the Ethics Commission within five business days of approval by: (a) the City elective officer, (b) any board on which the City elective officer serves, or (c) the board of any state agency on which an appointee of the City elective officer serves. This dataset includes SFEC Form 126 Notification of Contract Approval forms which were filed on paper with the Ethics Commission. Filings without a url in the "Filing" column can be found archived on the Ethics Commission website: https://sfethics.org/ethics/category/contracts For more information, see: https://sfethics.org/compliance/city-officers/city-contracts/contract-approval-by-city-elective-officers.
- API data.sfgov.org | Last Updated 2019-10-04T19:43:44.000Z
On January 1, 2019, new local laws went into effect that established new requirements for behested payment reports. If behested payments are made at a City officer’s behest, the donors and recipients of such payments may be required to file public disclosures regarding the payments. A donor must file Form SFEC-3620 if he or she makes a behested payment, or series of behested payments in a single calendar year of $10,000 or more at the behest of an officer. The donor only needs to make this disclosure if the donor is an “interested party” in a proceeding involving the officer that solicited the payment(s). If a donor has previously filed a Form SFEC-3.620 and during the same calendar year, subsequently makes an additional behested payment at the behest of the same officer, the donor must file an additional For SFEC-3.620 only if the donor has become involved in additional proceedings or made additional contacts that were not disclosed pursuant to section 3.620(a)(1)-(3) on the initial Form SFEC-3.620. Each row on this table represents a payee listed on a subtable of a Form 3620 filed with the Ethics Commission. The parent dataset called "SFEC Form 3620 - Donors of Behested Payments Report - Filings" can be access at the following URL: "https://data.sfgov.org/City-Management-and-Ethics/SFEC-Form-3620-Donors-of-Behested-Payments-Report-/2m4y-3tcg". Join this dataset with the sub-table using the DocuSignID.
- API data.sfgov.org | Last Updated 2019-11-04T16:25:55.000Z
Privately-owned public open spaces (POPOS) are publicly accessible spaces in forms of plazas, terraces, atriums, small parks, and even snippets which are provided and maintained by private developers. In San Francisco, POPOS mostly appear in the Downtown office district area. Prior to 1985, developers provided POPOS under three general circumstances: voluntarily, in exchange for a density bonus, or as a condition of approval. The 1985 Downtown Plan created the first systemic requirements for developers to provide publicly accessible open space as a part of projects in C-3 Districts. The goal was to “provide in the downtown quality open space in sufficient quantity and variety to meet the needs of downtown workers, residents and visitors.” (See Planning Code Section 138 for regulations). Since then, project sponsors for residential projects may provide POPOS instead of their required open spaces in the Downtown Residential (DTR) and Eastern Neighborhoods (Section 135 of the Planning Code). Learn more at http://sf-planning.org/privately-owned-public-open-space-and-public-art-popos
- API data.sfgov.org | Last Updated 2019-11-17T18:05:38.000Z
SF311 cases created since 7/1/2008 with location information. Download data using 'export' button to the right. Questions? View the FAQ (http://bit.ly/311faq) and the dataset changelog (http://bit.ly/311JuneChangelog) Want to map the data in your neighborhood? Check out https://sf.connect.socrata.com/ For more information about Open311, see http://www.open311.org/.
- API data.sfgov.org | Last Updated 2019-11-17T18:05:38.000Z
SF311 cases created since 7/1/2008 with location information. For more information about Open311, see http://www.open311.org/.
- API data.sfgov.org | Last Updated 2019-11-17T18:30:49.000Z
This dataset includes police incident reports filed by officers and by individuals through self-service online reporting for non-emergency cases. Reports included are those for incidents that occurred starting January 1, 2018 onward and have been approved by a supervising officer. Please see https://bit.ly/2x7Ta2P for additional documentation. Disclaimer: The San Francisco Police Department does not guarantee the accuracy, completeness, timeliness or correct sequencing of the information as the data is subject to change as modifications and updates are completed.
- API data.sfgov.org | Last Updated 2019-09-06T02:03:17.000Z
Reference data provided by the Crime Analysis Unit at the Police Department referenced in the Police Department Incident Reports: 2018 to present (https://data.sfgov.org/d/wg3w-h783) Transmitted by the department on May 2, 2018.