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

Oakland's 2013 Open Data Policy Resolution

Oakland's 2013 Open Data Policy Resolution

Oakland City Council Resolution 84659, adopted in October 2013, set an open data policy requiring machine-readable City Data in open standards, an inventory and dissemination plan, free reuse licensing, and regular public reports.

What the policy does

The resolution sets a council policy that Oakland will make every reasonable effort to publish City Data in machine-readable formats using prevailing open standards, kept in a catalog on one city website. It tells the City Administrator to support every department, set guidelines for identifying high-value data, engage the public, and follow privacy and security law.

Adoption context

The resolution was introduced by Councilmember Libby Schaaf, who later became mayor. It came after earlier steps: a 2012 council request for a cost-benefit study, a staff implementation report, and the launch of the data.oaklandnet.com portal in January 2013. It cites the California Public Records Act and Oakland's Sunshine Ordinance. The Sunlight Foundation's records note that Oakland received some help from that organization before the What Works Cities program.

Key provisions

  • Draft regulations with technical requirements for raw-format publishing, presented for public comment within 180 days.
  • An inventory and dissemination plan within twelve months, including costs and barriers to release.
  • Reports to the Finance and Management Committee every six months for two years, then yearly.
  • Data already public on the city website moved into the catalog within twelve months.
  • Free reuse licensing and updates frequent enough to keep data useful.
  • Clear descriptions for every dataset.

Guidelines it reflects

Oakland covers build on precedent, lists of holdings, license-free data, metadata, public participation and data quality.

What happened next

Oakland's portal and reporting schedule continued after the resolution. Its path from study to report, portal, then policy is a useful model for other cities. Compare it with San Francisco's 2013 legislation across the bay.

What this policy teaches about the value of operational data

Oakland's preamble says combining structured data from different sources helps "niche markets" get identified and developed. That is an early public statement that operational data is a raw material for new products. The guide from open data policy to data value follows that idea into the private sector, and sell my data explains next steps. 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

Did Oakland have a portal before the policy?

Yes. The resolution notes that Oakland launched its Open Data portal at data.oaklandnet.com in January 2013, about nine months before the council adopted the formal policy.

How often must Oakland report on open data?

Every six months to the Finance and Management Committee for the first two years, then once a year. Reports cover catalog updates, implementation progress, barriers and public uses.

Guidelines this policy reflects

Other policies in CA

Sources

  1. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.