
Minneapolis's open data policy, approved by the City Council in summer 2014, required an open data portal within 120 days. It set prioritization criteria, procurement terms that protect city data ownership, and an annual compliance report.
What the policy does
Minneapolis commits to proactively sharing its data through an Open Data Portal. The policy sets rules for building an open data framework into current and future systems, deciding which datasets to publish, and keeping them current. Published data must be available by API or bulk download, searchable by outside search engines, and open to public feedback.
Adoption context
The policy grew out of local civic advocacy and was championed on the council by Council Member Andrew Johnson. The city's policy page lists council approval on August 1, 2014. Press coverage reported that some language was changed late in the process, which let departments opt out of publishing certain data.
Key provisions
- An Open Data Portal within 120 days, with API or bulk access, update notices and a public feedback channel.
- Prioritization based on how often data is requested, whether it improves accountability or services, and whether it increases public knowledge.
- IT contracts awarded after January 1, 2015 must support open data and keep city ownership of its data.
- The Chief Information Officer manages the policy and files an Open Data Compliance Report each June 30.
- Departments name Open Data Coordinators and keep a comprehensive inventory labeled public, not yet public or protected.
- Private data should be aggregated, generalized or otherwise de-identified where possible so it can be published.
Guidelines it reflects
Minneapolis covers prioritization, outside services through its procurement clause, bulk data, public APIs, metadata and data quality.
What happened next
The city launched its open data portal in December 2014, on the 120-day timeline. Some advocates criticized the opt-out flexibility at the time. The policy remains a good case study in how wording choices affect what municipal open data policies actually require.
Why this matters for your business data
Minneapolis asks staff to de-identify, aggregate or generalize private records so they can be shared. Privacy-safe operational data can be valuable without exposing anyone. The de-identified data guide explains how, and the guide from open data policy to data value covers the business case. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
How quickly did Minneapolis have to launch a portal?
Within 120 days of the policy taking effect. The city launched its open data portal in December 2014.
Does the policy deal with vendor contracts?
Yes. Appropriate IT procurements awarded after January 1, 2015 must include provisions supporting open data. Where appropriate, these keep the city's ownership of its data and its ability to publish that data.
Guidelines this policy reflects
- 3. Goals and Values
- 4. Lists of Holdings
- 5. Prioritization
- 6. Outside Services
- 8. Open Formats
- 13. Metadata
- 18. Data Portals and Websites
- 19. Bulk Data
- 20. Public APIs
- 22. Real-Time Updates
- 24. Oversight Authority
- 25. Binding Regulations
- 26. Public Participation
- 27. Timelines
- 28. Data Quality
- 31. Future Review
Other policies in MN
Sources
Updated December 31, 2024.