What does the Washington DC 311 data include?

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

Do I need an account with Washington DC 311?

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

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.

Washington DC 311

Public data

Ready to useNo account needed

Service requests made to Washington, D.C.'s 311 line over the last 90 days, with call counts and dates. 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.

137,036service requests as of September 2026
About 11,000new service requests a week
1 tableone row per service request

What people use it for

Measure call frequencyUse service call counts to see which requests need the most attention.
Track additionsMonitor when requests are created to understand demand spikes.
Map request sourcesPlot coordinates and zip codes to see where calls come from.

What you get

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

Good to know

Each run replaces the table with requests from the current rolling 90-day window, so status changes show up on the next run. Requests that age out of the window disappear on the next run.

How it works

Choose Washington DC 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 Washington DC 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Washington DC 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Washington DC 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 requests from the current rolling 90-day window, so status changes show up on the next run. Requests that age out of the window disappear on 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 washingtondc_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://maps2.dcgis.dc.gov/dcgis/rest/services/DCGIS_DATA/ServiceRequests/FeatureServer/13

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` DC 311 service requests from the rolling last-90-days FeatureServer layer. Counted exactly 137,036 records via returnCountOnly=true on 2026-09-14, well under the full-scan cap, so each run replaces the destination with the current snapshot; requests that age out of the 90-day source window disappear from the next snapshot. ArcGIS native Date wire values are Unix epoch MILLISECONDS and are preserved as bigint.	beta	full	replace	`SERVICEREQUESTID`	-