Web GIS application · 2024 – 2026

A web editor for jurisdiction boundaries, with every version kept

Boundary edits used to be a manual merge-and-clip job in ArcGIS Pro. In this browser-based editor, staff pick a jurisdiction, pull up a location feature by its ID, merge it into the boundary or remove it, preview the result and confirm, with the support ticket attached. Written business rules guide the edits, so staff with no ArcGIS Pro experience can make fast, accurate and safe geometry edits. Every change archives the previous version first, and any version can be restored.

Organization
FilmLA
Year
2024 – 2026
Merge or remove
in the browser, in place of a manual merge and clip in ArcGIS Pro
Preview first
the new boundary shows on the map before anything is saved
No Pro needed
staff without ArcGIS Pro make fast, accurate, safe edits

Results

  • Boundary edits in the browser: pick a feature, merge or remove it, preview, confirm.
  • Every edit carries its support ticket and archives the previous version first; if the archive fails, nothing changes.
  • Any archived version can be restored, geometry only or in full.

My role

Designed and built the application and its deployment.

Stack

  • ArcGIS Maps SDK for JavaScript
  • ArcGIS Enterprise
  • SQL triggers
  • OAuth 2.0 (PKCE)
  • Vite
  • JavaScript
  • DOMPurify
Diagram: sign in with ArcGIS Enterprise (OAuth 2.0 PKCE), pick a jurisdiction and a location feature, then merge the feature into the boundary or remove it and preview the result, guided by written business rules. The current version is copied to an archive layer first, and if that fails the edit stops. Only the changed fields are then written to the live layer. Any archived version can be restored, geometry only or in full. Business rules, token refresh and unit tests sit around every edit.
Select, archive, edit, restore: no boundary change is written until the version before it is safe.

From ArcGIS Pro to the browser

Changing a jurisdiction boundary used to mean merging and clipping polygons by hand in ArcGIS Pro, a job only GIS staff could do. In the editor, staff pick a jurisdiction, enter a location’s ID to pull up the matching feature, and choose Merge or Remove. The new boundary is previewed on the map before anything is saved, and the edit is confirmed with its support ticket attached, so every change has an audit trail. Written business rules guide the edits, so people with no ArcGIS Pro experience can make geometry edits quickly, accurately and safely.

The editor, step by step

Start: Choose Edit or Restore, and which kind of jurisdiction to work on.
01 Start. Choose Edit or Restore, and which kind of jurisdiction to work on.
Pick a jurisdiction: Its boundary lights up on the map and the matching features are listed.
02 Pick a jurisdiction. Its boundary lights up on the map and the matching features are listed.
Open it: The jurisdiction and the chosen feature load beside the map. The pencil starts an edit.
03 Open it. The jurisdiction and the chosen feature load beside the map. The pencil starts an edit.
Merge or remove: Merge the feature into the boundary or cut it out, preview the change, then confirm it with its support ticket.
04 Merge or remove. Merge the feature into the boundary or cut it out, preview the change, then confirm it with its support ticket.
Restore: Every earlier version of a boundary is archived with its edit notes. Pick one and preview it before restoring it.
05 Restore. Every earlier version of a boundary is archived with its edit notes. Pick one and preview it before restoring it.

Choose Edit or Restore, and which kind of jurisdiction to work on.

Real screenshots. Identifying details are blurred.

Edits you can take back

Film permits depend on jurisdiction boundaries, so a bad edit has real consequences. The editor writes the current version to an archive layer before it changes anything. If that write fails, the edit stops. Only the fields that actually changed are sent, and any archived version can be put back onto the live layer, geometry only or in full.

  • Secure sign-in. ArcGIS Enterprise accounts through OAuth 2.0 with PKCE, so no client secret ships with the app. Tokens refresh on authentication errors, and a connection monitor warns when the network drops.
  • Lookups that keep up. SQL triggers in the database update the jurisdiction and school lookups when a boundary changes.
  • Tested. Unit tests, including a check that no secrets are committed, and a written test plan and code review.