Converting Coverage Annotation into the Geodatabase

Transcription

1 Converting Coverage Annotation into the Geodatabase The following steps outline a method for moving coverage annotation into the geodatabase (GDB) avoiding some known limitations: The size of coverage (and CAD) annotation elements imported into the GDB are reduced in size and therefore do not represent the intended size of the annotation. For example, annotation with $size = 5 in the coverage gets imported into the GDB with FontSize = 3.6. The reason this happens is because the height of the annotation is set to the GDB annotation s graphic envelope which includes space around its boarders. Due to the above limitation, and also due to the fact that a given level of annotation may have multiple sizes, the wrong symbol size may be imported and generated in the annotation symbol collection. It has proven to be too manual a process to modify the symbol, delete the original symbol and reset coverage annotation properties. Ideally when importing the coverage annotation into the GDB it has all of the necessary annotation levels in a single coverage rather than individual annotation levels in individual coverage. If individual coverages happens to be the case, this can be taken care of simply by appending the resulting GDB annotation feature classes into a single GDB annotation feature class with multiple levels. The following steps outline a precise method of maintaining the original annotation size and develop a symbol collection that is ideal for annotation editing and consistent with the ORMAP geodatabase design. 1) Pre-process the Coverage Annotation in Workstation ArcInfo a. Make a copy of the original coverage annotation (it will need to be modified and won t work the same way in the Workstation environment). b. DEFINE a projection for the Annotation Coverage. The conversion process may not work as expected if projection information is unknown. That is because the conversion process relies on a reference scale. The scale can not be established if projection information is unknown. Simply setting the projection properties of the data frame may not work. c. CALC $SYMBOL = $LEVEL. Each unique $level in the coverage must have a unique $symbol in the coverage otherwise when you view the coverage annotation level properties in ArcMap, there won t be a one to one relationship. This becomes an issue when you will try to establish the new symbol properties for each annotation level.

2 d. Preserve $SIZE by adding an item (e.g., ANNOSIZE) using CALC ANNOSIZE = $SIZE. In a later step, annotation size will be set to a single height for all annotation of a given level and scale. But there may have been situations where individual elements were calculated differently for cartographic purposes. If the value is preserved, then it can later be recalculated to its original intended size. For example, a standard size of 5 may be set to 4.8 so it fits better on the map. e. CALC $SIZE = 0. When the coverage annotation size = 0, the size of the annotation can be modified via the layer properties in ArcMap. This will enable us to control the size of the converted annotation based on established ORMAP annotation symbol standards. f. Associate MapNumber with each annotation element. This is required for the ORMAP mapping applications because annotation elements are dynamically filtered using this field. There are a variety of techniques for doing this. Some counties already have MapNumbers associated with their annotation elements so this step isn t required. g. Associate MapScale with each annotation element. This field is necessary for breaking the coverage annotation elements based on scale. Again, this can be done a variety of different ways using different overlay commands. 2) Prepare Annotation Definitions in ArcMap a. Add the coverage annotation layer into ArcMap b. Be sure to let the entire layer render completely before attempting to set the layers and symbols properties. These lists are populated during the drawing phase and if you stop the drawing prematurely, the lists may not get completed. c. Copy the layer multiple times for each level (e.g., 100, 200, etc) of standard annotation and each annotation feature-linked annotation (e.g., TaxlotNum, Code, etc). The idea is that each layer in the TOC will become a separate annotation feature class in the ORMAP geodatabase design. d. Rename each layer accordingly - In the graphic below it shows 40, 100, 200, 400 and 2000 scales for standard annotation and the 5 layers that represent the feature-linked annotation. Again, this is the same coverage added 10 times for the Polk Co pilot data (Note: it does not include all possible map scales).

3 e. Create a Definition Query for each layer. The idea is to isolate only the appropriate annotation for each layer so when it is time to convert, only the filtered annotation gets converted into the geodatabase. For standard annotation, you filter for the map scale of interest and filter out the featurelinked levels (see graphic above). For the feature-linked, you simply query on the level (see graphic below). Feature-linked annotation is not separated by scale. f. Set the appropriate symbol definitions for each level using the definitions in Appendix-A. Because $size was set = 0 in Workstation ArcInfo, the newly converted annotation will take on the size that is established via the layer properties in ArcMap. The symbol properties for standard annotation at each scale must be set accordingly based on Appendix A. For the feature-linked annotation levels, I simply use the 1200 scale ORMAP standard definitions. This process must be repeated for each layer in the TOC. Note when you view the symbols list via the layer properties, all levels/symbols are displayed regardless of the definition query. It is not necessary to take the time to symbolize layers that are being filtered out. For example, for feature-linked annotation layers, simply set the properties for only that one level.

