Configuring Maps

Map Sets

Map generation in PISCES is automated by using preconfigured map sets. Map sets are a composed of one or more PISCES-generated layers to be added to a template map document that can itself be expanded to generate multiple maps for one or more species. Map sets are highly customizable and allow the user to quickly create standardized map outputs.

Map sets have three main parts to their definition:

  1. Map set core (title, map-wide specifications, enabled/disabled, etc)
  2. Map layers (definitions for the database query, layer name, symbology, etc for each layer)
  3. Scope of the map output (selected species or species group)

To find out more about how mapping works in PISCES, see How mapping works in PISCES. To learn more about creating a new map, see Setting up a new map for export.

Map Set Core Definition

Defined in: defs_Query_Sets

For every map, define a single “map core” record in the defs_query_sets table. These “map cores” are templates that are used to generate all of the maps in a map set. To create a new map set, simply add a new record at the bottom of the table.

Field Name Description
ID Autonumber
Set_Name A name for the map
Map_Title A title for the map - used with the {Title} replacement variable
Short_Name A short name that will be used in other places in PISCES to reference this map. This should be short enough to read in another database field.
Set_Description A description for the map set to describe what it displays or how it differs from others
Base_MXD A base template mxd (see maps in the mxds/base folder for examples)
DDP_MXD A optional template to be used for data driven pages output
Iterator A table name and field to use as unique values for layer query bind variables in the format table_name:field_name. For maps queries that take bind variables and where you have specified ‘all’, PISCES retrieves all the unique values in the specified field and creates a new map for each one and passes that value in as the bind variable. For maps that specify all, without an iterator, the iterator defaults to Species:FID
Active A flag to control whether or not a map should be generated. Only checked (True) maps will be output.
Callback [Unimplemented]
Callback_Args [Unimplemented]

Layers in a Map Set

Table: Map_Queries

Each layer for a map set has to be defined in Map_Queries. The software has no limit on the number of layers to be added to a map, but you should limit the number of layers by time and view ability. A map must have at least one layer.

Map Set Output Scope (Query_Bind)

Table: Query_Bind

PISCES generates a map for every distinct value in the defs_Query_sets iterator column (table:column), passing the values in to each layer’s query as the “bind parameter” in the table Query_Bind. The bind parameter can be a species code, species groups or “all”. The bind parameter pulls all the species FIDs requested, and the mapping code will retrieve those records for a map set, expand any groups out to their species code and merge the resulting values.