Multiple Pages in a Layout

[AdamDavis]

Hi,

I am interested in the Multiple Pages in a Layout functionality.
I have only dipped my toe in this area so have a basic question regarding how it is put together.

It would seem that the creation of multiple pages in a layout is only accessible through the Data Driven Pages Wizard?
I would have thought that the functionality would be...
User is in layout. User right-clicks chooses New... Page... User sets up page bla bla bla.
Then the purpose of the automation would be to power this functionality to simply make it easier IF the user wanted to base it on a feature class / areas etc

Can anyone clarify what the functionality is?

Cheers,

Adam

[MichaelGrossman]

Adam,

The 9.4 data driven pages implementation is not what I would describe as multiple layouts.  You cannot, for example, add a second page, paste in a unique set of layout elements, and create a "page 2" that is unique from "page 1".  The implementation is really a group of functions that automate data frame map extents, and change certain text elements on the fly.  Map printing and exporting have also been enhanced to handle true multipage print spooling and multipage PDF export.

You can read more about the implementation and concepts in the help topic called "What are Data Driven Pages?"

Part of that help topic are the following statements about building full map books with ArcGIS 9.4

[INDENT]

Many projects require multiple page sizes, multiple index layers, or non-map information on some pages. For example, a state atlas may contain a title page, an overview map page, and a page for each county in the state.

Additionally, some counties that are home to large cities also contain inset maps. The atlas can be built using separate MXDs for overview map page, pages containing the inset maps and the remaining maps. Map scripting with Python can be used to be used to aggregate these pages into a single, multi-page PDF document.

[/INDENT]

We plan on uploading some sample map book creation Python scripts to the Geoprocessing Gallery sometime soon.

Sincerely,
Michael Grossman

[AdamDavis]

Hi Michael,

Thanks for the clarification. I think I got confused as I looked at it from a Multiple Layout perspective as that is what I 'wanted' to see - my fault.

I look forward to giving it try and see what it can do.

Due to this functionality are Multiple Layouts off the agenda for a future version or are Data-Driven Pages a stop gap?

Thanks again,

Adam

[JohnBlackmore]

I would be really interested in a true "Multiple Layouts" functionality as well.  I thought the same thing when i read about the data driven layouts and was disappointed to see that you can't have multiple layouts.  That would be a killer feature that i would use all the time!

John

[TodChee]

I would also be interested in being able to toggle between multiple layouts. 🙂

[TedCronin]

Michael -

How about a tips and tricks blog entry from your team for data driven pages and the like.

[MichaelGrossman]

Our goal in 9.4 was two-fold:
[INDENT]1) deliver a set of tools for building complete map books
2) provide an automated way to update layouts, data frames, and map documents[/INDENT]

Many people express a need for mulitple layouts because they want to achieve one of those two things.  There are also other reasons people want multiple layouts.  The 9.4 beta period will be very important for us, as we need to understand which problems 9.4 has actually solved, and which workflows still need solutions.

I think our future plans regarding multiple layouts will should be made with unfulfilled user requirements in mind.  For now, our solution is what you see in 9.4, focused on satisifying the above two requirements.  In the future, we can consider full multiple layouts but should do so with a set real world goals.  It would be great for us if you could provide additional details about multiple layout workflows.  I think that some needs could be covered with the new 9.4 python scripting experience.  Other requirements should go on ESRI's list for a future release.

Thanks,
Michael

[TedCronin]

So, it seems like it is not set in stone, and there is room for improvement especially with your use of dyanmic text.  What is your recommendation for multiple titles in a series of maps that participate as part of an overall product.  The ability to have one mxd, with mutiple titles.  Can we do that today with the solutions that you have provided in 9.4.  Side note:  When are we going to be able to store maps in a database.

[KimOllivier]

It looks great, I have several current applications that it will be very useful:

1. Mailmerge of a map into a letter.

At the moment I have a multi-stage process with several packages, especially Arcplot. Merging a map into Word is a nightmare, even worse now that they have disabled emf insertion blocks that I used for the map.

I think I can see how to make up a letter with a different address, name and map for each recipient. Just have to work out how to add the table that goes with the map for those people who can't read a map.
http://www.ollivier.co.nz/publication/uc2005/redcross.htm

2. A book of trail maps.
I like the idea of inserting a cover, contents and other non-map pages, but the help is a little vague on how I do that. Unless its a "pseudo map" composed of graphics and images?

3. I really like the dynamic selections to limit the layer contents. This is the challenge I had recently with some forest maps. I could do this with the NW mapbook, (great little variation on mapbook from the NorthWest office now unsupported) but it was too hard to keep working and I could not understand the vb6  and Map Objects well enough to hack it.

I would have liked to be able to control the page orientation so that I could output landscape or portrait, but these can be split into separate runs.

[KimOllivier]

After a bit of practice I have now completely replicated a DSMapBook application, plus a lot more. So rest easy all you DSMapBook enthusiasts. Some of the functions are still being worked on and renamed after the Pre-release, so there is a bit more to come.

The basic idea is that the "mapbook" is the output document, not the project MXD. So you can load a PDF title page first, then export a series of PDF maps, each with its own MXD with different styles and page layouts, and then the trailing pages. Finally close the output document. Being able to assemble the pages from PDF individual pages avoids having to post process individual maps.

There are additional tools to create strip map and grid indexes, and calculate adjacent sheet names, convergence and other settings needed for a series.

Programming using the high level functions is a much easier than hacking the VB6 code for me because I have avoided using VB. At the same time the available tools are much more powerful that DSMapBook ever was. Especially the dynamic text to allow custom dynamic labels, images apart from being able to switch different layers on for each map. Not the same options form, you have to write a Python script for some things but in the end much more powerful and extendable.