Bug in Subset ! Needs to Report

[blueyeti1881]

The Subset Generally works along with large range of set of input products. But when used Multi InSAR product, it fails to copy the Slave_Metadata and history node under Metadata information using GPT and xml.

When using Radar > Subset GUI , it successfully does copies all metadata but only when using GPT xml, it fails to add these two node in metadata

In the image both are subset using same input. The bottom is using Radar > Subset (GUI) that has 5 nodes under Metadata but upper one is using .xml that only has three nodes and don’t copy the Slave_Metadata and history section. I think this is a bug as I don’t see any option to solve this.

[diana_harosa]

Jira ticket SNAP-4155 created

[blueyeti1881]

Solution

Product Subset Dialog vs Graph Subset issue with Snaphu Export

Thank you for getting back to me. I figure out the solution. When using xml, there copy metadata option is false by default, if we change it to true then the issue get resolved. I appreciate your help.

[Sandy_Casper]

That’s a weird one with the subsetting. Usually, when the metadata or the bounds don’t match up after a crop, it’s a tiny glitch in how the coordinates are being read by the processor. Have you tried doing the subset through the GPT command line to see if it behaves differently than the GUI? Sometimes a quick refresh of the product nodes or clearing the cache helps reset those “invisible” offsets too.