Hello again ESRI Community,
I wanted to follow up on my original question and share where we’ve landed after working through a Customer Support process with SmartGov.
Our Planning Department now has a functional workflow that allows us to use packaged parcel data published from our Borough Assessing Office to populate parcel and ownership information in SmartGov. While the process is still manual, it is significantly more automated than our previous approach and greatly reduces opportunities for human error.
Below is the current workflow we are using.
ArcGIS Pro Workflow (Desktop): Creating Parcel Data
- Retrieve parcel data via an API connector and save to a local server.
- Clip redacted parcels to the jurisdictional boundary using
Geoprocessing → Clip. - Name output using a standardized convention (e.g., Redacted_Parcels_MMDDYYYY).
- Publish to ArcGIS Online with tags such as Planning and SmartGov.
- Layer must be Publicly shared (Admin-level publishing) — no token required.
ArcGIS Online Workflow - Creating Parcel Data
- Create a SmartGovParcels_Linked layer in AGOL. Data for this map should be utilized from a supplied parcel data source API.
- Use Tools → Analysis → Overlay → Clip to refine parcels to jurisdiction.
- Publish the result as a Hosted Feature Layer, again naming with the date.
- Maintain public sharing to support SmartGov access without authentication.
SmartGov Administration
- Navigate to Jurisdiction Setup → Mapping Setup.
- Add the AGOL Feature Service URL.
- Map the appropriate PARCEL_ID field.
- Under Job Setup → Parcel Loader – ArcGIS, run the Parcel Loader using the same URL.
- Verify that username/password fields are not populated.
- The Parcel Load Job itself is a configurable SmartGov job that may need to be customized or created with SmartGov Development support, depending on organizational needs.
SmartGov Permit Associations
- Open an existing permit.
- Add the parcel using the current Parcel ID.
- Mark it as the Primary Parcel and save.
- Verify successful linkage in Workspace → Map.
Thanks again to everyone who contributed insights earlier. I’m hopeful this recap helps others working through similar GIS ↔ permitting integrations, and I’d welcome hearing how others have refined or automated comparable workflows.
