Latest Contributions by MatthewDriscoll

It's March in Kansas. Tornado season is ramping up. And if you've worked in emergency management or public safety GIS, you know the drill — when something hits, people need tools now. So I tried an experiment: How fast can I go from zero to a working, mobile-friendly field assessment app using AI and the ArcGIS Maps SDK for JavaScript 5.0? The answer surprised me. The Scenario This is a fictional scenario used to demonstrate the workflow — no actual emergency occurred. A tornado rips through the county. Fire and rescue need to go door to door checking on residents and assessing damage. They need a map application — on their phone — where they can tap a parcel, flag injuries, structural damage, or trapped persons, add comments, and submit. The data needs to flow back to ArcGIS Online in real time so the office has a live picture of response progress. Full walkthrough: from ArcGIS Online setup to working field app. The Tools ◈ ArcGIS Online — hosted feature layers ◈ Claude AI — Anthropic's AI assistant ◈ ArcGIS Maps SDK for JavaScript 5.0 ◈ A web server — IIS in my case, but any will do. That's it. No frameworks, no build tools, no npm install. One HTML file. The Process I created a hosted feature layer in ArcGIS Online with the important fields for person and property assessment, then opened Claude, attached two example applications I'd previously built with SDK 5.0 (since the version is brand new and examples help the AI produce better code), described the scenario, and let it build. Did it work perfectly on the first try? No — and I left that in the video on purpose. Claude hit a script loading order issue, a geometry type mismatch, and a URL that needed a layer index appended. But each time, I pasted the error back in and Claude diagnosed and fixed it within seconds. The entire build-and-debug cycle took roughly 30 minutes. The result is a dark-themed emergency assessment app with aerial basemap imagery, a tornado path overlay, property search with wildcard matching, a responsive sidebar assessment form, and real-time data submission to ArcGIS Online — all in a single index.html file I dropped into an IIS folder. What I Learned Give AI examples. SDK 5.0 is new enough that Claude benefits from seeing real working code in the patterns you want. Attaching previous projects made a big difference in output quality. Linking to the SDK 5.0 documentation would likely help even more. Expect iteration, not magic. AI isn't going to hand you a perfect app on the first prompt. But it compresses what used to be hours of Stack Overflow and documentation hunting into a rapid conversation. The more you use it, the better your prompts get — and the better the results. Save your projects. The Claude project with all the prompts, examples, and conversation history is saved. Next time a similar scenario comes up — a flood, a wildfire, a hazmat incident — you have a template ready. You're not starting from scratch. Keep it real. This video intentionally shows the messy parts — the errors, the fixes, the rough edges. I wanted to showcase real-time capability, not sell a fantasy. There's still cleanup to do (centering, polish, etc.), but in an emergency, good enough right now beats perfect next week. What This Means for GIS Professionals AI isn't replacing us. It's an accelerator. You still need to know your data, your services, your projections, your deployment. What changes is the speed at which you can go from "I need this" to "here it is." And for emergency response, that speed saves lives. I'd love to see what others build with this approach. Drop a comment below or share your own experiments. And if you're curious about the new AI components in SDK 5.0 — that's a whole other rabbit hole worth exploring. Stay safe out there. ... View more

Esri Team, If we create custom div(s) is it best practice to keep them outside of the <calcite-shell> & <arcgis-map>?    I ask because I have done this and have run into some users not being able to get to those outside div(s).  When they try and click on one, the map is the focus, cannot reach the custom div.  It is only a few so far, and unfortunately not any users I personally know so I am having trouble finding what is going on.  My best guesses are that they have older windows, chrome, or their computers are not webGL compatible.  Or possibly a stacking issue. Or should I keep them outside the <arcgis-map> but inside the <calcite-shell> perhaps? Could we possible get a slot="manual" so we can keep them in the map but have more control?  Or am I missing something here? I isolated my custom div(s) from the shell for now...waiting to see if I get any more phone calls. #optionsDiv, #toolbarDiv, #topRightTools, #searchHelpPanel { pointer-events: auto; isolation: isolate; /* forces new stacking context */ } /* this does nothing */ arcgis-map:focus, arcgis-map *:focus { outline: none !important; } calcite-shell { isolation: isolate; }   ... View more