Create Master Projects

Multipage or tiled maps are a series of tiled, overlapping map sheets that are used when the incident area expands or is projected to expand larger than will fit on a single 1:24,000 map sheet. Multipage map examples include IAP maps, division or branch tiles, and structure triage maps.  Each map sheet should contain the required elements of the map and be able to be used individually and with adjoining map sheets.  An index map sheet may be added if a vicinity map is not placed on the individual map sheets and map sheets should be numbered sequentially. The map sheets should be created for the entire incident area.

Key Components

• Multiple map sheets called pages, tiles, or grids.
• One index map sheet if the vicinity map is not used.
• STANDL-SGD elements on each map sheet.
• Sequential ID on each map sheet.
• Lat/Long graticule on each map sheet.
• Complete coverage of an incident area.
• Fit entire division(s) on map sheet where practical–don't force field users to reference multiple maps.
• Add more labels when divisions span multiple map sheets–see annotation definition query How To below.
• Maps will be copied in black and white–don't rely on color.
• Map sheets must overlap.
• Index map is for reference only – keep it simple.
• Wildfire Daily Fire Perimeter polygon outline should be removed when visible under Event Line features (e.g., dozer line).

For the complete list of product standards and map examples, refer to the NWCG Standards for Geospatial Operations (GeoOps), PMS 936.

Job Aids

• Multipage Map Workflows
• YouTube Playlist: Create Incident Maps and Digital Products
• ESRI Help - Map Series in ArcGIS Pro.
• ESRI Job Aid - Slides from the Map Series Tech Workshop.
• ESRI Video - NACIS presentation on bookmark map series with lots of layout tips.

The key to a good briefing map is printing it large enough for the briefing area so everyone attending can see. This often entails "poster printing" and then taping together multiple sheets from the plotter. Some teams use projectors to display the briefing map, this can be an effective option when the situation allows for it as map size can be easily tailored to fit the space.

To aid in clarity at a distance, certain symbols should be enlarged to what may seem like comical proportions.

A "BAM Large Symbols" layer file is provided in the GeoOps Directory Structure and provides a good starting point.

Key Components

• Printed large enough to be visible and readable for everyone at the briefing.
• Enlarged symbols for legibility.
• Reduced clutter to enable clear communication.
• Often poster printed and assembled with tape.
• Wildfire Daily Fire Perimeter polygon outline should be removed when visible under Event Line features (e.g., dozer line).

For the complete list of product standards and map examples, refer to the NWCG Standards for Geospatial Operations (GeoOps), PMS 936.

Job Aids

• See NWCG Standards for Geospatial Operations (GeoOps), PMS 936 for current standards.
• YouTube Video: Briefing Map

Creating a BAM Project

The Briefing Area Map (BAM) is for displaying incident information during briefings. While it can be plotted on a standard Arch E size, it is usually plotted on several sheets of paper (tiled) and taped together to create the larger size.

1. Start with the ProProjectTemplate.aprx and ‘Save As’ to save your project using the standard GeoOps naming convention.  
   
    
2. Remove the Event Group – All Layers layer from the Contents Pane.
3. Add the ‘Event Group BAM Large Symbols’ lyrx from the tools\Event_Layer_Files folder.
   
    
4. Repair paths for the BAM Large Symbols layers to the Master Incident Geodatabase.
   
    
5. Copy and paste an Arch E Layout to preserve the original layout template, then rename the layout for your incident.
   
    
6. Open the Layout and zoom to your data.
7. Adjust base data feature size and labels for the large map size if needed. You may need to remove map elements (e.g. Contours) for the ICS features to be seen from a distance. Refer to GeoOps guidance and direction from your SITL about what information to include.
8. Export your map as a PDF using standard GeoOps file naming.

Plotting the BAM – Adobe

Since there are numerous options for plotting different size BAMs, there are multiple combinations of sizes and settings.  This document provides some general settings and an example, but you may need to adjust based on your desired BAM size. For this example we’ll create a 72” x 80” BAM on two sheets of paper (assuming the plotter paper width is 36” wide).

1. In Adobe Acrobat select your plotter from the drop-down menu and open the Properties dialogue window.
   
    
2. Select the Paper/Quality tab and then select Custom to create the custom page size of 36” x 80”.
   
    
3. Name your custom document size (e.g., Custom BAM) and save it. Use the drop-down to select your custom document size. You may need to select “More…” and scroll to the bottom of the list.
4. On the main print dialogue box, under the Page Sizing & Handling select Poster and set the scaling at 166% and the Overlap to 1 in.
   
    
5. You may need to adjust your Orientation settings to switch between Landscape/Portrait.
6. Print and tape together the two pages.

Plotting the BAM – HP Click

1. Drag and drop the map into the HP Click box to open the file. 
   
    
2. Rotate the image 90 degrees
   
    
3. Change the width to 70”
   
    
4. Left align the first page and print.
   
    
5. Drag and drop the map into the HP Click box again to print the second page.
6. Rotate the image 90 degrees and change the width to 70” again.
7. Right align the page and print.
   
    

42-Inch Plotters Information

• To print an Arch E (36” x 48”) on a 42” plotter, create a custom page size of 42” x 56” and select “Fit to Print”.
• To Print a BAM on a 42” plotter, create a custom page size of 41” x 112” and print as a poster at around 228% scaling.
• There are numerous size options for creating BAMs, so adjust these settings as needed.

There are two standard aviation maps, the Air Ops Map used by Air Operations personnel and the Pilot Map used by the pilots.

Key Components

• A table that includes the Lat/Long coordinates for point features.
• Pilot map is typically small for easy lap reading in the aircraft.
• Minimal clutter but enough detail so that incident features can be located.
• Wildfire Daily Fire Perimeter polygon outline should be removed when visible under Event Line features (e.g., dozer line).
   

For the complete list of product standards and map examples, refer to the NWCG Standards for Geospatial Operations (GeoOps), PMS 936.

Job Aids

• YouTube Video: Aviation Maps
• Create a coordinate point table (Pro).
• Data Source - TFR shapefile - shapefile download at top of page near NOTAM number. Alternatively, use the Current TFR Feature Layer.
• Data Source - FAA sectionals - Available as GeoTIFF or PDF download.
• Job Aid - FAA Aeronautical Chart User Guide.

The Progression Map displays the burn areas of the fire broken out by day (or as frequently as perimeter updates are available).

The most important step to creating a Progression Map comes long before even opening a progression project. Exporting an updated perimeter each day to the Progression GDB will save time and effort when it comes time to finally create the map product.

Key Components

• Colors should run cool to warm, with warm being the most recent perimeter.
• If more than 5 days are shown, predefined color ramps are generally more effective than discreet values.
• Fire Origin is generally the only ICS feature included.
• Elevation data such as DEM or Hillshade can be used "beneath" the progression for a nice visual effect.
• A table of daily and running total acreages can be included.

For the complete list of product standards and map examples, refer to the NWCG Standards for Geospatial Operations (GeoOps), PMS 936.

Job Aids

• Progression Map
• User-made Progression Tool available as part of PanunTools toolbox.
• YouTube Video: Progression Map