1 / 10

XML Extract

XML Extract. Paul Kimsey - 3/20/2006 Modified - 4 August 2009. XMLExtract creates a XML document containing all feature records in the NHDStatus table. The XML document is used to load edits to the original Personal GDB and the National Database.

evonne
Download Presentation

XML Extract

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XML Extract Paul Kimsey - 3/20/2006 Modified - 4 August 2009

  2. XMLExtract creates a XML document containing all feature records in the NHDStatus table. The XML document is used to load edits to the original Personal GDB and the National Database. See 1804_alb.xml for example document See 1804_alb.rcl for example document

  3. XMLExtract Checks • XMLExtract verifies all records in the NHDStatus table are in one of the feature classes or the NHDVerticalRelationship or the NHDReachCode_ComID table. • 2. XMLExtractverifies the NHDProcessingParameters table is populated properly. • 3. XMLExtract verifies all records in the NHDReachCrossReference table are properly populated. • 4. XMLExtract verifies all records in the NHDFeatureToMetadata • Table are populated correctly when more than one Metadata • record exists in the NHDStatus table

  4. Programs NHDUtilities XMLExtract

  5. Browse to Input Personal GDB File

  6. Select Personal GDB File Open

  7. Create XML Notice that the Output XML File has been populated for you

  8. Successful Completion: For Un-Successful Completion see next slide (Example Debug File)

  9. Example XMLExtract debug file Error occurred 11/30/2005 8:54:52 AM Record Call Stack Sequence – Bottom line is error line. ProcessNHDStatusRecords XMLExtractModule Line : 609 ReportError Errorhandeling Line : 39 Description Feature or relationship with COMID -244 not found Error occurred 11/30/2005 8:56:04 AM Record Call Stack Sequence – Bottom line is error line. ProcessNHDStatusRecords XMLExtractModule Line : 609 ReportError Errorhandeling Line : 39 Description Feature or relationship with COMID -10112 not found Error occurred 11/30/2005 8:56:28 AM Record Call Stack Sequence – Bottom line is error line. ProcessNHDStatusRecords XMLExtractModule Line : 609 ReportError Errorhandeling Line : 39 Description Feature or relationship with COMID 38686647 not found The three errors above represent a case in which the COMID exists in the status table but does not exist in the feature layers. Resolution: For each feature layer, select by attribute where COMID = 0 If possible, match the features with COMID = 0 to the cooresponding update records in the status table. If this is not possible, remove records from status table

  10. Output: 1804_geo.rcl, 1804_geo.xml

More Related