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

Browse Municipal Open Data Policies: An Index of Policies by Place, Date and Instrument

Browse Municipal Open Data Policies: An Index of Policies by Place, Date and Instrument

Browse an index of policies that US cities, counties and states adopted to publish government data openly. Explore each open data policy by place, adoption date or state, and see which of the 31 policy guidelines it reflects.

This index revives and rewrites a public reference on municipal open data policies. Each entry summarizes what a local government actually committed to, in original language, and links to the source document so you can read the policy itself.

Three ways to browse the index

Open data policies come in many legal forms, so the index is organized three ways:

  • All policies, A to Z lists every entry alphabetically by place, which is the fastest route if you already know the city or county you are looking for.
  • Policies by date arranges the same entries chronologically, from Washington, DC's 2006 memorandum on streaming performance data to the wave of city policies adopted in 2016 and 2017.
  • Policies by state groups entries geographically, which helps when you want to compare neighboring jurisdictions or see how a state's cities approached the same problem.

Every entry links to the open data policy guidelines it reflects, so you can move from a single policy to the provision it implements and then to other places that wrote the same provision differently.

What counts as an open data policy

An open data policy is any formal instrument in which a government commits to publishing the data it holds in a form the public can find, download and reuse. In practice the index includes:

  • Legislation and ordinances passed by a city council or county board, such as New York City's 2012 Local Law 11.
  • Executive orders and directives signed by a mayor or county executive, such as Boston's open data policy of 2014 and Chicago's 2012 order.
  • Council resolutions that state intent and direct staff to build a program.
  • Administrative and IT policies issued by a city manager, chief information officer or technology department.

The instrument matters. Legislation tends to survive changes in administration; executive orders and internal policies are faster to adopt but easier to let lapse. Many cities that have passed an open data policy started with one form and later upgraded to another.

How to read an entry

Each policy page follows the same structure: a plain-language summary, the context in which the policy was adopted, its key provisions, the guidelines it reflects, what happened next (through 2024), and a list of sources. Summaries are written fresh for this index and are not a substitute for the official text. Where a link to the original document has gone stale, the page points to an archived or mirrored copy.

Why this matters for your business data

The same ideas that made municipal open data policies work, such as an inventory of what you hold, documented formats, clear quality standards and careful handling of sensitive fields, are exactly what make private operational data valuable to the teams building AI and analytics products. A business that can describe its datasets the way a good open data program does is most of the way to knowing what that data is worth.

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

If you want to see how the public-sector playbook translates to a private company, start with from open data policy to data value, try the valuation calculator, or request a bid for a de-identified dataset.

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

Is this an official government database of open data policies?

No. It is an independent reference that summarizes publicly available policy documents. The official version of any policy is the one published by the government that adopted it, so each entry links to its source. Nothing in the index is legal advice, and policies may have been amended or replaced after the version summarized here.

Why do some cities appear more than once?

Many governments adopted more than one instrument. A mayor might sign an executive order first and then issue a detailed administrative policy, or a council might later write the program into law. San Francisco, Washington, DC, Seattle, Boston, Austin and New York City each appear more than once for this reason.

How current is the index?

The entries describe policies adopted between 2006 and 2017 and note later developments through the end of 2024. Open data programs change often, so check the government's own website for the latest version of any policy before relying on it.

Recently adopted policies in the index

PlaceAdoptedInstrumentGuidelines
Syracuse, NYJul 26, 2017Executive order1456781113
Knoxville, TNMay 2, 2017Executive order14578111319
Fort Collins, COFeb 7, 2017Council resolution12345678
Naperville, ILNov 15, 2016Council resolution45789101112
New Orleans, LASep 1, 2016Executive order (MJL 16-01)124511182124
Bellevue, WAAug 1, 2016Management policy15678101118
Milwaukee, WIJul 14, 2016Council resolution12356789
Saint Paul, MNApr 27, 2016Council resolution12578101113
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
San Jose, CAApr 5, 2016Council policy1681113182230
Baltimore, MDMar 7, 2016Ordinance1781113182426
Seattle, WAFeb 26, 2016Executive order17242627

Sources

  1. Sunlight Foundation, Open Data Policy Guidelines (historical reference)
  2. Sunlight Foundation open data policy collection (public GitHub repository)

Updated December 31, 2024.