Permits to open data
Nightly, changed OpenGov permit records are upserted into the city's permits dataset.
Socrata, now Tyler Data & Insights, runs open-data portals for many US cities and counties. Residents, journalists and other agencies query datasets of permits, service requests, budgets and inspections through the SODA API.
SentraBridge reads dataset rows and writes to datasets with upserts by row ID, so nightly publishing doesn't create duplicates. Flows choose which fields go public before writing. Rows pass through in memory and SentraBridge doesn't store them.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Dataset rows (set the dataset variable, e.g. abcd-1234) | list | create | yes | Row ID, Updated |
Nightly, changed OpenGov permit records are upserted into the city's permits dataset.
Closed service requests, without reporter details, are published each night.
Adopted and amended budget lines from Munis are published after each budget update.
A county or state dataset is read and loaded into the city database for analysis.
Systems cities commonly connect with Socrata, each with its own connector page.
Yes. The SODA API reads and writes dataset rows. Writes with a row ID are upserts.
Read permits changed since the last run, keep only public fields, and upsert them into the dataset each night. A template does this for OpenGov.
The Map step sends only the fields you choose. Rules can also drop records, such as cases involving minors.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.