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

Madison, Wisconsin's 2012 Open Data Ordinance

Madison, Wisconsin's 2012 Open Data Ordinance

Madison's 2012 ordinance added a section on public access to municipal data sets to the Madison General Ordinances. It required a single web portal, metadata and technical standards, regular updates, and annual reports on any data not yet published.

What the policy does

Madison's Common Council created Section 3.72 of the city's ordinances, titled "Public Accessibility to Municipal Data Sets." The structure and many definitions follow New York City's 2012 Local Law 11, adjusted for Wisconsin's public records statutes. The ordinance also created a public records opt-out procedure so that people whose safety could be at risk can ask the city to keep certain records confidential.

Adoption context

Madison passed the ordinance in August 2012, a few months after New York, making it one of the earliest cities to adapt the New York model. The city announced it as a new open data ordinance.

Key provisions

  • By September 30, 2013, published data sets had to be reachable through a single web portal linked from the city website.
  • Each agency must identify and publish its own data; IT provides consultation and technical support only.
  • From December 31, 2013, agencies that cannot publish all their public data sets must report annually on what is missing, why, and when it will be published.
  • Metadata for each data set, using a city template, and technical standards that favor open formats.
  • Data sets must be kept current and the public notified of updates.
  • A detailed list of exclusions, including personally identifiable information.

Guidelines it reflects

Madison covers lists of holdings, metadata, open formats, real-time updates, timelines and sensitive information.

What happened next

The ordinance's dates set up a public portal and annual reporting starting in 2013. Madison's approach of placing publishing responsibility on each agency, instead of on central IT, is a recurring design choice in municipal open data policies. Compare it with the central officer model in Kansas City's 2014 ordinance.

What this policy teaches about the value of operational data

Madison's metadata template and update rules show that a dataset's value depends on how well it is maintained. A business that wants to price its data should document fields, refresh schedules and sources first. Start with how to value my data and the de-identified data guide. 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

How is Madison's ordinance related to New York's open data law?

Madison borrowed much of its structure and definitions from New York City's 2012 Local Law 11, including the definitions of data, open standard and technical standard. It then adjusted the text for Wisconsin's public records statutes and the city's own ordinances.

What is the public records opt-out in the ordinance?

The ordinance told the city to create a procedure for people who believe releasing certain public records could endanger their safety to ask that those records be kept confidential. The City Attorney and IT were to develop the procedure together.

Guidelines this policy reflects

Other policies in WI

Sources

  1. City of Madison: new open data ordinance (historical link)
  2. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.