Dip Site

Fire Origin

- Gate

• r •

Helispot

Lookout

Other

r Uncontrolled Fire Edge

- Completed Line

~ );(. Completed Dozer line

H · Completed Hand Line

M Line Break Completed

X • Proposed Dozer Line

◊ Aerial Retardant Drop

◊ Air Tanker Retardant

- unknown ][ Branch Break - Wi ldfire Daily Fire Perimeter

Enter Title Here Incident Name Unit and Fire ID

Date and OP of Use 99,999 Acres at E" ective ~

0.25 0.5 ---===:::iMiles

en1-;1~~,~•~~r• AaesfromlR-,,c!Gl'S

North Americ..,, 19831n100,

11/12/2019 GeoOps

Multipage Maps

The key to creating multi-page maps is setting them up early and allowing for growth. This starts with the Grid Index and includes proper annotation and page queries. As soon as more than a single page is needed, jump straight into using an index grid, annotation, and page queries. Even if it feels like overkill at first, trying to fake it with dynamic labels or multiple maps will only cause headaches and mistakes down the line.

Create the Layout Page size will be dictated by the intended use. Multipage IAPs will be letter or tabloid size because they are printed in large quantities and distributed with the rest of the IAP. However, other maps can also be designed as multipage for ease of production. Division breakouts, for example, will usually be C or D sized to cover an entire division in detail and are often requested by Operations for use by leadership in the field.

Once the page size is set, setting up the layout is the first critical step. Because each page will be automatically generated based on the Grid Index and will have different features, best practice is to use an offset data frame layout (where the data frame is smaller than the page and the other elements are placed in the white space either to the side or above/below). This prevents any layout elements from obscuring data when all the different pages are created.

Adding all map elements (STANDL-SGD) at the beginning is important because the data frame size should not be changed after the Grid Index is created. Any time the data frame size or scale is modified in the layout, the Grid Index should be recreated (so it is best not to change it). Be sure to leave sufficient space to account for anything dynamic like the legend (which will change based on which area of the incident is displayed on each page).

Multipage Maps | 1

Geoprocessing

Grid Index Features

Parameters Environments

Out ut Feature Class

..,. I}. X

(±)

(J)

i2020_ProDemoFire_ABC123_iap_ Grid I ndex_24k Iii Input Features 8

