• iii

Spatial Data Diagnosis: Coordinating Common Map Extents and Boundaries


Blog series on reviewing spatial data and identifying broken files and issues, including coordinating common ArcGIS map extents and boundaries.

On today’s wild ride on the #MarcoMonday express, let’s give a shout out to boxes. Okay, maybe not the cardboard kind. Boxes – or rather, more so boundaries – of the geographic kind are our next stop on this quest.


What are the extents of the most commonly used datasets?

To answer this question, we can use either Integrated Marco Commander or Integrated Marco Mystic. Either way, the same tools will be employed. The interface, of course, is your choice.


Coordinate Accordingly


To find the extent of datasets and spatial data, it is best to run the marco coordinate tool. That seems too obvious, I know. However, I pinky promise I am not pulling your leg.


View of coordinate tool from Integrated Marco Commander application in Windows Command Prompt.

As with any use of the effervescent Integrated Marco Studio inventory capabilities, the marco container tool must be run first and foremost. Followed by this, the marco coordinate tool may be run to pull those values for the following types of data:

  • Data Frames

  • Bookmarks

  • Datasets

  • All of the Above

Once the coordinates are gathered, they are stored in the Marco Database, setting up home in the respective database tables for each type of data with the following fields:

  • X_MIN

  • X_MAX

  • Y_MIN

  • Y_MAX

These values represent the extents of each dataset, data frame, or bookmark. They show the ends