wv_correct Fails on New-style Vantor/Maxar XML Metadata with Namespaces

[Claire Porter]

Hi ASP team,

Vantor/Maxar recently started producing imagery with a new Catalog ID naming scheme that now includes a B as the first character (e.g., B020001100583F10) and uses namespaces in their XML metadata.  This seems to break wv_correct for WV01 imagery and may have consequences in other ASP utilities.  Here's the error we get from wv_correct.

ERROR: XML file "WV01_20260721214043_B020001100583F10_26JUL21214043-P1BS-600000237725_01_P017.xml" is lacking a valid image scan direction.

Looking at the v3.6.0/v3.7.0 wv_correct code, it is using methods like getTagName()/getElementsByTagName() which treat the full namespace:tagname string as one when parsing the XML, so we believe the DG namespaced metadata is causing wv_correct to read the XML as essentially empty.  The Xerces library also provides getLocalName()/getElementsByTagNameNS("*", ...) which ignores namespaces, so it is potentially a simple fix.

https://github.com/NeoGeographyToolkit/StereoPipeline/blob/5b20f704a7f40d717805aed5ec477724656248bd/src/asp/Camera/RPC_XML.cc#L836

https://github.com/NeoGeographyToolkit/StereoPipeline/blob/5b20f704a7f40d717805aed5ec477724656248bd/src/asp/Camera/XMLBase.h#L64

 

We can provide an example stereo pair if necessary. Many thanks,

Claire

--

Claire Porter

Polar Geospatial Center

University of Minnesota

612-625-6089

[Claire Porter]

Apologies for the incomplete post.  Here is a sample of the new XML style:

<?xml version='1.0' encoding='UTF-8'?>
<lv1b:isd xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:isdc="urn:X-maxar:product:producesvc:common:1.0" xmlns:lv1b="urn:X-maxar:product:producesvc:level1b:1.0">
  <lv1b:IMD>
    <isdc:VERSION>29.9</isdc:VERSION>
    <isdc:GENERATIONTIME>2026-06-01T20:38:01.000000Z</isdc:GENERATIONTIME>
    <isdc:PRODUCTORDERID>600000003935_01_P001</isdc:PRODUCTORDERID>
    <isdc:PRODUCTCATALOGID>None</isdc:PRODUCTCATALOGID>
    <isdc:IMAGEDESCRIPTOR>Basic1B</isdc:IMAGEDESCRIPTOR>
    <isdc:BANDID>Multi</isdc:BANDID>
    <isdc:PANSHARPENALGORITHM>None</isdc:PANSHARPENALGORITHM>
    <isdc:NUMROWS>9216</isdc:NUMROWS>
    <isdc:NUMCOLUMNS>9216</isdc:NUMCOLUMNS>
    <isdc:PRODUCTLEVEL>LV1B</isdc:PRODUCTLEVEL>
    <isdc:PRODUCTTYPE>Basic</isdc:PRODUCTTYPE>
    <isdc:NUMBEROFLOOKS>1</isdc:NUMBEROFLOOKS>
    <isdc:RADIOMETRICLEVEL>Corrected</isdc:RADIOMETRICLEVEL>
    <isdc:BITSPERPIXEL>16</isdc:BITSPERPIXEL>
    <isdc:COMPRESSIONTYPE>JPEG2000</isdc:COMPRESSIONTYPE>

...

[Oleg Alexandrov]

Claire,

I had Claude cook something up based on your XML preamble. Looks legit. Will be in build 2026-08-05 at our usual release page likely within a day. You can try testing it with a full stereo pair.

(BTW, as to our long-standing wish to have wv_correct support WV-3, it is in principle still on our radar, depending on our funding overlord priorities, just need to disentangle it from jitter properly and the signal is still subtle.)

Oleg

--
You received this message because you are subscribed to the Google Groups "Ames Stereo Pipeline Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ames-stereo-pipeline...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ames-stereo-pipeline-support/CAOr40CbWPjGaSiiUV-%3DP6obOsFop2Bhzvs4QLiew_x%2B7NJSXmg%40mail.gmail.com.