Do I need an account with Miami-Dade County FL 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.

Miami-Dade County FL 311

Public data

Ready to useNo account needed

Miami-Dade County FL 311 data, published as Miami-Dade County FL 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.

343,851rows as of September 2026
1 tablein your warehouse

What you get

Table Each row is

Table	Each row is
featureserver `featureserver`	All 343,851 Miami-Dade County 311 service requests created in 2023, one row per ticket (ticket_id is the unique business key; the layer also maintains its own system ObjectId). The vendor publishes one table per calendar year; data_311_2023 is the last year published and is final (last edited 2024-03-17). ArcGIS native pagination (resultOffset + resultRecordCount, page cap 1000) walks the whole table each run; the stop condition is read from the body (no 'exceededTransferLimit' flag on the final page). The three esriFieldTypeDate columns arrive as Unix epoch MILLISECONDS and are preserved as bigint, not converted.

featureserver

featureserver

All 343,851 Miami-Dade County 311 service requests created in 2023, one row per ticket (ticket_id is the unique business key; the layer also maintains its own system ObjectId). The vendor publishes one table per calendar year; data_311_2023 is the last year published and is final (last edited 2024-03-17). ArcGIS native pagination (resultOffset + resultRecordCount, page cap 1000) walks the whole table each run; the stop condition is read from the body (no 'exceededTransferLimit' flag on the final page). The three esriFieldTypeDate columns arrive as Unix epoch MILLISECONDS and are preserved as bigint, not converted.

How it works

Choose Miami-Dade County FL 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 Miami-Dade County FL 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Miami-Dade County FL 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 miamidade_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://services.arcgis.com/8Pc9XBTAsYuxx9Ny/arcgis/rest/services/data_311_2023/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` All 343,851 Miami-Dade County 311 service requests created in 2023, one row per ticket (ticket_id is the unique business key; the layer also maintains its own system ObjectId). The vendor publishes one table per calendar year; data_311_2023 is the last year published and is final (last edited 2024-03-17). ArcGIS native pagination (resultOffset + resultRecordCount, page cap 1000) walks the whole table each run; the stop condition is read from the body (no 'exceededTransferLimit' flag on the final page). The three esriFieldTypeDate columns arrive as Unix epoch MILLISECONDS and are preserved as bigint, not converted.	beta	staleness	merge	`ticket_id`	staleness_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 Miami-Dade County FL 311 data into your warehouse

Last updated 2026-10-16.