Baltimore Sensor Maps & Data - City Bylaws

Baltimore, Maryland operates municipal mapping and open-data services where city-managed sensor locations, telemetry datasets, and related access policies can be found. This guide explains where to locate live sensor maps and datasets, which city departments manage installations and data, and how local bylaws and permitting pathways typically apply. It also lists who to contact to request data, permits, or to report possible violations.

Primary public inventories and APIs are published through the Baltimore Open Data Portal and the Baltimore GIS map viewer. See dataset pages and mapping viewers for published sensor layers and metadata Baltimore Open Data Portal^[1] and Baltimore GIS Maps^[2]. These official pages are current as of February 2026 unless noted on each dataset.

Where to find sensor maps and datasets

Start with the city’s centralized sources and then check departmental inventory pages:

• Browse the Baltimore Open Data Portal datasets and APIs for sensor tables, telemetry feeds, and metadata.
• Use the Baltimore GIS viewer to layer sensors on maps, export shapes, and inspect location attributes.
• Contact the department listed in dataset metadata for asset ownership and access questions.

Who manages sensors and data

Different sensor types (traffic, environmental, parking, lighting) are typically managed by the department that owns the asset: Transportation, Public Works, Department of Transportation fleet/traffic units, or the city’s IT/Open Data office for data publishing. For installations on city property, right-of-way and attachment approvals are handled by the city agency that controls the infrastructure.

Penalties & Enforcement

Penalties specific to unauthorized sensor installation, tampering, or misuse of city-managed sensor data are not consolidated on the primary data pages; the portal dataset pages do not list enforcement fines or schedules for installations on city assets^[1]. Enforcement actions depend on the controlling department and local code provisions governing permits, attachments, and public-right-of-way use.

• Fine amounts: not specified on the cited page.
• Escalation: first, repeat, and continuing offence ranges are not specified on the cited page.
• Non-monetary sanctions: removal orders, cease-and-desist, seizure of equipment, or court action can be used by the enforcing department (specific remedies vary by department and code).
• Enforcer: owning department (Transportation, Public Works, or City IT) inspects and issues orders; complaints route to departmental contacts or 311 where applicable.
• Appeals/review: appeal paths depend on the departmental permit or code provision; specific time limits are not specified on the cited page.
• Defences/discretion: authorized permits, franchises, or written agreements with the city are usual defenses; discretionary waivers or variances are department-specific.

Common violations and typical outcomes

• Installing equipment on city poles without a permit — likely removal order and potential civil penalties.
• Accessing restricted telemetry that bypasses authorized APIs — suspension of access and possible legal action.
• Altering traffic or public-safety sensors — immediate enforcement and equipment seizure risk.

Applications & Forms

Permit and application names vary by department. The Open Data or GIS pages reference owning departments but do not publish a single citywide sensor installation form; check the owning department for right-of-way, attachment, or franchise application forms and fees^[2].

• Right-of-way or pole-attachment permit: check Transportation or Public Works for application name and submission instructions.
• Fees: department pages list fees when applicable; not specified on the central dataset pages.

Action steps

• Locate the sensor layer or dataset on the Open Data Portal and GIS viewer to confirm ownership and metadata.
• Contact the department listed in dataset metadata to request access, permissions, or clarifications.
• If installing equipment, apply for the appropriate right-of-way or attachment permit before installation.
• If you receive an enforcement notice, follow the appeal instructions on the notice and contact the issuing department promptly.

FAQ

Where can I download raw sensor data for Baltimore?

You can download published datasets and APIs from the Baltimore Open Data Portal and use the GIS viewer for spatial exports; contact the listed department for datasets not publicly published.

Do I need a permit to install a sensor on a city pole?

Yes, installations on city infrastructure generally require a right-of-way or attachment permit from the owning department; confirm permit names and submission steps with that department.

Who enforces removal of unauthorized devices?

The city department that owns the asset (Transportation or Public Works) or city inspectors typically enforce removal; complaints may be reported via the department contact or 311.

How-To

1. Search the Baltimore Open Data Portal for sensor-related datasets and read the dataset metadata for owner and contact information.
2. Open the Baltimore GIS Maps viewer to visualize sensor locations and export spatial data if available.
3. Contact the owning department listed in metadata to request additional access, datasets, or clarify permitting requirements.
4. If installing equipment on city property, apply for the department-specific right-of-way or attachment permit and await written approval before proceeding.

Key Takeaways

• Use the Open Data Portal and GIS viewer as the authoritative starting points for Baltimore sensor inventories.
• Department contacts listed in metadata are the official route for data requests, permits, and disputes.
• Unauthorized installations are subject to departmental enforcement; always confirm permit requirements first.

Help and Support / Resources

• Baltimore Open Data Portal
• Baltimore GIS Maps
• Baltimore Department of Transportation
• Baltimore Department of Public Works

1. [1] City of Baltimore Open Data Portal
2. [2] City of Baltimore GIS Maps