SPATIAL DATA TRANSFER STANDARD PART 3 ISO 8211 Encoding Contents 1 Introduction. . . . . . . . . . . . . . . . . . . . . 1 1.1 Purpose of ISO 8211 Encoding. . . . . . . . 1 1.2 Objectives. . . . . . . . . . . . . . . . . 1 1.3 Relationship to Other Standards . . . . . . 1 1.4 Status of Annexes . . . . . . . . . . . . . 1 2 Scope and Field of Application. . . . . . . . . . . . 2 2.1 Scope . . . . . . . . . . . . . . . . . . . 2 2.2 Field of Application. . . . . . . . . . . . 2 3 References. . . . . . . . . . . . . . . . . . . . . . 3 4 Definitions . . . . . . . . . . . . . . . . . . . . . 4 5 Nomenclature. . . . . . . . . . . . . . . . . . . . . 5 6 Specifications. . . . . . . . . . . . . . . . . . . . 7 6.1 Specifications of ISO 8211 Constructs . . . 7 6.1.1 Notational Conventions of Table 1 . 7 6.1.2 Tags, Names and Labels. . . . . . . 23 6.1.3 Permitted Variations in Field Controls and Formats. . . . . . . 23 6.1.4 Order of Data Items in Arrays . . . 24 6.2 Missing Data. . . . . . . . . . . . . . . . 25 6.2.1 Fields Missing from Entire Files. . 25 6.2.2 Fields Missing from Specific Data Records . . . . . . . . . . . . . 25 6.2.3 Consistently Missing Data Subfields 25 6.2.4 Intermittently Missing Data Subfields . . . . . . . . . . . . 25 6.3 Foreign Identifiers . . . . . . . . . . . . 25 6.4 Repeating Fields and Records. . . . . . . . 26 6.4.1 Repeating Fields. . . . . . . . . . 26 6.4.2 Repeating Records . . . . . . . . . 26 7 Assignment of Fields to Records and Files . . . . . . 27 7.1 Global Modules. . . . . . . . . . . . . . . 27 7.2 Other Modules . . . . . . . . . . . . . . . 27 7.3 Multivolume Files . . . . . . . . . . . . . 27 8 Record Structure. . . . . . . . . . . . . . . . . . . 28 8.1 Restriction on Primary Fields in Level 2 Files . . . . . . . . . . . . . . . . . . 28 8.2 Primary and Secondary Fields in Level 3 Files . . . . . . . . . . . . . . . . . . 28 8.3 Arbitrary Field Sequence. . . . . . . . . . 28 9 Data Representation . . . . . . . . . . . . . . . . . 29 9.1 Numeric Data. . . . . . . . . . . . . . . . 29 9.2 Dates . . . . . . . . . . . . . . . . . . . 29 9.3 Binary Data . . . . . . . . . . . . . . . . 29 10 Media Requirements . . . . . . . . . . . . . . . . . 30 10.1 General Requirements . . . . . . . . . . . 30 10.2 Magnetic Tapes . . . . . . . . . . . . . . 30 10.3 Flexible Diskettes . . . . . . . . . . . . 30 10.4 Magnetic Tape Cartridges and Cassettes . . 30 10.5 Compact Disk Read Only Memory. . . . . . . 30 11 Conformance. . . . . . . . . . . . . . . . . . . . . 31 ANNEXES. . . . . . . . . . . . . . . . . . . . . . . . . 32 A: Guidelines for Private Agreements . . . . . . . . . . 33 B: Field and Subfield Names and Mnemonics. . . . . . . . 34 B.1 Field Tag and Field Name . . . . . . . . . . 34 B.2 Subfield Label and Subfield Name . . . . . . 36 B.3 Field Composition. . . . . . . . . . . . . . 40 1 Introduction 1.1 Purpose of ISO 8211 Encoding The ISO 82111 encoding provides a representation of a Spatial Data Transfer Standard (SDTS) file set in a standardized method enabling the file set to be exported to or imported from different media by general purpose ISO 8211 software. 1.2 Objectives This encoding was selected with the following objectives: (a) to place this standard within a broader community of interchange based on a general purpose, interchange standard; (b) to place the encoding of this standard in a standardized vehicle that provides the syntax and semantics necessary to the transport of files, records, fields and subfields accompanied by their data description in a machine readable form; (c) to provide for media independence of the transfer file set; (d) to provide for future extensions of the standard (e.g. adding new modules, fields, subfields) without compromise of the then existing implementations; (e) to provide for user extensions without compromising the constructs of the standard. 1.3 Relationship to Other Standards ISO 8211 is a general purpose, media-independent interchange standard whose variable length records may be written on any medium that is able to accept them, including communications lines. In order to promote transfer, the user is advised to employ media for which volume and file structure standards exist as well as widespread implementations. The specific requirements for currently standardized media are given in section 10. 1.4 Status of Annexes The annexes do not form an integral part of the standard but are added to provide additional information and explanation. 1ISO 8211 Information Processing - Specification for a Data Descriptive File for Information Interchange (1985) is also the ANSI standard, ANSI/ISO 8211, and the Federal Information Processing Standard, FIPSPUB 123. 2 Scope and Field of Application 2.1 Scope This part of the standard specifies an encoding of an SDTS file set in ISO 8211 and on standardized media. 2.2 Field of Application This part of the standard applies to all ISO 8211 encodings of part 1 of this standard and to user extensions (see part 3, annex A) of this standard. 3 References When any of the standards cited in this section is superseded by an approved revision, the revision shall apply. ANSI X3.122-1986, Computer Graphics Metafile (CGM), FIPSPUB 128, 16 Mar 1987. ANSI X3.27-1987, American National Standard for File Structure and Labelling of Magnetic Tapes for Information Interchange (ISO 1001) ANSI/ISO 4341-1978, American National Standard for Magnetic Tape Cassette and Cartridge Labelling and File Structure for Information Interchange ANSI/ISO 8211-1986, American National Standard for Information Processing - Specification for a Data Descriptive file for Information Interchange (also FIPS 123) ISO 6093-1985, Information Processing - Specification for Representation of Numeric Values in Character Strings for Information Interchange ISO 9293-1986, Volume and File Structure of Flexible Disk Cartridges for Information Interchange ISO 9660-1986, Volume and File Structure of CD-ROM for Information Interchange 4 Definitions The terms used in this part of the standard are limited to those terms in common usage, or defined in part 1 or part 2, or those found in the cited ISO 8211 document. 5 Nomenclature The methodology of this part is to define ISO 8211 constructs which, for the purpose of transfer, accept the logical constructs of part 1 of the standard and preserve their meaning. Where possible, a correspondence is maintained between the module subfields and fields of part 1 and the ISO 8211 subfields and fields maintaining both identification and order when required. The content and size of a transfer determine what fields are present and how they are collected into records and the records into files. Part 1 allows the user considerable freedom to structure records and files as needed and this part does likewise. Table 1, in section 6, contains the specification for the ISO 8211 encoding of all module fields defined in part 1, section 5. The constructs of table 1 are related to the logical constructs of part 1 by section references, e.g., (see part 1, 5.d..), and by the following nomenclature equivalents: Part 1 Table 1 (1) Module Subfield Subfield/Element Subfield Name/ Label Mnemonic Module Field Field Field Name Name Field Mnemonic Tag Domain Data type/format (1) ISO 8211 nomenclature The identification nomenclature of part 1 has been used for most of the corresponding constructions of this part. The mnemonic for a module field becomes an ISO 8211 tag and the mnemonic for a subfield becomes an ISO 8211 label. Table 1 specifies any exceptions to this practice. The field names are the corresponding names in part 1. Specifications for the substantive contents and semantics of the user data subfields corresponding to the tags and labels are found in parts 1 and 2. The following is a concordance relating the ISO 8211 data types of this Part to the data types and domains of part 1, section 4.2.1. Generic ISO 8211 Part 1 Type Data Type Data Type(s); Domain Text A A; Graphic characters, Alphanumeric, Alphabetic Integer I I; Integer Real, fixed R R; Real Real, float S S Logical C C Binary B B, BUI, BIdd, BUdd, BFPdd; Binary The following domains may result in any one of the ISO 8211 data types depending on their use: Allowable values, Standard code sets and Standard field where domain is defined in Data Dictionary. 6 Specifications This section specifies the allowable subset of tags, names, labels, formats and other control information necessary to the transfer of spatial data. It specifies the limits allowed users for those ISO 8211 parameters that are permitted to vary such that transfer may be accomplished. The specifications for several media are also provided. Note: Annex A suggests methods by which private agreements can extend the standard within the general specifications of ISO 8211 in order that the user can, by private agreement, transfer data not anticipated by this standard in a manner that does not conflict with this standard. 6.1 Specifications of ISO 8211 Constructs Table 1 specifies the ISO 8211 tags, control fields, names, labels and formats reserved by this standard for the transfer of a set of complete modules as single or multiple files. The field controls in table 1 are based on the following rule. An ISO 8211 vector data structure (1x00) is used for all primary fields and other fields of part 1 that do not repeat within a module record. An ISO 8211 array data structure (2x00) is used for fields that may repeat within a module record. Alternatives to the field controls of table 1 are specified in 6.4.1. 6.1.1 Notational Conventions of Table 1 The contents of table 1 are formatted as follows: Tag st00fuName& (See part 1, section reference) [n]|[m,n] Label& - continued to next line as necessary Format; where: Tag is a four character ISO 8211 tag st00fu are the ISO 8211 field controls (6 bytes) where: s is the data structure code t is the data type code 00 are required characters f is the printable graphic for the field terminator u is the printable graphic for unit terminator Note: The printable graphics ";" and "&" at other locations in table 1 represent FT(1/14) and UT(1/15), the required delimiters of the data description subfields. Name& is the ISO 8211 name and "&" represents its delimiter [ ] signifies that no labels are specified [n] signifies n subfield elements of an n-tuple [m,n] signifies the number of elements in a two dimensional array; often an n-tuple, repeating m times Where n is not explicitly specified, it is determined by the number of items in the user's n-tuple. Where m is not explicitly specified, the field is a repeating n-tuple whose first extent is determined from the data in the ISO 8211 field. Label& is an ISO 8211 vector label or Cartesian label and "&" represents its delimiter A vector label identifies the components of an n-tuple and has the form, lab1!lab2!...labn. A Cartesian label identifies the columns of a repeating table and has the form, *col1!col2!...coln. Format; is the ISO 8211 format control and ";" represents its delimiter. When explicitly specified for a subfield, the ISO 8211 data type format code (i.e., A, I, R, S, C, B) is given. The formats of subfields with user delimiters or fixed extents will require completion by the user. The presence of "z" implies that the data type must be supplied by the user from the list of allowed types. See 6.1.3 (e) for format variations. The presence of: "lowercase" implies a user assigned name, label or data type code. Solid lines, "______", group associated sets of tags and field descriptions that form a spatial data module (i.e., the associated fields lie between the solid lines). The primary field of the set is listed first and the secondary fields, if any, are listed after the primary field. Table 1 Specification of Tags, Field Controls, Names, Labels and Formats ISO 8211 File Control Field 0000 0000;&external file title& [] & ; Note: This field exists only in the ISO 8211 data descriptive record and contains a human-readable file title ISO 8211 Record Identifier Field 0001 0100;&DDF RECORD IDENTIFIER& [] & ; Note: This field is required by ISO 8211 in each record and contains a unique identifier of a data record. It is not the SDTS record identifier, RCID. Global Information Modules (See part 1, 5.2) IDEN 1600;&IDENTIFICATION& (See part 1, 5.2.1.1) [15] MODN!RCID!STID!STVS!DOCU!PRID!PRVS!PDOC! TITL!DAID!DAST!MPDT!DCDT!SCAL!COMT& (A,I,11A,I,A); CONF 1600;&CONFORMANCE& (See part 1, 5.2.1.2) [6] FFYN!VGYN!GTYN!RCYN!EXSP!FTLV& (4A,2I); Table 1 (continued) ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); CATD 1600;&CATALOG/DIRECTORY& (See part 1, 5.2.2.1) [10] MODN!RCID!NAME!TYPE!VOLM!FILE!RECD!EXT R!MVER!COMT& (A,I,4A,z,3A); where z implies (I|A). CATX 1600;&CATALOG/CROSS- REFERENCE& (See part 1, 5.2.2.2) [7] MODN!RCID!NAM1!TYP1!NAM2!TYP2!COMT& (A,I,5A); CATS 1600;&CATALOG/SPATIAL DOMAIN& (See part 1, 5.2.2.3) [10] MODN!RCID!NAME!TYPE!DOMN!MAP!THEM!AG OB!AGTP!COMT& (A,I,8A); SCUR 1600;&SECURITY& (See part 1, 5.2.3) [8] MODN!RCID!CLAS!CTRL!RLIS!RVDT!RVIS!COMT& (A,I,6A); FRID 2600;&Foreign ID& [m,2] *MODN!RCID& (A,I); IREF 1600;&INTERNAL SPATIAL REFERENCE& (See part 1, 5.2.4.1) [17] MODN!RCID!COMT!SATP!XLBL!YLBL!HFMT!VFMT! SFAX!SFAY!SFAZ!XORG!YORG!ZORG!XHRS!YHRS !VRES& (A,I,6A,6R,z,z,z); where z implies (I|R|S) XREF 1600;&EXTERNAL SPATIAL REFERENCE& (See part 1, 5.2.4.2) [10] MODN!RCID!COMT!RDOC!RSNM!VDAT!SDAT!HD AT!ZONE!PROJ& (A,I,8A); Table 1 (continued) ATID 1600;&ATTRIBUTE ID& [2] MODN!RCID& (A,I); RGIS 1600;®ISTRATION& (See part 1, 5.2.4.3) [3] MODN!RCID!COMT& (A,I,A); EADS 2600;&EXTERNAL REFERENCE SPATIAL ADDRESS& [m,3] *X!Y!Z& (3z); where z implies (R|S). IADS 2600;&INTERNAL REFERENCE SPATIAL ADDRESS& [m,3] *X!Y!Z& (3z); where z implies (I|R|S|B). When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. SPDM 1600;&SPATIAL DOMAIN& (See part 1, 5.2.5) [5] MODN!RCID!DTYP!DSTP!COMT& (A,I,3A); DMSA 2600;&DOMAIN SPATIAL ADDRESS& [m,3] *X!Y!Z& (3z); where z implies (I|R|S|B). When Domain Spatial Address = "INTERNAL" and when B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. DDDF 1600;&DATA DICTIONARY/DEFINITION& (See part 1, 5.2.6.1) [8] MODN!RCID!EORA!EALB!SRCE!DFIN!AUTH!ADSC& (A,I,6A); Table 1 (continued) DDOM 1600;&DATA DICTIONARY/DOMAIN& (See part 1, 5.2.6.2) [10] MODN!RCID!ATLB!AUTH!ATYP!ADVF!ADMU!RAV A!DVAL!DVDF& (A,I,6A,z,A); z implies (A|I|R|S|C|B) When B is specified the ISO 8211 binary data type may be extended by the Attribute Domain Value Format subfield, ADVF. DDSH 1600;&DATA DICTIONARY/SCHEMA& (See part 1, 5.2.6.3) [12] MODN!RCID!NAME!TYPE!ETLB!EUTH!ATLB!AUTH! FMT!UNIT!MXLN!KEY& (A,I,8A,I,A); STAT 1600;&TRANSFER STATISTICS& (See part 1, 5.2.7) [6] MODN!RCID!MNTF!MNRF!NREC!NSAD& (A,I,2A,2I); Data Quality (See part 1, 5.3) DQHL 1600;&LINEAGE& (See part 1, 5.3.1) [3] MODN!RCID!COMT& (A,I,A); ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); FRID 2600;&FOREIGN ID& [m,2] *MODN!RCID& (A,I); DQPA 1600;&POSITIONAL ACCURACY& (See part 1, 5.3.2) [3] MODN!RCID!COMT& (A,I,A); ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); Table 1 (continued) FRID 2600;&FOREIGN ID& [m,2] *MODN!RCID& (A,I); DQAA 1600;&ATTRIBUTE ACCURACY& (See part 1, 5.3.3) [3] MODN!RCID!COMT& (A,I,A); ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); FRID 2600;&FOREIGN ID& [m,2] *MODN!RCID& (A,I); DQLC 1600;&LOGICAL CONSISTENCY& (See part 1, 5.3.4) [3] MODN!RCID!COMT& (A,I,A); ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); FRID 2600;&FOREIGN ID& [m,2] *MODN!RCID& (A,I); DQCG 1600;&COMPLETENESS& (See part 1, 5.3.5) [3] MODN!RCID!COMT& (A,I,A); ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); Table 1 (continued) FRID 2600;&FOREIGN ID& [m,2] *MODN!RCID& (A,I); ATPR 1600;&ATTRIBUTE PRIMARY& (See part 1, 5.4.1) [2] MODN!RCID& (A,I); OBID 1600;&SPATIAL OBJECT ID& [2] MODN!RCID& (A,I); ATTP 1x00;&PRIMARY ATTRIBUTES& [n] attribute1!attribute2!...!attributen& (z,z...); x is selected to be consistent with the data type z implies (A|I|R|S|C|B) ATSC 1600;&ATTRIBUTE SECONDARY& (See part 1, 5.4.2) [2] MODN!RCID& (A,I); ATTS 1x00;&SECONDARY ATTRIBUTES& [n] attribute1!attribute2!...!attributen& (z,z...); x is selected to be consistent with the data type z implies (A|I|R|S|C|B) COMP 1600;&COMPOSITE& (See part 1, 5.5) [3] MODN!RCID!OBRP& (A,I,A); ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); FRID 2600;&FOREIGN ID& [m,3] *MODN!RCID!USAG& (A,I,A(1)); Table 1 (continued) CPID 2600;&COMPOSITE ID& [m,2] *MODN!RCID& (A,I); Vector Modules (See part 1, 5.6) PNTS 1600;&POINT-NODE& (See part 1, 5.6.1) [3] MODN!RCID!OBRP& (A,I,A); SADR 1600;&SPATIAL ADDRESS& [3] X!Y!Z& (3z); where z implies (I|R|S|B) When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); LNID 2600;&LINE ID& [m,3] *MODN!RCID!USAG& (A,I,A(1)); ARID 2600;&AREA ID& [m,2] *MODN!RCID& (A,I); CPID 2600;&COMPOSITE ID& [m,2] *MODN!RCID& (A,I); RPID 2600;&REPRESENTATION MODULE ID& [m,2] *MODN!RCID& (A,I); Table 1 (continued) OSAD 2600;&ORIENTATION SPATIAL ADDRESS& [m,3] *X!Y!Z& (3z); where z implies (I|R|S|B) When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. PAID 2600;&ATTRIBUTE PRIMARY FOREIGN ID& [m,3] *MODN!RCID!ATLB& (A,I,A); SSAD 1600;&SYMBOL ORIENTATION SPATIAL ADDRESS& [m,3] *X!Y!Z& (3z); where z implies (I|R|S|B) When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. LINE 1600;&LINE& (See part 1, 5.6.2) [3] MODN!RCID!OBRP& (A,I,A); ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); PIDL 1600;&POLYGON ID LEFT& [2] MODN!RCID& (A,I); PIDR 1600;&POLYGON ID RIGHT& [2] MODN!RCID& (A,I); SNID 1600;&STARTNODE ID& [2] MODN!RCID& (A,I); Table 1 (continued) ENID 1600;&ENDNODE ID& [2] MODN!RCID& (A,I); CCID 2600;&CHAIN COMPONENT ID& [m,3] *MODN!RCID!USAG& (A,I,A(1)); SADR 2600;&SPATIAL ADDRESS& [m,3] *X!Y!Z& (3z); where z implies (I|R|S|B) When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. CPID 2600;&COMPOSITE ID& [m,2] *MODN!RCID& (A,I); RPID 2600;&REPRESENTATION MODULE ID& [m,2] *MODN!RCID& (A,I); ARC 1600;&ARC& (See part 1, 5.6.3) [5] MODN!RCID!OBRP!SRFC!ORDR& (A,I,2A,I); ARAD 2600;&ARC ADDRESS& [3,3] CTAD!STAD!ENAD*X!Y!Z& (3z); where z implies (I|R|S|B). When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. ELAD 2600;&ELLIPSE ADDRESS& [2,3] MJRA!MNRA*X!Y!Z& (3z); where z implies (I|R|S|B). Table 1 (continued) When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. CADR 2600;&CURVE ADDRESS& [m,3] *X!Y!Z& (3z); where z implies (I|R|S|B) When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); CPID 2600;&COMPOSITE ID& [m,2] *MODN!RCID& (A,I); RPID 2600;&REPRESENTATION MODULE ID& [m,2] *MODN!RCID& (A,I); RING 1600;&RING& (See part 1, 5.6.4) [3] MODN!RCID!OBRP& (A,I,A); LAID 2600;&LINE OR ARC FOREIGN ID& [m,3] *MODN!RCID!USAG& (A,I,A(1)); PLID 2600;&POLYGON ID& [m,2] *MODN!RCID& (A,I); POLY 2600;&POLYGON& (See part 1, 5.6.5) [m,3] *MODN!RCID!OBRP& (A,I,A); Table 1 (continued) ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); RFID 2600;&RING ID& [m,3] *MODN!RCID!USAG& (A,I,A(1)); CHID 2600;&CHAIN ID& [m,3] *MODN!RCID!USAG& (A,I,A(1)); CPID 2600;&COMPOSITE ID& [m,2] *MODN!RCID& (A,I); RPID 2600;&REPRESENTATION MODULE ID& [m,2] *MODN!RCID& (A,I); Raster Form (See part 1, 5.7) RSDF 1600;&RASTER DEFINITION& (See part 1, 5.7.2) [21] MODN!RCID!OBRP!AQMD!AQDT!COMT!CMNM!D EFI! CMPR!CMMD!RWXT!CLXT!SCOR!SCPT!TIDX!TIF T!TIDS ALTN!FSCN!ASPR!NLAY& (A,I,8A,2I,5A,I,A,R,I); RATP 2600;&RASTER ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); LDEF 2600;&LAYER DEFINITION& [m,14] *LNAM!CODE!FMT!BMSK!NROW!NCOL!MINV!MA XV! SORI!SOCI!RWOO!CLOO!INTR!COMT& (3A,C,2I,2z,4I,2A); where z implies (A|I|R|S|C|B) When B is specified the ISO 8211 binary data type may be extended by the Format subfield, FMT. Table 1 (continued) LATP 2600;&LAYER ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); CPID 2600;&COMPOSITE ID& [m,2] *MODN!RCID& (A,I); CELL 1600;&CELL& (See part 1, 5.7.3) [6] MODN!RCID!NCEL!ROWI!COLI!TIND& (A,4I,z); where z implies (I|B) When B is specified the ISO 8211 binary data type may be extended by the Tesseral Index Format subfield of the Raster Definition field, RSDF/TIFT. SADR 1600;&SPATIAL ADDRESS& [3] X!Y!Z& (3z); where z implies (I|R|S|B) When B is specified for internal spatial address subfields, the ISO 8211 binary data type is extended by the HFMT (for X and Y) and VFMT (for Z) subfields of the associated Internal Spatial Reference module record. ATID 2600;&ATTRIBUTE ID& [m,2] *MODN!RCID& (A,I); CVLS 2600;&CELL VALUES& [m,n] & (z); where z implies (A|I|R|S|C|B) When B is specified the ISO 8211 binary data type may be extended by the Format subfield of the Layer Definition field, LDEF/FMT. Note: There are no labels for this field. The order of the data is specified by the contents of RSDF/OBRP and the order of layers in RSDF/LDEF (see part 1, 5.7.1.1). To reduce the number of implementation options, only one ISO 8211 CVLS field shall be used per ISO 8211 record. Table 1 (continued) Let the V(l,s,v) represent the organization of raster data into layers (l), swathes (s) and values (v), where the order of l and s can be interchanged depending on the Object Representation code (OBRP), and let the following symbol represent the iteration mechanisms available for storing raster data: R: iterations for multiple layers or multiple swathes handled by iterations of the ISO 8211 record B: iterations for multiple layers handled by iterating blocks of records #: iterations for multiple layers of swathes handled by iterating subfields of the CVLS field and let V(l:X,s:X,v:X) and V(s:X,l:X,v:X) represent the way in which the raster elements are combined with the iteration mechanisms, where X can be R,B,or #, then the following table denotes the relationships between object representation codes and possible raster organizations: Raster Field CVLS Matrix OBRP Organization Controls Dimension Comment GI V(l:R,s:#,v:#) 2600 2 or 3 May not be practical for large images GI V(1:B,s:R,v:#) 1600 or 1 or 2 For general swath 2600 GJ V(s:R.1;#,v:#) 2600 2 or 3 For general swath GK V(l:B,s:R,v:R) 1000 or 1 element Swath is a run, one 1600 single subfield per CVLS field GM - - - CVLS field not used Whenever field controls of 2600 are used (for a 2 or 3 dimensional matrix), indicating the presence of a matrix in field's subfields, the array descriptor of ISO 8211, 6.2.4 (dope vector), shall be used to indicate the dimension and the extents of the dimension of the matrix. Table 1 (continued) Graphic Representation (See part 1, 5.8) TEXT 1600;&TEXT REPRESENTATION& (See part 1, 5.8.1) [14] MODN!RCID!BSCL!SSCL!LSCL!CLDX!CHHT!FTDX !TPTH! UTXA!VTXA!CHEX!CHSP!SANG& (A,5I,R,I,3A,3R); LNRP 1600;&LINE REPRESENTATION& (See part 1, 5.8.2) [8] MODN!RCID!BSCL!SSCL!LSCL!CLDX!LTYP!LWTH& (A,6I,R); SYRP 1600;&SYMBOL REPRESENTATION& (See part 1, 5.8.3) [8] MODN!RCID!BSCL!SSCL!LSCL!CLDX!SMKR!MKS Z& (A,6I,R); AFIL 1600;&AREA FILL REPRESENTATION& (See part 1, 5.8.4) [9] MODN!RCID!BSCL!SSCL!LSCL!CLDX!FTYP!HIDX! PIDX& (A,5I,A,2I); CLRX 1600;&COLOR INDEX& (See part 1, 5.8.5) [6] MODN!RCID!RED!GREN!BLUE!BLCK& (A,I,4R); FONT 1600;&FONT INDEX& (See part 1, 5.8.6) [3] MODN!RCID!FNTN& (A,I,z); where z implies I|A. 6.1.2 Tags, Names and Labels The tags, names, and labels shall conform to the meanings specified in part 1 and to table 1. The spelling of tags, names and labels shall conform to the spellings of table 1. Labels shall occur in the order specified in table 1 (see 6.2 for missing data specifications). Where there is a requirement in part 1 for the preservation of the order of module fields and (or) subfields or for the associations between module fields or subfields, this ordering shall be preserved by the order of the ISO 8211 records, fields and subfields. Note: This section is a constraint on the permissiveness of part 1, 4.1.3.1 and 4.1.3.3.3 with respect to order. Data descriptive fields that have no specified labels may be augmented by user-supplied labels for the identification of subfield data (see part 1, 5.4). ISO 8211 does not allow duplicate tags in the same data descriptive record. When there is a need to have duplicate instances of the same generic field description of table 1 in the same data descriptive record, a tag is permitted to have an optional fifth character to make the tags for the two instances unique. For example two attribute modules may be encoded in the same file with primary attribute tags: ATTP1 1600;&PRIMARY ATTRIBUTES& STATE!COUNTY!LANDTYPE& (A(2),A(15),I(1)); ATTP2 2600;&PRIMARY ATTRIBUTES& *VEG_TYPE!STOCKING_DATE& (I(1),A(8)); The length of the tags within a file must be uniform. Thus when a fifth character is required for uniqueness for some tags, all tags must be five character tags. The use of the character "blank" is not recommended. 6.1.3 Permitted Variations in Field Controls and Formats ISO 8211 field controls and formats shall conform to table 1 in the following manner: (a) Data Structure (byte 1) -- This control shall agree with the structure of the data in the field. Structure codes of 1 and 2 are interchangeable according to the specifications of 6.4.1. (b) Data Type (byte 2) -- This control shall agree with the data type of the corresponding user data. (c) Reserved bytes (bytes 3-4) -- No variation. (d) Printable Delimiters (bytes 5-6) -- The printable graphics to be substituted on display for the field terminator and the unit terminator may be selected by the user to prevent conflict with the data. Note: The printable graphics, ";" and "&" at other locations in table 1 represent FT(1/14) and UT(1/15). (e) Format -- The format shall agree with the user data in data type. The widths of fixed- width subfields and the delimiters of variable-width subfields shall agree with the data. Note: The format controls of table 1 are specifications that do not include the subfield extents. If used without change the subfield extents would default in ISO 8211 to variable-length subfields with the system delimiter, (1/15). This might result in poor file design; for reasons of efficiency, fixed width subfields are preferred over variable width subfields. Note: The field terminator (FT(1/14)) and the subfield terminator, either the user selected terminator or the unit terminator (UT(1/15) are not considered a part of the user data and are not subject to the domain constraints that apply to the user data. 6.1.4 Order of Data Items in Arrays The order of data items in arrays must match the order of the ISO 8211 subfield labels. In ISO 8211 the subfield labels for an array are specified as the Cartesian product of vector labels. These labels when multiplied out correspond to the order of the data. a!b!c!...!n*x!y!z = ax ay az bx by bz cx... nz Notice that the labels in the last vector vary fastest in the sequence. Hence, the order of data in arrays is essentially row-order, with the rightmost label varying fastest. When the first vector label is preceded by an asterisk (referred to as a null vector label in ISO 8211), then the Cartesian product of the vector labels can be thought of collectively as an n-tuple, and this n-tuple can be repeated in the data. In other words, this allows a single field to have multiple values corresponding to the same set of subfield labels. If an array has a fixed dimension and extent in all data records and a Cartesian label is not required, the label may be replaced by an array descriptor comprising the dimension of the array followed by the extent of each vector, all separated by commas. For instance for a 2 dimensional array with 1024 rows and 512 columns, this descriptor will be: 2,1024,512. This descriptor is also referred to as a "dope vector." 6.2 Missing Data See part 1, 4.1.3.3.5, 4.1.3.3.6 and 4.1.3.3.9. This section specifies the methods by which the implementation permits the representation of missing data. 6.2.1 Fields Missing from Entire Files When a data field is missing from all the data records of a file, the corresponding tag and data descriptive field may be omitted from the DDR of the file. (See part 1, 4.1.3.3.5) 6.2.2 Fields Missing from Specific Data Records Missing fields may be indicated by omitting the tag from the data record directory and the field from user data area of the data record. (See part 1, 4.1.3.3.5) 6.2.3 Consistently Missing Data Subfields When a labeled data subfield is consistently missing throughout a file in one of the tagged fields specified in table 1, then the subfield label corresponding to that data subfield may be omitted from the list of labels. The remaining labels shall occur in the order specified in table 1. (See part 1, 4.1.3.3.6.) 6.2.4 Intermittently Missing Data Subfields When a data subfield is intermittently missing, a delimited data format shall be specified and a null data value comprising zero bytes shall be placed in the user data field followed by the appropriate delimiter. (See part 1, 4.1.3.3.9) 6.3 Foreign Identifiers Foreign identifiers shall agree in data structure, data type and format with their references. The referenced record shall exist in the transfer file set. 6.4 Repeating Fields and Records 6.4.1 Repeating Fields Where part 1 permits or requires repeated fields (within and (or) between module records and (or) between modules) a data structure control of 2 (array) may be used allowing multiple instances of the data n-tuples in the same field. This can reduce overhead and keep similar data in close proximity. Conversely, where table 1 specifies a structure control of 2, a structure control of 1 may be used, possibly requiring use of additional fields with the same tag. Regardless of the structure control, the option also exists to use additional fields with the same tag and (or) to place the data in a separate record. Changes to the specifications of table 1 are further subject to the restrictions of sections 7 and 8. The required ordering of fields shall always be preserved. Note: It is advisable to keep both fields and records to a reasonable maximum length. 6.4.2 Repeating Records When a file contains records having repeated fixed formats, the user may drop the ISO 8211 leader/directory as specified in that standard. Note: This is most applicable to those modules that are relational in structure and should be transparent to the user. 7 Assignment of Fields to Records and Files This section assigns ISO 8211 field to ISO 8211 records and ISO 8211 records to ISO 8211 files. These assignments are determined by the specifications of part 1, table 3b with the further constraints of part 1, 4.1.3.4.1, section 7 of this part and ISO 8211 ordering constraints. 7.1 Global Modules Each ISO 8211 record shall contain the ISO 8211 fields representing one and only one module record. Each ISO 8211 file shall contain the ISO 8211 records representing the data of one and only one global module. 7.2 Other Modules The ISO 8211 records containing data from modules not included in 7.1 may contain ISO 8211 fields from one or more modules subject to the general constraints of this section. The ISO 8211 files containing data from modules not included in 7.1 may contain ISO 8211 records from one or more modules subject to the general constraints of this section. Note: The user should not indiscriminately merge unrelated modules. 7.3 Multivolume Files Nothing in this section shall prevent the user form constructing multi-volume files if this is required by the volume of data and supported by the media standards. Multi-volume files shall be described in the Catalog/Directory module. In the event the media do not support multi-volume files, any multiple files necessary to transfer large volumes of data shall be described in the Catalog/Directory module. 8 Record Structure See part 1, 4.1.3.4.1. A record may contain fields from more than one module. This section provides specifications for resolving and preventing conflicting associations of primary and secondary fields. 8.1 Restriction on Primary Fields in Level 2 Files A record in a level 2 file shall not contain two or more primary fields having, in that record, a common secondary field or fields. 8.2 Primary and Secondary Fields in Level 3 Files A record in a level 3 file may contain multiple primary fields without restriction. The logical association of primary fields with secondary fields shall be determined by the ISO 8211 inter-field tree structure (see ISO 8211 clauses 5.2.2 and 5.3.2). 8.3 Arbitrary Field Sequence In order to specify an arbitrary sequence of fields, a tree in which all fields are offspring of the ISO 8211 record identification field may be used. 9 Data Representation 9.1 Numeric Data Character representation of numeric data shall conform to ISO 6093 with the provision that FULL STOP, i.e., period, shall be used for the decimal mark. Numeric fields shall be right adjusted. 9.2 Dates A date in a numeric field shall be entered in the format YYYYMMDD. 9.3 Binary Data Binary data shall be represented in ISO 8211 bit fields and subfields. These bit fields shall conform to the specifications of ISO 8632-3. The ISO 8211 subfield widths shall be specified as B(n) and the additional X3.122 format information shall be placed in the applicable Data Dictionary/Domain or Data Dictionary/Schema or Internal Spatial Reference or Raster module. 10 Media Requirements The variable length records of ISO 8211 may be written on several media. This section specifies requirements for several standardized media. 10.1 General Requirements The ISO 8211 logical records shall be written, blocked and spanned across the media physical records (blocks, sectors or packets) without further record demarcations. Any unused bytes of the last media record of a file shall be filled with CARET characters (5/14). 10.2 Magnetic Tapes The ISO 8211 records shall be blocked and spanned into fixed length records of 2048 bytes in a blocksize of 2048 bytes conforming to level 2 of ANSI X3.27 and other applicable standards. 10.3 Flexible Diskettes Diskettes shall be written in conformance to ISO 9293. The ISO 8211 records shall be blocked and spanned into sectors without record delimiters or control fields other than the record length provided in ISO 8211. 10.4 Magnetic Tape Cartridges and Cassettes The ISO 8211 records shall be blocked and spanned into fixed length records of 2048 bytes in a blocksize of 2048 bytes conforming to level 2 of ANSI/ISO 4341 and other applicable standards. 10.5 Compact Disk Read Only Memory The ISO 8211 records shall be blocked and spanned into fixed length media records of 2048 bytes in a Logical Block size of 2048 bytes with Record Format = 0 conforming to level 1 of ISO 9660 and other applicable standards. 11 Conformance A Spatial Data Transfer file set is in conformance with this standard when all data files, records and fields are in conformance with the applicable media standards, ISO 8211, the specifications of part 3, sections 6 to 10 of this standard, and the required specifications of parts 1 and 2 of this standard. A single, simple README file, that informs the recipient of the nature of the file set, may be provided as the first file on a sequential media volume set and in the root directory of a random access media volume. Part 3 ANNEXES Informative Annex A: Guidelines for Private Agreements Private agreements limit the scope of transfer and are discouraged. Recurring needs for similar private agreements with a significant number of users should be referred to the maintenance organization of the standard. The inclusion of ancillary data should be accomplished within the framework of ISO 8211 by defining private tags, names and labels. Inasmuch as ISO 8211 permits the association of tags within records, there is no need to compromise the tags and labels of this standard and conforming software. The following guidelines insure that no compromise will exist: (a) Do not use the tags, names and labels of this standard with any other meaning or with controls not specified for use with them. (b) Define private agreement tags, names and labels as a completely separate set using lower case characters and in full compliance with ISO 8211. (c) Users anticipating the participation in private agreements should design software processing tags and fields within the context of ISO 8211 and subfields within the context of this standard. (d) Use the 0002 tag of ISO 8211 in the DDR to describe the nature of the private agreement and to alert the recipient of the presence of the agreement. Informative Annex B: Field and Subfield Names and Mnemonics Nomenclature of Annex B In this annex, the uppercase field tags and subfield labels are explicitly specified by part 3 of the standard as are the capitalized, lowercase field names. The lowercase subfield names are commentary from part 1. The required subfield labels, X, Y, Z, of spatial address fields are not tabulated. B.1 Field Tag and Field Name This annex is an alphabetical listing of all the ISO 8211 tags with their associated field names. They are specified by the mnemonics and field names of part 1 section 5. AFIL Area Fill Representation ARAD Arc Address ARC Arc ARID Area ID ATID Attribute ID ATPR Attribute Primary ATSC Attribute Secondary ATTP Primary Attributes ATTS Secondary Attributes CADR Curve Address CATD Catalog/Directory CATS Catalog/Spatial Domain CATX Catalog/Cross Reference CCID Chain Component ID CELL Cell CHID Chain ID CLRX Color Index COMP Composite CONF Conformance CPID Composite ID CVLS Cell Values DDDF Data Dictionary/Definition DDOM Data Dictionary/Domain DDSH Data Dictionary/Schema DMSA Domain Spatial Address DQAA Attribute Accuracy DQCG Completeness DQHL Lineage DQLC Logical Consistency DQPA Positional Accuracy EADS External Reference Spatial Address ELAD Ellipse Address ENID Endnode ID FONT Font Index FRID Foreign ID IADS Internal Reference Spatial Address IDEN Identification IREF Internal Spatial Reference LAID Line or Arc Foreign ID LATP Layer Attribute ID LDEF Layer Definition LINE Line LNID Line ID LNRP Line representation OBID Spatial Object ID OSAD Orientation Spatial Address PAID Primary Attribute Foreign ID PIDL Polygon ID Left PIDR Polygon ID Right PLID Polygon ID PNTS Point-Node POLY Polygon RATP Raster Attribute ID RFID Ring ID RGIS Registration RING Ring RPID Representation Module ID RSDF Raster Definition SADR Spatial Address SCUR Security SNID Startnode ID SPDM Spatial Domain SSAD Symbol Orientation Spatial Address STAT Transfer Statistics SYRP Symbol Representation TEXT Text Representation XREF External Spatial Reference B.2 Subfield Label and Subfield Name This section is an alphabetical listing of all subfield labels and their associated subfield names. The labels are specified by the mnemonics of part 1 section 5 as are the subfield names. ADMU Attribute Domain Value Measurement Unit ADSC Attribute Authority Description ADVF Attribute Domain Value Format AGOB Aggregate Object AGTP Aggregate Object Type ALTN Number of Lines per Alternation AQDT Acquisition Date AQMD Acquisition Device/Method ASPR Aspect Ratio ATLB Attribute Label ATYP Attribute Domain Type AUTH Attribute Authority BLCK Black Intensity Component BLUE Blue Component BMSK Bitmask BSCL Base Scale CHEX Character Expansion Factor CHHT Character Height CHSP Character Spacing CLAS Security Class CLDX Color Index CLOO Column Offset Origin CLXT Column Extent CMMD Data Compression Method CMNM Cell Module Name CMPR Data Compression CODE Cell Code COLI Column Index COMT Comment CTAD Center Address CTRL Control CVAL Cell value DAID Data ID DAST Data Structure DCDT Data Set Creation Date DEFI Default Implementation DFIN Definition DOCU Standard Documentation Reference DOMN Domain DSTP Domain Spatial Address Type DTYP Spatial Domain Type DVAL Domain Value DVDF Domain Value Definition EALB Entity/Attribute Label ENAD End Address EORA Entity or Attribute ETLB Entity Label EUTH Entity Authority EXSP External Spatial Reference EXTR External FFYN Composites FILE File FMT Format FNTN Font FSCN First Scan Direction FTDX Font Index FTLV Feature Level FTYP Fill Style Type GREN Green Component GTYN Vector Topology HDAT Horizontal Datum HFMT Horizontal Component Format HIDX Hatch Index INTR Intracell Reference Location KEY Key LNAM Layer Name LSCL Large Scale Maximum LTYP Line Type LWTH Line Width MAP Map MAXV Maximum Value MINV Minimum Value MJRA Conjugate Diameter Point-Major Axis MKSZ Marker Size MNRA Conjugate Diameter Point-Minor Axis MNRF Module Name Referred MNTF Module Type Referred MODN Module Name MPDT Map Date MVER Module Version MXLN Maximum Subfield Length NAM1 Name 1 NAM2 Name 2 NAME Name NCEL Number of Cells NCOL Number of Columns NLAY Number of Layers NREC Module Record Count NROW Number of Rows NSAD Spatial Address Count OBRP Object Representation ORDR Order PDOC Profile Documentation Reference PIDX Pattern Index PRID Profile Identification PROJ Projection PRVS Profile Version RAVA Range or Value RCID Record ID RCYN Raster RDOC Reference Documentation RECD Record RED Red Component RLIS Release Instructions ROWI Row Index RSNM Reference System Name RVDT Review Date RVIS Review Instructions RWOO Row Offset Origin RWXT Row Extent SANG Skew Angle SATP Spatial Address Type SCAL Scale SCOR Scan Origin SCPT Scan Pattern SDAT Sounding Datum SFAX Scale Factor X SFAY Scale Factor Y SFAZ Scale Factor Z SMKR Symbol Marker Type SOCI Scan Origin Column SORI Scan Origin Row SRCE Source SRFC Surface SSCL Small Scale Minimum STAD Start Address STID Standard Identification STVS Standard Version THEM Theme TIDS Tesseral Indexing Description TIDX Tesseral Indexing TIFT Tesseral Index Format TIND Tesseral Index TITL Title TPTH Text Path TYP1 Type 1 TYP2 Type 2 TYPE Type UNIT Unit USAG Usage Modifier UTXA Horizontal Text Alignment VDAT Vertical Datum VFMT Vertical Component Format VGYN Vector Geometry VOLM Volume VRES Vertical Resolution Component VTXA Vertical Text Alignment XHRS X Component of Horizontal Resolution XLBL Spatial Address X Component Label XORG X Origin YHRS Y Component of Horizontal Resolution YLBL Spatial Address Y Component Label YORG Y Origin ZONE Zone Number ZORG Z Origin B.3 Field Composition This section is an alphabetical listing of ISO 8211 tags with field names and an ordered list of their associated subfield labels with their subfield names. FIELD MNEMONIC SUBFIELD MNEMONIC FULL NAME AFIL Area Fill Representation MODN Module Name RCID Record ID BSCL Base Scale SSCL Small Scale Minimum LSCL Large Scale Maximum CLDX Color Index FTYP Fill Style Type HIDX Hatch Index PIDX Pattern Index ARAD Arc Address CTAD Center Address STAD Start Address ENAD End Address ARC Arc MODN Module Name RCID Record ID OBRP Object Representation SRFC Surface ORDR Order ARID Area ID MODN Module Name RCID Record ID ATID Attribute ID MODN Module Name RCID Record ID ATPR Attribute Primary MODN Module Name RCID Record ID ATSC Attribute Secondary MODN Module Name RCID Record ID ATTP Primary Attributes ATTS Secondary Attributes CADR Curve Address CATD Catalog/Directory MODN Module Name RCID Record ID NAME Name TYPE Type VOLM Volume FILE File RECD Record EXTR External MVER Module Version COMT Comment CATS Catalog/Spatial Domain MODN Module Name RCID Record ID NAME Name TYPE Type DOMN Domain MAP Map THEM Theme AGOB Aggregate Object AGTP Aggregate Object Type COMT Comment CATX Catalog/Cross Reference MODN Module Name RCID Record ID NAM1 Name 1 TYP1 Type 1 NAM2 Name 2 TYP2 Type 2 COMT Comment CCID Chain Component ID MODN Module Name RCID Record ID USAG Usage Modifier CELL Cell MODN Module Name RCID Record ID NCEL Number of Cells ROWI Row Index COLI Column Index TIND Tesseral Index CHID Chain ID MODN Module Name RCID Record ID USAG Usage Modifier CLRX Color Index MODN Module Name RCID Record ID RED Red Component GREN Green Component BLUE Blue Component BLCK Black Intensity Component COMP Composite MODN Module Name RCID Record ID OBRP Object Representation CONF Conformance FFYN Composites VGYN Vector Geometry GTYN Vector Topology RCYN Raster EXSP External Spatial Reference FTLV Feature Level CPID Composite ID MODN Module Name RCID Record ID CVLS Cell Values CVAL Cell value DDDF Data Dictionary/Definition MODN Module Name RCID Record ID EORA Entity or Attribute EALB Entity/Attribute Label SRCE Source DFIN Definition AUTH Attribute Authority ADSC Attribute Authority Description DDOM Data Dictionary/Domain MODN Module Name RCID Record ID ATLB Attribute Label AUTH Attribute Authority ATYP Attribute Domain Type ADVF Attribute Domain Value Format ADMU Attribute Domain Value Measurement Unit RAVA Range or Value DVAL Domain Value DVDF Domain Value Definition DDSH Data Dictionary/Schema MODN Module Name RCID Record ID NAME Name TYPE Type ETLB Entity Label EUTH Entity Authority ATLB Attribute Label AUTH Attribute Authority FMT Format UNIT Unit MXLN Maximum Subfield Length KEY Key DMSA Domain Spatial Address DQAA Attribute Accuracy MODN Module Name RCID Record ID COMT Comment DQCG Completeness MODN Module Name RCID Record ID COMT Comment DQHL Lineage MODN Module Name RCID Record ID COMT Comment DQLC Logical Consistency MODN Module Name RCID Record ID COMT Comment DQPA Positional Accuracy MODN Module Name RCID Record ID COMT Comment EADS External Reference Spatial Address ELAD Ellipse Address MJRA Conjugate Diameter Point-Major Axis MNRA Conjugate Diameter Point-Minor Axis ENID Endnode ID MODN Module Name RCID Record ID FONT Font Index MODN Module Name RCID Record ID FNTN Font FRID Foreign ID MODN Module Name RCID Record ID USAG Usage Modifier IADS Internal Reference Spatial Address IDEN Identification MODN Module Name RCID Record ID STID Standard Identification STVS Standard Version DOCU Standard Documentation Reference PRID Profile Identification PRVS Profile Version PDOC Profile Documentation Reference TITL Title DAID Data ID DAST Data Structure MPDT Map Date DCDT Data Set Creation Date SCAL Scale COMT Comment IREF Internal Spatial Reference MODN Module Name RCID Record ID COMT Comment SATP Spatial Address Type XLBL Spatial Address X Component Label YLBL Spatial Address Y Component Label HFMT Horizontal Component Format VFMT Vertical Component Format SFAX Scale Factor X SFAY Scale Factor Y SFAZ Scale Factor Z XORG X Origin YORG Y Origin ZORG Z Origin XHRS X Component of Horizontal Resolution YHRS Y Component of Horizontal Resolution VRES Vertical Resolution Component LAID Line or Arc Foreign ID MODN Module Name USAG Usage Modifier RCID Record ID LATP Layer Attribute ID MODN Module Name RCID Record ID LDEF Layer Definition LNAM Layer Name CODE Cell Code FMT Format BMSK Bitmask NROW Number of Rows NCOL Number of Columns MINV Minimum Value MAXV Maximum Value SORI Scan Origin Row SOCI Scan Origin Column RWOO Row Offset Origin CLOO Column Offset Origin INTR Intracell Reference Location COMT Comment LINE Line MODN Module Name RCID Record ID OBRP Object Representation LNID Line ID MODN Module Name RCID Record ID USAG Usage Modifier LNRP Line representation MODN Module Name RCID Record ID BSCL Base Scale SSCL Small Scale Minimum LSCL Large Scale Maximum CLDX Color Index LTYP Line Type LWTH Line Width OBID Spatial Object ID MODN Module Name RCID Record ID OSAD Orientation Spatial Address PAID Primary Attribute Foreign ID MODN Module Name RCID Record ID ATLB Attribute Label PIDL Polygon ID Left MODN Module Name RCID Record ID PIDR Polygon ID Right MODN Module Name RCID Record ID PLID Polygon ID MODN Module Name RCID Record ID PNTS Point-Node MODN Module Name RCID Record ID OBRP Object Representation POLY Polygon MODN Module Name RCID Record ID OBRP Object Representation RATP Raster Attribute ID MODN Module Name RCID Record ID RFID Ring ID MODN Module Name RCID Record ID USAG Usage Modifier RGIS Registration MODN Module Name RCID Record ID COMT Comment RING Ring MODN Module Name RCID Record ID OBRP Object Representation RPID Representation Module ID MODN Module Name RCID Record ID RSDF Raster Definition MODN Module Name RCID Record ID OBRP Object Representation AQMD Acquisition Device/Method AQDT Acquisition Date COMT Comment CMNM Cell Module Name DEFI Default Implementation CMPR Data Compression CMMD Data Compression Method RWXT Row Extent CLXT Column Extent SCOR Scan Origin SCPT Scan Pattern TIDX Tesseral Indexing TIFT Tesseral Index Format TIDS Tesseral Indexing Description ALTN Number of Lines per Alternation FSCN First Scan Direction ASPR Aspect Ratio NLAY Number of Layers SADR Spatial Address SCUR Security MODN Module Name RCID Record ID CLAS Security Class CTRL Control RLIS Release Instructions RVDT Review Date RVIS Review Instructions COMT Comment SNID Startnode ID MODN Module Name RCID Record ID SPDM Spatial Domain MODN Module Name RCID Record ID DTYP Spatial Domain Type DSTP Domain Spatial Address Type COMT Comment SSAD Symbol Orientation Spatial Address STAT Transfer Statistics MODN Module Name RCID Record ID MNTF Module Type Referred MNRF Module Name Referred NREC Module Record Count NSAD Spatial Address Count SYRP Symbol Representation MODN Module Name RCID Record ID BSCL Base Scale SSCL Small Scale Minimum LSCL Large Scale Maximum CLDX Color Index SMKR Symbol Marker Type MKSZ Marker Size TEXT Text Representation MODN Module Name RCID Record ID BSCL Base Scale SSCL Small Scale Minimum LSCL Large Scale Maximum CLDX Color Index CHHT Character Height FTDX Font Index TPTH Text Path UTXA Horizontal Text Alignment VTXA Vertical Text Alignment CHEX Character Expansion Factor CHSP Character Spacing SANG Skew Angle XREF External Spatial Reference MODN Module Name RCID Record ID COMT Comment RDOC Reference Documentation RSNM Reference System Name VDAT Vertical Datum SDAT Sounding Datum HDAT Horizontal Datum ZONE Zone Number PROJ Projection