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

Open Formats: Open Data Policy Guideline 8

Open Formats: Open Data Policy Guideline 8

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.

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

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

PlaceAdoptedInstrumentGuidelines
Portland, ORSep 30, 2009Council resolution37810162230
San Francisco, CAOct 29, 2010Ordinance47811182526
Cook County, ILMay 4, 2011Ordinance12378131825
Raleigh, NCFeb 7, 2012Council resolution381618
New York, NYMar 7, 2012Local law (Local Law 11 of 2012)14578101118
Philadelphia, PAApr 26, 2012Executive order (No. 1-12)34578182224
Madison, WIAug 15, 2012Ordinance457810111318
Chicago, ILDec 10, 2012Executive order34678101113
Montgomery County, MDDec 17, 2012County legislation (Bill 23-12, Open Data Act)457811131822
San Francisco, CAMar 28, 2013Ordinance34578101118
South Bend, INAug 22, 2013Executive order237810182528
Austin, TXAug 26, 2013Administrative memo123457810
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Oakland, CAOct 15, 2013Council resolution (No. 84659)2345781011
Honolulu, HINov 27, 2013Ordinance237810111820
Los Angeles, CADec 18, 2013Executive directive (No. 3)37818222630
Pittsburgh, PAMar 19, 2014Ordinance12345678
Hartford, CTMar 26, 2014Executive order34789182224
Boston, MAApr 7, 2014Executive order3891318202425
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Cincinnati, OHMay 29, 2014Administrative regulation8101122242629
Chattanooga, TNMay 31, 2014Executive order123467810
Kansas City, MOJun 19, 2014Ordinance (No. 140443)81018242713
Washington, DCJul 21, 2014Executive directive (Mayor's Order 2014-170)12356789
Minneapolis, MNAug 1, 2014Council-adopted policy34568131819
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
San Diego, CANov 24, 2014Administrative policy45818202427
Charlotte, NCJan 1, 2015IT policy2781924
Denton, TXFeb 9, 2015Administrative directive357811121618
Detroit, MIFeb 19, 2015Executive order818
Boston, MAJul 30, 2015Administrative policy478132425
Suffolk County, NYJul 31, 2015Administrative policy78131820222426
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Durham, NCNov 23, 2015Administrative policy7818192430
Tulsa, OKDec 21, 2015Executive order123458910
Seattle, WAFeb 1, 2016Administrative policy (CTO policy)14678101112
Baltimore, MDMar 7, 2016Ordinance1781113182426
San Jose, CAApr 5, 2016Council policy1681113182230
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
Saint Paul, MNApr 27, 2016Council resolution12578101113
Milwaukee, WIJul 14, 2016Council resolution12356789
Bellevue, WAAug 1, 2016Management policy15678101118
Naperville, ILNov 15, 2016Council resolution45789101112
Fort Collins, COFeb 7, 2017Council resolution12345678
Knoxville, TNMay 2, 2017Executive order14578111319
Syracuse, NYJul 26, 2017Executive order1456781113

Sources

  1. Sunlight Foundation, Open Data Policy Guidelines (historical reference)
  2. City of New York open data technical standards manual

Updated December 31, 2024.