Error: [NodeId: TOPSAR-Split] java.util.NoSuchElementException

Hello everyone,

I’m using snap from the gpt command line tool and I’m getting the following error:
Error: [NodeId: TOPSAR-Split] java.util.NoSuchElementException

the graph I’m trying to run is the following:

and the corresponding command is this:

'/home/user/snap/bin/gpt' '/home/user/preprocess/RES/TOPSAR_Coreg_ifg_ESD_Polariz_wkt.xml' '-Pinput1=/mnt/large_drive/test/00_data/S1A_IW_SLC__1SDV_20190108T170653_20190108T170720_025389_02CFCA_76BF.SAFE/manifest.safe' '-Pinput2=/mnt/large_drive/test/00_data/S1B_IW_SLC__1SDV_20190102T170611_20190102T170638_014318_01AA3A_DF7C.SAFE/manifest.safe' '-Pinput3=IW3' '-Pinput4=POLYGON ((10.3736250515922 46.2926414044154, 11.437197045721 46.2926414044154, 11.437197045721 46.8928102266238, 10.3736250515922 46.8928102266238, 10.3736250515922 46.2926414044154))' '-Pinput5=VV', '-Pinput6=false', '-Ptarget1=/mnt/large_drive/test/01_ifg/20190108_20190102_SLC_Coregistered_VV_IW3.dim' '-Ptarget2=/mnt/large_drive/test/01_ifg/20190108_20190102_SLC_Coregistered_VV_IW3_nocorrect.dim' '-Ptarget3=/mnt/large_drive/test/01_slc/20190108_20190102_SLC_Coregistered_VV_IW3im.dim'

I’m running on Ubuntu 18.04 with the latest version of SNAP installed with all the toolboxes, downloaded from here SNAP Download – STEP

What should I check? Why is it not finding the TOPSAR-Split operator?

Accorindg to this post it seems to happen when the wktAoi paramteers is used:

I don’t know why. Maybe @lveci can help here?

It culd be that some characters in the wkt are not valid for the XML.
How is your AOI defined?
If you follow this defineiont, ther e should actually be now problem.
Well Known Text – GISWiki

The strange thing is that the same process used to work couple of weeks ago. Removing the AOI seems to solve the problem. Did the last update introduce something new in the AOI definition?

Edit: the process dies OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f7f84f00000, 268959744, 0) failed; error=‘Cannot allocate memory’ (errno=12)

@marpet Anyway, the wktAoi is defined correctly POLYGON ((10.3736250515922 46.2926414044154, 11.437197045721 46.2926414044154, 11.437197045721 46.8928102266238, 10.3736250515922 46.8928102266238, 10.3736250515922 46.2926414044154))

Is it possible to roll back to an older version of snap and being able to retrieve the orbit files? This is why I was forced to update it recently.

Yes, the wkt looks good. And actually wkt does not contain any characters which need to be escaped in XML.

I’m not familiar with SAR processing and which changes has been made in the past. So, this should be answered by @lveci or @jun_lu.

@lveci could you check this one please?

The only recent change has been to support the new RFI metadata.

I’ve been able to get a NoSuchElement exception when the aoi doesn’t intersect any of the bursts.
In this case it will now throw “wktAOI does not overlap any burst”