[ Event Point • [ Iii ;====================: [ Event Polygon • [ Iii ;===::::::::::::================: [ Event Line • [ Iii ;====================:

• Iii

~ Generate Polygon Grid that intersects input feature layers or datasets

~ Use Page Unit and Scale

Map Scale

Polygon Width

[~ _______ 10_.4~3[ [inches

Polygon Height

[~ _______ 13_.7~5[ [inches

on Grid Ori in Coordinate

X 200670.555243702 V I Number of Rows

Number of Columns

Starting Page Number

D Start labeling from the Origin

24000 [

4221138.60446997 [

11/12/2019

Create the Grid Index

Stay on the Layout View and open the Grid Index Features tool.

1. Set it to cover Event Point and Event Polygon. Usually this is sufficient, but if there are line features that need to be included that extent beyond these, add Event Line. It is easy to delete extra grid features that are not needed.

2. Check the boxes for Generating a Grid that intersects the input dataset and Using the Page Unit and Scale

3. Set the map scale to 24,000 (or whatever scale being used, but 24k is the standard). If the map is already set to 24k, this will populate automatically.

4. By checking the Use Page Unit and Scale box, the Polygon width and height will automatically calculate based on the data frame dimensions in the layout. This is why setting up the layout first is critical. Do not change this setting.

5. The number of Rows and Columns may seem odd, ignore it for now. Do not change this setting. If too many index features are created, double-check the other settings.

Multipage Maps | 2

Ir;! (;1t;1log IE] mp,~p 2020 ProDt!moFire ~ layout 1h17 Port

, ..... _ ...

ict;'~ height/wi th

't:if!k, 1-----'5!--f,r"\-=----'---.!®l'~~eeir"' aul tJ' ,.-t-----r---,-----,

X

1,223,m · II + !:.i il ~ I

~ Layout_11x17_Port

D1 -· e M,...._._ ___ .._ __ __,

Sia h Haul P>OS Site 2

114.3728520"W46.9660681"N v

•,

~ SelectedFe~tures:10 Il l;!

------~

X

... , DP-51 \ • ~

-13 Mi e'bP

P-42 Restrict d g,to height/ idth

i,~-32

'• •

CMD1 ~ Martel Mt

®

Slash Haul Site 2

11/12/2019

Place the Grid Index

Delete any unnecessary grid features that were created. If unsure, all or some can also be moved off to the side while the rest are positioned.

Position the grid features so that the entire incident is covered with a little overlap on each edge.

Multipage Maps | 3

3 Page 4

age 5

Page 2 Page 6

Page 7

Page 1

ffl Event_PointAnno_24k X

Selection:

.LI OBJECTI

Add a new field in this table. 167

168 /J ::::l:J <I\IU I> /"\II lllt:I

Page 8 Page 9

11/12/2019

Update the grid feature attributes so that the Page Name and Number are consistent and understandable. These fields will be used to dynamically subtitle each page in the final product. The name can be either the page number as well or something logical like the Divisions covered by the feature (just be sure that is updated as Divisions change or pages move).

A common numbering standard is clockwise from the Fire Origin, but most important is that it is clear and labeled on the products Index Page.

Create the Annotation

If an annotation layer at the appropriate scale has not already been created, follow the documentation on the Annotation Page [LINK] to create it.

Add a new field to the Annotation layer to use for the Page Queries. This field will set which page the annotation will display on. Name it PageName and use Text as the type.

Work through the map, page by page, making sure that every Division and Branch visible on the page is labeled. This will entail creating some extra annotation features for most pages. Managing these additional features comes down to personal preference, but it is often easiest to keep things consistent by creating the necessary break labels for each page and attributing

Multipage Maps | 4

/ r 00

00 :J:

~ o _.,P i

Page8

X' DivT ~

·,s,

',s,

n,

Div T

Div T

Branch I Branch I

:::: Event_PomtAnno_24k X ~ Fields: Event_PointAnno_24k lffll i2020_ProDemoFi re_AB ... p_Grid lndex_24k

Field: IF:'l Calculate Selection: ~ Zoom To !rd; Switch ~ Clear @:lDelete § Copy

_,i OBJ ECTID SHAPE FeaturelD ZOrder AnnotationClasslD • El ement SymbollD Status TextString PageName FontName

177 Polygon <Nul l> <Null > Division Blob 5 Placed Div T Page 7 Arial

178 Polygon <Null > <Nu ll > Division Blob l Placed Div e Page 2 Arial

184 Polygon <Nul l> <Nul l> Division Blob Placed DivT Page 8 Arial

185 Polygon <Null > <Null > Division Blob Placed DivT Page 1 Arial

188 Polygon <Null > <Nu ll> Division Blob Placed Div M Page 8 Arial

189 Polygon <Nul l> <Nu ll> Division Blob Placed Div C Page 1 Arial

11/12/2019

them with the proper page number. Even though labels can sometimes be placed in the overlapping areas of adjacent pages, this can lead to oversights when pages or breaks inevitably change.

It is critical that each annotation feature be attributed correctly for the Page Query to work. The PageName field in the annotation layer must match the corresponding PageName field in the Grid Index layer.

NOTE: In the workflow outlined here, it is only necessary to set the page name for Division and Branch labels as they are typically the only feature that span multiple pages. Other feature labels will bypass the Page Query as shown in a later step.

Multipage Maps | 5

.....

Paste

Cut

Copy

Layout

... ◄CJ►

"' Navigate

Insert

+

~

[ij

J Clipboard Navigate

Contents

'f

Contents

I Search

1: '!:::: ~ ~ ~ -Map Series Pages

~ ~ Layout_ 11x17 _Port

j1 Page 1

'-- 2 Page 2

'-- 3 Page 3

'- 4 Page 4

'-- 5 Page 5

'-- 6 Page 6

'- -7 Page 7

'-- 8 Page 8 :

'·· 9 Page 9

Analysis View Imagery

~CJ § Select Al l ~ Clear Selection Select Orientation

Delete

Elements

.., 11-

p

Share

IEi • 11!'.;;J ~ Rulers

~ Guides l,I~ i,:,i

Activate " i<: ~ :,,i Bookmark

O!]

<None >

The la out has no series .

Spatial Define a series of pages that span a range of map extents.

Layout Properti es X

General [;'.] Enable Help with map series

Page Setup

Map Series I~ Spatial ·I Define a series of pages that span a range of map extents.

Color Management v Index Layer

Map frame I~ Map Frame • I Layer I Bl 12020 ProDemoFire ABC123 iap Grid Index 24k • I Name Field I PageName ·I Sort Field IPageName ·I

[;'.] Sort Ascending

v Optiona l Fie lds

Group By I <None> ·I I Page Number I PageNumber ·I I First Page 1, :1 Rotation I <None > ·I Spatial Reference I <None > ·I

v Map Extent

0 Best Fit Extent

Margin Size ~ !Percent· I

Round scale to nearest f,oool ® Center and Maintain Scale

Scale I 1:24,000 ·I U Use ~cale ,rom , Ield

Scale Field <None> . D Clip to index feature

I OK 1 1

Cancel I

11/12/2019

Enable and Configure the Map Series

Return to the Layout View and select the Spatial option under Map Series on the Layout ribbon.

1. Set the Index Layer to the Grid Index.

2. Set the Page Name and Number fields.

3. Set the Map Extent to to Center and Maintain Scale and make sure the scale is set to 24k (or whatever scale the Grid Index was created at if using a different scale)

This will enable each page’s view on the Map Series tab of the Table of Content.

Multipage Maps | 6

Layer Properties: Event_PointAnno_24k X

General

Metadata

Source

Elevation

Selection

Display

Cache

Definition Query

Time

Range

Joins

Relates

Page Query

Map Series Page Filter

Filter rows based on the current map series page. The values in this field are

matched against the current map series page name. The filter is only applied

when a map series is enabled.

I I PageName ~ I Show features that:

@ Match I 0 Don't Match

~-O_K_~I I Cancel

_. ~ mpiap_2020_ProDemoFire

_. ✓ Event_PointAnno_24k

~ All Other Points - DP, H, Staging, etc.

D Branch, Segment, Zone,

D Division

~ Origin, Spot Fire, Hot Spot

~ Repair

_. ✓ Event_PointAnno_2f PAGE QUERY I ~ All Other Points - DP, H, Staging, etc.

~ Division

~ Branch, Segment, Zone,

~ Origin, Spot Fire, Hot Spot

~ Repair

_. ~ i2020_ProDemoFire_ABC123_iap_Gridlndex_24k

□ _. ~ 2020 Event Group Layer Point Labels Defined

11/12/2019

Set the Page Query

Open the annotation layer properties from the Map View and set the Page Query to Match on PageName.

NOTE: This will affect which features display in both the Layout and Map View. The query will be applied based on which page is selected in the layout but will also affect which features display when switched back to the Map View.

At this point, only the Division and Branch labels for the active page should be visible. To display the rest of the labels without worrying about their page, add a second copy of the annotation layer to the Map View and turn off the Division and Branch classes. To help differentiate between the two layers, add an identifier to the name of the layer with the Page Query.

Multipage Maps | 7

Llh 'J I Aa

Chart Table Additional Symbol Frame • Frame Surrounds •

~ Rectang le •

/), Dynamic Text •

D • 0 Rectang le • ~ Picture <;°}, Add •

N Line •

+.

All• . . . -Surrounds ___ _, Layout_ 11x17_Port

Map Series

--,-,..-w--,-,..-,-.,..,,--u-,.-,..--"-' -.... - 1-1 Page Name Page Number 1

Page With Count Page 1 of9 Page 1

a e

Page 1

H-30/DP-4

•

Page 7

11/12/2019

Final Layout and Review

Add the Page Name as Dynamic Text to the Layout Title Block. This will update automatically for each page generated.

Turn off the Index Grid before exporting the Map Series. The grid should not be displayed on any of the individual pages, only on the Index Page. Turn off, or set to highly transparent, the Fire Polygon. Event Polygon should not obscure the base topography or any other information.

Walk through each page from the Layout View to double-check that no labels are missing and all the other standard elements are correct.

Multipage Maps | 8

View Imagery Share Format - .......

~ iJ I I ~ ➔ l@:ii

Project Layout Task Layout Layout Template File Item ~

Save As Print Export -

Export Opt ions X

PDF Settings I Map Series I

@ All (9 pages)

0 Current (page 7)

U Selected Index Features

0 Selected Pages

0 Page Numbers (for example: "1, 3, 5-12"):

7 I Export Pages As:

I single PDF File ~1 LJ Show Selection Symbology for Index Features

I OK 11

Cancel I

11/12/2019

Export the Map Series

From the Share tab on the Ribbon, export the Layout.

The Export Option will allow the export of all, one, or some of the pages and whether they will be saved as a single PDF or individual pages.

Always use the GeoOps standard naming convention.

{product}_{size}_{orientation}_{pages}_{currentDate}_{currentTime}_{incidentName}_ {incidentID}_{useDate&OP}.pdf Eg. iap_11x17_port_MPall_20200617_2120_ProDemoFire_ABC123_0618Day.pdf

Multipage Maps | 9

mpiap Index 2020 ProDemoFire ABC123 mpiap index 11x17 Port ArcGIS Pro

dicator • t 0 5 10 c-

Llh ■ o - Aa N ~ c -• -

North Scale legend Chart Table Add itiona l Symbol Arrow · Bar · Frame .. Frame Surrounds ..

Map Surrounds

[El mpiap_i ndex_2020_ProDemoFire ~ mp1ap_1ndex_ 11 x17 _Port X

I I 11 - 6 11 -s I I ;1 -3 -2 -1 i,I

b"ry lttl elf:n""nt ln t his layout15dynam lcl lhry itte!IOUlced fromthe~tilblel'lthe

1""'-""""-'-"'and rhc:Mefil<Jillal'ropert10 fflillnMapV,ewforthosprO)l'Cl

lf501llele!ll~5appear1obem1SS!f1Q, l/w,pi11hlo ~tablel'llhl!:mammai,Yll?WI

need!.toberep.,,rf!d

Thel11odentNamc,Ul'IIQUClO,AcroaQC,aridAcre;,ge Sou..OP/0.tesetm lhe~tablewrl

P0!)Uiffl:l'l ~ ry1)flljec:t and,;hookl°"updated •~elv afte< per,mder ch;lnqes, pr,o, to reopeniOQ

afl'rpto,ects.

"'1m1p T'°", Dal" and OP a( U,.,,, illld Author Name a, ~111Nm111 Met.rdatilproP"ftleand1>~pc,pula(" a ll

1empl1>1cs ln1hls pm)ect.

If desired, subsliluU,lh!..tatic~xt ~tsbo!low for thcdyn;im,c t.e,111nthe l;,your: ,

;~i{ ~o.:.,

~ Rectangle •

P~ Dynamic Text ·

Text

D · 0 Rectangle • ~ Picture e;"}, Add •

- · ,t,/ Une •

• • • Point

Graphics

Pro Demo Fire Incident Name

Unit and Fire ID Date and OP of Use

99.ffi-llu...crMl l2t!I.!£!

(~~ New·

c!'~ Import

Styles

0 0.5 1 2 ~ Miles

+ Add

Item ...

Favorites

11/12/2019

Create the Index Page

Because the page quereis affect the layer in the Map View and other layouts as well, it is usually easier to manage a separate Map View for the Index Page or possibly even an a new Project. With multiple Map and Layout Views in a single project, the chance for accidental crossover increases greatly, especially when copy/pasting.

The Index Page is for reference only and should be kept simple. The intent is for easy identification of which detail page is needed. The Index Grid is the primary feature. It should be visible and labeled. Division and Branch Breaks should be shown and labeled so field personnel can quickly find the detail pages for their assignment area. If other point features are shown, they must be labeled.

Multipage Maps | 10