
San Francisco's 2010 open data ordinance (Ord. 293-10) codified the 2009 mayoral directive as Chapter 22D of the Administrative Code, requiring departments to publish datasets on a city portal under rules and standards set by the Committee on Information Technology.
What the ordinance does
Ordinance 293-10 added Chapter 22D, "Open Data Policy," to San Francisco's Administrative Code. It cites Mayor Newsom's 2009 directive and says departments should go further to make their data available in a more timely and efficient way. The text records the ordinance as approved on November 18, 2010.
Key provisions
- Department duty. Every department, board, commission and agency must make reasonable efforts to publish datasets it controls, consistent with privacy law and city standards.
- Single portal. Datasets go on a web portal linked to the city's main website.
- Quarterly reviews. Departments review their progress on publicly requested datasets every quarter.
- COIT rules. The Committee on Information Technology must issue rules within 60 days, covering technical publishing requirements (favoring non-proprietary standards), department implementation plans that account for their datasets, and open data clauses in city contracts.
- Licensing. COIT is asked to evaluate a generic license, such as Creative Commons, that would allow copying and derivative works at no cost.
- Public comment. Before issuing rules, COIT must take public comment, including from developers who have built apps on open data.
Which guidelines it reflects
The ordinance reflects lists of holdings, sensitive information, open formats, license-free data, binding regulations and public participation. This mapping is a reading of the text; the original annotators did not tag this document.
What happened next
The chapter was amended in 2013 to create a Chief Data Officer role, departmental data coordinators and publication deadlines. See the 2013 San Francisco ordinance.
Why this matters for your business data
San Francisco's lawmakers asked for public comment from the people actually building on the data, a reminder that data value is set by its users. Buyers of private operational data ask predictable questions about formats, update frequency and licensing terms. Our guide on how to value your data lists them, and you can request a bid to see real demand.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
What is Chapter 22D?
Chapter 22D of the San Francisco Administrative Code is the city's codified open data policy. It was created by Ordinance 293-10 in 2010 and later amended. It sets the duties of departments and the body responsible for open data rules and standards.
Did the 2010 ordinance require an open license?
Not outright. It asked the Committee on Information Technology to evaluate whether a generic license such as Creative Commons was appropriate and, if so, to specify its terms in the open data standards.
Guidelines this policy reflects
- 4. Lists of Holdings
- 7. Sensitive Information
- 8. Open Formats
- 11. License-Free
- 18. Data Portals and Websites
- 25. Binding Regulations
- 26. Public Participation
Other policies in CA
Sources
Updated December 31, 2024.