Every RAPT layer in one friendly place — hazards, infrastructure, and people & community. Search it, preview it on the map, and add what you need to your own map. No menu‑digging.
Take your selected layers into your own ArcGIS Online map — three ways, no rebuilding.
One click opens a fresh Map Viewer in your org with the item-backed layers pre-loaded and fully RAPT-styled. Sign in, then Save as your own web map.
Map Viewer's Add → From URL box takes one endpoint per paste. Click below to copy each layer in turn: paste it, add it, then click again for the next. Works for all 106 layers, including the real-time feeds.
A valid web map definition for power users — copy it into ArcGIS Assistant, download it, or use the REST addItem call to drop a finished map straight into your content.
A plain-English guide for the RAPT / Experience Builder team. The whole thing was built with no hand-written code — just plain-English requests to an AI tool, which found RAPT’s layers and wrote the page.
You write no code. You just describe the goal, the way you’d say it to a colleague: “Find all of RAPT’s layers and where each one lives, and build a searchable catalog that shows them on a map and lets people add them to their own map.” The AI builds it. You shape it the same conversational way — “make it full-screen,” “add a table view,” “let the filters combine” — and it updates each time.
You never go hunting for anything. From that one request, the AI finds RAPT’s published map, pulls in all 106 layers, and picks up the web address of every layer — automatically. That collection becomes the catalog. The same request works on any RAPT or ArcGIS map you point it at.
You get back a single file. Open it and it works in any web browser — nothing to install, nothing to set up. Everything you see — the search, the filters, the three views, the map preview, adding layers — is already inside that one file. It’s the same kind of web page Experience Builder uses, so it drops right in.
Adding the catalog to your app is one step. In Experience Builder, drop in the Embed widget and give it the web address (link) of your hosted page:
Insert → Embed → paste the link.
The live, fully interactive catalog appears right inside your app — search, filters, the map — working exactly as it does on its own. Nothing to rebuild.
The only thing this needs is for the page to be hosted somewhere it can be reached by a link — which is next.
Don’t let “hosting” sound bigger than it is. You already host fema.gov, the RAPT tool, and your maps — on systems the government has already approved. This is one small web page. It fits the very same place your approved web content already lives. You’re not hosting something new and risky; you’re hosting one more simple file next to things far bigger than it.
And a single static page is one of the safest things you can host:
So the question isn’t “can we host this safely” — it’s just where the file goes:
The one thing to avoid for production is a random commercial host (like the one this quick demo sits on). Anywhere already trusted for your other web content is fine.
It stays entirely in the Esri world. The map, the layers, and the sign-in all come from Esri’s own services. It embeds inside Experience Builder like any other Esri piece — nothing new or foreign is introduced.
It holds nothing, so there’s nothing to breach. No database, no copies of data, no passwords in the file. It only reads your live Esri layers — read-only, it never changes your services.
Security is Esri’s, not the tool’s. Public layers stay open; any protected layer still requires the user’s normal ArcGIS sign-in. It can’t show anyone something they aren’t already allowed to see.
Easy to keep running — the “bus factor.” It’s one plain, readable file. If the person who built it walks away, anyone — any developer, or an AI tool in minutes — can open it and change it. A custom Experience Builder or Esri build needs specialist expertise and tooling; one simple file is far less risky to own over the years.
(It’s also built to the usual Section 508 accessibility expectations — keyboard-friendly, readable contrast, proper labels.)