Page Definition Query improvement

11-21-2012 07:10 PM
Status: Open
Labels (1)
Occasional Contributor III

Page Definition Queries are very useful, however they have the potential to be much more so. Rather than only being able to turn features on/off based on them having a field which matches (or doesn't) the page name, the ability to use SQL queries (mush like regular definition queries) would enable much greater scope for filtering features.

An example might be a a state-wide feature class containing many classes of road from major highway to dirt track. Depending on the scale of each data driven page, the level of road class dsplayed may need to be changed (i.e. only showing major highways at small scales when lower classes cause cluttering, and showing minor roads/tracks at large scales).

To facilitate this, the Index Layer would be populated with fields corresponding to layers which are to have Page Definitions applied. These fields would contain the values to be matched in the definition, in the above example the values would be road classes. The Page Definition could then contain an SQL query where the field in the road dataset containing Road Class is selected, a boolean operator is selected and the corresponding field in the Index Layer is is selected.

The below example selects the major roads (Classes 1 & 2) for display on the State-wide page.


Currently the most efficient way to accomplish this in both workflow and drawing performance is to author the symbology for multiple layers that makes sense at each scale and then set visible scale ranges on the layers.
That's great that there is a way to achieve this Chris, and while it is the most efficient at the moment, I believe it's not the BEST solution that could be provided.
"Page Definition Queries are very useful, however they have the potential to be much more so."

Could not agree more! I'd promote this 10,000 times if it'd give this idea the attention it deserves.

I'm currently supporting the creation of a statewide atlas. The tiles are based on townships and these often reside in multiple counties. In the locator map we are highlighting the counties in which the tile sits.

As far as I can tell the current functionality of DDP and Page Definitions does not allow for multiple counties to be selected (Please correct me if I'm wrong!). Not to mention I'd need to switch the page name in DDP to a different attribute and that attribute would need to contain values for several counties. The ability to use SQL queries would be incredibly valuable! This seems like a no-brainer to me.

I'd love to see this also.  There is a partial workaround I find myself doing: add extra fields to all the relevant data that match the page name map series fields and use those fields to attempt to control visibility.  This isn't always possible though depending on the complexity of how and what visibility and symbology I'm attempting to control, it only works for simple situations.  I'm using Pro and if Pro has a solution I haven't found it yet.