Put the work on the map.
Automatically.
Add and update features on ArcGIS feature layers, turn latitude and longitude into map points, and write PostGIS geometry, all from the same flows that move your records.
| attribute | value |
|---|---|
| PERMIT_NO | B26-01182 |
| TYPE | Residential solar |
| STATUS | Issued |
| geometry | x: -119.77, y: 36.79 (WGS84) |
Add and update features.
The ArcGIS connector reads features (queried in WGS84, 4326) and adds or updates them with attributes and geometry. Errors ArcGIS reports inside a successful response are caught and logged per feature.
- Issued permits, code cases, 311 requests as points
- Attributes mapped like any other fields
- ArcGIS sandbox layer for practice
Coordinates in, geometry out.
The Make map point step builds an ArcGIS point or GeoJSON from latitude and longitude fields, and can drop records with no coordinates. Write to database does the same for a PostGIS column in the spatial reference you choose.
- ArcGIS or GeoJSON point formats
- Drop or keep records without coordinates
- Esri World Geocoder and US Census Geocoder for addresses
State Plane in, web maps out.
Reproject between coordinate systems with every NAD83 State Plane zone (feet and meters) and every UTM zone built in, so nothing is looked up online. Check locations catches swapped latitude and longitude, points at 0,0 and points outside your county before they reach a map.
- Reproject X/Y fields or whole geometries
- Check locations: Valid and Invalid outputs
- GeoJSON and zipped Shapefile files, in memory
| attribute | value |
|---|---|
| PERMIT_NO | B26-01182 |
| TYPE | Residential solar |
| STATUS | Issued |
| geometry | x: -119.77, y: 36.79 (WGS84) |
Add, update and delete features.
Edit ArcGIS layer keeps a feature layer in step with your system: it matches features by OBJECTID, GlobalID or your own key field, updates the ones that exist, adds the rest, and deletes what's gone, in batches with a result for every feature.
- Upsert by key field
- All-or-nothing per batch
- Feature IDs in run history, never attributes
See it in real flows.
Publish issued permits to an ArcGIS map layer
Nightly, reads permits issued since the last run from the city database and adds them as points on an ArcGIS feature layer.
Sentra 311 → PostgreSQL / PostGISCopy 311 requests into the city database, with map points
Every 15 minutes, upserts new and changed Sentra 311 requests into a PostGIS table, with a map point built from latitude and longitude.
Sentra 311 → Sentra Scheduler → PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP server311 triage: route every request to the right system
Cleans and checks changed 311 requests, sends bad ones to a data-quality sub-flow, checks the city database to see if each is new, then routes new…
Questions, answered
Do you support ArcGIS Online and Enterprise?
The connector works with ArcGIS feature layer REST endpoints, which both provide. Each city's layer URL and sign-in are set on the connection.
Can we geocode addresses?
Yes, with the Esri World Geocoder or the free US Census Geocoder as a Look up step.
Which coordinate systems are included?
All NAD83, NAD83(HARN) and NAD83(2011) State Plane zones in US feet and meters, all UTM zones, WGS 84 (4326) and Web Mercator (3857). They ship with SentraBridge, so reprojection works on closed networks.
See your own systems connected.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.