
Guideline 9 asks governments to offer data in several appropriate formats for different audiences, pairing human-friendly reports with the structured data behind them and offering bulk downloads.
Beyond a single format
Guideline 8 sets a floor: data must be machine-readable and open. Guideline 9 asks for judgment about distribution. Different users need different things. A council member wants a readable report; a researcher wants the underlying table; a developer wants an API or a bulk file.
The guideline's example is a report best distributed as a document but containing figures that are more useful as structured data. The answer is to publish both, linked by metadata so users can move from one to the other.
How policies typically phrase it
- Permission or a requirement to publish through several methods, such as the portal, APIs and bulk downloads.
- A requirement to release underlying data alongside reports and dashboards.
- Accessibility language ensuring data works for the widest range of users.
- Technical standards that address multiple formats for different purposes.
Places whose policies adopted it
Fewer policies address this guideline explicitly. Boston's 2014 executive order lets departments publish through the portal or other methods consistent with citywide API and format standards. Washington, DC's 2014 directive calls for technical standards ensuring data is machine-readable and accessible to the broadest range of users for varying purposes. Hartford's 2014 order defines open formats with external search accessibility in mind.
Other tagged examples include Asheville, Cambridge, Jackson and Naperville.
Common pitfalls
- Dashboards with no download, which look open but block reuse.
- Reports and data published separately with no link between them.
- One audience only, whether that is developers or casual readers.
Matching formats to audiences
A practical way to apply this guideline is to think in terms of user groups:
- Residents and officials need summaries, charts and maps that explain what the data shows.
- Journalists and researchers need full tables they can download and analyze.
- Developers need APIs and stable endpoints they can build applications on.
- Other agencies need bulk exports and documentation for internal integration.
Publishing a single data set through several channels is not duplication if each channel is generated from the same source. Modern portals typically render a table, a chart view, a download and an API from one upload. The policy's job is to require that the structured data always be available behind whatever presentation layer is offered, and that accessibility standards be met so people using assistive technology can reach it too.
Why this matters for your business data
Data buyers also differ. Some want a one-time historical file to train a model; others want a recurring feed. Offering your operational data in the shape a buyer needs, with documentation, widens your market.
Learn how deliveries are structured on sell my data, or get a bid to see which formats buyers ask for. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
How is this different from Guideline 8?
Guideline 8 requires machine-readable open formats. Guideline 9 goes further, asking governments to offer multiple appropriate formats and distribution methods so different audiences can use the same information.
Should reports be published with their data?
Yes. The guideline recommends releasing the structured data behind a report alongside the report itself, with metadata connecting the two.
What distribution methods do policies mention?
Commonly an open data portal, bulk downloads, APIs and, in some cases, real-time feeds, each governed by technical standards.
Policies in the index that reflect guideline 9
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Hartford, CT | Mar 26, 2014 | Executive order | 34789182224 |
| Boston, MA | Apr 7, 2014 | Executive order | 3891318202425 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| 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 |
| Tulsa, OK | Dec 21, 2015 | Executive order | 123458910 |
| Las Vegas, NV | Apr 12, 2016 | Administrative policy (City Manager policy CM510) | 12345678 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| Naperville, IL | Nov 15, 2016 | Council resolution | 45789101112 |
Sources
Updated December 31, 2024.