Latest Contributions by Brian_McLeer

Overview GitHub: https://github.com/brianmcleer/add-edit-etl-widget Add, Map & Edit Data is a customized widget that combines two of Esri's out of the box widgets, Add Data and Edit, and drops a field-mapping step in between them. It came out of a recurring headache I kept running into. Someone has a spreadsheet or a layer they want to get into an existing editable layer, but the incoming field names never line up with the target, so the data has to be reshaped outside Experience Builder before anyone can edit it. I wanted the whole thing, add, map, load, and edit, to happen in one widget without leaving the app. The user adds data the same way the stock Add Data widget works, from a file, a URL, or ArcGIS content. Then they map the incoming fields onto the target layer's fields. The mapping handles one to one, many to one, one to many, and many to many, so you can concatenate a couple of fields into one, split one field into several, coalesce, drop in a constant, or write a small expression when you need it. After a quick validate and preview, it loads the records into the target layer in batches, and then they can edit what they just loaded on the map with the regular Edit tools. As with my other widgets, the target layer and the options all live in the settings panel, so you point it at your own layer without editing code. Mappings also export and import as XML, which means a mapping you build once for a recurring load can be saved and reused instead of rebuilt every time. Adding your data The add step is the stock Add Data experience, so the source can come from three places: A file from your computer. Supported uploads are shapefile, file geodatabase, CSV, GeoJSON, KML, and GPX. Shapefiles and file geodatabases have to be zipped. Esri's limits apply here: CSV is capped at 1,000 records, the other types at 4,000, with a 2 MB limit for shapefiles and 10 MB for everything else, and up to 30 files at once. A URL to a web service. You can point at a feature service, map service, vector tile service, image service, scene service, WFS, WMS, WMTS, KML, GeoJSON, or CSV. ArcGIS content. Search your own content, your groups, your organization, and public content, including ArcGIS Living Atlas of the World. Whatever the source, once it is in, the mapping step lines its fields up with your target layer, so the format it arrived in does not matter by the time the records get written. Features Really this is a lightweight ETL tool that runs inside Experience Builder. Add is the extract, the mapping step is the transform, and writing to the target layer is the load, so the kind of reshaping you would normally do in a desktop tool or a separate ETL step happens right in the app instead. A lightweight, in-app ETL workflow: extract with Add Data, transform with the field mapping, and load into your target layer, with no separate desktop or ETL step. Add Data, field mapping, load, and Edit in one guided widget. Field mapping across one to one, many to one, one to many, and many to many, with type coercion and validation before anything is written. A validate and preview step, then a batched load with a progress readout. Mapping export and import as XML for repeatable, reusable loads. Optional add of the target layer to the map, with zoom to the loaded features and zoom to a feature when it is selected during editing. A configurable zoom scale, so zoom to actually changes scale instead of only panning. The Edit permissions, snapping options, and advanced editing tools surfaced in the settings panel. Keyboard accessible controls and screen reader labels throughout. Requirements ArcGIS Experience Builder Developer Edition 1.19 or 1.20, which run React 19. EB 1.18 and earlier run React 18 and are not supported. Install Download the attached zip and extract it. Drop the add-edit-etl folder into client\your-extensions\widgets so its manifest.json sits directly inside client\your-extensions\widgets\add-edit-etl, not nested a second level deep. Run npm install in the client folder, then restart. The full steps, including the duplicate-name fix, are in the README on GitHub. Feedback This is the first version, so expect a few rough edges. If you run into a bug or have an idea for something it should do, please leave it in the comments on this post and I will take a look. Credits and license This is a derivative work based on Esri's Add Data and Edit widgets, both by the Esri R&D Center Beijing, published under the Apache License, Version 2.0. It has been combined, modified, and extended by the City of Grand Junction, CO. Licensed under Apache-2.0. Original work copyright Esri; modifications copyright City of Grand Junction, CO. Changelog July 23, 2026:  v1.2.1 updates the widget for Experience Builder 1.21 compatibility, with the manifest and package versions bumped to 1.21 and a widget-level tsconfig added for cleaner editor type resolution. July 7, 2026:  Insert, update, or upsert. Pick a key field and a reload updates records in place instead of duplicating them. Check data before you load. Reports nulls, bad values, domain violations, and duplicate keys without writing anything. New transforms: date parsing with a format hint, value maps for recoding, unit conversion, and {field} templates. Failed rows download as a CSV with the error for each. XML export now carries everything, including the load mode and key. June 23, 2026: Add multiple target layers and on-map symbology editing, move and restyle the symbology panel. June 22, 2026: Initial release, now on GitHub. ... View more

A custom widget for ArcGIS Experience Builder. A resident enters an address, the widget returns which polygon zone the address falls in, then renders a configurable template populated with that zone's fields. Workflow is generic: address in, polygon match out, template populated with matched zone attributes. Possible use cases include council districts, polling places, school boundaries, snow routes, code enforcement zones, leaf pickup areas, garbage day, or anything point-in-polygon. Configurable via the settings panel or XML import/export. Repo: https://github.com/brianmcleer/zone-lookup-widget A couple notes: The spatial query does an exact intersect first, then a 30m buffered retry if nothing hits. Helps with geocoders that return points slightly off the parcel. There's an "Optimize for iframe" toggle in settings that makes the widget fill its parent height. Useful when the host page sets a fixed iframe height. Same widget works in regular EB layouts without the toggle. XML config import/export round-trips most settings (template, labels, brand colors, feature toggles, and so on). The zone layer data source itself does not, since EB stores it as an app-specific UUID rather than a URL. Re-link the layer after import. Changelog: 7/24/26:  Updated the Zone Lookup widget for Experience Builder 1.21. This release resolves TypeScript editor errors related to Experience Builder runtime properties. No runtime functionality was changed. ... View more

Custom Experience Builder widget. Upload a CSV or Excel file of addresses, geocode them against any ArcGIS Locator, and see the matched points on a connected Map widget. Results export as GeoJSON, KML, or Shapefile. GitHub: https://github.com/brianmcleer/csv-geocoder-widget Built and tested on Experience Builder 1.19 and 1.20. Install steps and feedback link are in the GitHub README. Zip attached below. Changelog: 7/23/26:  Updated the CSV Geocoder widget to work with Experience Builder 1.21. Added a Review Failures panel for failed and low-score addresses. Added search and more details for failed records, including the original CSV values, submitted address, score, reason, and closest match. Improved the back button, keyboard navigation, and focus behavior in the failure review panel. Fixed the TypeScript, JSX, and ArcGIS module errors that came up after moving to 1.21. Added the needed Excel typings and updated the widget metadata and documentation. Updated the GitHub publish script to use the 1.21 widget folder. Updated the publish process so node_modules, .vs, build files, and other development files are not included in GitHub or the release ZIP. ... View more