What does the Scottsdale AZ 311 data include?

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

Do I need an account with Scottsdale AZ 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.

Scottsdale AZ 311

Public data

Ready to useNo account needed

Scottsdale 311 requests with workgroup assignment, status, 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.

238,770service requests as of September 2026
About 1,200new service requests a week
1 tableone row per service request

What people use it for

Balance workgroup loadGroup requests by workgroup to see which team handles the most calls.
Track current statusFilter by request status to see open work and recent closures.
Find problem areasUse coordinates to map where calls cluster across the city.

What you get

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

Good to know

Each run replaces the table with the currently published requests, so status changes and closure dates show up on the next run. Requests removed from the public layer disappear on the next run.

How it works

Choose Scottsdale AZ 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 Scottsdale AZ 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Scottsdale AZ 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Scottsdale AZ 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 the currently published requests, so status changes and closure dates show up on the next run. Requests removed from the public layer 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 scottsdale_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://developers.arcgis.com/rest/services-reference/enterprise/query-map-service-layer/

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`mapserver` The currently published Scottsdale 311 public service-request collection (Workgroup, RequestType, RequestStatus, Address, coordinates, CreatedDate, ClosedDate). Observed coverage is 238,770 records across 239 offset pages of 1,000 — the whole collection is re-fetched on every run and replaces the destination, so later status changes and closures are captured. ArcGIS native Date fields (CreatedDate, ClosedDate) are returned as Unix epoch MILLISECONDS and preserved as bigint; coverage is as published in the layer, and historical completeness or long-term retention is not asserted.	beta	full	replace	`Requests`	-