Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Policy index / Open data policy index
Open data policy index

San Francisco Open Data Ordinance Amendments (2013)

San Francisco Open Data Ordinance Amendments (2013)

San Francisco's 2013 ordinance rewrote Chapter 22D of the Administrative Code, giving a mayor-appointed Chief Data Officer the job of setting open data standards, requiring core metadata, and setting deadlines for departments to publish data.

What the ordinance does

This ordinance amends sections 22D.1 through 22D.3 of the Administrative Code to update open data standards and set deadlines for release. Its findings trace the policy's history from the 2009 mayoral directive through the 2010 ordinance and an earlier 2013 amendment that created the Chief Data Officer (CDO) position. It also proposes something new: giving residents secure access to their own data held by the city.

Key provisions

  • Chief Data Officer. Appointed by the mayor, the CDO drafts rules and technical standards and decides, within the law, which datasets are appropriate to disclose.
  • Principles. Prioritize data of likely public interest, keep data free of charge, and exclude privileged, law enforcement, security, personal and proprietary information.
  • Metadata. Datasets should include metadata, API documentation and licensing terms. Core metadata covers title, description, tags, last update, publisher, contact, unique identifier and access level.
  • Coordination. The CDO maintains DataSF, collects department plans, creates quarterly report templates and presents an annual citywide plan.
  • Licensing and comment. The CDO sets licensing guidelines and must seek public comment before major changes to the rules.

Which guidelines it reflects

The annotated text covers fourteen guidelines, among them prioritization, sensitive information, permanent access, oversight authority, binding regulations and future review.

What happened next

DataSF continued as the city's open data program under the Chief Data Officer role this law defined. For the earlier steps, see Executive Directive 09-06 and the 2010 ordinance.

Why this matters for your business data

The 2013 amendments list the metadata every dataset should carry, and that list is close to what a data buyer expects: a clear title, a description, a last-updated date, an owner and stable identifiers. Well-documented data is easier to price and to sell. See de-identified data for how records are prepared, and how to value your data for what drives price.

We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Our compliance promise: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Frequently asked questions

What metadata does San Francisco's ordinance require?

At a minimum, common core metadata covers each dataset's title, description, tags, last update, publisher, contact information, unique identifier and public access level, as the Chief Data Officer defines them. Datasets should also include API documentation and licensing terms where possible.

Does the ordinance let San Franciscans see their own data?

It directs the Chief Data Officer to set up a process giving residents secure access to their private data held by the city, and its findings call for a strategy to return citizen data to people who request it. That is separate from publishing open data, which excludes personal information.

Guidelines this policy reflects

Other policies in CA

Sources

  1. Original committee document (historical; may no longer resolve)
  2. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.