Do I need an account with San Antonio TX 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 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.

San Antonio TX 311

Public data

Ready to useNo account needed

San Antonio TX 311 data, published as San Antonio TX 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.

505,451rows as of September 2026
About 7,400new rows a week
1 tablein your warehouse

What you get

Table Each row is

Table	Each row is
featureserver `featureserver`	All records of the publisher's "311 All Service Calls" layer (505,451 rows as measured 2026-09-16). The publisher truncates and reloads the layer on each periodic refresh, so OBJECTID is only a per-run row id and no stable business key exists (CaseID is a 0 sentinel on every row); this resource mirrors the current layer on every run with a full replace. Date fields (OpenedDateTime, SLADate, ClosedDateTime, ReportStartingDate, ReportEndingDate) travel as ArcGIS native date values (Unix epoch milliseconds) and are preserved as bigint.

featureserver

featureserver

All records of the publisher's "311 All Service Calls" layer (505,451 rows as measured 2026-09-16). The publisher truncates and reloads the layer on each periodic refresh, so OBJECTID is only a per-run row id and no stable business key exists (CaseID is a 0 sentinel on every row); this resource mirrors the current layer on every run with a full replace. Date fields (OpenedDateTime, SLADate, ClosedDateTime, ReportStartingDate, ReportEndingDate) travel as ArcGIS native date values (Unix epoch milliseconds) and are preserved as bigint.

How it works

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

Vendor documentation: https://services.arcgis.com/g1fRTDLeMgspWrYp/arcgis/rest/services/311_All_Service_Calls/FeatureServer/0

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`featureserver` All records of the publisher's "311 All Service Calls" layer (505,451 rows as measured 2026-09-16). The publisher truncates and reloads the layer on each periodic refresh, so OBJECTID is only a per-run row id and no stable business key exists (CaseID is a 0 sentinel on every row); this resource mirrors the current layer on every run with a full replace. Date fields (OpenedDateTime, SLADate, ClosedDateTime, ReportStartingDate, ReportEndingDate) travel as ArcGIS native date values (Unix epoch milliseconds) and are preserved as bigint.	beta	full	replace	`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 San Antonio TX 311 data into your warehouse

Last updated 2026-10-16.