
Browse open data policies in the order they were adopted, from Washington, DC's 2006 memorandum and San Francisco's 2009 directive through the surge of city policies in 2014 to 2017. The timeline shows how municipal open data policies matured.
The list below is ordered from oldest to newest. Each year groups the cities, counties and districts that adopted a policy in that year.
The early experiments (2006 to 2010)
The first wave was small and mostly executive. In 2006 Washington, DC's city administrator directed agencies to stream operational performance data to the city website. In 2009 Portland, Memphis and San Francisco followed with a council resolution, an executive order and a mayoral directive, and San Francisco wrote its program into ordinance in 2010. These early documents focused on publishing what was already collected and on launching a central catalog.
Legislation arrives (2011 to 2013)
Between 2011 and 2013 open data moved into law. Cook County, Raleigh, Madison, Montgomery County and Honolulu adopted ordinances or legislation, and New York City's 2012 Local Law 11 set a deadline for agencies to publish their public data sets on a single portal. Chicago and Philadelphia used executive orders that created chief data officer roles. This period introduced inventories, technical standards and compliance plans.
The spread to mid-sized cities (2014 to 2017)
From 2014 onward the number of cities that have passed an open data policy grew quickly, with many mid-sized cities adopting policies in a common structure: goals, definitions, an inventory, prioritization, privacy safeguards, a portal, an oversight role, timelines and periodic review. Boston's open data policy, Pittsburgh's legislation and the policies of Louisville, Las Vegas, Tulsa, Naperville and Syracuse illustrate that maturing template, which maps closely to the open data policy guidelines.
Why this matters for your business data
The timeline shows a shift from "publish what you have" to "manage data as an asset", with inventories, quality checks and owners for every dataset. Private companies are on the same path. Operational records that are documented, consistent and refreshed on a schedule are worth far more to AI and analytics buyers than a one-time export.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
See from open data policy to data value or estimate what your records could be worth with the valuation calculator.
Frequently asked questions
What was the first open data policy in the index?
The earliest entry is a June 2006 memorandum from Washington, DC's city administrator directing agencies to stream performance data to the city website. It predates the term "open data policy" as it is used today, but it established the idea of publishing operational data proactively.
Why did so many cities adopt policies after 2014?
Several forces converged: model policy language became widely available, national philanthropic programs offered technical assistance to mid-sized cities, and portal software made publishing easier. Cities could adapt a proven structure rather than drafting from scratch.
Open data policies by adoption date
2006
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Washington, DC | Jun 12, 2006 | Executive memorandum | 1131822 |
2009
2010
2011
2012
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Raleigh, NC | Feb 7, 2012 | Council resolution | 381618 |
| New York, NY | Mar 7, 2012 | Local law (Local Law 11 of 2012) | 14578101118 |
| Providence, RI | Mar 19, 2012 | Resolution | 31824262729 |
| Philadelphia, PA | Apr 26, 2012 | Executive order (No. 1-12) | 34578182224 |
| Madison, WI | Aug 15, 2012 | Ordinance | 457810111318 |
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| Montgomery County, MD | Dec 17, 2012 | County legislation (Bill 23-12, Open Data Act) | 457811131822 |
2013
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| San Francisco, CA | Mar 28, 2013 | Ordinance | 34578101118 |
| South Bend, IN | Aug 22, 2013 | Executive order | 237810182528 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Louisville, KY | Oct 11, 2013 | Executive order (No. 1, Series 2013) | 1234781018 |
| Oakland, CA | Oct 15, 2013 | Council resolution (No. 84659) | 2345781011 |
| Hennepin County, MN | Oct 23, 2013 | Resolution of support (MetroGIS Policy Board) | 1236 |
| Honolulu, HI | Nov 27, 2013 | Ordinance | 237810111820 |
| Los Angeles, CA | Dec 18, 2013 | Executive directive (No. 3) | 37818222630 |
2014
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Hartford, CT | Mar 26, 2014 | Executive order | 34789182224 |
| Boston, MA | Apr 7, 2014 | Executive order | 3891318202425 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Cincinnati, OH | May 29, 2014 | Administrative regulation | 8101122242629 |
| Chattanooga, TN | May 31, 2014 | Executive order | 123467810 |
| Phoenix, AZ | Jun 18, 2014 | Administrative policy | 13726 |
| Kansas City, MO | Jun 19, 2014 | Ordinance (No. 140443) | 81018242713 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| Minneapolis, MN | Aug 1, 2014 | Council-adopted policy | 34568131819 |
| Houston, TX | Sep 18, 2014 | Administrative policy (AP 8-7) | 234567810 |
| San Diego, CA | Nov 24, 2014 | Administrative policy | 45818202427 |
2015
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Charlotte, NC | Jan 1, 2015 | IT policy | 2781924 |
| Denton, TX | Feb 9, 2015 | Administrative directive | 357811121618 |
| Detroit, MI | Feb 19, 2015 | Executive order | 818 |
| Boston, MA | Jul 30, 2015 | Administrative policy | 478132425 |
| Suffolk County, NY | Jul 31, 2015 | Administrative policy | 78131820222426 |
| Jackson, MS | Sep 1, 2015 | Executive order (No. 2015-06) | 12345678 |
| Cambridge, MA | Sep 21, 2015 | Ordinance | 12345678 |
| Asheville, NC | Oct 13, 2015 | Council resolution | 13489101118 |
| Durham, NC | Nov 23, 2015 | Administrative policy | 7818192430 |
| Tulsa, OK | Dec 21, 2015 | Executive order | 123458910 |
2016
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| New York, NY | Jan 5, 2016 | Local law (Local Law 7 of 2016) | 124 |
| Seattle, WA | Feb 1, 2016 | Administrative policy (CTO policy) | 14678101112 |
| Seattle, WA | Feb 26, 2016 | Executive order | 17242627 |
| Baltimore, MD | Mar 7, 2016 | Ordinance | 1781113182426 |
| San Jose, CA | Apr 5, 2016 | Council policy | 1681113182230 |
| Las Vegas, NV | Apr 12, 2016 | Administrative policy (City Manager policy CM510) | 12345678 |
| Saint Paul, MN | Apr 27, 2016 | Council resolution | 12578101113 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| Bellevue, WA | Aug 1, 2016 | Management policy | 15678101118 |
| New Orleans, LA | Sep 1, 2016 | Executive order (MJL 16-01) | 124511182124 |
| Naperville, IL | Nov 15, 2016 | Council resolution | 45789101112 |
2017
Sources
Updated December 31, 2024.