Identify Feature Changes Between Map Editions

Have you ever wanted to identify what features changed between your different map editions? If so, the  recently released Batch Manage Layer Snapshot Fields tool is for you. It extends the Calculate Layer Snapshot tool available in Esri Production Mapping that aides in identifying edits and symbology changes between map editions, thereby eliminating what could be a lengthy and time-consuming process. By using the Batch Manage Layer Snapshot Fields tool in conjunction with the Calculate Layer Snapshot tool you can focus your cartographic visual review on changed areas only.

To get started, run the Batch Manage Layer Snapshot Fields tool on one or more feature layers from the “1st edition” of your map. The tool calculates the snapshot value of the geometry, extent, and symbology of the features in a long integer field. Additionally, several metadata fields are added and populated with date/time, user name, reference scale, and a historical string. Once features are edited, the Compare Layer Snapshot tool can then be used to find out what features have changed. It simply recalculates the snapshot of the features and compares them to the stored value. Below is an example of a road feature in two different editions of the map. Image 1 illustrates a road feature in the first edition. Image 2 illustrates the same road feature after it was extended in the second edition of the map. The features has been selected by the Compare Layer Snapshot tool.

You can use the tool as-is or further customize it to meet your own purposes. You will need ArcGIS 10.1 for Desktop Standard or Advanced license level as well as Esri Production Mapping 10.1 to run this tool.

Note: This tool modifies the schema of your database and adds one or more new fields to the input feature layer(s). It’s highly recommended you create a backup your workspace before running this tool.

This entry was posted in Mapping and tagged . Bookmark the permalink.

Leave a Reply

2 Comments

  1. iori105 says:

    Does it work on the dataset which is archiving enabled?