4 Another important note although standards exist, when you set the symbol properties for each symbol / scale, it is important to use the sizes and symbols that best match your current system. For example, if you create bearing and distance elements at 100 scale consistently at 4 on the ground, it doesn t make sense to use the state standard of 5 because each new default element created would be 5 and would not match the all the other 4 annotation. Also take the time to compare the geodatabase annotation to your coverage annotation. In Polk Co we noticed that bearing and distances best match the coverage annotation using Arial Narrow rather than Arial suggested by the standard. g. Save the Map Document once you have gone through the effort of creating the layers, definition queries, and setting the symbol properties you want to save them. In the future, if you want to run the conversion again on an updated coverage, simply replace the older coverage with the newer one and the MXD will reference it with all of the layer properties you saved. h. Open the Import Coverage Annotation Geoprocessing Tool it can be found under ArcToolbox Conversion Tools To Geodatabase.

5 i. Convert the standard annotation into the geodatabase i. Select the appropriate layer (e.g., StdAnno.igds 100scale) ii. Specify output GDB annotation feature class name (e.g., Anno0100scale) iii. Always set reference scale to 1200 (for standard and feature-linked) iv. Verify that create annotation classes from levels is checked. v. Click OK j. Repeat the above step for each standard annotation level this could be automated by duplicating the steps in a single model or using the scripting environment to loop through each layer in the TOC. k. Convert the feature-linked annotation into the geodatabase i. Select the appropriate layer (e.g., FLAnno.igds TaxlotNum) ii. Specify output GDB annotation feature class name (e.g.,taxlotnumberanno) iii. Always set reference scale to 1200 (for standard and feature-linked) iv. Verify that create annotation classes from levels is checked. v. Check the Feature-linked option vi. Browse to the layer in the ORMAP GDB design that annotation should be linked to.

6 vii. Click OK l. Repeat the above step for each feature-linked annotation level again, this could be automated by duplicating the steps in a single model or using the scripting environment to loop through each layer in the TOC. Note coverage annotation converted into feature-linked annotation feature classes does not automatically create the link between the annotation and the feature. The process of taking dumb annotation and linking it to the feature requires that the Annotation FeatID = the OID of the feature. The process of automating the link can be done using a series of geoprocessing steps. This was outlined in the Labels & Annotation Workshop presented during the Fall of m. Save and close ArcMap 3) Additional Geoprocessing steps a. Use the Calculate Field Geoprocessing Tool to calculate Fontsize to equal the preserved coverage annotation size (e.g., AnnoSize) identified in step

7 1d. This will reset the size of the converted annotation to match the original size of the coverage annotation. Again this step helps us with the situations where some individual annotation elements were sized differently from the standard. The following steps are optional and may not apply for all conversion efforts. It depends on the data being converted and whether or not the coverage supports the attributes in the ORMAP geodatabase design. The purpose of these steps are to make the annotation feature classes consistent with the ORMAP annotation design and mostly involves attribute manipulation. b. Use the Add Field Geoprocessing Tool to add a field called MapNumber if your original coverage annotation uses a different field name (e.g., MapNum), then add a field consistent with the model. c. Use the Calculate Field Geoprocessing Tool to calculate MapNumber to equal the other existing MapNum d. Use the Delete Field Geoprocessing Tool to remove the no longer needed field (MapNum) Now the new annotation feature class has a field that matches the ORMAP geodatabase design. These same steps can be applied to other fields like MapScale, AutoWho, AutoDate, AutoMethod, etc. Even if these fields don t exist in the original coverage, it still makes sense to add these fields so they can be automatically updated in the ORMAP editing applications. Note: all of the steps up to this point can be automated using the geoprocessing framework. Model Builder could easily be used to automate the process for a single layer. Scripting could be used to automate the entire conversion by looping through each layer in the process. 4) Final Clean-up in ArcCatalog The following steps can not be automated in the geoprocessing framework. For those of you that are going to convert coverage annotation into the geodatabase on a regular basis you may not want to go through these steps each time or you may want to at least abbreviate some of the steps. Optional steps will be noted. a. Set field for feature-linked annotation during the conversion of featurelinked annotation there was never a setting to specify which attribute on the linked feature class the annotation would be linked to. i. Open the feature class properties dialog for the feature-linked annotation. ii. Click on the Annotation Classes tab

8 iii. Set the appropriate Label field. In the graphic below, TaxCode is the field used for the TaxCodeAnno feature class. iv. In some cases an expression may also be added. For example, with TaxLotAcres you may want to append Ac. to the string. b. (Optional) Rename annotation class by default, the coverage level number becomes the name. You can simply rename it using the Rename button (see above graphic). This is not critical to the conversion but when setting the Target Layer in the Editor Toolbar, users will see the level number rather than the more descriptive name.

9 c. (Optional) Rename annotation symbols in the collection by default, the coverage level number becomes the symbol name. You can simply rename it using the Rename button (see above graphic). This is not critical to the conversion but when viewing the symbol list in the Editor Toolbar, users will see the level numbers rather than the more descriptive names. d. Add additional symbols to the symbol collection there are situations in the State standard that suggest multiple sizes for a give level. Here you have the opportunity to create those additional symbols that can be easily selected from the symbol collection.

