Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Policy index / Open data policy index
Open data policy index

Milwaukee's 2016 Open Data Policy

Milwaukee's 2016 Open Data Policy

Milwaukee's 2016 open data policy, adopted by council resolution, commits the city to regularly releasing publishable data in open formats with metadata and historical archives. It defines protected and sensitive information in detail.

What the policy does

Milwaukee's policy commits the city to publishing structured, standardized, machine-readable data to improve services, transparency and coordination. It sets out what the program covers, what it excludes, and how data is prioritized. Publication order is based on relevance, ease of access and other criteria set by the city's IT management division and confirmed by the City Information Management Committee.

Adoption context

The policy was adopted in July 2016, during a wave of mid-sized cities formalizing open data. According to the Sunlight Foundation's published collection, Milwaukee had that organization's formal help through the What Works Cities program. The policy is frank about limits: it says capacity and demand will decide how fast the data library grows.

Key provisions

  • A precise definition of metadata: last update date, refresh frequency, format, field names and field explanations.
  • Open data defined as available online in an open format, free to access and download in full, with no legal encumbrances.
  • A nine-part definition of protected information, including deliberative records, proprietary software, internal administrative data and personally identifiable or financial identifying information.
  • Commitments to high-quality data with metadata and permanence, historical archives, and measuring effectiveness against city priorities.
  • Support for innovative use by the public and partners.

Guidelines it reflects

Milwaukee is a strong example of metadata, archival material, prioritization, sensitive information, funding and future review.

What happened next

Milwaukee went on to operate a public open data portal under the policy. Its detailed metadata definition is one of the clearer ones in the index and is worth reading for anyone drafting municipal open data policies. Compare it with Madison's 2012 ordinance elsewhere in Wisconsin.

What this policy teaches about the value of operational data

Milwaukee's metadata checklist (last updated, refresh rate, format, field names, field meanings) is close to what a data buyer asks for before making an offer. Companies that document their operational data this way get better bids. Learn more in how to value my data and get a bid when ready. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Our compliance promise: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Frequently asked questions

What does Milwaukee's policy count as metadata?

The date the data was last updated, how often it is refreshed, its format, and the field names with an explanation of each field. This short list makes datasets understandable without a call to city staff.

Does the policy exclude personal information?

Yes. Protected information includes any data containing personally identifiable or financial identifying information that can be tied to an individual, such as home addresses, personal phone numbers, Social Security numbers or driver's license numbers.

Guidelines this policy reflects

Other policies in WI

Sources

  1. City of Milwaukee Open Data Policy (historical PDF link)
  2. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.