First – thank you to Esri and everyone else (FEMA GIS, NAPSG Foundation) who makes all of our geospatial tools available for Urban Search and Rescue (US&R). We finally have a common operating platform and mobile apps that firefighters can use. The below is an attempt to help make this system better and prevent us from losing traction with our System members.
During the Champlain Tower Collapse in Surfside, FL we needed to make quick paper maps for the field and incident command post briefings. Our audience is primarily Firefighters, Urban Search and Rescue Teams.
The Problem The Print Widget in Web AppBuilder (we call it “the Intel Manager”) and Web Map Viewer Printing do not provide a printed map that meets our standards. This meant we relied heavily on GIS Professionals off-site and resulted in some teams using other systems (e.g., Powerpoint, SARTopo, hand-drawn maps) that were not tied into our common operating picture. This was a problem on this deployment and will be a big challenge with hurricane response later this year.
Solution: A printing tool that works in ArcGIS Online that has the following capabilities. Please note, ArcGIS Sever is not an option for us. We just need this to work by signing in with our accounts.
1) Preview - Provide a print preview and bounding box - people need to know what map extent they are going to get before they hit print. In addition, it seemed like the PDF produced did not even match what we had on-screen. See the SARTopo video below, we like how they let you select a scale and/or bounding area, center of the map, etc.
2) GeoPDF with QR - The PDF product should be a GeoPDF with scannable QR Codes similar to SARTopo / CalTopo. The PDF should be hosted and accessible via QR Code without any extra work.
3) Grid - USNG / Lat Long Grids similar to SARTopo / CalTopo - for printed maps a USNG Grid is a national standard for search and rescue.
4) North Arrow - this is a standard element for maps.
5) Border - Less white space - we should be able to select the amount of white space/border.
6) Legend - Control over the legend - right now it seems like the legend is never formatted correctly?
7) Page Sizes - a 24x36 and similar size is a must. Also, just use plain language alongside ARCH and ANSI codes, people don't have these memorized!
8 Scale – the scale bar always seems to have strange decimals or not whole numbers? Is there a way to fix this?
While we know the push is to use mobile apps (Survey123, QuickCapture, Field Maps - and we do!), first responders are going to want a printed map for a very long time - for at least the next 10 years. If we cannot get a good printed map out of the system they will continue to seek alternatives, which defeats the purpose of a common operating platform.
Brandy Florida Task Force 1
Santiago Florida Task Force 2
More information about our tools https://www.responsesystem.org/usrfielddocumentationnapsginfo
Not so good map made with Web AppBuilder (off-centered, no north arrow, wierd legend and scale bar, etc.):
Slightly better map made with SARTopo (but not using our common operating platform or imagery)
SARTopo Examples below:
Ideal Map made with ArcGIS Pro:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.