
Guideline 8 asks an open data policy to require machine-readable, structured, non-proprietary formats, so that published data can be reused by any software rather than only read by people.
What open formats means
Publishing data is not the same as making it usable. A scanned PDF of a spreadsheet is technically public but practically useless for analysis. This guideline asks policies to require three qualities: machine-readable (software can parse it), structured (fields and records are consistent) and open (no single vendor controls the format). The textbook example is CSV instead of a proprietary spreadsheet file.
Because standards evolve, the guideline treats "open formats" as a rolling list maintained by standards bodies rather than a fixed menu written into law.
How policies typically phrase it
- A definition of "open format" as non-proprietary, platform-independent and machine-readable.
- A requirement that data sets on the portal be published in such formats.
- Delegation to a technical standards document that can be updated without amending the policy.
- A requirement that data be accessible to external search tools.
Places whose policies adopted it
This is the single most frequently tagged guideline in the collection. Raleigh's 2012 resolution established an open data catalog of city data in open formats. Detroit's 2015 executive order asked a task force to recommend how data could be published in formats readable by people and processable by machines. Boston's open data policy of 2014 required citywide standards for format and publishing.
Other examples include New York City, Chicago, Cook County and Montgomery County.
Common pitfalls
- PDF as a data format. Documents are fine as companions, not substitutes.
- Hard-coding a format in law, which ages badly as standards change.
- Inconsistent schemas across releases, which breaks every tool built on the data.
Choosing formats in practice
Format choices depend on the kind of data. Common open, machine-readable choices that technical standards documents point to include:
- Tabular data: CSV, with consistent headers and a documented character encoding.
- Nested or record data: JSON or XML, often served through an API.
- Geographic data: GeoJSON, shapefiles or other open geospatial formats.
- Documents: text-searchable files paired with the structured data they summarize.
Beyond the file type, structure matters. Consistent column names, one record per row, standard date formats and stable codes make data far easier to reuse than a file that is technically open but laid out like a printed report. Many cities therefore wrote short style guides alongside their policies, and kept them separate from the policy text so they could be updated as practices changed.
Why this matters for your business data
Format is one of the biggest drivers of what operational data is worth. Buyers pay more for clean, consistently structured exports than for data trapped in screenshots, PDFs or one-off spreadsheets, because every hour of cleanup comes out of the price.
The valuation calculator factors data structure into its estimate, and how to value my data explains why. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
What is a machine-readable format?
A format that software can reliably parse into fields and records without human interpretation. CSV, JSON and XML are common examples; scanned images and most PDFs are not.
Why avoid proprietary formats?
Proprietary formats may require specific paid software, can change without notice and may become unreadable over time. Open formats keep data usable by anyone and preserve it for the long term.
Should a policy list specific formats?
The guideline suggests delegating format lists to a technical standards document that can be updated, rather than writing specific formats into the policy text.
Policies in the index that reflect guideline 8
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Portland, OR | Sep 30, 2009 | Council resolution | 37810162230 |
| San Francisco, CA | Oct 29, 2010 | Ordinance | 47811182526 |
| Cook County, IL | May 4, 2011 | Ordinance | 12378131825 |
| Raleigh, NC | Feb 7, 2012 | Council resolution | 381618 |
| New York, NY | Mar 7, 2012 | Local law (Local Law 11 of 2012) | 14578101118 |
| 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 |
| 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 |
| Honolulu, HI | Nov 27, 2013 | Ordinance | 237810111820 |
| Los Angeles, CA | Dec 18, 2013 | Executive directive (No. 3) | 37818222630 |
| 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 |
| 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 |
| 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 |
| Seattle, WA | Feb 1, 2016 | Administrative policy (CTO policy) | 14678101112 |
| 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 |
| Naperville, IL | Nov 15, 2016 | Council resolution | 45789101112 |
| Fort Collins, CO | Feb 7, 2017 | Council resolution | 12345678 |
| Knoxville, TN | May 2, 2017 | Executive order | 14578111319 |
| Syracuse, NY | Jul 26, 2017 | Executive order | 1456781113 |
Sources
Updated December 31, 2024.