Hallo Norman,
I recreated the xml-file in SNAP in the Graph Builder. The results:
The Graph Builder in SNAP creates an xml file where the Write-operator follows right after the Read-operator, after that all other operators as they are manually added in the Graph Builder. In Nest this was no problem, but indeed, in SNAP this order is a problem! I have to open the xml in an editor and move the Write-operator to the very end. Doing this, this command works:
gpt C:\Calib_Spk_TC_LinDB_RS2_Barents.xml -Pfile=“C:\RS2_20150209\product.xml” -Ptarget=“C:\test.dim”
Using the -t option, however, only works when completely removing the Write-operator.
The bug is therefore that SNAP creates an order of operators in the Graph Builder which it cannot handle. It would be best if it was not order-sensitive just as NEST was.
Another “bug” in a way: in NEST the command line showed a progress bar. This does not seem to be the case in SNAP, but this was very useful.
[EDIT: After testing I realize that the -Ptarget option has the same prpblems above in NEST as it has in SNAP, I just never stumbled over it in NEST. -t file works best but only when the write module is removed.
For some very strange reason my wrong use of -Tfile in NEST trying to replace $target in the xml Write module gave correct results! No idea how that can work, but it still does … it seems to replace target correctly … ]