For All Extents and Purposes...
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.
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.
As with any use of the effervescent Marco 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
- 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:
These values represent the extents of each dataset, data frame, or bookmark. They show the ends of the Earth…or at least, how that particular file sees it. Stored as WGS1984 format, these values may then be pulled into ArcMap, properly reprojected if need be, and visualized to create neat little (or large) bounding boxes representing the areas and files in question.
Don’t believe me? See for yourself.
This allows you to visualize the locations of your data for whatever reason you see fit. This could be for reporting purposes, showcasing the extent of spatial data to highlight the boundaries of regions a project in which a project may currently be taking place. This could be for QA/QC purposes, double-checking that the files you do have in a specific location actually match the region intended. This could also be fore genuine curiousity. Want to figure out which datasets focus most in Texas versus California? Hot doggie, this is a good way to find out!
The intention of utilizing this particular feature of Integrated Marco Studio is entirely up to you. What are other purposes you could envision your team needing to visualize data boundaries that were not listed above?
About This Series
In the coming weeks, we will explore ways in which to answer these common questions and get the most out of your spatial data. Want to jump ahead and tackle these for yourself? Follow the links below or view the cheatsheet here.
- Week 1 - What user is responsible for the most broken map documents and layer files? Hint, Gerta may be the culprit.
- Week 2 - What are the most commonly referenced datasets in broken map documents? Heat maps are friends, not foes.
- Week 3 - How do I find which datasets are associated with specific keywords? Take matchmaking to a new level.
- Week 4 - What maps have not been access for more than five weeks? Data age is just a number.
- Week 5 - How many maps are using non-standard geographic transformations? Maybe more than you think.
- Week 6 - What are the extents for the most used datasets? For all extents and purposes, it's a must-know.
- Week 7 - What data matches x and y terms? Get your search on.