What does the Raleigh NC 311 data include?

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

Do I need an account with Raleigh NC 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.

Raleigh NC 311

Public data

Ready to useNo account needed

Raleigh 311 requests with addresses, status, response hours, and resolution information. 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.

15,641service requests as of September 2026
About 320new service requests a week
1 tableone row per service request

What people use it for

Measure response speedUse response-hour data to see how quickly the city handles each request type.
Track current workloadFilter by status to see which requests are open and which are resolved.
Map problem areasGroup requests by address and zip code to find neighborhoods in need.

What you get

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

Good to know

Each run replaces the table with the currently published requests, so closures and status changes show up on the next run. Requests that the city removes from the public layer disappear on the next run.

How it works

Choose Raleigh NC 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 Raleigh NC 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Raleigh NC 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Raleigh NC 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 closures and status changes show up on the next run. Requests that the city removes 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 raleigh_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://services.arcgis.com/v400IkDOw1ad7Yad/arcgis/rest/services/Ask_Raleigh_Requests/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` All 311 service requests currently published in the Ask Raleigh Requests ArcGIS feature layer (layer Service Request), an anonymous public collection. Each run takes a fresh full snapshot of the current exposed collection and replaces the destination, so a request the city removes from the layer is dropped on the next snapshot and edits to already-loaded requests (status, resolution or closure timestamps) arrive as currently published. The publisher states the layer updates about twice a day but documents no retention period, so this connector covers the currently exposed collection and does not claim full history. Measured source volume: 15,641 records (counted on the live endpoint 2026-09-14 with returnCountOnly; an independent count hours earlier the same day read 15,632, so the layer is live and growing). Records are keyed by the layer's native OBJECTID (its uniqueIdField, system-maintained); NUMBER (Service Request Number) is the vendor-marked unique request identifier and is also unique on the source. ArcGIS Date fields (APPLIED_DATE, FIRST_RESPONSE_TIME, ASSIGNED_ON, RESOLVED_AT, CLOSED_AT, SYS_UPDATED_ON) arrive as Unix epoch milliseconds and are preserved as bigint with the exact wire values and their millisecond unit unchanged.	beta	full	replace	`OBJECTID`	-