
Guideline 11 asks open data policies to state explicitly that public data carries no license restrictions, ideally by placing it in the public domain, because copyright rules for state and local governments vary.
Why licensing needs to be explicit
Federal government works in the United States are excluded from copyright, but the federal statute is silent on state and local government works, and state rules differ. That uncertainty discourages reuse: a developer or researcher cannot be sure whether a city's data can be republished.
Guideline 11 resolves the uncertainty by asking policies to say clearly that public data is license-free, preferably dedicated to the worldwide public domain, and labeled that way on the portal.
How policies typically phrase it
- A statement that public data sets carry no license requirement or restriction on use.
- A public domain dedication, sometimes naming a standard instrument such as CC0.
- Terms of use limited to disclaimers rather than restrictions.
- An optional request that redistributors cite the source, without making citation a condition of use.
Places whose policies adopted it
New York City's 2012 Local Law 11 bars license requirements and restrictions on use, and Madison's 2012 ordinance uses closely parallel language. Chicago's 2012 order handles the question through portal terms of use developed by the city's technology department.
Other tagged examples include Montgomery County, Honolulu, Denton, New Orleans and Washington, DC (2014).
Common pitfalls
- Silence. Saying nothing about licensing leaves reusers guessing.
- Attribution requirements that, while reasonable elsewhere, create legal exposure for publishers and journalists.
- Portal defaults. Some platforms apply their own license unless the government overrides it.
Choosing a public domain instrument
When a policy commits to license-free data, the practical question is how to label it. Common options include:
- A plain-language statement on the portal that data is in the public domain.
- Creative Commons CC0, which waives rights to the extent the law allows and is widely recognized internationally.
- The Open Data Commons Public Domain Dedication and License (PDDL), designed specifically for databases.
Whatever the instrument, the label should appear consistently on every data set, including in machine-readable metadata, so automated tools can detect it. Governments should also check that the portal platform does not apply a default license that conflicts with the policy. Where some data does carry restrictions, for example third-party content the government does not own, those exceptions should be flagged individually rather than applied to the whole catalog.
Why this matters for your business data
Licensing runs the other way in the private market. When a business sells or licenses operational data, the terms define what the buyer can do with it, for how long and for which purpose. Clear terms protect the seller and make the data easier to buy.
Sell my data explains how data licensing works for businesses, and you can get a bid to see real terms. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Is city data automatically in the public domain?
Not necessarily. US federal works are excluded from copyright, but state and local government works are governed by varying rules. That is why the guideline asks policies to declare public data license-free explicitly.
What is CC0?
CC0 is a Creative Commons tool that dedicates a work to the public domain to the extent the law allows, waiving copyright and related rights so anyone can reuse it.
Can a city ask users to cite its data?
Yes. Several policies ask redistributors to identify the source and version of a data set. The guideline distinguishes encouraging citation from making attribution a legal condition of use.
Policies in the index that reflect guideline 11
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| San Francisco, CA | Oct 29, 2010 | Ordinance | 47811182526 |
| 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 |
| Montgomery County, MD | Dec 17, 2012 | County legislation (Bill 23-12, Open Data Act) | 457811131822 |
| San Francisco, CA | Mar 28, 2013 | Ordinance | 34578101118 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| 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 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| Houston, TX | Sep 18, 2014 | Administrative policy (AP 8-7) | 234567810 |
| Denton, TX | Feb 9, 2015 | Administrative directive | 357811121618 |
| Jackson, MS | Sep 1, 2015 | Executive order (No. 2015-06) | 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 |
| 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 |
| 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 |
| Knoxville, TN | May 2, 2017 | Executive order | 14578111319 |
| Syracuse, NY | Jul 26, 2017 | Executive order | 1456781113 |
Sources
Updated December 31, 2024.