10 Appendix A provided by Rodney Thearault from DOR. Again, take the time to compare these values against the sizes used in your current system. Scale Scale Scale Scale Scale Scale Scale Scale Scale Scale Level Name Font Grd Grd Grd Grd Grd Grd Grd Grd Grd Grd 10 PUBLIC ROAD NAME ALTERNATE Arial 1.40' 2.80' 4.20' 5.60' 7.00' 10.00' 16.00' 32.00' 64.00' ' 10 PUBLIC ROAD NAME LARGE Arial 2.00' 4.00' 6.00' 8.00' 10.00' ' 40.00' 64.00' ' 13 PRIVATE ROAD ANNOTATION Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 64.00' ' 16 RAILROAD NAME Arial 2.00' 4.00' 6.00' 8.00' 10.00' 20.00' 28.00' ' ' 19 EASEMENT Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 80.00' ' 20 STATION (ETC) Arial 0.50' 1.00' 1.50' 2.00' 2.50' 5.00' 10.00' 20.00' 40.00' ' 23 WATER BODY NAME LARGE Italic ) 2.00' 4.00' 6.00' 8.00' 10.00' 20.00' 50.00'? 40.00' ' ' 23 WATER BODY NAME SMALL Italic ) 2.00' 4.00' 6.00' 8.00' 10.00' 20.00' 28.00' 40.00' 64.00' ' 25 RIVER NAME LARGE Italic ) 2.00' 4.00' 6.00' 8.00' 10.00' 20.00' 50.00'? 40.00' ' ' 25 RIVER NAME SMALL Italic ) 2.00' 4.00' 6.00' 8.00' 10.00' 20.00' 28.00' 40.00' 64.00' ' 27 CREEK NAME Italic ) 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 64.00' ' 29 CANAL NAME Italic ) 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 64.00' ' 30 MISC HYDRO ANNO Arial 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 64.00' ' 34 BEARING & DISTANCE Arial 0.50' 1.00' 1.50' 2.00' 2.50' 5.00' 10.00' 20.00' 40.00' ' 35 SURVEY # Arial 0.80' 1.60' 2.40' 3.20' 4.00' 8.00' ' 64.00' ' 36 REFERENCE NOTES Arial 0.50' 1.00' 1.50' 2.00' 2.50' ' 20.00' 40.00' ' 37 TAXLOT # Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 64.00' ' 38 TAXLOT ACRES Arial 0.80' 1.60' 2.00' 3.20' 4.00' 8.00' 16.00' 32.00' 48.00' ' 41 SUBDIVISION NAME LARGE Shadow ( 30 Degree Angle ) ' 7.20' 9.60' 12.00' 24.00' 48.00' 96.00' ' ' 41 SUBDIVISION NAME SMALL Shadow 2.40' 2.40' 3.60' 4.80' 6.00' 12.00' 24.00' 48.00' 96.00' ' 42 BLOCK # Arial 2.00' 4.00' 6.00' 8.00' 10.00' 20.00' 40.00' 56.00' ' LOT # Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 80.00' ' 45 SECTION # Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 80.00' ' 46 GOV. LOT # & ACRES Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 64.00' ' 47 D.L.C. NAMES Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' ' 48 MEANDER NAMES Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 80.00' ' 49 STANDARD PARALLEL Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' ' 54 TAXCODE Arial 5.00' 10.00' 15.00' 20.00' 25.00' 50.00' ' ' ' ' 55 SPECIAL BOUNDARY Arial 0.80' 1.60' 2.40' 3.20' 4.00' 8.00' 16.00' 32.00' 64.00' ' 56 ZONE ANNOTATION Italic ) Underline 2.40' 4.80' 7.20' 9.60' 12.00' 20.00' 48.00' 96.00' ' ' 57 CITY LIMITS ANNOTATION Arial 0.80' 1.60' 2.40' 3.20' 4.00' 8.00' 16.00' 32.00' 64.00' ' 58 ADJACENT ( CO.STATE & NATIONAL FOREST ) Shadow ' 7.20' 9.60' 12.00' 24.00' 48.00' 96.00' ' ' 59 LANDMARK ( TOWN, PEAKS & ETC. ) Arial 0.80' 1.60' 2.40' ' 8.00' 16.00' ' ' 61 VEGETATION ANNOTATION Arial 0.80' 1.60' 2.40' ' 8.00' 16.00' 32.00' 64.00' ' 62 MAP INDEX Arial 2.00' 4.00' 6.00' 8.00' 10.00' ' 40.00' 64.00' ' 62 SEE MAPS Arial 1.00' 2.00' 3.00' 4.00' 5.00' 10.00' 20.00' 40.00' 64.00' '

11