Baltimore Open Data Publication Standards & API Guide

Baltimore, Maryland maintains a municipal open data portal and publication standards to make city datasets discoverable, machine-readable, and reusable for residents, developers, and agencies. This guide explains the publication expectations, API access patterns, governance roles, and operational steps to publish or request data for Baltimore’s open data platform. It summarizes who enforces standards, what common compliance issues look like, how to submit datasets or requests, and practical steps to consume APIs for civic applications. For official portal documentation see the Baltimore Open Data Portal data.baltimorecity.gov^[1].

What the standards cover

The publication standards typically describe required metadata fields, acceptable file formats (CSV, GeoJSON, JSON), schema and field naming conventions, licensing expectations, update cadence, and API endpoint structure. They advise on personal data redaction and record retention when publishing city-held datasets. Required metadata and schema templates are provided through the portal and must be completed for each dataset prior to publication.

Penalties & Enforcement

Enforcement responsibility for open data publication and compliance resides with Baltimore City’s Department of Information Technology and the City Solicitor for legal matters. Operational oversight, publication review, and portal administration are managed by the City IT/Open Data team; public complaints can be filed through Baltimore 311 for accessibility and compliance issues, or escalated to the City Solicitor for legal remedies Department of Information Technology^[2]311^[3].

Monetary fines or statutory penalties specifically tied to open data publication are not specified on the cited pages; the portal and IT policy focus on administrative controls and corrective actions rather than enumerated fines. If a dataset or API endpoint violates privacy or statutory disclosure rules, legal remedies and penalties would follow applicable Baltimore City or Maryland law, and may be handled by the City Solicitor or relevant regulatory agency, depending on the subject matter.

Escalation, sanctions, and appeal

• Non-monetary sanctions may include removal of published datasets, suspension of publishing privileges, or restriction of API access by the City IT team.
• Legal action or court processes are governed by the City Solicitor when statutory violations occur; exact procedures and timelines are not specified on the cited pages.
• Complaints and inspection requests should be submitted via Baltimore 311 or the Department of Information Technology contact channels listed in Resources.
• Appeals or formal reviews are generally handled through administrative channels or legal counsel; time limits for appeals are not specified on the cited pages.

Common violations

• Publishing personally identifiable information without redaction or legal basis.
• Missing or incorrect metadata and schema that prevent dataset reuse.
• Publishing outdated or inaccurate data that misleads public users.

Applications & Forms

The portal provides metadata templates and dataset submission workflows; there is no separate published municipal ‘‘open data release’’ form referenced on the public portal pages. For dataset publication, follow the portal’s submission process or contact the City IT Open Data team for guidance. Specific application names, form numbers, deadlines, and fees are not specified on the cited pages.

How-To

1. Prepare the dataset: clean data, remove personal identifiers, and map fields to portal metadata requirements.
2. Choose formats: export machine-readable files (CSV, JSON, GeoJSON) and ensure consistent encoding and datatypes.
3. Draft metadata: include title, description, update cadence, contact, license, and data dictionary.
4. Publish via the portal’s dataset submission workflow and configure API endpoints or Socrata/CKAN settings as required.
5. Test the API: verify endpoints, query parameters, and paging; update rate limits and client keys if applicable.
6. Monitor and maintain: schedule updates, respond to user feedback, and correct errors reported via 311 or IT contact points.

FAQ

How do I request a dataset that is not on the portal?

Submit a data request to the Department of Information Technology or file a 311 service request asking for dataset publication; include intended use, required fields, and preferred cadence.

What formats and licenses are accepted?

The portal favors open, machine-readable formats such as CSV, JSON, and GeoJSON and encourages open licensing; consult the portal metadata guidance for specific license selection.

Are APIs free to use and are there rate limits?

APIs are publicly accessible through the portal, but any rate limits, API keys, or terms of use are determined by the portal administrator and are not specified on the public policy pages.

Key Takeaways

• Follow portal metadata and schema templates to ensure publishability and reuse.
• The portal emphasizes administrative corrections over fixed fines; monetary penalties are not listed on policy pages.
• Report accessibility or compliance problems via Baltimore 311 or contact the City IT Open Data team.

Help and Support / Resources

• Baltimore Open Data Portal
• Baltimore Department of Information Technology - Open Data
• Baltimore 311 (report issues, request datasets)