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

Montgomery County's 2012 Open Data Act (Bill 23-12)

Montgomery County's 2012 Open Data Act (Bill 23-12)

Montgomery County, Maryland's Open Data Act (Bill 23-12, December 2012) requires a single open data portal, a technical standards manual, an Open Data Implementation Plan with prioritization criteria, and public tracking of Public Information Act requests.

What the policy does

Bill 23-12 adds an Open Data article to Chapter 2 of the Montgomery County Code. Like New York City's 2012 Local Law 11, which it closely follows, it defines data, public data sets and technical standards. It then requires county agencies to publish eligible data on one portal, with no registration or license restrictions and with access for outside search engines.

Adoption context

The County Council passed the act in December 2012. It was one of the first county-level open data laws. Montgomery County added a feature many cities skipped: a public website tracking requests under the Maryland Public Information Act and the county's responses, plus reports to the Council.

Key provisions

  • Some public data sets online within one year, and every agency publishing at least one on the schedule set by the plan.
  • An Open Data Implementation Plan from the Chief Administrative Officer that ranks data sets by accountability, public knowledge, agency mission, economic opportunity and public demand.
  • A technical standards manual within 180 days.
  • Machine-processable formats, update notices, and updates on the plan's schedule.
  • A public feedback mechanism that agencies must consider when setting priorities.
  • The plan must address when data sets can be changed or removed from public access, which touches permanence.

Guidelines it reflects

The act covers prioritization, license-free data, metadata, permanent access, public participation and timelines.

What happened next

The county published its Open Data Implementation Plan in 2014, and that plan's dataset scoring appendix was later cited in the Sunlight Foundation's guidance on prioritization. The county's open data portal grew from this framework. Compare it with New York City's 2012 Local Law 11.

What this policy teaches about the value of operational data

Montgomery County ranks datasets partly by whether they "create economic opportunity." That is a direct statement that data has market value. Businesses can rank their own operational data the same way: which records are unique, recurring and useful to model builders? Try the valuation calculator or read how to value my data. 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

Does the Open Data Act let residents sue to force publication?

No. The act says that neither it nor the Implementation Plan creates a private right of action, and that failure to comply does not create liability for the county.

How does the act decide which data comes first?

The Chief Administrative Officer's Implementation Plan ranks data sets by whether they increase accountability, improve public knowledge, support an agency's mission, create economic opportunity, or answer demand identified through public consultation.

Guidelines this policy reflects

Other policies in MD

Sources

  1. Montgomery County Open Data Implementation Plan FY14 (historical link)
  2. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.