This week's new feature series focuses on using text columns for classes in hatch maps and territory maps. In previous versions of MapViewer, classes for hatch maps and territory maps required a numerical data value. If you did not have numerical values to use for your classes, it was necessary to assign a numerical to each class, resulting in tedious data modifications. Now, you can create these classes based on a column of text! Create classes based on salespersons' names, geographical regions, or any other string of text!
Below are step-by-step instructions to create a territory map using this convenient new feature! In this example, I am creating a territory map showing which countries are in which continents. I began with a boundary file defiining the countries and a worksheet containing each country name, which is the PID for each object, and the continent to which it belongs, which will be used for the class column. You can download the files I used and the finished projects here. The boundary file, world_countries.gsb, is simply the WORLD.gsb file from the MapViewer 8 Samples directory that I edited to suit my map!
Sample data sheet snippet
Before creating maps with text-based classes, it is important to be sure your class names are set up correctly. The text strings must match exactly in order for an object to be added to the correct class. For example, "Jen" and "Jenn" would create two different classes, and "Area1", "Area 1", and "Area-1" would create different classes. However, the classes are not case-sensitive, so "Jen", "JEN", and "jen" would only create one class.
Let's get started!
The territory map is complete! Quickly add a legend to your map with the Map | Add | Legend command! If desired, use the Property Manager to make adjustments to your display.
To create a hatch map using text classes, the process is quite similar:
Map page of the hatch map Property Manager
After creating your hatch or territory map from text classes, if an area is not colored as expected, check to be sure the PID for that area matches the PID from the data file. You can also check to be sure there are no typos or spelling errors in the class name assigned to the area in your data file.
Stay tuned next week for a look at the powerful new query across multiple layers feature!
Do you have any questions about this post? Do you have an idea for a blog post or have a topic you'd like to see featured? Let me know! Leave a comment, or send an email to firstname.lastname@example.org.
When you subscribe to the blog, we will send you an e-mail when there are new updates on the site so you wouldn't miss them.