Stack Symbols: A New Methodology for

Mapping Complex Environmental Data in ArcView GIS


 

Abstract

Stack Symbols ArcView extension was developed by WESTON to automate the repeated mapping of very large three-dimensional environmental data. Stack Symbols extension demonstrates an innovative use of graphics for data symbolization using Avenue and customized font-set. Use of the extension reduced the task completion period from 4 persons a week (160 hrs) to two persons a day (16 hrs), along with aesthetically pleasing and understandable maps. The paper describes the process of developing Stack Symbols and its associated tools in ArcView GIS, that would help environmental agencies implement more communicative maps with significant time-savings.

Author's

Rajendra Dutt and Erik W. Hetzel


Introduction

Stack Symbols were developed specifically for an environmental assessment/remediation project that contained a very complex and large dataset. A large amount of historical data had to be integrated into the database that would include additional sampling data. The sampling information was undertaken in a manner that data did not always correspond well.

The project currently holds more than one million records stored in Microsoft Sequel Server database and is still growing. The data is arranged with the samples as the basic unit of information, uniquely identified by a Sample_id. Generally, each sample is taken at a specific depth interval. Depth intervals of the samples are not consistent throughout the dataset. At a single location total number of samples could vary from 1 to 48 with depth intervals that are often not consistent.

Every unique location (in Plan view ) was identified as Location_id. New samples were added to the dataset almost every day. Data set was updated twice a week. ArcView created event themes with locational information coming directly from the Access database.

Client had specifically requested paper maps for reporting the sample results, which had to show data in an aesthetically pleasing and easy to understand format.

 

Initial Attempts

Generating the maps that displayed all the results in postings boxes was a very time consuming exercise. It took about four analysts working full time to finish all the maps in a week. By the time the maps were done, they had to be updated again because the data had changed.

The default ArcView symbol sets could not accommodate such a large number of sample types. The results had to be posted with information that could be coming from multiple fields. The shear size of the data that had to be posted could not be accommodate in the weekly schedule.

Manual generation of postings map was very time consuming. Also once the maps were created they could not be reused in any way, because the data was already old, and posting boxes were done manually anyway.

 

The Stack Symbols Solution

The idea came out of the realization that a customized font type was required that could symbolize sample data for each location.

The fonts would have same point of reference but different horizontal bands that could be colored to display result values (see figure)

Hence we developed a new custom font type called stacked bar symbols. Macromedia Fontographer version 4.1 was used to design and generate the new True Type font. A composite marker palette was created in ArcView using the characters from this new font. Twenty-one separate characters formed the basis for each bar in the stacked symbol representation. Character sizing and placement in Fontographer was critical to the proper display in ArcView, and special care was taken to ensure that characters overlaid one another cleanly.

When we tried using the fonts to symbolize the data, we realized that we could not use them directly.

 

The Need for Stack Symbols

The idea of Stacked Bar Symbols could not be easily implemented with standard symbolization. A single ArcView theme can only have one legend. In our case we had to first use the depth interval value to decide the font type and then use the result value to symbolize the font color.

This is when we thought of creating symbolized graphics on top of the location theme features. These graphics were to generated using stacked bar symbols font set. The challenge was to make these graphics look and feel like single symbol for each location_ID (NOT sample_ID). At the same time these stack symbols had to be easy to move around, and intelligent enough to know their respective Location_ID and all the Sample_Ids that formed them. We achieved this through ObjectTags.

 

Map with results Before Stack Symbols:

 

Map with results using Stack Symbols

 


Development Environment of Stack Symbols

Stack Symbols were exclusively developed in Avenue, the programming language of ArcView GIS. Stack Symbols were developed to be used by two kinds of users:

  1. Departmental Cartographers who would use the ArcView project file, and could perform some of the tasks manually. It gives them more flexibility in developing the maps.
  2. Environmental Engineers are the End Users who are supplied with the Stack Symbols ArcView Extension. Most of the data processing tasks as run in the background thus minimizing unnecessary complexity and confusion.

 


How Stacks Are Generated

When latest Data becomes available from the database group, it is processed to generate MSAccess database that would be used by the GIS Group. GIS Group reorganizes the data into tables and queries according to our needs. Queries are also created to generate the data for Stack Symbols. At a time Stack Symbols process about 8000 sample records, which is a considerably smaller number compared to overall GIS dataset of about 650,000 records.

To generate Stack Symbols these 8000 records are further processed:

  1. Depth Intervals for each location_ID are ranked and used to populate a new field called "Rank".
  2. Locations with total number of samples greater than 21 are flagged in a new Boolean field named "RankAbv21"

Whenever a new project is created for Stack Symbols, the ArcView palette containing the Stacks font set is saved with the ArcView project so that it would always be available in the memory when the project is loaded.

Finally, Stack Symbols are generated for each location_ID with topmost stack showing results of sample with Rank value 1. The color of the stack symbol is determined by a logic that depends upon the depth and result value of a sample.

 

The Steps and the Logic followed by the Stack Symbols scripts:

Get a new copy of Stack Palette
 For each unique Sample_ID at the location
    1. Get the Rank Value
    2. Set the appropriate font type and create graphic
    3. Get Sample result value
    4. Use logic to identify the color for the stack graphic (blue, cyan, green, yellow, orange, red, violet)
    5. Set graphic color
    6. Set object tag for the graphic to Sample_ID
End
Group all the graphics for the location
Set object tag for the final stack symbol to Location_ID

Once the stacks are generated the they are resized, using customized tools that would increase or decrease Stack Symbol sizes.

Overlapping stacks are moved around little bit to get a more legible and aesthetically pleasing map. Automated line generating tool draws a line between a stack and its source location. This helps minimize the confusion about the source location for a stack symbol when it is moved.

 

Sample Map

 


Limitations of current Stack Symbols Extension

1. Gaps in Depth Intervals:
If there was a gap between the two sample depths it was not visible in the Stack Symbols.
2. Overlapping Depth Intervals:
If Depth intervals among the samples overlapped Stack Symbols could showed misleading information.
3. Actual Result Value was not shown.
4. Limit of 21 Depth Intervals:
The database contained Locations where the total number of samples exceeded 21. Ideally speaking the stack symbols should be able to accommodate any number of samples and depth intervals.


Future Developments

Stack Symbols extension will eventually develop into an end user tool that will help clients create stack symbols as part of the larger interface that has been developed by WESTON.

    1. It uses a set of graphics instead of fonts. This lends a new level of flexibility with the stacks. Now an unlimited number of samples and depth intervals can be accommodated.
    2. Gaps between the stacks are shown in the stack symbols graphics.
    3. Actual result values are also posed inside the stacks.
    4. Depth intervals are also labeled to minimize confusion when depth intervals are overlapping.

Current Look of Stack Symbols

 


Acknowledgements

The authors would like to acknowledge the WESTON GIS Staff who were actively involved in the development, implementation and the updates of Stack Symbols Extension.

 


Rajendra Dutt (Primary Author)

GIS Analyst IV

Roy F. Weston, Inc. - Knowledge Systems & Solutions - http://ks2.net
1400 Weston Way, Bldg. 9-2S, West Chester, PA 19380
Phone 610.701.3603
Fax 610.701.3651
Email duttr@mail.rfweston.com

 

Erik W. Hetzel

GIS Technical Manager

Roy F. Weston, Inc. - Knowledge Systems & Solutions - http://ks2.net
1400 Weston Way, Bldg. 9-2S, West Chester, PA 19380
Phone (610) 701-3481
Fax (610) 701-3651
Email hetzele@mail.rfweston.com