=============================================================================== ============== DLG2ARC TOOLKIT ==================== ============== TO CREATE ARC COVERAGES FROM DLG FILES ==================== ============== 04/21/97 ==================== =============================================================================== USAGE: ------ To start the tool, at the Arc: prompt, type: &r dlg2arc ASSUMPTIONS AND DEPENDENCIES: ----------------------------- 1. File extensions MUST be either ".dd" for DLG Standard-format files or ".do" for DLG Optional-format files. 2. All files with these extensions in a directory will be mass-processed. A mixture of DLG-Optional and DLG-Standard (the old format) can exist in the same directory and will be processed. All scales of DLG data will be mass-processed. AML PROGRAMS NEEDED: -------------------- dlg2arc.aml - begins DLG-to-Arc mass process, makes list file of DLGs to convert into coverages dlg2arc.menu - menu allowing user to set up DGL-to-Arc process dlg2arc_mass.aml - program to mass-process many DLGs dlg2arc_sing.aml - converts a single DLG file into ARC coverage(s) dlg2arc_fixlevel.aml - checks DLG level code in the header and modifies it to a "3" if necessary (the DLGARC command expects a "3") AML CALLING SEQUENCE: --------------------- dlg2arc first calls dlg2arc.menu, and then calls dlg2arc_mass, which calls dlg2arc_sing, which calls dlg2arc_fixlevel. However, each of these sub-AMLs can also be run stand-alone. See Section B below and the AML headers for more information on individual usages of the AMLs. NOTES ON DIRECTORY STRUCTURE: ----------------------------- This tool does not enforce any particular directory structure. TO CREATE COVERAGES FROM DLG FILES: ----------------------------------- 1. Put the 4 AML programs in some common directory. The DLG files can be in the same directory as the AMLS, or can be in another directory. Both Optional-format (*.do) and Standard-format (*.dd) files can be processed at the same time, as can be a mixture of different-scale data. 2. To process all DLG files (with *.d* extensions) in the current directory: a) Invoke Arc/INFO (Note: AMLs were developed under Arc Version 7.0.3, and may not work properly with an earlier Arc version). b) If AMLs are not in current directory, &amlpath "where AMLs are", OR &r path/path/dlg2arc c) Arc: &run dlg2arc The dlg2arc AML creates a list file (./qfile) of all *.d* files in the current workspace directory, and then calls dlg2arc_mass.aml, which loops through all the DLG files and runs dlg2arc_sing.aml. Output coverages and Arc watch files will be placed in the directory from which Arc is invoked and the AMLs are run. The original DLG files are retained as-is. Coverage coordinates will be in the selected Precision, and any Y-Shift entered will be added to the Y-coordinate values. 3. To mass-process only selected *.d* DLG files in a directory, you can create a list file (any name is fine) of just those that you wish to process. If any or all of these files do not exist in the current directory from which you want to start Arc/INFO, include the full pathnames to those DLG files in the list file. Then ... Arc: &run dlg2arc_mass (Eg. &run dlg2arc_mass dlglist DOUBLE -4000000) The dlg2arc_mass AML reads the list file, looping through each DLG file in the list and processing each through dlg2arc_sing.aml. Output coverages and Arc watch files will be placed in the directory from which Arc is invoked and the AMLs are run. The original DLG files are retained as-is. 4. If you only want to process a single DLG file, call the dlg2arc_sing.aml AML from command line: Arc: &run dlg2arc_sing (Eg. &run dlg2arc_sing quad1.do optional single 0) The dlg2arc_sing AML will process the DLG_file into a coverage containing spatial elements and MAJOR/MINOR attribute codes. A separate point coverage will be created if points exist in the DLG file. DLG FILE AND COVERAGE NAMING CONVENTIONS: ----------------------------------------- What follows is only a recommended naming convention for DLG files and resulting coverages. Coverage names created by these dlg2arc_* AMLs will reflect the names of the original DLG files (before the .extension), with an "x" at the end for point features. However, file extensions MUST be either ".dd" for DLG Standard-format files or ".do" for DLG Optional-format files. HOWEVER, if the corresponding "dlg_translate" Attribute Translation toolkit of AMLs is going to be run on the output coverages of this "dlg2arc" package, then the following naming conventions are MANDATORY. The "dlg_translate" AMLs require that coverages suffixes be the 2-letter category abbreviations below. The recommended naming convention is to suffix the DLG files with a 2-character DLG overlay abbreviation before the file extension: bd = Boundaries................ political and administrative boundaries hp = Hypsography............... topographic contours and bathymetry hy = Hydrography............... streams, lakes, and rivers lu = Land Use and Land Cover.. interpreted land surface characteristics ms = Manmade Structures........ urban areas, buildings, and parks mt = Miscellaneous Transportation ... pipelines and transmission lines nv = Non-Vegetative Features....... disturbed surface, quarries pl = Public Land Survey System (PLSS) rd = Roads and Trails rr = Railroads sc = Vegetative Surface Cover.. woods and orchards sm = Survey and Markers...... geodetic, horizontal and vertical control An "x" at the end of the coverage name indicates Point features, i.e. having only one x,y coordinate pair. For example: The DLG hydro file for a quad named "denver" would be: denverhy.do (or .dd) The hydro line, poly, and node coverage would be: denverhy The hydro point coverage would be: denverhyx The contour lines are in coverage: denverhp The contour spot elevations are in coverage: denverhpx ADDITIONAL DLG PROCESSING TOOLS AVAILABLE: ------------------------------------------ Once the DLG files are converted into Arc coverages, the "dlg_translate" toolkit can be run on the coverages to translate DLG MAJOR/MINOR INFO attributes into symbol-based, descriptive attributes. To do this: 1. Unpack the dlg_translate.tar file into your favorite AML directory. 2. Go to the directory where the output coverages from "dlg2arc" reside. 3. ARC: &amlpath "your AML directory path" 4. &r dlg_translate (Ex: &r dlg_translate denver where covers are named denverhy, etc.) See the associated README file for the dlg_translate kit for more information.