Hi Luis,
thanks for checking this. Did you try to reproduce our issue via GUI or GPT? We are always using GPT and are still forced to use Version 1.1.2. because of another issue already reported on the STEP forum, so we are actually quite interested to know how you managed to successfully process the data, using the new release, at all? We are aware that in principle older versions are not supported but I will sent you a separate email on this topic later today.
But back to the issue discussed in this topic: In another test we did, we noticed that if we switch the products being used as master and slave in the BackGeocoding step the shifting issue is removed. So there really is something fishy going on here…
Best regards,
Sven.