
Kansas City's Ordinance 140443 (June 2014) wrote an open data policy into the municipal code. It requires public data to be published in machine-readable open formats, keeps the existing portal running, and creates an Open Data Officer and departmental liaisons.
What the policy does
The ordinance adds an "Open Data Policy" article to Chapter 2 of Kansas City's Code of Ordinances. Its central rule is that public data should, whenever feasible, be freely available online in a machine-readable open format that people can download and reuse with ordinary free software. Because it is in the code, the policy carries more weight than a resolution and lasts beyond any one administration.
Adoption context
Kansas City already had a portal. The ordinance notes that data.kcmo.org launched in January 2013, and it follows an earlier council resolution supporting open data. The 2014 ordinance turned that support into lasting law. The city later adopted more open data legislation in 2015 (listed separately in the original collection).
Key provisions
- Technology purchases and processes should help publish data in open standards and formats.
- Public data should be published in both raw and processed form, with a description of its source and quality.
- The Open Data Portal must be maintained, and the public must be notified if it moves.
- The City Manager designates an Open Data Officer to run the portal and coordinate publishing.
- Each department names open data liaisons. They identify unpublished data, record written reasons when data is withheld, and set publishing timelines.
Guidelines it reflects
The ordinance addresses open formats, open access, data portals, oversight authority and timelines. Its requirement to describe each dataset's source and quality also touches metadata.
What happened next
Kansas City continued developing its program and passed further open data legislation in October 2015. The 2014 ordinance is a short example of a council codifying a portal that already existed. For a comparison with a longer code-based approach, see Madison's 2012 ordinance.
Why this matters for your business data
The ordinance asks for data in raw form along with notes on where it came from and how reliable it is. Data buyers ask for exactly that today. Clear provenance and quality notes raise the price of any dataset, public or private. If your company produces steady operational records, start with how to value my data or get a bid. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Does the ordinance require every dataset to be published?
No. It applies "whenever feasible" and "to the extent prudent and practical." Departmental liaisons can recommend withholding data for confidentiality, intellectual property, security or privacy reasons, but they must keep a written justification when they do.
Where is the policy codified?
It forms Article XVI of Chapter 2 of the Kansas City, Missouri Code of Ordinances, Sections 2-2130 through 2-2135, as enacted by Ordinance No. 140443.
Guidelines this policy reflects
Sources
Updated December 31, 2024.