7/23/09 NCGMP09 -- a proposed standard format for digital publication of geologic maps version 0.8.2b, July 23, 2009 By USGS National Geologic Map Database Project and Pacific Northwest Geologic Mapping Project [Contributors: Ralph Haugerud, Stephen Richard, David Soller, and Evan Thoms (in alphabetical order)] CONTENTS: 1) NCGMP09-0.8.2.doc and NCGMP09-0.8.2.pdf -- documentation of design 2) NGMDB_Vocabs_5-2009 -- NGMDB standard vocabularies, specified in NCGMP09 3) NCGMP09_Template9.3_7-23-09.mdb -- Arc 9.3 template for NCGMP09 4) NCGMP09_Template8.3_7-23-09.mdb -- Arc 8.3 template for NCGMP09 5) NCGMP09_tools-0.8.2 -- scripts to create and validate NCGMP09 database structure 6) Example_map_databases_7-23-09: A) Nearly complete implementation of NCGMP09, for Tonto National Forest map (version 9.3 geodatabase) (Steve Richard, 5/1/09). Symbol identifiers are AzGS internal symbol numbers; we're still working a scheme to map these to FGDC symbols. The OrientationPoints are not symbolized because they depend on AzGS fonts. We're working on a representation-based scheme. B) Tonto National Forest map, in Arc v. 8.3 (Steve Richard, 7/23/09) C) Partial implementation of NCGMP09 for the Camas quad in WA,OR (see also http://pubs.usgs.gov/sim/3017/) (Evan Thoms, 5/7/09). Note how the original LTYPE values have been parsed into separate fields in the line feature classes, how features are symbolized off the FGDCSymbol field (and the accompanying problem of displaying a readable symbol type label - layer files are included in the zip file in addition to a style file for this purpose), the implementation of the DescriptionOfMapUnits (DescriptionOfMapUnits has been joined to MapUnitPolys and is browsable in the mxd through the use of the HTML popup tool), and how ExtendedAttributes are browsable through relates built in the map, particulaly GeochemistryPoints and GeochronPoints and a couple of the faults which are subsets of a larger structure. To browse StandardLithology and ExtendedAttributes entries for specific map unit polys, you will have to remove the join on MapUnitPolys, build relates between DescriptionOfMapUnits and StandardLithology and/or ExtendedAttributes (MapUnit is the key field), and then build a relate between MapUnitPolys and DescriptionOfMapUnits. COMMENTS? Please contact us at ncgmp09@flagmail.wr.usgs.gov ------------------------------------------------------ ------------------------------------------------------ PREVIOUS VERSIONS: Version 0.8.2 (May 15, 2009) CONTENTS: 1) NCGMP09-0.8.2.doc and NCGMP09-0.8.2.pdf -- documentation of design 2) NGMDB_Vocabs_5-2009 -- NGMDB standard vocabularies, specified in NCGMP09 3) NCGMP09_Template9.3_4-27-09.mdb -- Arc 9.3 template for NCGMP09 4) NCGMP09_scripts_0.8.2 -- scripts to create and validate NCGMP09 database structure 5) Example_map_databases_5-15-09: A) nearly complete implementation of NCGMP09, for Tonto National Forest map (version 9.3 geodatabase) (Steve Richard, 5/1/09). Symbol identifiers are AzGS internal symbol numbers; we're still working a scheme to map these to FGDC symbols. The OrientationPoints are not symbolized because they depend on AzGS fonts. We're working on a representation-based scheme. B) Partial implementation of NCGMP09 for the Camas quad in WA,OR (see also http://pubs.usgs.gov/sim/3017/) (Evan Thoms, 5/7/09). Note how the original LTYPE values have been parsed into separate fields in the line feature classes, how features are symbolized off the FGDCSymbol field (and the accompanying problem of displaying a readable symbol type label - layer files are included in the zip file in addition to a style file for this purpose), the implementation of the DescriptionOfMapUnits (DescriptionOfMapUnits has been joined to MapUnitPolys and is browsable in the mxd through the use of the HTML popup tool), and how ExtendedAttributes are browsable through relates built in the map, particulaly GeochemistryPoints and GeochronPoints and a couple of the faults which are subsets of a larger structure. To browse StandardLithology and ExtendedAttributes entries for specific map unit polys, you will have to remove the join on MapUnitPolys, build relates between DescriptionOfMapUnits and StandardLithology and/or ExtendedAttributes (MapUnit is the key field), and then build a relate between MapUnitPolys and DescriptionOfMapUnits. --- END ---