Do I need an account with Santa Fe NM 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.

Santa Fe NM 311

Public data

Ready to useNo account needed

Santa Fe NM 311 data, published as Santa Fe NM 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.

37,872rows as of September 2026
1 tablein your warehouse

What you get

Table Each row is

Table	Each row is
featureserver `featureserver`	City of Santa Fe report-a-problem requests from the public ArcGIS layer 'CRM___Report_a_Problem_1'. Each request is one Survey123 submission row; form-branch columns are sparse Survey123 answers that are null for problem types they do not apply to. The layer is re-read in full on every run (37,872 rows as of 2026-09-16, by far within read budget), keyed on the system-maintained row id objectid and merged on the Survey123 submission id globalid so re-reads update request status without duplicating rows. Every published field lands as the city publishes it, including reporters' names, phone numbers and email addresses, utility account numbers, and birth dates and driver's license numbers on some dog complaints. ArcGIS native Date columns (CreationDate, EditDate, end_time, resolved_on, trash_date_and_at_what_time_did_) arrive as epoch milliseconds and are kept as bigint; detect_timestamps is disabled so they are not misread as Unix seconds. New submissions effectively stopped in April 2026 (805 in January 2026, 138 in April, 0 to 2 a month since), while existing requests are still being edited, so treat it as the form's history rather than a live intake feed.

featureserver

featureserver

City of Santa Fe report-a-problem requests from the public ArcGIS layer 'CRM___Report_a_Problem_1'. Each request is one Survey123 submission row; form-branch columns are sparse Survey123 answers that are null for problem types they do not apply to. The layer is re-read in full on every run (37,872 rows as of 2026-09-16, by far within read budget), keyed on the system-maintained row id objectid and merged on the Survey123 submission id globalid so re-reads update request status without duplicating rows. Every published field lands as the city publishes it, including reporters' names, phone numbers and email addresses, utility account numbers, and birth dates and driver's license numbers on some dog complaints. ArcGIS native Date columns (CreationDate, EditDate, end_time, resolved_on, trash_date_and_at_what_time_did_) arrive as epoch milliseconds and are kept as bigint; detect_timestamps is disabled so they are not misread as Unix seconds. New submissions effectively stopped in April 2026 (805 in January 2026, 138 in April, 0 to 2 a month since), while existing requests are still being edited, so treat it as the form's history rather than a live intake feed.

How it works

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

Vendor documentation: https://services7.arcgis.com/p0Gk2nDbPs7KEqSZ/arcgis/rest/services/service_06e888807858433c8c54132d4465b54b/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` City of Santa Fe report-a-problem requests from the public ArcGIS layer 'CRM___Report_a_Problem_1'. Each request is one Survey123 submission row; form-branch columns are sparse Survey123 answers that are null for problem types they do not apply to. The layer is re-read in full on every run (37,872 rows as of 2026-09-16, by far within read budget), keyed on the system-maintained row id objectid and merged on the Survey123 submission id globalid so re-reads update request status without duplicating rows. Every published field lands as the city publishes it, including reporters' names, phone numbers and email addresses, utility account numbers, and birth dates and driver's license numbers on some dog complaints. ArcGIS native Date columns (CreationDate, EditDate, end_time, resolved_on, trash_date_and_at_what_time_did_) arrive as epoch milliseconds and are kept as bigint; detect_timestamps is disabled so they are not misread as Unix seconds. New submissions effectively stopped in April 2026 (805 in January 2026, 138 in April, 0 to 2 a month since), while existing requests are still being edited, so treat it as the form's history rather than a live intake feed.	beta	full	merge	`objectid`	-

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 Santa Fe NM 311 data into your warehouse

Last updated 2026-10-16.