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 Diego Open Data Policy (2014)

San Diego Open Data Policy (2014)

San Diego's Open Data Policy, effective January 1, 2015, put a Chief Data Officer in charge of a citywide data inventory, technical publishing guidelines with an API requirement, and annual compliance plans with a five-year target for high-value datasets.

What the policy does

The policy turns a 2013 council resolution of support into an operating framework. Its stated purpose is to make city data available online using open standards, while admitting plainly that the city holds many datasets and has limited resources for a new program. Its structure (an inventory, a web API requirement, annual compliance plans and a five-year horizon for high-value data) closely resembles New York City's 2012 Local Law 11.

Key provisions

  • Chief Data Officer. A mayoral designee oversees implementation.
  • Inventory. The CDO writes guidelines for inventorying city datasets and publishes department inventories.
  • Technical guidelines. Publishing standards favor voluntary consensus standards and must include a web API so applications can request data directly. The guidelines are reviewed every year.
  • Reporting. A status report is due within 180 days, and a compliance plan within 18 months and every year after.
  • High-value data. The compliance plan lists high-value datasets, chosen after public input, with a target of publishing all of them within five years.
  • Exclusions and disclaimers. Defined exclusions cover protected records, deliberative material, employee records and proprietary software, and the portal carries terms of use and a no-warranty disclaimer.

Which guidelines it reflects

Notable alignments include lists of holdings, prioritization, open formats, public APIs, oversight authority and timelines. The original collection also listed the council resolutions and implementation plan that surround this policy.

What happened next

San Diego appointed a Chief Data Officer and launched its open data portal at data.sandiego.gov in July 2016. Local reporting at the time counted 44 datasets at launch, drawn from a larger inventory the city had compiled under the policy.

Why this matters for your business data

San Diego's "high-value dataset" test is a useful lens for private data too. Not every table is worth publishing or licensing; the ones that matter are regularly updated, granular and tied to real activity. Our valuation calculator helps you see which of your datasets fit that profile, and the guide on de-identified data explains how they are prepared.

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

When did San Diego's open data policy take effect?

The policy set its effective date as the later of the authorizing resolution taking effect or January 1, 2015. It followed a council resolution supporting an open data policy that the council approved in December 2013.

Does the policy require an API?

Yes. The technical guidelines the Chief Data Officer prepares must provide a web application programming interface, so software can request and receive public datasets directly from the portal rather than relying only on manual downloads.

Guidelines this policy reflects

Other policies in CA

Sources

  1. Original policy document (historical; may no longer resolve)
  2. Policy text (Sunlight Foundation open data policy collection, GitHub)
  3. KPBS: First records released on San Diego's open data site (2016)

Updated December 31, 2024.