Download
1 / 14
140 likes | 210 Views
XML2PersonalGDB. The XML2PGDB utility loads and validates transactions from an XML document into a copy of the original extract data. The updates can then be QC’ed to ensure that they were applied correctly. This process mimics the
E N D
The XML2PGDB utility loads and validates transactions from an XML document into a copy of the original extract data. The updates can then be QC’ed to ensure that they were applied correctly. This process mimics the USGS load and validate process used in updating the national database.
XML2PersonalGDB Checks 1. verifies that all records in the NHDStatus table are also in one of the feature class tables, the NHDVerticalRelationship, or the NHDReachCode_ComID tables in the original extract data. 2. verifies that the NHDProcessingParameters table is properly populated. 3. verifies that all records in the NHDReachCrossReference table are properly populated. 4. verifies that all new Reachcodes are in the NHDReachCode_ComID table. 4. verifies that all features with a common Reachcode also have the same GNIS_ID & GNIS_Name. 5. verifies that the XML is in a geographic coordinate system. 6. verifies that there is no network in the original extract data.
Program Files NHDUtilities XML2PersonalGDB
Open GDB File - Browse to Personal GDB File In 1804_qc folder (Copy of original extract 1804_gdb)
Load Notice that Input RCL File has been automatically populated
Successful Completion: See next slide for Un-Successful Completion (Debug File)
Example XML2PGDB debug file Error occured 5/24/2005 4:15:24 PM Record Call Stack Sequence - Bottom line is error line. ProcessXMLTransactions LoadXML2GDB Line : 762 ReportError CommonProcedures Line : 144 Description No CreateMetadata transactions found. The input file must contain at least 1 CreateMetadata transaction. --------------------------------------------------------------------------------------------------------------------------------- Error occured 8/26/2005 11:19:17 PM Record Call Stack Sequence - Bottom line is error line. Description ERROR: NHD.NHDFlowline_High Feature139341758: Reachcode 10290201007833 does not exist (-9) Description ERROR: NHD.NHDFlowline_High Feature 139341759: Reachcode 10290201007834 does not exist (-9) --------------------------------------------------------------------------------------------------------------------------------- Error occured 6/7/2005 4:04:42 PM Record Call Stack Sequence - Bottom line is error line. ProcessXMLTransactions LoadXML2GDB Line : 890 ModifyFeature 132630029: LoadXML2GDB Line : 1212 StoreFeatureGeometry LoadXML2GDB Line : 2469 StoreLine LoadXML2GDB Line : 2568 Description The coordinates or measures are out of bounds. (-2147220936) --------------------------------------------------------------------------------------------------------------------------------- Error occured 11/4/2005 5:21:56 PM Record Call Stack Sequence - Bottom line is error line. ProcessXMLTransactions LoadXML2GDB Line : 934 ModifyFeature 112672735: LoadXML2GDB Line : 1310 ReportError CommonProcedures Line : 148 Description ModifyFeature 112672735: Feature not found (-9)
Fixing errors in the debug file • Error-correction is best performed on the projected data (usually, the alb.mdb file), which is then reprojected into geographic coordinates, and then re-extracted into XML. • When re-running XML2PGDB, ensure that the target QC personal geodatabase file is a brand-new copy of the original unprojected data. • Don’t forget to remove any networks from either the corrected data or the QC data before re-running XML2PGDB
(Fixing errors in the debug file) Description No CreateMetadata transactions found. The input file must contain at least 1 CreateMetadata transaction. Solution Create metadata record using NHD Geo Edit Tools, rerun XML2PGDB Description NHD.NHDFlowline_High Feature 139341759: Reachcode 10290201007834 does not exist (-9) Solution Fix entries in NHDStatus, NHDReachCrossReference, NHDReachCodeComID tables, rerun XML2PGDB Description The coordinates or measures are out of bounds. (-2147220936) Solution Project edited personal geodatabase from projected system into geographic system, re-extract XML data, rerun XML2PGDB Description ModifyFeature 112672735: Feature not found (-9) Solution 1. determine if NHDStatus table has a delete or create record for this feature 2. remove network from both GEO and (new copy of) QC personal geodatabases and rerun XML2PGDB Description GNIS attributes of feature -1507 were not the same as the GNIS attributes of other features with reachcode 16020204000040 Solution Find feature -1507, compare GNIS_ID and GNIS_Name to those of other features with the same Reachcode, modify GNIS_ID and GNIS_Name of feature -1507, rerun XML2PGDB Description NHDVerticalRelationship -331: Invalid AboveComId in vertical relationship Solution Create metadata record using NHD Geo Edit Tools, rerun XML2PGDB
(Fixing errors in the debug file) Description No NHDReachcode_comid record found for reachcode ‘10040101004800’ Solution Stewardship partners must contact USGS before this fix to confirm that the error occurs in the distribution database: 1. Add a record into the Reachcode_ComID table with a unique negative ComID, GNIS_ID, GNIS_Name, and the (confirmed) pre-existing ReachCode that caused the error (e.g. 10040101004800’) 2. Add a record into the NHDStatus table with the negative ComID and status set to “Add Feature”
