Do I need an account with Prince George's County 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.

Will running it again create duplicate rows?

No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

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.

Prince George's County MD 311

Public data

Ready to useNo account needed

Prince George's County MD 311 data, published as Prince George's County MD 311 publishes it. 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.

444,109rows as of September 2026
1 tablein your warehouse

What you get

Table Each row is

Table	Each row is
records `records`	Prince George's County 311 service request records. First sync is the full history (watermark on the request-opened date), later runs fetch only requests opened after the cursor and merge updates them in place by service_request. This dataset has no modified-date column at all, so a status change on an already-loaded row is never re-fetched by any plan; only creation-time changes are captured. The publisher's refresh is irregular (currently stalled since 2026-07-20). The dataset carries 9 exact duplicate rows of 3 requests, which the merge on service_request collapses: 444,100 requests from 444,109 rows on 2026-09-16.

records

records

Prince George's County 311 service request records. First sync is the full history (watermark on the request-opened date), later runs fetch only requests opened after the cursor and merge updates them in place by service_request. This dataset has no modified-date column at all, so a status change on an already-loaded row is never re-fetched by any plan; only creation-time changes are captured. The publisher's refresh is irregular (currently stalled since 2026-07-20). The dataset carries 9 exact duplicate rows of 3 requests, which the merge on service_request collapses: 444,100 requests from 444,109 rows on 2026-09-16.

How it works

Choose Prince George's County 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

Do I need an account with Prince George's County MD 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Prince George's County 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.
Will running it again create duplicate rows?: No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
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 princegeorgescountymd_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.princegeorgescountymd.gov/d/2ywx-ipcd

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` Prince George's County 311 service request records. First sync is the full history (watermark on the request-opened date), later runs fetch only requests opened after the cursor and merge updates them in place by service_request. This dataset has no modified-date column at all, so a status change on an already-loaded row is never re-fetched by any plan; only creation-time changes are captured. The publisher's refresh is irregular (currently stalled since 2026-07-20). The dataset carries 9 exact duplicate rows of 3 requests, which the merge on service_request collapses: 444,100 requests from 444,109 rows on 2026-09-16.	beta	watermark	merge	`service_request`	backfill_days

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.

Get Prince George's County MD 311 data into your warehouse

Last updated 2026-10-16.