What does the Encinitas CA 311 data include?

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

Do I need an account with Encinitas CA 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. Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.

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.

Encinitas CA 311

Public data

Ready to useNo account needed

Service requests reported to Encinitas, California's 311 line, as the city publishes them. 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.

What people use it for

Track how long requests take to resolveCompare when a request is made and when it is resolved.
Watch demand over timeTrack how many requests are made, week by week or year by year.
Map where requests come fromPlot requests using their location to see where they cluster.

What you get

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

Good to know

Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.

How it works

Choose Encinitas CA 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 Encinitas CA 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Encinitas CA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Encinitas CA 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 re-reads everything and updates rows that changed. Rows the source removes stay in your table.
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 encinitas_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://datainsights.encinitasca.gov/d/62v4-sf7z

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` Encinitas service requests. Each sync reads the current published dataset and updates records by requestid. Source deletions are not removed from the destination.	beta	full	merge	`requestid`	-