WPC1 2B Zq!qDLG-3/SDTS Transfer Description Document 7Xdp@Q@a1Legal1 1.1 1.1.1 etc.a2Legal1 1.1 1.1.1 etc.2)}5}}/}a3Legal1 1.1 1.1.1 etc.$ a4Legal1 1.1 1.1.1 etc.$ a5Legal1 1.1 1.1.1 etc.$   a6Legal1 1.1 1.1.1 etc.$   2\1}[}U0m+a7Legal1 1.1 1.1.1 etc.$  a8Legal1 1.1 1.1.1 etc.$  I. A. 1. a.(1)(a) i) a)ҫdp@Q@<p`(,Prestige 12cpi (10pt)Xo PQXP8`:Century-WPhoolbook 12pt (SA)XXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XT PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)X P QP8` CXo P QXP8`:Century-WPhoolbook 12pt (SA)XZ P QP8` CXo P QXP8`:Century-WPhoolbook 12pt (SA)X P QP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)X PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)X PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ PQP8` C PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ PQP8` CXo PQXP8`:Century-WPhoolbook 12pt (SA)XZ P QP8` CXo P!QXP8`:Century-WPhoolbook 12pt (SA)X P"QP8` CXo P#QXP8`:Century-WPhoolbook 12pt (SA)XZ P$QP8` CXo P%QXP8`:Century-WPhoolbook 12pt (SA)X P&QP8` CXo P'QXP8`:Century-WPhoolbook 12pt (SA)XZ P(QP8` CXo P)QXP8`:Century-WPhoolbook 12pt (SA)XZ P*QP8` CXo P+QXP8`:Century-WPhoolbook 12pt (SA)X P,QP8` CXo P-QXP8`:Century-WPhoolbook 12pt (SA)XZ P.QP8` CXo P/QXP8`:Century-WPhoolbook 12pt (SA)XZ P0QP8` CXo P1QXP8`:Century-WPhoolbook 12pt (SA)X P2QP8` CXo P3QXP8`:Century-WPhoolbook 12pt (SA)X P4QP8` CZ P5QP8` CXo P6QXP8`:Century-WPhoolbook 12pt (SA)XZ P7QP8` CXo P8QXP8`:Century-WPhoolbook 12pt (SA)X P9QP8` CXo P:QXP8`:Century-WPhoolbook 12pt (SA)X P;QP8` CXo P<QXP8`:Century-WPhoolbook 12pt (SA)XZ P=QP8` CXo P>QXP8`:Century-WPhoolbook 12pt (SA)XZ P?QP8` CXo P@QXP8`:Century-WPhoolbook 12pt (SA)X2113|d 1 .1 .1 .1 .1 .1 .1 .1 #Xo PQXP# I. A. 1. a.(1)(a) i) a)#Xo PQXP# I. A. 1. a.(1)(a) i) a)DLG3 SDTS Transfer Description `|!(#GPage ĝ DLG3 SDTS Transfer Description May 7, 1996      Purpose of this Document  This document describes how U.S. Geological Survey (USGS) digital line graph 3 (DLG3) files are transferred using the Topological Vector Profile (TVP) of the Spatial Data Transfer Standard (SDTS). The document is divided into four sections:  1.) Transfer Overview overviews the structure of the DLG3 SDTS transfer including an summary of the modules included and description of equivalent DLG3 and SDTS spatial concepts.  2.) SDTS Module Contents ĩ This section enumerates the fields and subfields of each SDTS module used in the transfer, showing each subfield's contents and where this information was obtained.  3.) Master Data Dictionary Transfer Module Contents Instead of being included with each transfer of DLG3 data, the Data Dictionary/Definition and Data Dictionary/Domain modules are transferred in a separate master data dictionary transfer. This section describes the modules in the master data dictionary transfer.  4.) Attribute Modules This describes the Attribute Primary modules and how DLG3 attribute codes are converted into attributes in the SDTS. References FIPS PUB 173: Spatial Data Transfer Standard(August28, 1992). Available from The National Technical Information Service, U.S. Department of Commerce, Springfield, VA 22161. Text online at Anonymous FTP sit sdts.er.usgs.gov, directory "standard" Part4: topological Vector Profile (July6, 1993). Available from The National technical Information Service, U.S. Department of Commerce, Springfield, VA 22161. Text online at Anonymous FTP site sdts.er.usgs.gov, directory "standard" Cartography and Geographic Information Systems, Vol 19, No. 5, December 1992, Amercian Congress on Surveying and Mapping, Special Issue on SDTS. Text of some articles on line at Anonymous FTP sit sdts.er.usgs.gov, directory "articles" USGS Publication: Digitial Line Graphs fron 1:24,000Scale Maps, Data Users Guide. Available from U.S. Geological Survey, National Center, Reston, VA 22092 USGS Publication: Digitial Line Graphs fron 1:100,000Scale Maps, Data Users Guide. Available from U.S. Geological Survey, National Center, Reston, VA 22092 SDTS Software and Datasets. For the latest available, see Anonymous FTP site sdts.er.usgs.gov, directory "software" and "datasets"  Table of Contents      1. Transfer Overviewp"(#J1 ` ` ` 1.1 Modules Which Apply to an Entire Transferp"(#J2 ` ` ` 1.2 Modules Which Apply to a Particular 2D Manifoldp"(#J3 ` ` ` 1.3 Modules Included in Master Data Dictionary Transferp"(#J3 ` ` ` 1.4 Module and File Namesp"(#J4 ` ` ` 1.5 File Orderp"(#J4 ` ` ` 1.6 Spatial Reference Systemsp"(#J6 ` ` ` 1.7 Spatial Objectsp"(#J7  2. Transfer Module Contentp"(#J9 ` ` ` 2.1 AHDR (Attribute Primary)p`"(#I10 ` ` ` 2.2 CATD (Catalog / Directory)p`"(#I12 ` ` ` 2.3 CATS (Catalog / Spatial Domain)p`"(#I12 ` ` ` 2.4 CATX (Catalog / CrossReference)p`"(#I13 ` ` ` 2.5 DDSH (Data Dictionary / Schema)p`"(#I14 ` ` ` 2.6 DQAA (Data Quality/Attribute Accuracy)p`"(#I15 ` ` ` 2.7 DQCG (Data Quality/Completeness)p`"(#I15 ` ` ` 2.8 DQHL (Data Quality/Lineage)p`"(#I16 ` ` ` 2.9 DQLC (Data Quality/Logical Consistency)p`"(#I16 ` ` ` 2.10 DQPA (Data Quality/Positional Accuracy)p`"(#I17 ` ` ` 2.11 FF01 (Composite)p`"(#I18 ` ` ` 2.12 IDEN (Identification)p`"(#I19 ` ` ` 2.13 IREF (Internal Spatial Reference)p`"(#I21 ` ` ` 2.14 Lenn (Line)p`"(#I22 ` ` ` 2.15 Nann (PointNode for Area Points)p`"(#I23 ` ` ` 2.16 NEnn (PointNode for Entity Points)p`"(#I24 ` ` ` 2.17 NOnn (PointNode for Planar Nodes)p`"(#I25 ` ` ` 2.18 Npnn (PointNode)p`"(#I26 ` ` ` 2.19 Pcnn (Polygon)p`"(#I27 ` ` ` 2.20 SPDM (Spatial Domain)p`"(#I28 ` ` ` 2.21 STAT (Transfer Statistics)p`"(#I29 ` ` ` 2.22 XREF (External Spatial Reference)p`"(#I30  3. Master Data Dictionary Transfer Modulesp`"(#I31 ` ` ` 3.1 MDEF (Data Dictionary / Definition)p`"(#I31 ` ` ` 3.2 MDIR (Catalog / Directory)p`"(#I32 ` ` ` 3.3 MDOM (Data Dictionary / Domain)p`"(#I33 ` ` ` 3.4 MIDE (Identification)p`"(#I34 ` ` ` 3.5 MQCG (Data Quality/Completeness)p`"(#I35 ` ` ` 3.6 MQHL (Data Quality/Lineage)p`"(#I35` ` ` 4. Attribute Modulesp`"(#I36 ` ` ` 4.1 Introductionp`"(#I36 ` ` ` 4.3 Attribute Secondary Modulesp`"(#I37 ` ` ` 4.4 Attribute Modules by Themep`"(#I38 ` ` ` 4.5 Attribute Valuesp`"(#I39 ` ` ` 4.6 Feature Attribute Primary Modulesp`"(#I40 ` ` ` ` ` Hypsographyp`"(#I40 ` ` ` ` ` Hydrographyp`"(#I41 ` ` ` ` ` Vegetative Surface Coverp`"(#I44 ` ` ` ` ` NonVegetative Featuresp`"(#I44 ` ` ` ` ` Boundariesp`"(#I45 ` ` ` ` ` Survey Controlp`"(#I47 ` ` ` ` ` Roads and Trailsp`"(#I48 ` ` ` ` ` Railroadsp`"(#I50 ` ` ` ` ` Pipelinesp`"(#I52 ` ` ` ` ` Manmade Featuresp`"(#I53 ` ` ` ` ` Public Land Surveyp`"(#I57 ` ` ` 4.7 Coincidence Attribute Primary Modulep`"(#I59 ` ` ` 4.8 Elevation Attribute Primary Modulep`"(#I59 ` ` ` Route Attribute Primary Modulep`"(#I60 ` ` ` 4.9 Agency Attribute Primary Modulep`"(#I61 ` ` ` 4.10 State Attribute Secondary Modulep`"(#I61 ` ` ` 4.11 County Attribute Secondary Modulep`"(#I61 ` ` ` 4.12 Populated Places Attribute Secondary Modulep`"(#I62 ` ` ` 4.13 Airport Names Attribute Secondary Modulep`"(#I63 ` ` ` 4.14 Land Grant Attribute Secondary Modulep`"(#I63     1 .1 .1 .1 .1 .1 .1 .1 Legala1Legal. Transfer Overview A DLG3 SDTS transfer is created from one or more DLG3 files. Each DLG3 file is converted to one SDTS twodimensional manifold, the SDTS's term for a topologically structured planar graph with twodimensional objects. One or multiple 2D manifolds may be included in one transfer. Multiple 2D manifolds are included in a transfer for (1) DLG3 Roads and Trails, Railroads, and Pipelines which are combined into a "transportation" transfer or (2) 1:100,000scale DLGs where a transfer consists of 7.5 or 15 minute partitions of a 30 minute by 30 minute area (transportation themes are also combined into one transfer in this situation.) In other cases, a transfer will consist of one 2D manifold (one DLG3 file.) A DLG3 SDTS transfer consists of a group of SDTS modules, each in a separate ISO 8211 file. On media which have directory structures, each transfer is placed in a separate directory. On media with a sequential structure, such as ANSIlabeled tapes, the files for a transfer are grouped on the media with the Identification module placed first. Not all module types defined by the SDTS are included; only some are applicable to TVP and DLG3 transfers. Some module types apply to an entire transfer. Other module types apply to a specific 2D manifold and will be repeated for each 2D manifold; for example, each 2D manifold will have its own set of spatial object modules. Others may be repeated multiple times for a specific 2D manifold; for example, there are two or more Attribute Primary modules for each 2D manifold.  a2Legal Modules Which Apply to an Entire Transfer  Except for Attribute Primary modules, there will be exactly one of each of the following modules. T ddxh  ddxh  T BRRBRRModule NameModule TypeDescriptionAQQAQQAAttribute PrimaryContains attributes of spatial objects. The structure, number, and name of modules will vary with the DLG3 theme being transferred. Attribute Primary modules are described in detail in section 4. AQQ AQQAHDRAttribute PrimaryDLG3 "header" information which does not have a predefined location within the SDTS@PP@PPCATDCatalog/ DirectoryDirectory of each module included in or referenced by the transfer @PP @PPCATSCatalog/ Spatial DomainCatalog of the relationships of modules to 2D manifolds, themes, and maps @PP @PPCATXCatalog/ Cross ReferenceCatalogs relationships between modules @PP @PPDDSHData Dictionary/ SchemaDescribes the structure of attributes in Attribute Primary modules @PP @PPDQAAAttribute AccuracyContains the data quality report for Attribute AccuracyI@PPI@PPDQCGCompletenessContains the data quality report for CompletenessI@PPI@PPDQHLLineageContains the data quality report for Lineage @PP @PPDQLCLogical ConsistencyContains the data quality report for Logical Consistency @PP @PPDQPAPositional AccuracyContains the data quality report for Positional Accuracy @PP @PPFF01CompositeContains composite objects for each 2D manifold "surface." @PP @PPIDENIdentificationContains global identification information for the transfer@PP@PPIREFInternal Spatial ReferenceDescribes the internal spatial reference system and its relationship to the external spatial reference system@PP@PPSPDM (Used only for 1:2,000,000scale DLGs)Spatial DomainDefines the minimum and maximum limits of a geographic areal domain within which the spatial addresses of the transfer are contained (Not used for 1:100,000 and 1:24,000scale DLGs)I@PPI@PPSTATStatisticsContains statistics on each module in the transfer:BRR:BRRXREFExternal Spatial ReferenceDescribes the external spatial reference system  a2Legal Modules Which Apply to a Particular 2D Manifold  These modules will be repeated for each 2D manifold (corresponding to one DLG3 file): T ddx ddx T ZBRRZBRRModule NameModule TypeDescription @PP @PPLELine (Complete Chains)Contains complete chain spatial objects @PP @PPNAPointNode (Area Points)Contains area point spatial objects@PP@PPNEPointNode (Entity Points)Contains entity point spatial objects (this module is omitted if the transfer does not contain entity points)I@P PI@P PNOPointNode (Nodes)Contains node spatial objects@PP@PPNP (Not used for 1:2,000,000scale DLGs)PointNode (Generic Points)Contains point spatial objects for the four registration points used in DLG3 files (registration points correspond to map quadrangle corners for 1:24,000 and 1:100,000scale DLG3's):BRR:BRRPCPolygonContains GTPolygon spatial objects (including Universe Polygon and Void Polygons) The last two characters of the module name will be the same for a particular 2D manifold and will correspond to the Aggregate Object subfield value in the Catalog/Spatial Domain module. The first 2D manifold will be "01"; all digits 09 and all uppercase letters AZ are possible in these two characters.  a2Legal Modules Included in Master Data Dictionary Transfer  To avoid duplication, the data dictionary is transferred in a master data dictionary transfer as described in Section 3. T ddx8 ddx8 T ZBRRZBRRModule NameModule TypeDescription@PP@PPMDEFData Dictionary/ DefinitionContains definitions of entities and attributesI@PPI@PPMDIRCatalog/ DirectoryDirectory of each module included in the transferI@PPI@PPMDOMData Dictionary/ DomainContains the domain of values for attributes @PP @PPMIDEIdentificationContains global identification information for the transfer @PP @PPMQCGData Quality/ CompletenessCompleteness data quality report for the master data dictionary:BRR:BRRMQHLData Quality/ LineageLineage data quality report for the master data dictionary a2Legal Module and File Names Module names are shown in the previous tables. These are standardized by the TVP. In cases where there is a potential for multiple instances of a module type within a transfer, some characters of the module name will vary. These are indicated by dashes in the names. The TVP standardizes file names to be a 4character transfer base name followed by the module name. The extension will always be DDF. For 1:24,000 & 1:100,000scale DLG3's, the transfer base name is an abbreviation for the theme contained in a transfer followed by an arbitrary two characters. For example, in a transfer of the hydrography theme, the Identification module file might be named HY01IDEN.DDF. For 1:2,000,000scale DLG3's, the transfer base name is the two letter state abbreviation followed by the theme abbreviation. For example, in a transfer of the hydrography theme of the state of Virginia, the Identification module will be named VAHYIDEN.DDF. The following abbreviations are used in file names for themes: J ddx  ddx J i@ Pi@ P#Z PQP#AbbreviationTheme Namei@ Pi@ PHPHypsographyI@ PI@ PHYHydrographyI@ PI@ PSCVegetative Surface CoverI@ PI@ PNVNonVegetative FeaturesI@ PI@ PBDBoundariesI@ PI@ PSMSurvey Control and Markers@ P@ PTRTransportation (contains Roads and Trails, Railroads, and Pipelines, Transmission Lines, and Miscellaneous Transportation Features)I@ PI@ PMSManmade FeaturesyB RyB RPLU.S. Public Land Survey System#Xo PQXP#  a2Legal File Order  DLG3 SDTS transfers use 9track magnetic tape conforming to ANSI X3.27 (commonly known as "ANSIlabeled tapes.") A tape may contain multiple transfers; each transfer begins with an Identification module. The first file on a tape is a README file which is an ASCII text file, not an ISO 8211 file. Next are the files for the master data dictionary transfer. Finally are the files for one or more SDTS transfers containing DLG3 data. The following table illustrates the order of files. T ddx ddx T B B RB B RFile NameModule TypeComments9@@P9@@PREADMEASCII text file, not an SDTS moduleI@ @ PI@ @ PDLG3MIDE.DDFIdentificationPart of master data dictionary transferI@ @ PI@ @ PDLG3CATD.DDFCatalog/ DirectoryPart of master data dictionary transferI@ @ PI@ @ PDLG3MDEF.DDFData Dictionary/ DefinitionPart of master data dictionary transferI@ @ PI@ @ PDLG3MDOM.DDFData Dictionary/ DomainPart of master data dictionary transferI@ @ PI@ @ PDLG3MQHL.DDFData Quality/ LineagePart of master data dictionary transferI@ @ PI@ @ PDLG3MQCG.DDFData Quality/ CompletenessPart of master data dictionary transfer*@@P*@@PThe following files are repeated for each transfer (bbbb indicates a file name base which is common to all files in a transfer, or indicates part of a file name which is variable)i@ @ Pi@ @ PbbbbIDEN.DDFIdentificationIndicates the beginning of a transferI@ @ PI@ @ PbbbbCATD.DDFCatalog/ DirectoryCatalog of all modules in a transferI@ @ PI@ @ PbbbbCATX.DDFCatalog/ CrossReferenceI@ @ PI@ @ PbbbbCATS.DDFCatalog/ Spatial DomainI@ @ PI@ @ PbbbbIREF.DDFInternal Spatial ReferenceI@ @ PI@ @ PbbbbXREF.DDFExternal Spatial ReferenceI@ @ PI@ @ PbbbbSPDM.DDFSpatial DomainOnly used for 1;2,000,000scale DLG3'sI@ @ PI@ @ PbbbbDDSH.DDFData Dictionary/ SchemaI@ @ PI@ @ PbbbbDQHL.DDFData Quality/ LineageI@ @ PI@ @ PbbbbDQPA.DDFData Quality/ Positional AccuracyI@ @ PI@ @ PbbbbDQAA.DDFData Quality/ Attribute AccuracyI@ @ PI@ @ PbbbbDQLC.DDFData Quality/ Logical ConsistencyI@ @ PI@ @ PbbbbDQCG.DDFData Quality/ Completeness@ @ P@ @ PbbbbA.DDFAttribute PrimaryNumber of and names of Attribute Primary modules will vary with theme (see section 4)M@ @ PM@ @ PbbbbB.DDFAttribute SecondaryNumber of and names of Attribute Secondary modules will vary with theme and scale (they are only used with 1:2,000,000scale DLG3's; see section 4)I@ @ PI@ @ PbbbbFF01.DDFComposite @ @ P @ @ PbbbbNA.DDFPointNodeContains area point objects; one module per 2D manifold@ @ P@ @ PbbbbNE.DDFPointNodeContains entity point objects; one module per 2D manifold (omitted if a 2D manifold does not contain entity points) @ @ P @ @ PbbbbNO.DDFPointNodeContains planar node objects; one module per 2D manifold@ @ P@ @ PbbbbNP.DDFPointNodeContains point objects for the four quadrangle corners of a DLG in 1:24,000 and 1:100,000scale only; one module per 2D manifold @ @ P @ @ PbbbbLE.DDFLineContains complete chain objects; one module per 2D manifold:B B R:B B RbbbbPC.DDFPolygonContains GTpolygon objects; one module per 2D manifold  a2Legal Spatial Reference Systems  As required by the TVP, spatial addresses (coordinates) are stored internally as 32bit signed binary integers. This coordinate system is known as the internal spatial reference system. The external spatial reference system is a groundbased coordinate system; the Universal Transverse Mercator (UTM) grid system is used for 1:24,000 and 1:100,000scale DLG3's. Geographic coordinates are used as the external spatial reference system for 1:2,000,000scale DLG3's. The Z coordinate is not used in DLG3's. Internal system spatial addresses in 1:24,000 and 1:100,000scale DLG3's are in centimeters. The external system spatial addresses for these scales are in meters. Internal system spatial addresses for 1:2,000,000scale DLG3's are in millionths of degrees of latitude and longitude. The external system spatial addresses for this scale are in decimal degrees. The Internal Spatial Reference module contains transformation parameters to transform from internal to external spatial addresses. Scale factors for both X and Y specify that coordinates are multiplied by .01 for 1:24,000 and 1:100,000scale DLG3's and by 0.000001 for 1:2,000,000scale DLG3's. Origins of 0.0 indicate that there is no translation of coordinates. This conversion can be expressed by the following formulas: (XINTERNAL * Scale_Factor_X) + X_Origin = XEXTERNAL (YINTERNAL * Scale_Factor_Y) + Y_Origin = YEXTERNAL The following table shows an example of converting from internal to external spatial addresses. r dd~xx dd~xx r &@@ @ @ @ P@@ @ @ @ P&#T PQP#DLG scaleSpatial Address Coordinate LabelInternal Spatial AddressScale FactorOriginExternal Spatial Address&k@@ @ @ @ Pk@@ @ @ @ P&1:24,000 &X447181970.01 0.0447181.97&{BB B B B R{BB B B B R&1:100,000Y4386108690.01 0.04386108.69&K@AAAAQK@AAAAQ&1:2,000,000Xܩ1005248730.000001 0.0ܩ100.524873&kBBBBBRkBBBBBR&Y364995020.000001 0.036.499502  #Xo PQXP#a2Legal Spatial Objects  DLG3 spatial objects are converted to corresponding SDTS spatial objects as shown in the following table:  ^ ddxt 0  ddxt 0 ^ BBBRBBBRDLG3 Spatial ObjectSDTS Spatial ObjectObject Representation CodeModule Name@@@P@@@PNode Planar NodeNONO @@@P @@@PLine Complete ChainLELE @@@P @@@PDegenerate Line Entity PointNENE@@@P@@@PArea (Maps to one of the three according to attribution)GTPolygon Universe Polygon or Void PolygonPC PW PXPC@@@P@@@Pand > Area PointNANABBBRBBBRRegistration Point (Not applicable to 1:2,000,000scale DLG3's) PointNPNP a2Legal Surface Composite Module (FF01) Each DLG3 transfer contains a Composite module, named FF01, which contains objects representing each surface in the transfer. Surface is a DLG term which is equivalent to the SDTS 2D manifold term. One DLG3 file (one theme for one partition) is equivalent to one surface. The composite objects for each surface contain pointers to the spatial object modules and header attributes which make up the surface. This module is used in addition to the Catalog/Spatial Domain module to determine which modules contain spatial objects of a particular surface. The added benefit to using a composite module to identify a surface is that attribute records can be pointed to by the composite records thereby attributing the whole surface.  a1Legal. Transfer Module Content The following tables describe the fields and subfields contained in modules in SDTS transfers created from DLG3 files. Modules are ordered alphabetically by module name. Attribute Primary modules for attributes of spatial objects and modules in the master data dictionary transfer are described in separate sections.     Sources Under the column heading "Source" the following terms are used: Profile the data are defined within SDTS as implemented by the Topological Vector Profile Generated there is a simple generation or counting involved which is normally done within a computer program External data was obtained from sources other than the DLG3 file (includes USGS Publications, DLG3 Product Specifications, Internal Databases, etc...) DLG3 implies that the data was extracted from a DLG3 file  a2Legal AHDR (Attribute Primary) The AHDR Attribute Primary module is used to transfer information from the header of a particular DLG3 file which does not have a standard location within the SDTS. There will be one record for each DLG3 in the transfer. ^ BR Z BR Z ^ @P@ P@P@ PAttribute Primary Header r (AHDR) Contents SourceB RBRB RBRFieldSubfield@P@P@P@PPrimaryModule Name"AHDR"Profile, external@ P@ P@ P@ PFieldRecord IDAs defined by order in this moduleGenerated@ P@ P@ P@ PBANNERText which often identifies the software which produced the DLGDLG3 File ID & Description Records@ P@ P@ P@ PPrimary SOURCE_DATEDate of original source materialDLG3 File ID & Description Records@ P@ P@ P@ PAttributesDATE_QUALIFIERDate qualifierDLG3 File ID & Description Records@ P@ P@ P@ PFieldQUAD_NUMBER *Arbitrary quad numberDLG3 File ID & Description Records@ P@ P@ P@ PL_PRIM_INTERVAL *Largest primary contour intervalDLG3 File ID & Description Records@ P@ P@ P@ PL_PB_INTERVAL *Largest primary bathymetric contour intervalDLG3 File ID & Description Records@ P@ P@ P@ PS_PRIM_INTERVAL *Smallest primary contour intervalDLG3 File ID & Description Records@ P@ P@ P@ PS_PB_INTERVAL *Smallest primary bathymetric contour intervalDLG3 File ID & Description Records@ P@ P@ P@ PCODED_FLAG *Coded flag DLG3 File ID & Description Records@ P@ P@ P@ PEDGEWS *Status Flag for West EdgeDLG3 File ID & Description Records@ P@ P@ P@ PEDGEWR *Reason for West Edge Status FlagDLG3 File ID & Description Records@ P@ P@ P@ PEDGENS *Status Flag for North EdgeDLG3 File ID & Description Records@ P@ P@ P@ PEDGENR *Reason for North Status FlagDLG3 File ID & Description Records@ P@ P@ P@ PEDGEES *Status Flag for East EdgeDLG3 File ID & Description Records@ P@ P@ P@ PEDGEER *Reason for East Status FlagDLG3 File ID & Description Records@ P@ P@ P@ PEDGESS *Status Flag for South Edge DLG3 File ID & Description Records@ P@ P@ P@ PEDGESR *Reason for South Status FlagDLG3 File ID & Description Records@ P@ P@ P@ PVERTICAL_DATUM *Datum used for elevation attribute values: "NGVD" National Geodetic Vertical Datum of 1929 "NAVD" North American Vertical Datum of 1988 "LOCAL MEAN SEA LEVEL"DLG3 File ID & Description Records@ P@ P@ P@ PSW_LATITUDE *Latitude of SW registration pointDLG3 ControlPoint Identification Record@ P@ P@ P@ PSW_LONGITUDE *Longitude of SW registration pointDLG3 ControlPoint Identification Record@ P@ P@ P@ PNW_LATITUDE *Latitude of NW registration pointDLG3 ControlPoint Identification Record@ P@ P@ P@ PNW_LONGITUDE *Longitude of NW registration pointDLG3 ControlPoint Identification Record@ P@ P@ P@ PNE_LATITUDE *Latitude of NE registration pointDLG3 ControlPoint Identification Record@ P@ P@ P@ PNE_LONGITUDE *Longitude of NE registration pointDLG3 ControlPoint Identification Record@ P@ P@ P@ PSE_LATITUDE *Latitude of SE registration pointDLG3 ControlPoint Identification RecordB R B RB R B RSE_LONGITUDE *Longitude of SE registration pointDLG3 ControlPoint Identification Record #Z PQP#* All indicated subfields are not included in the AHDR module for 1:2,000,000scale DLG3's#Xo PQXP#  a2Legal CATD (Catalog / Directory)  The Catalog/Directory module contains a directory of all modulesbelonging to a single SDTS transfer. It identifyies the file in which each module is contained.   T ddx5 x ddx5 x T *@@ P*@@ PCatalog/Directory (CATD)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"CATD"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGeneratedI@@ PI@@ PNameName of module referencedProfile @@ P @@ PTypePrimary field name from module referencedProfileI@@ PI@@ PFileFile of the module referencedDLG3, profile @@ P @@ PExternalModule is external to the transfer "Y/N"ExternalBB RBB RModule VersionVersion of the module referenced by, or included in the transfer (used to indicate the version of the master data dictionary)External  a2Legal CATS (Catalog / Spatial Domain)  The Catalog/Spatial Domain module is used to specify the aggregate object, map, or theme to which a module applies.  T ddx`  ddx`  T *@@ P*@@ PCatalog/Spatial Domain (CATS)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"CATS"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGeneratedI@@ PI@@ PNameName of module referencedProfile @@ P @@ PType Primary field name of module referencedProfileI@@ PI@@ PMapName of digital cartographic unit DLG3I@@ PI@@ PThemeCategory nameDLG3@@ P@@ PAggregate Object Arbitrary identifier which uniquely identifies a particular aggregate object (2D manifold); the * wildcard is used for a module which applies to all 2D manifolds; a null value is used if there is only one 2D manifold in a transferGenerated:BB R:BB RAggregate Object Type"GT" indicating that the object is a 2D manifoldProfile  a2Legal CATX (Catalog / CrossReference)  The Catalog/CrossReference module is used to describe relationships between modules.  T ddx`  ddx`  T *@@ P*@@ PCatalog/CrossReference (CATX)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"CATX"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGeneratedI@@ PI@@ PName 1Name of module referencedProfile, DLG3 @@ P @@ PType 1 Primary field name of module referenced by Name 1ProfileI@@ PI@@ PName 2Name of module referencedProfile, DLG3 @@ P @@ PType 2Primary field name of module referenced by Name 2Profile:BB R:BB RComment Text stating the meaning of the crossreferenceExternal For DLG3, Cat/Xref records are included to denote a relationship between "NP" points and the DQ Linage report, and the ATPR module and the Null Scheme used as described in the Logical Consistency Module  a2Legal DDSH (Data Dictionary / Schema)  The Data Dictionary / Schema Module describes structure of the Attribute Primary and Secondary modules.  T ddx`  ddx`  T *@@ P*@@ PData Dictionary / Schema (DDSH)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"DDSH"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGenerated @@ P @@ PNameName of module with data to which the schema appliesProfile@@ P@@ PType"ATPR" for Attribute Primary modules & ATSC for Attribute Secondary modules (type of module with data to which the schema applies)ProfileI@@ PI@@ PAttribute LabelName of attribute labelExternalI@@ PI@@ PAttribute Authority"USGS/NMD"ExternalI@@ PI@@ PFormatFormat of the attribute subfieldExternal @@ P @@ PUnitMeasurement unit for attribute subfieldExternal @@ P @@ PMaximum Subfield LengthMaximum length of the subfield (maximum number of characters)ExternalBB RBB RKeyNOKEY, PKEY, FKEY, PFKEY (indicates whether attribute is part of primary or foreign relational key)External  a2Legal DQAA (Data Quality/Attribute Accuracy) The Data Quality/Attribute Accuracy module contains the data quality report in narrative form. T ddx`  ddx`  T *@@ P*@@ PData Quality/Attribute Accuracy (DQAA)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"DQAA"Profile @@ P @@ PRecord ID 1" (only one DQAA record in our application)Generated:BB R:BB RCommentNarrative describing the data quality information External  a2Legal DQCG (Data Quality/Completeness) The Data Quality/Completeness module contains the data quality report in narrative form. T ddx`  ddx`  T @@ P@@ PData Quality/ Completeness (DQCG)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"DQCG"Profile @@ P @@ PRecord ID 1" (only one DQCG record in our application)Generated:BB R:BB RCommentNarrative describing the data quality information External  a2Legal DQHL (Data Quality/Lineage) The Data Quality/Lineage module contains the data quality report in narrative form.  T ddx`  ddx`  T *@@ P*@@ PData Quality/Lineage (DQHL)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"DQHL"Profile @@ P @@ PRecord ID 1" (only one DQHL record in our application)Generated:BB R:BB RCommentNarrative describing the data quality information External  a2Legal DQLC (Data Quality/Logical Consistency) The Data Quality/Logical Consistency module contains the data quality report in narrative form.  T ddx`  ddx`  T @@ P@@ PData Quality/Logical Consistency (DQLC)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"DQLC"Profile @@ P @@ PRecord ID 1" (only one DQLC record in our application)Generated:BB R:BB RCommentNarrative describing the data quality information External  a2Legal DQPA (Data Quality/Positional Accuracy) The Data Quality/Positional Accuracy module contains the data quality report in narrative form.  T ddx`  ddx`  T @@ P@@ PData Quality/Positional Accuracy (DQPA)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"DQPA"Profile @@ P @@ PRecord ID 1" (only one DQPA record in our application)Generated:BB R:BB RCommentNarrative describing the data quality information External a2Legal FF01 (Composite) The FF01 Composite module is used in DLG3 transfers to transfer composite objects for each surface in a transfer. Surface is a DLG term which is equivalent to a 2D manifold. One DLG3 file is one surface. This module allows modules and records which make up each surface to be easily identified. The Attribute ID field points to a record in the AHDR Attribute Primary module which contains surfacespecific header information which does not have a standard location within the SDTS. The Foreign ID field points to the spatial objects which compose this surface.    ^ dd$ <\  dd$ <\  ^ @P@ P@P@ PF Composite (FF01)ContentSourceHP@PHP@PFieldSubfield!@ P@ P!@ P@ PPrimaryModule Name"FF01"Profile@ P@ P@ P@ PFieldRecord ID Defined by order in this moduleGeneratedA P@ PA P@ PObject Representation"FF"Profile@ P@ P@ P@ P^Attribute ID  Foreign IDModule Name"AHDR"Profile, ExternalD@ P@ PD@ P@ PFieldRecord IDRecord number of record in AHDR module which contains header attributes which apply to this surfaceGenerated@ P@ P@ P@ P ^Foreign IDModule NameName of spatial object module which is part of this surfaceProfile, External5B RB R5B RB RField  (repeating)Record IDRecords in module which are components of this surface. A negative record count is used to indicate that all records in the module are components.Generated  a2Legal IDEN (Identification)  The Identification module contains global information which serves to identify the transfer.  ^ dd$   dd$   ^ @P@ P@P@ PIdentification (IDEN)ContentSourceHP@PHP@PFieldSubfield!@ P@ P!@ P@ PPrimaryModule Name"IDEN"Profile@ P@ P@ P@ PFieldRecord ID "1" (only one IDEN record in our application)External@ P@ P@ P@ PStandard ID"SPATIAL DATA TRANSFER STANDARD"Profile@ P@ P@ P@ PStandard Version"1994 June 10"Profile@ P@ P@ P@ PStandard Documentation Reference"FIPS PUB 1731"Profile@ P@ P@ P@ PProfile Identification"SDTS TOPOLOGICAL VECTOR PROFILE"Profile@ P@ P@ P@ PProfile Version"VERSION 1 JUNE 10, 1994"Profile@ P@ P@ P@ PProfile Documentation Reference"FIPS 1731 PART 4"Profile@ P@ P@ P@ PTitleName of digital cartographic unit (Ex: Lake Of the Ozarks, MO/transportation)DLG3 File ID & Description Records (concatenation of name of digital cartographic unit and category name)@ P@ P@ P@ PData Structure"DLG3"Deduced from the data source@ P@ P@ P@ PMap DateDate of original source material or revision date, whichever is laterDLG3 File ID & Description Records@ P@ P@ P@ PData Set Creation DateDate from computer system's clock referring to SDTS TransferGenerated@ P@ P@ P@ PScaleScale of the source analog map used to create the DLGDLG3 File ID & Description Records@ P@ P@ P@ PComt This transfer requires an external data dictionary from the U.S. Geological Survey, NAtional Mapping Division, with a four character code of DLG3, Version Number_______ 1.01(100K), 2.00(1:2M), 3.00(24K) Profile, Annex A@ P@ P@ P@ PConformanceComposites"Y"Profile@ P@ P@ P@ PVector Geometry"Y"for 1:24,000 & 1:100,000scale DLG3's Nfor 1:2,000,000scale DLG3'sProfile@ P@ P@ P@ PVector Topology"Y"Profile)@ P@ P)@ P@ PRaster"N"Profile@ P@ P@ P@ PExternal Spatial Reference"1"ProfileYB RB RYB RB RFeatures Level"4"Profile  a2Legal IREF (Internal Spatial Reference)  The Internal Spatial Reference module is used to describe the internal spatial reference system and its relationship to the external spatial reference system.  ^ ddxh\  ddxh\  ^ *@@@ P*@@@ PInternal Spatial Reference (IREF)ContentsSourceI@ @@PI@ @@PFieldSubfieldi@ @@ Pi@ @@ PPrimaryModule Name"IREF" ProfileI@ @@ PI@ @@ PFieldRecord IDDefined by order in this moduleGeneratedI@ @@ PI@ @@ PSpatial Address Type"2TUPLE"Profile, DLG3@ @@ P@ @@ PSpatial Address X Component Label"EASTING" ```for 1:24,000 & 1:100,000scale DLG3's LONGITUDE ```for 1:2,000,000scale DLG3'sProfile, DLG3@ @@ P@ @@ PSpatial Address Y Component Label"NORTHING" ```for 1:24,000 & 1:100,000scale DLG3's LATITUDE ```for 1:2,000,000scale DLG3'sProfile, DLG3 @ @@ P @ @@ PHorizontal Component Format"BI32" (32bit signed binary integer)Profile @ @@ P@ @@ PScale Factor X0.01 ```for 1:24,000 & 1:100,000scale DLG3's 0.000001 ```for 1:2,000,000scale DLG3'sDLG3@ @@ P@ @@ PScale Factor Y0.01 ```for 1:24,000 & 1:100,000scale DLG3's 0.000001 ```for 1:2,000,000scale DLG3'sDLG3I@ @@ PI@ @@ PX Origin0.0DLG3I@ @@ PI@ @@ PY Origin0.0DLG3 @ @@ P @ @@ PX Component of Horizontal ResolutionResolutionDLG3 File Identification Record:B BB R:B BB R@Y Component of Horizontal ResolutionResolutionDLG3 File Identification Record  a2Legal Lenn (Line)  The Line module is used to transfer complete chains for a particular 2D manifold.  ^ ddxP  ddxP  ^ +@@@ P+@@@ PH Line (LEnn)ContentsSourceJ@ @@PJ@ @@PFieldSubfield+@ @@ P+@ @@ PPrimaryModule NameModule name beginning with "LE"Profile, generated @ @@ P @ @@ PFieldRecord IDDLG3 Element internal ID numberDLG3 Line ID record element ID@ @@ P@ @@ PObject Representation Code"LE"Profile@ @@ P@ @@ P^Attribute ID Foreign IDModule NameModule name of the Attribute Primary record referencedExternal @ @@ P @ @@ PFieldsRecord IDID of the Attribute Primary module record referencedGenerated sequentially as DLG3 is processed @ @@ P @ @@ P^Polygon ID Left Foreign IDModule NameName of the Polygon Module referencedProfile, generated@ @@ P@ @@ PFieldRecord IDDLG3 Element ID of the area at the left of the lineDLG3 Line ID record, left area internal element ID @ @@ P @ @@ P^Polygon ID Right Foreign IDModule NameName of the Polygon Module referencedProfile, generated@ @@ P@ @@ PFieldRecord IDDLG3 Element ID of the area at the right of the lineDLG3 Line ID record, right area internal element ID @ @@ P @ @@ P^Start Node ID Foreign IDModule NameName of planar node module referencedProfile, generated@ @@ P@ @@ PFieldRecord IDDLG3 Element ID of the node at the start of the lineDLG3 Line ID record, start node internal element ID @ @@ P @ @@ P^End Node ID Foreign IDModule NameName of planar node module referencedProfile, generatedA AA QA AA QFieldRecord IDElement ID of the node at the end of the lineDLG3 Line ID record, end node internal element ID@ @@ P@ @@ PܩSpatial AddressX componentThe value of each of the coordinates for the DLG3 lineDLG3 line coordinate string recordsB BB RB BB RFields (Repeating)Y componentThe value of each of the coordinates for the DLG3 lineDLG3 line coordinate string records a2Legal Nann (PointNode for Area Points)  The NA PointNode module transfers area points for a particular 2D manifold.  ^ ddx4  ddx4  ^ *@@@ P*@@@ PPointNode (Area Points) . (NAnn)ContentsSourceI@ @@PI@ @@PFieldSubfield*@ @@ P*@ @@ PPrimaryModule Name Module name beginning with "NA"Profile, GeneratedI@ @@ PI@ @@ PFieldRecord IDDLG3 Element internal ID numberDLG3 @ @@ P @ @@ PObject Representation"NA"Profile @ @@ P @ @@ PܩSpatial Address FieldX ComponentThe coordinate value of the representative point for the areaDLG3 Area Identification Record @ @@ P @ @@ PY ComponentThe coordinate value of the representative point for the areaDLG3 Area Identification Record @ @@ P @ @@ P^Area ID Foreign IDModule NameName of the polygon module referencedProfile:B BB R:B BB RFieldRecord IDDLG3 internal element ID of the areaDLG3 Area Identification Record  a2Legal NEnn (PointNode for Entity Points)  The NE PointNode module transfers entity points for a particular 2D manifold. ^ ddx < ddx < ^ *@@@ P*@@@ P PointNode (Entity Points) (NEnn)ContentsSourceI@ @@PI@ @@PFieldSubfield*@ @@ P*@ @@ PPrimaryModule Name Module name beginning with "NE"Profile, generated @ @@ P @ @@ PFieldRecord IDDLG3 element internal ID numberDLG3 Line ID Record @ @@ P @ @@ PObject Representation"NE"Profile@ @@ P@ @@ PܩSpatial Address FieldX ComponentThe value of the first coordinate pair listed with a DLG3 degenerate lineDLG3 Coordinate String records@ @@ P@ @@ PY ComponentThe value of the first coordinate pair listed with a DLG3 degenerate lineDLG3 Coordinate String records @ @@ P @ @@ P^Attribute ID Foreign ID FieldModule Name Name of the Attribute Primary Module referencedExternal@ @@ P@ @@ PRecord IDRepresents Record ID of Attribute Primary record referencedGenerated @ @@ P @ @@ P^Area ID Foreign IDModule NameModule name of the polygon module referencedProfileB BB RB BB RRecord IDDLG3 Internal Element ID of either the left or right area of a degenerate lineDLG3 Line ID Record  a2Legal NOnn (PointNode for Planar Nodes)  The NO PointNode module transfers planar nodes for a particular 2D manifold. ^ ddx4x  ddx4x  ^ *@@@ P*@@@ PPointNode (Planar Nodes) * (NOnn)ContentsSourceI@ @@PI@ @@PFieldSubfieldi@ @@ Pi@ @@ PPrimaryModule NameModule name beginning with "NO"Profile, generated @ @@ P @ @@ PFieldRecord IDDLG3 Element internal ID numberDLG3 Node Identification Record @ @@ P @ @@ PObject Representation"NO"DLG3, profile @ @@ P @ @@ PܩSpatial Address FieldX Component The value of the spatial address of the nodeDLG3 Node Identification Record @ @@ P @ @@ PY Component The value of the spatial address of the nodeDLG3 Node Identification Record@ AA Q@ AA Q^Attribute ID Module Name Name of the Attribute Primary module referencedExternal*BBBR*BBBRForeign ID FieldRecord IDRepresents Record ID of Attribute Primary record referencedGenerated sequentially as DLG3 is processed  a2Legal Npnn (PointNode)  This module contains point spatial objects which are used to transfer the four registration points contained in DLG3 files (typically corresponding to quadrangle corners.) This module is not included for 1:2,000,000scale DLG3's.  ^ ddx  ddx  ^ *@@@ P*@@@ P PointNode (NPnn)ContentsSourceI@ @@PI@ @@PFieldSubfield*@ @@ P*@ @@ PPrimaryModule Name Module name beginning with "NP"Profile, generatedM@ @@ PM@ @@ PFieldRecord IDwhere controlpoint label =SW then "1" NW then "2" NE then "3" SE then "4"Value determined from controlpoint label from the DLG3 ControlPoint Identification Record@ @@ P@ @@ PObject Representation"NP" DLG3, profile@ @@ P@ @@ PܩSpatial Address FieldX Component The easting value of the "SW", "NW", "NE", or "SE" DLG3 control point addressesDLG3 Control Point Identification RecordB BB RB BB RY Component The northing value of the "SW", "NW", "NE", or "SE" DLG3 control point spatial addressesDLG3 Control Point Identification Record  a2Legal Pcnn (Polygon)  The Polygon module is used to transfer GTpolygons, universe polygons, and void polygons for a particular 2D manifold.  ^ ddxHHP  ddxHHP  ^ *@@@ P*@@@ P Polygon  (PCnn)ContentsSourceI@ @@PI@ @@PFieldSubfield*@ @@ P*@ @@ PPrimaryModule Name Module name beginning with "PC"Profile, generated@ @@ P@ @@ PFieldRecord IDDLG3 Element internal ID numberDLG3 Area Identification Record element ID@ @@ P@ @@ PObject Representation Code"PC" (GTpolygon), "PW" (universe polygon), or "PX" (void polygon); choice made according to attributionDLG3, profile @ @@ P @ @@ P^Attribute ID Foreign IDModule Name Name Attribute Primary Module referencedProfile:B BB R:B BB RFieldRecord IDRecord ID of Attribute Primary record referencedGenerated sequentially as DLG3 is processed # P QP# a2Legal SPDM (Spatial Domain) #Xo P QXP# The Spatial domain module specifies a geographic areal domain within which the spatial addresses of the transfer are contained. ^ ddxHHP  ddxHHP  ^ *@@@ P*@@@ P#Z P QP#Spatial Domain (SPDM)ContentsSourceI@ @@PI@ @@PFieldSubfield*@ @@ P*@ @@ PPrimaryModule Name  SPDMProfile@ @@ P@ @@ PFieldRecord ID 1",,,(only one record in this application) Generated @ @@ P @ @@ PSpatial Domain Type MINMAXProfile, External @ @@ P @ @@ PDomain Spatial Address Type INTERNALProfile, External@ @@ P@ @@ PDomain Spatial AddressX componentMinimum X value of the spatial domainDLG3 ControlPoint Identification Record Southwest corner@ @@ P@ @@ PMIN valueY componentMinimum Y value of the spatial domainDLG3 ControlPoint Identification Record Southwest corner@ @@ P@ @@ PDomain Spatial AddressX componentMaximum X value of the spatial domainDLG3 ControlPoint Identification Record Northeast cornerB BB RB BB RMAX valueY conponentMaximum Y value of the spatial domainDLG3 ControlPoint Identification Record Northeast corner#Xo P QXP# a2Legal STAT (Transfer Statistics) The Transfer Statistics module contains statistical information about the modules in a transfer. There is one record for each module in a transfer.  T ddx` ` ddx` ` T i@@ Pi@@ PTransfer Statistics (STAT)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"STAT"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGenerated @@ P @@ PModule Type ReferredPrimary field name of module referencedProfile I@@ PI@@ PModule Name ReferredName of module referencedProfile @@ P @@ PModule Record CountTotal number of records in module referencedGenerated:BB R:BB RSpatial Address CountTotal number of spatial address fields in module referencedGenerated a2Legal XREF (External Spatial Reference) The External Spatial Reference module describes the external spatial reference system.  T ddx ( ( ddx ( ( T *@@ P*@@ PExternal Spatial Reference (XREF)ContentsSource9@@P9@@PPrimary Field*@@ P*@@ PModule Name "XREF"Profile @@ P @@ PRecord ID  1"```(only one record in this application)Generated@@ P@@ PReference System Name "UTM"```for 1:24,000 & 1:100,000scale DLG's GEO```for 1:2,000,000scale DLGsProfile, DLG3M@@ PM@@ PHorizontal Datum "NAS" North American 1927 "NAX" North American 1983 "Puerto Rico" "Old Hawaiian" "Local (Astro)"DLG3 File ID & Description RecordsBB RBB RZone Number (This field not included for 1:2,000,000scale DLG3s)UTM ZoneDLG3 File & Description Records  a1Legal. Master Data Dictionary Transfer Modules The Data Dictionary/Definition and Data Dictionary/Domain modules are transferred separately in a master data dictionary which conforms to the requirements of Annex A of the TVP. Each master data dictionary contains a version number, indicated in the Identification module and the Catalog / Directory module. Transfers which reference this master data dictionary must also include the version number in these modules. The version number should be checked to verify that the master data dictionary is the correct version for the DLG3 transfer. New versions of the data dictionary may be created to correct errors, add entities, add attributes, and modify definitions. The data dictionary is designed to include DLG3 entities and attribute which are not collected currently but may exist in older DLG3; therefore, it is unlikely that entities and attributes will be deleted from new versions of the data dictionary. In addition to the Data Dictionary/Definition and Data Dictionary/Domain modules, the master data dictionary transfer includes Identification, Catalog/Directory, Data Quality/Completeness, and Data Quality/Lineage modules. a2Legal MDEF (Data Dictionary / Definition) This module contains the definitions and authorities for entities and attributes.  T ddx` ` ddx` ` T *@@ P*@@ PData Dictionary / Definition (MDEF)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"MDEF"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGenerated @@ P @@ PEntity or Attribute"ENT" entity "ATT" attributeProfileI@@ PI@@ PEntity/Attribute LabelName of attribute or entity labelExternal @@ P @@ PSourceSource of the definition (not used for most definitions in DLG3)ExternalI@@ PI@@ PDefinitionTextExternalI@@ PI@@ PAttribute Authority"USGS/NMD"External:BB R:BB RAttribute Authority Description"United States Geological Survey, National Mapping Division"External  a2Legal MDIR (Catalog / Directory)  The Catalog/Directory module contains a directory of modules, identifying the file in which each module is contained.   T ddx5[ ddx5[ T *@@ P*@@ PCatalog/Directory (MDIR)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"MDIR"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGeneratedI@@ PI@@ PNameName of module referencedProfileI@@ PI@@ PTypePrimary field name from module referencedProfileI@@ PI@@ PFileFile name of the module referencedDLG3, profileI@@ PI@@ PExternalModule is not external to the transfer ("N")External:BB R:BB RModule VersionVersion of the module included in the transfer (used to indicate the version of the master data dictionary)External  a2Legal MDOM (Data Dictionary / Domain)  This module describes the domain of values for attributes.  T ddx`  ddx`  T *@@ P*@@ PData Dictionary / Domain (MDOM)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"MDOM"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGeneratedI@@ PI@@ PAttribute LabelName of attribute label External @@ P @@ PAttribute Authority"USGS/NMD" "FIPS"External@@ P@@ PAttribute Domain Type"ALPHANUM" "ENUMERATED" "FIPSCODE" "GR_CHARS" "INTEGER" "REAL"External@@ P@@ PAttribute Domain Value Format"A" "I" "R"External @@ P @@ PAttribute Domain Value Measurement UnitMeasurement unit of attribute value, if applicableExternalM@@ PM@@ PRange or ValueDescribes the use of the value in Domain Value: "MIN" value is minimum of range "MAX" value is maximum of range "VALUE" enumerated valueExternalI@@ PI@@ PDomain ValueValid value for this attributeExternal:BB R:BB RDomain Value DefinitionDefinition of value in Domain Value subfieldExternal  a2Legal MIDE (Identification)  The Identification module contains global information which serves to identify the master data dictionary transfer. Note that the Data ID subfield contains the version number.  ^ dd$   dd$   ^ @P@ P@P@ PIdentification r (MIDE)ContentSourceHP@PHP@PFieldSubfield!@ P@ P!@ P@ PPrimaryModule Name"MIDE"Profile@ P@ P@ P@ PFieldRecord ID "1" (only one record in this application)Profile@ P@ P@ P@ PStandard ID"SPATIAL DATA TRANSFER STANDARD"Profile@ P@ P@ P@ PStandard Version"1992 AUGUST 28"Profile@ P@ P@ P@ PStandard Documentation Reference"FIPS PUB 173"Profile@ P@ P@ P@ PProfile Identification"SDTS TOPOLOGICAL VECTOR PROFILE"Profile@ P@ P@ P@ PProfile Version"13 JULY 1993"Profile@ P@ P@ P@ PProfile Documentation Reference"FIPS 173 PART 4"Profile@ P@ P@ P@ PTitle"MASTER DATA DICTIONARY FOR UNITED STATES GEOLOGICAL SURVEY (USGS) DIGITAL LINE GRAPH 3 (DLG-3) DATADLG3 File ID & Description Records@ P@ P@ P@ PData IDVersion number of this master data dictionaryExternal@ P@ P@ P@ PData StructureMASTER DATA DICTIONARYDeduced from the data source@ P@ P@ P@ PData Set Creation DateDate from computer system's clockGeneratedD@ P@ PD@ P@ PComment"This transfer is intended to be used in conjunction with a USGS DLG-3 spatial data transfer to form a conforming SDTS transfer."Profile, generated@ P@ P@ P@ PConformanceComposites"N"Profile@ P@ P@ P@ PVector Geometry"N"Profile@ P@ P@ P@ PVector Topology"N"Profile@ P@ P@ P@ PRaster"N"Profile1B RB R1B RB RFeatures Level"4"Profile  a2Legal MQCG (Data Quality/Completeness) The Data Quality/Completeness module contains the data quality report in narrative form. T ddx`  ddx`  T @@ P@@ PData Quality/ Completeness (MQCG)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"MQCG"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGenerated:BB R:BB RCommentNarrative describing the data quality information External  a2Legal MQHL (Data Quality/Lineage) The Data Quality/Lineage module contains the data quality report in narrative form.  T ddx`  ddx`  T *@@ P*@@ PData Quality/Lineage (MQHL)ContentsSource9@@P9@@PPrimary Fieldi@@ Pi@@ PModule Name"MQHL"ProfileI@@ PI@@ PRecord IDDefined by order in this moduleGenerated:BB R:BB RCommentNarrative describing the data quality information External  a1Legal. Attribute Modules   a2Legal Introduction  The SDTS model of spatial phenomena describes the real world as consisting of entities which are characterized by attributes which have attribute values. DLG3 does not explicitly use this entityattributeattribute value model. Instead it assigns any number of "attribute codes" to spatial objects. Looking more closely at these DLG3 attribute codes, it can be seen that there are codes which identify real world entities and codes which represent attributes of those entities. The SDTS implementation of DLG3 identifies which DLG3 attribute codes identify entities and which identify attributes of those entities. There are two ways in the SDTS of identifying the entity type for a particular object in an SDTS transfer. One method is to create a separate Attribute Primary module for each entity type; in this method the entity type is assigned to a particular attribute and Attribute Primary module through the Data Dictionary/Schema module. The second method is specified in the TVP: a generic ENTITY_LABEL attribute is specified by the TVP, its value identifies the entity type. This method does not require separate Attribute Primary modules for each entity type. It is this second method which is used in DLG3 transfers. In most cases a DLG3 spatial object will have one code which identifies a real world entity. This DLG3 code is used as the value for the ENTITY_LABEL attribute in the SDTS transfer. The codes which identify entities are listed for each theme. Other DLG3 codes are converted to appropriate values for other attributes. These attributes may have true/false values, enumerated values, or quantitative values obtained from DLG3 codes. Attributes will vary with the DLG3 theme. # P QP#a2Legal Attribute Primary Modules#Xo PQXP# There will always be at least one Feature Attribute Primary module (transfers of transportation will include a separate Feature Attribute Primary module for each of the three transportation themes). The Feature Attribute Primary module contains the ENTITY_LABEL attribute which contains the 7digit DLG3 attribute code which identifies the real world entity. Additional attributes provide additional descriptive and parameter information about the entity. These additional attributes will differ with theme. The name of the Feature Attribute Primary module will vary with theme: AHPF Hypsography AHYF Hydrography ASCF Vegetative Surface CoverANVF Nonvegetative Features ABDF Boundaries ASMF Survey Control and Markers ARDF Roads and Trails ARRF Railroads AMTF Pipelines, Transmission Lines, and Miscellaneous Transportation Features AMSF Manmade Features APLF U.S. Public Land Survey System Each transfer may contain one Coincidence Attribute Primary module, named ACOI. This contains records indicating that a feature is coincident with a feature in another DLG3 theme. For example, roads are frequently coincident with boundaries and the Public Land Survey. This is separate table because there may be multiple values of the COINCIDENT attribute (coincident with multiple themes) for one spatial object. The TVP specifies that attributes which can have more than one value be separated into their own Attribute Primary module. A particular spatial object will have an attribute record for each value: a particular object may have no, one, or more attribute records to which it points. ACOI Coincidence for all themes Depending upon the theme there may be additional Attribute Primary modules to handle other attributes which can have multiple values for one entity instance: elevation on Hypsography, federal agency on Boundaries, and route numbers on Roads and Trails. ABDM Agencies for Boundaries ARDM Route Numbers for Roads & Trails AHPF Elevation in Feet for Hypsography AHPR Elevation in Meters for Hypsography # PQP# a2Legal Attribute Secondary Modules #Xo PQXP# Attribute Secondary modules are only included in transfers created from 1:2,000,000scale DLG3's. These DLGs store information in companion text files which serve as input to the conversion process. The information in these text files serve to further describe attribute major minor pairs contained in the DLG file. As mapped into SDTS, this additional information is placed in Attribute Secondary modules. Each record of these Attribute Secondary modules is linked to records in other attribute modules by relational key. Attribute module subfields that participate in these linkages are identified as a foreign or primary keys in the Data Dictionary / Schema module. When attribute records in two separate modules reference each other by relational key, the relationship between the modules is recorded by a Catalog / CrossReference module record. The attribute secondary modules included in transfers for 1:2,000,000scale DLG3's in SDTS carry information on federal land grant names, state and county names by FIPS codes, populated place names along with the respective Census population values, and airport names. The attribute secondary names are as follows: BFPC County Names by FIPS Code BFPS State Names by FIPS Code BMSP Populated Place Names with Populations BMTA Airport Names BGRL Land Grant Names # PQP#a2Legal Attribute Modules by Theme #Xo PQXP# The following table summarizes which Attribute modules are used for transfers of each theme. T dd$ |  dd$ | T @ @P@ @P n DLG3 r ThemePP"Z+Attribute Primary Modules ăB B RB B RModule NameModule Description4@@P4@@PHypsographyACOI * AHPF AHPR * AHPT *Coincidence Feature Elevation Feet Elevation Meters@ @ P@ @ PHydrographyACOI * AHYFCoincidence Feature@ @ P@ @ PVegetative Surface CoverACOI * ASCFCoincidence Feature@ @ P@ @ PNonvegetative FeaturesACOI * ANVFCoincidence Feature@ @ P@ @ PBoundariesACOI * ABDF ABDM BFPC ** BFPS **Coincidence Feature Agency County Names State Name@ @ P@ @ PSurvey Control and MarkersACOI * ABDFCoincidence Feature@ @ P@ @ PTransportationACOI * AMTF ARDF ARDM ARRF BMTA ** BFPS **Coincidence Feature Miscellaneous Transportation Feature Roads and Trails Route Roads and Trails Feature Railroads Airport Names State Name@ @ P@ @ PManmade FeaturesACOI * AMSF BMSP ** BFPC ** BFPS **Coincidence Feature Populated Place Names County Names State NameB B RB B RU.S. Public Land Survey SystemACOI * APLF BGRL ***Coincidence Feature Land Grant Names #Z PQP#* ` ` ` Indicated modules may be absent ** ` ` ` Indicated modules are only used for 1:2,000,000scale DLG3's *** ` ` ` Indicated modules may be absent and are only used for 1:2,000,000scale DLG3's # PQP# a2Legal Attribute Values #Xo PQXP# Descriptive and parameter DLG3 codes are converted to attributes which will vary from theme to theme. There are several general types of these attributes: Attributes which have a true/false value indicating whether an attribute (as indicated by the existence or nonexistence of a particular DLG3 code) is true or not. Example: PHOTOREVISEDhhh'Y' if DLG3 code for photorevised is present, indicating feature is photorevised. hhhSpace if not present, indicating not photorevised. Attributes which have values derived from DLG3 minor codes. For example: ELEVATION Value is obtained from a DLG3 minor code. Some attributes have values which are set based on multiple DLG3 codes. When possible, attributes similar to DLGE attributes were used. Example: RELATION_TO_GROUND'U' underground DLG3 code 0500601 'E' elevated DLG3 code 0500603 'T' tunnel DLG3 code 0500604 Attributes will have a "not applied" value defined in the Data Dictionary/Domain module and shown in the tables in this document. For character data, this value will be all space characters. For integer and real data, this value will be a negative value with all digits being 9 (the actual number will depend upon the length of the subfield.) Not applied means that the attribute has not been applied for any reason including not specified, unknown, and not applicable (since there is one Entity Attribute Primary module for each theme, it must contain attributes which are applicable to only some entities.) It is not possible to specify the exact reason an attribute is not applied in a DLG3 transfer. In some cases one DLG3 object has multiple DLG3 codes which can be considered entities. In frequently encountered cases, special attributes have been created for entities which are often combined with other DLG3 entities. For example, in the Boundaries theme, an area can be both a civil township and an incorporated city as well an additional feature (for example, a local park.) Therefore, townships and cities have their own separate attributes and are not used to set the value of the ENTITY_LABEL attribute. In infrequent cases where there is more than one value for the ENTITY_LABEL attribute, a separate Attribute Primary module record is created for each value. DLG3 attribute code 0000000 represents the "outside area" of the DLG3 coverage which corresponds to the SDTS universe polygon. Universe polygons do not have Attribute Primary module records. Most DLG3 themes have attribute codes which identify "void areas." These correspond to SDTS void polygons. These are areas with characteristics like the universe polygon, typically interior areas in which data were not collected. Void polygons do not reference Attribute Primary module records. DLG3 objects which do not have any attribution do not have Attribute Primary module records. a2Legal Feature Attribute Primary Modules There will be one Feature Attribute Primary module for each DLG3 theme in a transfer. The attributes in the module will vary with the DLG3 theme. The following tables show the structure of the Entity Attribute Primary module for each DLG3 theme. r ddx8 ddx8 r &@@@@@P@@@@@P&AHPF Feature Attribute Primary Module`(#?(Hypsography)&ZB B B B B RZB B B B B R&Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&I@ @ @ @ @ PI@ @ @ @ @ P&SUPPLEMENTARY0200202AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&AMENDED0200204AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&APPROXIMATE0200610AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&DEPRESSION0200611AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&GLACIER_OR_SNOW0200612AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&UNDERWATER0200613AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&BEST_ESTIMATE0200614AN/A1"Y" (applied) or blank&M@ @ @ @ @ PM@ @ @ @ @ P&SPOT_CATEGORY02600__AN/A2First 2 digits of DLG3 major code of coincident category; 2 blanks indicates not applied&yB B B B B RyB B B B B R&PHOTOREVISED0200000AN/A1"Y" (applied) or blankNotes: The following are the entities in the Hypsography theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code) Definition 0200200` ` ` Contour 0200201` ` ` Carrying contour 0200203* Continuation contour 0200205 Bathymetric contour 0200206*Depth curve 0200207 Watershed divide 0200208 Closure line 0200299 Processing line 0200300 Spot elevation, less than third order 0200301 Spot elevation, less than third order, not at ground level 7 spaces` ` ` No DLG3 entity but has other attributes *Not currently used but may exist in older DLG3's. The DLG3 codes for SUPPLEMENTARY and AMENDED can frequently appear in conjunction with other "entity" codes. Therefore they have separate attributes instead of being used to set the ENTITY_LABEL attribute value. r ddx(H ddx(H r &@@@@@P@@@@@P& AHYF Feature Attribute Primary Module`(#?(Hydrography) ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks& @ @ @ @ @ P @ @ @ @ @ P&PHOTOREVISED0500000AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&RELATION_TO_ GROUND0500601 0500603 0500604AN/A1"U" (underground) "E" (elevated) "T" (tunnel) " " (not applied)&@ @ @ @ @ P@ @ @ @ @ P&VERTICAL_ RELATION0500602 0500617AN/A1"O" (overpassing) "U" (under passing) " " (not applied)&@ @ @ @ @ P@ @ @ @ @ P&BANK0500605 0500606AN/A1"R" (right bank) "L" (left bank) " " (not applied)&@ @ @ @ @ P@ @ @ @ @ P&OPERATIONAL_ STATUS0500607 0500611AN/A1"U" (under construction) "A" (abandoned) " " (not applied)& @ @ @ @ @ P @ @ @ @ @ P&SALT0500608AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&UNSURVEYED0500609AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&INTERMITTENT0500610AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&SUBMERGED0500612AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&DRY0500614AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&MINERAL_OR_ HOT0500615AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&NAVIGABLE0500616AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&EARTHEN0500618AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&INTERPOLATED0500619AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&ELEVATION051____ 052____ 056____ 057____RMETERS8Reals to the nearest 0.01 meter; 9999.99 indicates not applied&@ @ @ @ @ P@ @ @ @ @ P&ROTATION_ ANGLE0530___*IDEGREES3Integers to the nearest degree; 99 indicates not applied&@ @ @ @ @ P@ @ @ @ @ P&RIVER_MILE055____RMILES6Reals to the nearest 0.1 mile; 999.9 indicates not applied&:B B B B B R:B B B B B R&BEST_ESTIMATE0580000AN/A1"Y" (applied) or blank Notes: The following are the entities in the Hydrography theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition 0500001Upper origin of stream 0500002Upper origin of stream at water body 0500003Sink, channel no longer evident 0500004Stream entering water body 0500005Stream exiting water body 0500100Alkali flat 0500101Reservoir 0500102Covered reservoir 0500103Glacier or permanent snow field 0500104Salt evaporator 0500105Inundation area 0500106Fish hatchery or farm 0500107Industrial water impoundment 0500108Area to be submerged 0500109Sewage disposal pond or settling basin 0500110Tailings pond or settling basin 0500111Marsh, wetland, swamp, or bog 0500112Mangrove area 0500113Rice field0500114Cranberry bog 0500115Flats (tidal, mud, sand, or gravel) 0500116Bays, estuaries, gulfs, oceans, or seas 0500117Shoal 0500118Soda evaporator 0500119Duck evaporator 0500121Obstruction area in water area 0500200Shoreline 0500201Manmade shoreline 0500202Closure line 0500203Indefinite shoreline 0500204Apparent limit 0500205Outline of a Carolina bay 0500206Danger curve 0500207Apparent shoreline 0500208Sounding datum 0500209Lowwater line 0500299Processing line 0500300Spring 0500301Nonflowing well 0500302Flowing well 0500303Riser 0500304Geyser 0500305Windmill 0500306Cistern 0500400Rapids 0500401Falls 0500402Gravel pit or quarry filled with water 0500403Gaging station 0500404Pumping station 0500405Water intake 0500406Dam or weir 0500407Canal lock or sluice gate 0500408Spillway 0500409Gate (flood, tidal, head, or check) 0500410Rock 0500411Crevasse 0500412Stream 0500413Braided stream 0500414Ditch or canal 0500415Aqueduct 0500416Flume 0500417Penstock 0500418Siphon 0500419Channel in water area 0500420Wash or ephemeral drain 0500421Lake or pond 0500422Coral reef 0500423Sand in open water 0500424Spoil area, dredge area, or dump area 0500425Fish ladders 0500426Holiday area 7 spaces` ` ` No DLG3 entity but has other attributes r ddx(` ddx(` r &@@@@@P@@@@@P& ASCF Feature Attribute Primary Module`(#6(Vegetative Surface Cover) ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&yB B B B B RyB B B B B R&BEST_ESTIMATE0780000AN/A1"Y" (applied) or blank Notes: The following are the entities in the Vegetative Surface Cover theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition 070 0101Woods or brushwood 070 0102Scrub 070 0103Orchard or plantation 070 0104Vineyard  070 0105Scattered trees 070 0200Closure line 070 0201*Edge of surface cover at builtup 070 0299Processing line 7 spaces` ` ` No DLG3 entity but has other attributes  * ` ` ` Not currently used but may exist in older DLG3's.  r ddx(` ddx(` r &@@@@@P@@@@@P& ANVF Feature Attribute Primary Module`(#7(NonVegetative Features) ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&I@ @ @ @ @ PI@ @ @ @ @ P&PHOTOREVISED0800000AN/A1"Y" (applied) or blank&yB B B B B RyB B B B B R&BEST_ESTIMATE0880000AN/A1"Y" (applied) or blank Notes: The following are the entities in the Nonvegetative Features theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition 080 0100Glacial moraine 080 0101Gravel beach 080 0102Sand area or beach 080 0103Shifting sand or dune area 080 0104Lava 080 0200Closure line080 0299*Processing line 080 0300*Located surface feature 7 spaces` ` ` No DLG3 entity but has other attributes  * ` ` ` Not currently used but may exist in older DLG3's.  r ddxt L ddxt L r &@@@@@P@@@@@P& ABDF Feature Attribute Primary Module`l(#@(Boundaries) ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&I@ @ @ @ @ PI@ @ @ @ @ P&CIVIL_TOWNSHIP0900100AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&CITY0900101AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&NATIONAL_FOREST0900104AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&WILDERNESS_AREA0900106AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&AHUPUAA0900135AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&HAWAIIAN_HOMESTEAD0900136AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&FEDERALLY_ ADMIN+0900401AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&IN_DISPUTE+0900601AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&STATE *09100__AN/A2State FIPS codes; all blanks indicates not applied&@ @ @ @ @ P@ @ @ @ @ P&COUNTY *0920___AN/A3County FIPS codes; all blanks indicates not applied&@ @ @ @ @ P@ @ @ @ @ P&TOWNSHIP_CODE09300__ 0940___AN/A5Civil township or equivalent FIPS codes; all blanks indicates not applied&I@ @ @ @ @ PI@ @ @ @ @ P&PHOTOREVISED0900000AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&MONUMENT_NUMBER095____ 096____AN/A6Letters or numbers; all blanks indicates not applied&yB B B B B RyB B B B B R&BEST_ESTIMATE0980000AN/A1"Y" (applied) or blank + These attributes are only used on 1:2,000,000scale DLGs and may be authorized for use in the future for 1:100,000scale DLGs. * These attributes are foreign keys into attribute secondary modules in transfers of 1:2,000,000scale DLG3's Notes:The DLG3 codes for CIVIL_TOWNSHIP, CITY, NATIONAL_FOREST, WILDERNESS_AREA, AHUPUAA, HAWAIIAN_HOMESTEAD, and FEDERALLY_ADMIN can frequently appear in conjunction with other "entity" codes. Therefore they have separate attributes instead of being used to set the ENTITY_LABEL attribute value. The following are the entities in the Boundaries theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition 090 0001Monumented point on a boundary 090 0002 Boundary turning point 090 0103National park 090 0105National wildlife refuge 090 0107Indian reservation 090 0108Military reservation 090 0109*Nonmilitary government reservation 090 0110Federal prison 090 0111Miscellaneous Federal reservation 090 0113* Land grant 090 0129Miscellaneous State reservation 090 0130State park 090 0131State wildlife refuge 090 0132State forest 090 0133State prison 090 0134County game preserve 090 0150Large park 090 0151Small park 090 0197Canada 090 0198Mexico 090 0199Open water 090 0200 Approximate boundary 090 0201Indefinite boundary 090 0202Disputed boundary 090 0203Historical line 090 0204Boundary closure line 090 0299Processing line 090 0301Reference monuments 7 spaces` ` ` No DLG3 entity but has other attributes  * ` ` ` Not currently used but may exist in older DLG3's.  r ddxh8 ddxh8 r &@@@@@P@@@@@P& ASMF Feature Attribute Primary Module ` (#> (Survey Control) ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &9@@@@@P9@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&I@ @ @ @ @ PI@ @ @ @ @ P&STATE15100__AN/A2State FIPS codes&I@ @ @ @ @ PI@ @ @ @ @ P&COUNTY1520___AN/A3County FIPS codes&}B B B B B R}B B B B B R&ELEVATION153____ 154____ 155____ 156____ 157____RMETERS 8Reals to the nearest 0.01 meter; 9999.99 indicates not applied Notes:  The following are the entities in the Survey Control and Markers theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition 1500200Closure Line 1500300Horizontal control station, permanent mark 1500301Horizontal and vertical control station 1500302Horizontal control station, vertical angle bench mark 1500303Horizontal control station, checked spot elevation 1500310Vertical control station, tablet 1500311Vertical control station, no tablet 1500320Boundary monument, tablet 1500321Boundary monument, no tablet 1500330Reference monument 1500331U.S. mineral or location monument 1500332Other control point 7 spaces` ` ` No DLG3 entity but has other attributes  * ` ` ` Not currently used but may exist in older DLG3's.  r ddx( h0D ddx( h0D r &@@@@@P@@@@@P& ARDF Feature Attribute Primary Module`(#<(Roads and Trails) ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&I@ @ @ @ @ PI@ @ @ @ @ P&ARBITRARY_EXT1700216AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&RELATION_TO_GROUND1700601 1700606 1700612 1700614 1700618AN/A1"T" (tunnel) "S" (submerged) "D" (doubledecked) "E" (elevated) "R" (on drawbridge) " " (not applied)&@ @ @ @ @ P@ @ @ @ @ P&VERTICAL_RELATION1700602 1700607AN/A1"O" (overpassing) "U" (under passing) " " (not applied)&Q@ @ @ @ @ PQ@ @ @ @ @ P&OPERATIONAL_STATUS1700603 1700604 1700611AN/A1"U" (under construction, classification known) "X" (under construction, classification unknown) "P" (proposed) " " (not applied)&@ @ @ @ @ P@ @ @ @ @ P&ACCESS_RESTRICTION1700609 1700610AN/A1"T" (toll road) "P" (private) " " (not applied)&I@ @ @ @ @ PI@ @ @ @ @ P&OLD_RAILROAD_GRADE1700605AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&WITH_RAILROAD1700623AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&COVERED1700624AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&HISTORICAL1700600*AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&LIMITED_ACCESS1700608*AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&PHOTOREVISED1700000AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&LANES171____ILANES2"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&ROAD_WIDTH1700650 1700659IFEET3Rounded to nearest multiple of 10; 99 indicates not applied&yB B B B B RyB B B B B R&BEST_ESTIMATE1780000AN/A1"Y" (applied) or blank Notes:Č The following are the entities in the Roads and Trails theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition 1700001Bridge abutment 1700002Tunnel portal 1700004Gate 1700005Culdesac 1700006Dead end 1700007Drawbridge 1700201Class 1, undivided 1700202Class 1, divided by centerline 1700203Class 1, divided, lanes separated 1700204Class 1, one way 1700205Class 2, undivided 1700206Class 2, divided by centerline 1700207Class 2, divided, lanes separated 1700208Class 2, one way 1700209Class 3 1700210Class 4 1700211Trail, other than 4WD 1700212Trail, 4WD 1700213Footbridge 1700214Road ferry crossing 1700215Perimeter of parking area 1700217Class 3, divided by centerline 1700218Class 3, divided, lanes separated 1700219Class 4, one way 1700220Closure line 1700221Class 3, one way 1700222Road in transition 1700299Processing line 1700401Traffic circle 1700402Cloverleaf or interchange 1700403Tollgate 1700404Weight station 1700405Nonstandard section of road 1700406*Covered bridge 1700613In service facility, rest area 7 spaces` ` ` No DLG3 entity but has other attributes * ` ` ` Not currently used but may exist in older DLG3's.  r ddx|hL ddx|hL r &@@@@@P@@@@@P& ARRF Feature Attribute Primary Module`(#B(Railroads) ă&B B B B B RB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&@ @ @ @ @ P@ @ @ @ @ P&RELATION_TO_ GROUND1800601 1800609 1800611AN/A1"T" (tunnel) "E" (elevated) "R" (drawbridge) " " (not applied)&@ @ @ @ @ P@ @ @ @ @ P&VERTICAL_ RELATION1800602 1800605AN/A1"O" (overpassing) "U" (under passing) " " (not applied)&M@ @ @ @ @ PM@ @ @ @ @ P&OPERATIONAL_ STATUS1800603 1800604 1800608AN/A1"A" (abandoned) "D" (dismantled) "U" (under construction) " " (not applied)&@ @ @ @ @ P@ @ @ @ @ P&ACCESS_ RESTRICTIONS1800612 1800613AN/A1"P" (private) "G" (U.S. government) " " (not applied)&I@ @ @ @ @ PI@ @ @ @ @ P&NARROW_GAUGE1800606AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&IN_SNOWSHED1800607AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&RAPID_TRANSIT1800610AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&JUXTAPOSITION1800614AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&ARBITRARY_ EXTENSION1800210AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&HISTORICAL1800600*AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&PHOTOREVISED1800000AN/A1"Y" (applied) or blank& @ @ @ @ @ P @ @ @ @ @ P&TRACKS181____ITRACKS2Decimal digits; 9 indicates not applied&@ @ @ @ @ P@ @ @ @ @ P&ROTATION_ANGLE183____*IDEGREES3Whole degrees in range 0 to 359; 99 indicates not applied&yB B B B B RyB B B B B R&BEST_ESTIMATE1880000AN/A1"Y" (applied) or blank Notes:  The following are the entities in the Railroads theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition  1800001Bridge abutment 1800002Tunnel portal 1800003Crossover 1800007Drawbridge 1800201Railroad 1800202Railroad in street or road 1800204Carline 1800205Cog railroad, incline railway, logging tram 1800207Railroad ferry crossing 1800208Railroad siding or spur 1800209Perimeter or limit of yard 1800211Closure line 1800299Processing line 1800400Railroad station, perimeter of station 1800401Turntable 1800402Roundhouse 7 spaces` ` ` No DLG3 entity but has other attributes  * ` ` ` Not currently used but may exist in older DLG3's.  r ddx( hhD8 ddx( hhD8 r &@@@@@P@@@@@P& AMTF Feature Attribute Primary Module`D(#B(Pipelines) ă&aB B B B B RaB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks &@ @ @ @ @ P@ @ @ @ @ P&RELATION_TO_GROUND1900600 1900603 1900606AN/A1"U" (underground) "A" (above ground) "S" (submerged)&@ @ @ @ @ P@ @ @ @ @ P&OPERATIONAL_STATUS1900601 1900602 1900604AN/A1"U" (under construction) "A" (abandoned) "C" (closed)&@ @ @ @ @ P@ @ @ @ @ P&UNIMPROVED1900605AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&NUCLEAR1900607AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&ARBITRARY_EXTENSION1900205AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&PHOTOREVISED1900000AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&ROTATION_ANGLE1930___*IDEGREES3Whole degrees in range 0 to 359; 99 indicates not applied &@ @ @ @ @ P@ @ @ @ @ P&BEST_ESTIMATE1980000AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&#Z PQP#STATE **19600__AN/A2#Xo PQXP#State FIPS codes; all blanks indicates not applied#Z PQP#&B B B B B RB B B B B R&AIRPORT **197____AN/A4Airport name identifier; all blanks indicates not applied#Xo PQXP# #Z PQP#* Not currently used but may exist in older DLG3's. ** Indicated fields will only appear in transfers of 1:2,000,000scale DLG3's and are foreign keys into attribute secondary modules#Xo PQXP#  Notes:  The following are the entities in the Pipelines, Transmission Lines, and Miscellaneous Transportation theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL(DLG3 code)Definition  1900001End of transmission line 1900002End of pipeline at oil or gas field 1900003End of pipeline at refinery, depot, ... 1900004Steel or concrete tower on transmission line 1900201Pipeline 1900202Power transmission line 1900203Telephone or telegraph line 1900204Aerial tramway, monorail, or ski lift 1900206Closure line 1900299Processing line 1900300*Seaplane anchorage 1900400Power station 1900401Substation 1900402Hydroelectric plant 1900403Landing strip, airport, perimeter of airport 1900404Heliport, perimeter of heliport 1900405Launch complex, perimeter of launch complex 1900406Pumping station or compressor station 1900407Seaplane ramp or landing area 1900408Measuring station, or valve station 7 spaces` ` ` No DLG3 entity but has other attributes  * ` ` ` Not currently used but may exist in older DLG3's.  r ddxT8 ddxT8 r &@@@@@P@@@@@P& AMSF Feature Attribute Primary Module`(#;(Manmade Features) ă&^B B B B B R^B B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@ @@@@P@ @@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&@ @ @ @ @ P@ @ @ @ @ P&RELATION_TO_ GROUND2000601 2000617AN/A1"U" (underground) "S" (submerged)&@ @ @ @ @ P@ @ @ @ @ P&OPERATIONAL_ STATUS2000602 2000603 2000618AN/A1"C" (under construction) "A" (abandoned) "R" (ruin)& @ @ @ @ @ P @ @ @ @ @ P&PRODUCT2000604 2000605 2000606 2000607 2000609 2000610 2000611 2000612 2000619 2000620 2000621 2000622 2000623 2000624AN/A1"W" (water) "O" (oil) "G" (gas) "C" (chemical) "V" (gravel) "S" (sand) "L" (clay) "B" (borrow) "A" (caliche) "H" (chert) "I" (cinder) "P" (pumice) "E" (shale) "R" (scoria)&M@ @ @ @ @ PM@ @ @ @ @ P&COVERED2000608AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&TOWER_TYPE2000613 2000614AN/A1"R" (radio) "L" (lookout)&M@ @ @ @ @ PM@ @ @ @ @ P&UNINCORPORATED2000615AN/A1"Y" (applied) or blank&M@ @ @ @ @ PM@ @ @ @ @ P&NO_POPULATION2000616AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&NATIONAL_ CAPITAL+2000690AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&STATE_ CAPITAL+2000691AN/A1"Y" (applied) or blank&M@ @ @ @ @ PM@ @ @ @ @ P&COUNTY_SEAT+2000692AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&POPULATION_ CLASS+2000680 2000681 2000682 2000683 2000684 2000685 2000686IN/A2Last digit of DLG3 minor code: digits 0 through 6; 9 indicates not applied&M@ @ @ @ @ PM@ @ @ @ @ P&PHOTOREVISED2000000AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&WIDTH202____IMILS ON MAP4Integer value obtained from minor code; 999 indicates not applied&@ @ @ @ @ P@ @ @ @ @ P&ROTATION_ ANGLE2030___*IDEGREES3Integer value 0359 obtained from minor code; 99 indicates not applied&]A A A A A Q]A A A A A Q&BEST_ESTIMATE2080000AN/A1"Y" (applied) or blank&@@@@@P@@@@@P&#Z PQP#STATE **20600__AN/A2State FIPS code; all blanks indicates not applied&B B B B B RB B B B B R&POPULATED_PLACE **207____AN/A4Populated place name identifier; all blanks indicates not applied#Xo PQXP# + These attributes will exist only on 1:2,000,000scale DLGs. * Not currently used but may exist in older DLG3's. #Z PQP#** Indicated fields will only appear in transfers of 1:2,000,000scale DLG3's and are foreign keys into attribute secondary modules #Xo PQXP# Notes: The following are the entities in the Manmade Features theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition 2000001*End point of linear manmade feature* 2000002*Point on linear manmade feature* 2000100Church complex 2000101School campus 2000102Hospital complex 2000103Orphanage 2000104Prison compound 2000105Trailer park 2000120Ski area 2000122Athletic field 2000123Golf course 2000124Shopping center 2000125Zoo 2000126Drivein theater 2000127Racetrack or raceway 2000128Playground 2000140Marina 2000141Cable area 2000150Builtup area 2000160Industrial park 2000161Materials storage area 2000162Refinery or industrial plant 2000163Tailings 2000164Intricate surface area 2000165Oil sump or sludge pit 2000180Tank farm 2000181Feedlot 2000182Experimental farm 2000183Proving grounds2000184Firing range 2000200Conveyor 2000201Boardwalk 2000202Wall 2000203Sea wall 2000206Fence line 2000207Flume (nonwater) 2000209Sewer line 2000211Coke ovens 2000212Recreational slide 2000213Screen (drivein theater) 2000214Drag strip, racetrack, raceway 2000215Athletic track 2000250Arbitrary closure line 2000299Processing line 2000300Grave site 2000301Historical marker 2000302Mine tunnel entrance or cave 2000303Mine shaft 2000304Prospect 2000305Tower 2000306Burner/stack 2000307Drilled well 2000308Cliff dwelling 2000309Light 2000310Brick kiln 2000311Drill hole 2000312*Watermill 2000313*Anchorage 2000314Guzzler 2000315Located object or landmark object 2000316Campsite 2000317Wind generator 2000400Building 2000401*Second class building 2000402Church 2000403School 2000404Municipal building 2000405Courthouse 2000406Post office 2000407City or town hall 2000408Hospital 2000409Prison 2000410Town, settlement, locality 2000411Amphitheater 2000412Customs building 2000420Cemetery 2000421Sewage disposal plant 2000422Waterworks 2000423Oil reservoir 2000424Drilled well field 2000425Tank 2000426Offshore oil or gas platform 2000427Mine dump2000428Open pit mine 2000429Quarry 2000430Strip mine 2000431Landfill 2000432Pit, unconsolidated material 2000433Radio or television facility 2000434Storage bin 2000435Levee 2000436Spoil bank 2000438Reclaimed area 2000445Fairgrounds 2000446Rodeo grounds 2000447Corral 2000448Boat ramp 2000449Campground 2000450Fort 2000451Swimming pool 2000452Archeological site, ruin 2000453Recreation area, public use area 2000454Picnic area 2000455Port of entry 2000456Stadium 2000465Pile, dolphin, stump, snag 2000466Breakwater, jetty, pier, dock, wharf 2000467Exposed wreck or wreckage 2000468Sunken wreck 2000469Dry dock 7 spaces` ` ` No DLG3 entity but has other attributes * ` ` ` Not currently used but may exist in older DLG3's.  r ddx PX ddx PX r &@@@@@P@@@@@P& APLF Feature Attribute Primary Module`(#:(Public Land Survey) ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ENTITY_LABELAN/A77digit DLG3 code or blanks&I@ @ @ @ @ PI@ @ @ @ @ P&ID_IN_FIELD3000040AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&WITH_HORIZONTAL3000041*AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&WITH_ELEVATION3000042*AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&APPROXIMATE_POS3000201AN/A1"Y" (applied) or blank&I@ @ @ @ @ PI@ @ @ @ @ P&PROTRACTED_POS3000202AN/A1"Y" (applied) or blank&@ @ @ @ @ P@ @ @ @ @ P&ORIGIN_OF_SURVEY30600__IN/A22digit code from table 33 of Part 3 of Standards for DLGs; 9 indicates not applied& @ @ @ @ @ P @ @ @ @ @ P&TOWNSHIP302____ 303____AN/A8Township number& @ @ @ @ @ P @ @ @ @ @ P&RANGE304____ 305____AN/A8Range number&I@ @ @ @ @ PI@ @ @ @ @ P&SECTION301____AN/A4Section number&I@ @ @ @ @ PI@ @ @ @ @ P&LAND_GRANT *307____AN/A4Land grant identifier& @ @ @ @ @ P @ @ @ @ @ P&MONUMENT_NUMBER308____ 3000625AN/A8Land grant monument number&yB B B B B RyB B B B B R&BEST_ESTIMATE3080000AN/A1"Y" (applied) or blank #Z P QP#* These attributes are foreign keys into attribute secondary modules in transfers of 1:2,000,000scale DLG3's #Xo P!QXP# Notes: The following are the entities in the Public Land Survey System theme which are identified by the ENTITY_LABEL attribute: ENTITY_LABEL (DLG3 code)Definition 3000001PLSS section corner 3000002*Point on section line 3000003Closing corner 3000004Meander corner 3000005Auxiliary meander corner 3000006Special meander corner 3000007Witness corner 3000008Witness point 3000009Angle point 3000010Location monument 3000011Reference monument 3000012Quartersection corner 3000013Tract corner 3000014Land grant or donation land claim corner 3000015Arbitrary section corner 3000100Indian lands 3000101Homestead entries 3000102Donation land claims 3000103Land grants or civil colonies 3000104Private extension of PLSS3000105Area of public and private survey overlap 3000106Overlapping land grants 3000107Military reservation 3000108Private survey 3000109Other reservation 3000198Water 3000199Unsurveyed area 3000203Arbitrary closure line 3000204Base line 3000205*Claim line, grant line 3000299Processing line 3000300Location monument 3000301Isolated found section corner 3000302Witness corner (off surveyed line) 7 spaces` ` ` No DLG3 entity but has other attributes * ` ` ` Not currently used but may exist in older DLG3's.   a2Legal Coincidence Attribute Primary Module Transfers will have one Coincidence Attribute Primary module, unless there are no records for it. This module contains records indicating that an entity is coincident with an entity in another DLG3 theme. For example, roads are frequently coincident with boundaries and the Public Land Survey. This is separate table because there may be multiple values of the COINCIDENT attribute (coincidence with multiple themes) for one spatial object. The TVP specifies that attributes which can have more than one value be separated into their own Attribute Primary module. A particular spatial object will have an attribute record for each value: a particular object may have no, one, or more attribute records to which it points. r dd}` dd}` r &@@@@@P@@@@@P& ACOI Coincidence Attribute Primary Module`<(#@All Themesă&B B B B B RB B B B B R&Attribute LabelDLG CodeFormatUnitsLengthValue Domain &BBBBBRBBBBBR&COINCIDENT0_9 00__AN/A2First 2 digits of major code of coincident category  a2Legal Elevation Attribute Primary Module  Transfers of the Hypsography theme will have one or two Elevation Attribute Primary modules. These contain the elevations of contours and spot elevations. It is necessary to store these elevations in a separate module because carrying contours can have multiple elevation values. (The Hydrography and Survey Control themes also use elevation attributes but in the Feature Attribute Primary module; features in those themes can not have multiple elevation values and therefore do not require the elevation attribute to be in a separate module.) The units of elevations will be the same as the units used in the input DLG3. In some instances a DLG3 will contain elevations in both feet and meters, one example being topographic contours in one unit and bathymetric contours in another unit. In such situations there will be two Elevation Attribute Primary modules, one for each unit. The Elevation Attribute Primary module for feet is named AHPT; the Elevation Attribute Primary module for meters is named AHPR. r ddx$<e ddx$<e r &@@@@@P@@@@@P& AHPR/AHPT Elevation Attribute Primary Module``(#>Hypsography ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain&}B B B B B R}B B B B B R&ELEVATION021____ 022____ 023____ 024____ 025____RFEET or METERS8Reals to the nearest 0.01; 9999.99 = not applied Route Attribute Primary Module This module is used to transfer route numbers for transfers of the Roads and Trails theme. There are two attributes: ROUTE_NUMBER and ROUTE_TYPE. ROUTE_NUMBER includes a one or two character jurisdiction (I, US, etc.), a space, followed by an alphanumeric route number. ROUTE_TYPE is used to transfer such designations as "business" and "alternate"; it will be blank if a route does not have such a designation. A single spatial object may have multiple route numbers and thus have multiple entries in this table. r ddxhh8 ddxhh8 r &@@@@@P@@@@@P&ARDM Route Attribute Primary Module`(#;Roads and Trails ă&ZB B B B B RZB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &@@@@@P@@@@@P&ROUTE_NUMBER172____ 173____ 174____ 175____ 176____ 177____AN/A7"I " (Interstate), "US ", "SR " (State Route), "RR " (Reservation Route), or "CR " (County Route) followed by route number&B B B B B RB B B B B R&ROUTE_TYPE1700615 1700616 1700617 1700619 1700620 1700621 1700622AN/A9"Bypass" "Alternate" "Business" "Spur" "Loop" "Connector" "Truck"; all blanks indicates not applied a2Legal Agency Attribute Primary Module  This module, used for transfers of the Boundary theme, contains codes identifying the administering agency for federal lands. It is possible for multiple agencies to claim jurisdiction over the same land and thus there may be more than one record for a single spatial object. The Agency module is only used for 1:2,000,000scale Boundary DLGs and some 1:100,000scale Boundary DLGs. r ddx$p8D ddx$p8D r &@@@@@P@@@@@P& ABDM Agency Attribute Primary Module`8(#@Boundaries ă&B B B B B RB B B B B R& Attribute LabelDLG CodeFormatUnitsLengthValue Domain &*BBBBBR*BBBBBR&AGENCY0970___IN/A3Agency codes (defined in the Data Dictionary/Domain) # P"QP# a2Legal State Attribute Secondary Module#Xo P#QXP# This module is only included in transfers created from 1:2,000,000scale DLG3's. It is included for the Boundary, Transportation, and Manmade Features themes. The 1:2,000,000scale DLG3 data is distributed on a state by state basis. This module will contain one record that carries the name of the state being transferred. All attributes from other modules that reference the primary key of this module will be described as foreign keys in the Data Dictionary / Schema module. When a relational link between modules exists, that relationship will be described by a Catalog / CrossReference module record. r ddx$p8D ddx$p8D r &@@@@@P@@@@@P& BFPS State Attribute Secondary Module`(#?Boundaries, `p(#<Transportation, `(#7& Manmade Features ă&B B B B B RB B B B B R& Attribute LabelKEYFormatUnitsLengthValue Domain &AAAAAQAAAAAQ&STATEPrimary KeyAN/A2State FIPS code&qBBBBBRqBBBBBR&#Z P$QP#STATE_NAMENo KeyAN/A69The state name#Xo P%QXP# # P&QP# a2Legal County Attribute Secondary Module #Xo P'QXP#This module is only included in transfers created from 1:2,000,000scale DLG3's. It is included for the Boundary and Manmade Features themes. The 1:2,000,000scale DLG3 data includes companion text files that carry the names of the counties identified by county FIPS codes. The county attribute secondary module carries these names and relates them to other attribute modules using their county FIPS codes as a key. All attributes from other modules that reference the primary key of this module will be described as foreign keys in the Data Dictionary / Schema module. When a relational link between modules exists, that relationship will be described by a Catalog / CrossReference module record. r ddx$p8D ddx$p8D r &@@@@@P@@@@@P& BFPC County Attribute Secondary Module`8(#@Boundaries `(#7& Manmade Features ă&B B B B B RB B B B B R&#Z P(QP# Attribute LabelKEYFormatUnitsLengthValue Domain &AAAAAQAAAAAQ&STATEPrimary & Foreign KeyAN/A2State FIPS code&QAAAAAQQAAAAAQ&COUNTYPrimary KeyAN/A3 County FIPS code#Xo P)QXP#&2BBBBBR2BBBBBR&#Z P*QP#AREA_NAMENo KeyAN/A69The county or county equivalent name#Xo P+QXP# # P,QP# a2Legal Populated Places Attribute Secondary Module #Xo P-QXP#This module is only included in transfers created from 1:2,000,000scale DLG3's. It is included for the Manmade Features theme. The 1:2,000,000scale DLG3 data includes companion text files that carry the names of populated places within the state along with the Census population values for each. The populated places attribute secondary module carries this information and relates it to other attribute modules using the POPULATED_PLACE index number as a key. All attributes from other modules that reference the primary key of this module will be described as foreign keys in the Data Dictionary / Schema module. When a relational link between modules exists, that relationship will be described by a Catalog / CrossReference module record. r ddxp8D ddxp8D r &@@@@@P@@@@@P& BMSP Populated Place Attribute Secondary Module `(#9Manmade Features ă&B B B B B RB B B B B R&#Z P.QP# Attribute LabelKEYFormatUnitsLengthValue Domain &QAAAAAQQAAAAAQ&POPULATED_PLACEPrimary KeyAN/A4Populated place index number&QAAAAAQQAAAAAQ&POP_PLACE_NAMENo KeyAN/A42Name of the populated place&QAAAAAQQAAAAAQ&COUNTYForeign KeyAN/A3 County FIPS code#Xo P/QXP#&2BBBBBR2BBBBBR&#Z P0QP#POPULATIONNo KeyIPeople101990 Census Population (if available)#Xo P1QXP# # P2QP# a2Legal Airport Names Attribute Secondary Module #Xo P3QXP#This module is only included in transfers created from 1:2,000,000scale DLG3's. It is included for the Transportation theme. The 1:2,000,000scale DLG3 data includes companion text files that carry the names of airports within the state. The airport names attribute secondary module carries this information and relates it to other attribute modules using the AIRPORT index number as a key. All attributes from other modules that reference the primary key of this module will be described as foreign keys in the Data Dictionary / Schema module. When a relational link between modules exists, that relationship will be described by a Catalog / CrossReference module record.# P4QP# r ddx$p8D ddx$p8D r &@@@@@P@@@@@P& BMTA Airport Names Attribute Secondary Module `(#=Transportation ă&B B B B B RB B B B B R&#Z P5QP# Attribute LabelKEYFormatUnitsLengthValue Domain &QAAAAAQQAAAAAQ&AIRPORTPrimary KeyAN/A4 Airport index number#Xo P6QXP#&qBBBBBRqBBBBBR&#Z P7QP#AIRPORT_NAMENo KeyAN/A42Name of the airport#Xo P8QXP# # P9QP#a2Legal Land Grant Attribute Secondary Module #Xo P:QXP#This module is only included in transfers created from 1:2,000,000scale DLG3's. It is included only for states that contain Federal land grants in transfers of the U.S. Public Land Survey theme. The 1:2,000,000scale DLG3 data includes companion text files that carry the names of Federal land grants within the state. The land grant attribute secondary module carries this information and relates it to other attribute modules using the LAND_GRANT index number as a key. All attributes from other modules that reference the primary key of this module will be described as foreign keys in the Data Dictionary / Schema module. When a relational link between modules exists, that relationship will be described by a Catalog / CrossReference module record. r ddxSUp8D ddxSUp8D r &@@@@@P@@@@@P& # P;QP#BGRL Land Grant Attribute Secondary Module `(#5U.S. Public Land Survey#Xo P<QXP# ă&B B B B B RB B B B B R&#Z P=QP# Attribute LabelKEYFormatUnitsLengthValue Domain &QAAAAAQQAAAAAQ&LAND_GRANTPrimary KeyAN/A4 Land grant index number#Xo P>QXP#&qBBBBBRqBBBBBR&#Z P?QP#LAND_GRANT_NAMENo KeyAN/A75Name of the land grant#Xo P@QXP#