
Guideline 10 asks open data policies to remove barriers such as registration, fees and usage limits, so anyone can access public data at any time without identifying themselves or explaining why.
What open access requires
Even data in perfect formats can be closed off by friction: mandatory accounts, access fees, rate limits, restrictive terms of use. Guideline 10 asks policies to address these barriers directly, whether they were imposed deliberately or emerged by accident from a software choice.
The goal is broad, non-discriminatory, free access. Anyone should be able to download public data anonymously and at any time, without providing a reason.
How policies typically phrase it
- A requirement that public data sets be available without registration or fees.
- Terms of use drafted to maximize, not restrict, reuse.
- Requirements that data be reachable by external search engines and automated tools.
- Notice mechanisms that tell users when data is updated.
Places whose policies adopted it
New York City's 2012 Local Law 11 requires that public data sets be available without registration, license requirements or restrictions on use, while allowing the city to ask redistributors to identify the source. Chicago's 2012 order requires formats that permit automated processing and accessibility to external search. San Francisco's 2013 ordinance takes a softer line, allowing "reasonable, user-friendly" registration requirements under standards adopted by the city.
Other tagged examples include Louisville, Oakland, Madison and Saint Paul.
Common pitfalls
- Registration walls justified as usage tracking.
- API keys with low limits that block bulk reuse.
- Terms of use that quietly reintroduce restrictions the policy removed.
Writing open terms of use
Terms of use are where open access is often won or lost. Terms consistent with this guideline tend to share several traits:
- They disclaim warranties and liability rather than restricting use.
- They do not require registration, payment or justification for access.
- They allow commercial and non-commercial reuse alike.
- They may ask users to cite the source, but do not make citation a condition of use.
- They avoid clauses that let the publisher revoke access to particular users.
Technical choices matter as well. If an API is the only access route and it imposes low rate limits, heavy users are effectively shut out; offering bulk downloads alongside APIs solves that. Making portals crawlable by search engines also helps the public find data without knowing where to look.
Why this matters for your business data
Public open data is free by design. Private operational data is different: it is proprietary, and access to it is what a buyer pays for. Understanding why governments give their data away, and why companies building AI still need more, explains why private data commands a price.
Our pillar on open data policy to data value explores that contrast, and how to value my data shows what drives price. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Can a government require registration to download open data?
The guideline recommends against it. Some policies allow light registration, but strong policies require that public data be accessible anonymously, without fees or justification.
Are API rate limits a barrier to open access?
They can be, if they prevent bulk or automated reuse. Offering bulk downloads alongside APIs is a common way to avoid that problem.
How do terms of use affect open access?
Terms of use can undo an open policy by restricting reuse or imposing conditions. The guideline asks that terms maximize accessibility and reuse.
Policies in the index that reflect guideline 10
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Portland, OR | Sep 30, 2009 | Council resolution | 37810162230 |
| New York, NY | Mar 7, 2012 | Local law (Local Law 11 of 2012) | 14578101118 |
| Madison, WI | Aug 15, 2012 | Ordinance | 457810111318 |
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| 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 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| 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 |
| Houston, TX | Sep 18, 2014 | Administrative policy (AP 8-7) | 234567810 |
| 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 |
| Seattle, WA | Feb 1, 2016 | Administrative policy (CTO policy) | 14678101112 |
| 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 |
Sources
Updated December 31, 2024.