Region 6 Seamless Annotation Geodatabase Development

1. Region 6 Seamless Annotation Geodatabase Development Presented byAndy Bury and Morgan OmdalTetra Tech, Inc.April, 2009

2. Presentation Outline • Project History and Objectives • Project Details • Project Results • Lessons Learned

3. Historical Context • Region 6 uses digital annotation files for map production • GSTC quad-based annotation as E00 or TXT files • Difficult to use and did not cover the entire Region • 1,279 quads out of 1366 had TXT annotation

4. Project Objectives • Seamless annotation feature class geodatabase • Features from all 1:24,000-scale quad maps in Region 6 • Defined according to the ½ inch = 1 mile scale (1:126,720) specifications

5. Results • Tetra Tech delivered a seamless annotation feature class geodatabase for all of Region 6 • 98 annotation classes • Met USDA Forest Service cartographic and symbol standards • Appropriate for 1:126,720 scale maps, but maintained much of the information from the 1:24,000 scale maps

6. Project Development Details • Data collection • Base map layer compilation • Geodatabase design • Converting/Importing annotation • Placing annotation • Quality assurance

7. Data Collection • Base map data layers • Used to replicate features on a forest service visitor’s map • Point and line features symbolized to standard sizes and widths • TXT annotation files • Used to import quad based annotation where available • Hard/Soft copy SEQs • Used as a guide for positioning labels and as annotation source when TXT files are unavailable

8. Setting Up the Databases • Base Map Geodatabase • Reproject layers to the appropriate projection/datum • Import layers into a Geodatabase • Allows for Map Caching • Annotation Geodatabase • Designing the Geodatabase • What symbol/annotation classes are included? • Will the annotation by displayed using a different projection?

9. Geodatabase Design • What symbol/annotation classes are included? • Symbol classes allow functional groupings of similar feature labels • Allows for on/off toggling in map TOC • Region 6 had 98 total symbol classes! • Annotation classes allow cartographic groupings of similar symbol parameters • Will the annotation be displayed using a different projection? • Horizontal annotation will rotate • Isolate labels to manage separately

10. Annotation Geodatabase Design

11. Subtype Details of an Annotation GDB Feature Class • An annotation feature class contains user-defined symbol classes (subtypes) and annotation classes • Annotation classes correspond to the cartographic standards developed by the agency • Unique symbol classes for horizontal labels

12. Converting/Importing Annotation 7.5 Minute Topological Maps USFS Visitor Maps Quad Based | 1:24k Scale | *.e00 or *.txt Seamless | ½” = 1 Mile | *.gdb or *.mdb

13. Importing From TXT/DGN Files • Run an AML to reference quad based annotation • Output is a Coverage • Select on DGN attributes to import to specific symbol classes using “Convert Coverage Annotation to Geodatabase Annotation” • Calculating Symbol ID and Annotation ID codes • Calculate status field for “placed” or “unplaced”

14. Automating the Process • Build a Model to automate the process of importing annotation to Geodatabase

15. Other Methods of Converting/Importing Annotation • Convert feature labels to Annotation • Outdated information contained in quad based TXT files or feature names that are frequently updated • Roads from INFRA • Recreation site names • Create annotation from scratch where TXT files are not available

16. Placing Annotation: Pieces to a Puzzle • Variations in font size and reference scale produce jumbled and overlapping labels • Drag, rotate, flip, resize, explode, merge and position text into a “best fit” location as to minimize overlap with features and other annotation • Use specific criteria or “Rules of Thumb” to place each label appropriately

17. Placing Annotation: Pieces to a Puzzle • Annotation along a linear feature • Horizontal annotation around a point or within a region • Avoiding overlapping annotation • Repeating annotation for large features • Precise spacing between annotation and features

18. Quality Assurance • Compare final product with hard/soft copy SEQs • Edge match adjacent quads and remove duplicate labels • Review attribute table to ensure Symbol ID and Annotation ID codes are assigned appropriately

19. Lessons Learned • Map caching significantly reduced refreshing speed • SDE editing frequently caused computer crashes • Worked on local machines, then appended groups of annotation together • Various methods of converting/importing annotation created thousands of “default” or unnecessary annotation classes • Applied a script to delete unused classes

20. Lessons Learned Cont. • A single annotation feature class for an entire forest region was too big to manage easily • Limit annotation feature classes to a single CSA • Limit annotation feature classes to particular symbol types • E.g. hydro annotation • Keep the number of symbol classes minimal … don’t get too specific unless necessary • Annotation of different symbol classes can share an annotation class

21. Are You Covered? Q U E S T I O N S ?