
Baltimore's 2016 ordinance wrote the city's open data program into the City Code, keeping Open Baltimore as the central portal, putting a Chief Data Officer in charge and requiring an annual open data report.
What the ordinance does
The ordinance adds an Open Data Program subtitle to Article 1 of the Baltimore City Code. It defines open data as data published online in an open format with no legal encumbrances on reuse, separates publishable data from protected and sensitive information, and makes the Chief Data Officer responsible for the program.
One notable line: datasets on the portal are offered on an open license basis, explicitly allowing copying, redistribution, modification and use for commercial as well as non-commercial purposes.
Adoption context
Before 2016, Baltimore's open data work rested on an executive order from 2011. Councilman Brandon Scott sponsored the bill to make the program permanent in law, and the council passed it in March 2016, according to contemporary local tech press coverage.
Key provisions
- Proactive release of all publishable data in open formats, with documentation and permanence.
- Continued maintenance of the Open Baltimore portal as the single home for city data.
- Protected information (withheld under the Maryland Public Information Act or other law) and sensitive information are excluded.
- Each agency names a lead open data coordinator.
- Regular opportunities for public feedback and collaboration.
- An annual open data report to the Mayor and Council due by June 30.
Guidelines this policy reflects
This index reads the ordinance as touching proactive release, sensitive information, open formats, license-free data, metadata, portals, oversight authority and public participation.
What happened next
The ordinance remained the legal basis for Baltimore's program. In 2021 the city announced a relaunch of its open data portal under Mayor Scott, citing the 2016 law's requirements for regular publication of data such as crime statistics and salaries.
Why this matters for your business data
Baltimore's explicit permission for commercial reuse shows how much licensing terms drive value. Data buyers in AI and analytics care first about whether they may legally use a dataset, then about its quality. When a business licenses its own operational data, clear rights and clear exclusions matter just as much. See how to value my data and 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
Can businesses use Baltimore's open data commercially?
Under the ordinance, datasets on the portal are offered on an open license basis with no restrictions on copying, publishing, modifying or using the data for commercial or non-commercial purposes, subject to the disclaimers the city must post.
Who runs Baltimore's open data program?
The ordinance puts the Chief Data Officer in charge, with authority to adopt rules, coordinate agency open data leads, encourage public participation and prepare the annual open data report.
Guidelines this policy reflects
- 1. Proactive Release
- 7. Sensitive Information
- 8. Open Formats
- 11. License-Free
- 13. Metadata
- 18. Data Portals and Websites
- 24. Oversight Authority
- 26. Public Participation
Other policies in MD
Sources
Updated December 31, 2024.