What does the Baltimore MD 311 data include?

One table, service requests, with one row per service request.

Do I need an account with Baltimore MD 311?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan. Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.

Will running it again create duplicate rows?

No. Each run replaces the table, so it never holds two copies of the same row.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Baltimore MD 311

Public data

Ready to useNo account needed

Service requests logged with Baltimore, Maryland's 311 line, as the city currently publishes them. Ingest delivers this data to a data warehouse you own as one table, and updates it on the schedule you choose. There is no code to write and nothing to install.

853,855service requests as of September 2026
About 24,000new service requests a week
1 tableone row per service request

What people use it for

See which problems are commonCount requests by type to see what residents report most.
See which neighborhood reports whatBreak requests down by neighborhood or council district.
See which department handles whatBreak requests down by the agency responsible for each one.
Track how long requests take to closeCompare when each request opens and closes.

What you get

Table	Each row is
Service requests `featureserver`	One service request

Good to know

Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.

How it works

Choose Baltimore MD 311. The data is public, so there is nothing to sign in to.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

What does the Baltimore MD 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Baltimore MD 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Baltimore MD 311 data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan. Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.
Will running it again create duplicate rows?: No. Each run replaces the table, so it never holds two copies of the same row.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector baltimore_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://services1.arcgis.com/UWYHeuuJISiGmgXx/arcgis/rest/services/311_Customer_Service_Requests_current/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` Baltimore 311 customer service requests served by the City's ArcGIS "current" layer (311 Customer Service Requests 2026). Every run pages the complete currently exposed collection in RowID order and replaces the destination, so rows the source no longer returns on a later run are removed (full replace semantics). The publisher scopes this layer to calendar 2026; the "_current" URL does not prove retention or rollover into later years, so this connector documents the currently exposed collection, not lifetime municipal history, and no future retention is guaranteed. Rows without an activity timestamp (LastActivityDate is null for over a third of the collection) are still loaded. ArcGIS native Date fields arrive as epoch milliseconds and are preserved as bigint with their raw values, in the units the API sends.	beta	full	replace	`RowID`	-