Hi @rheinason,
I’ve been able to fix the issue in VisualARQ 2.7.4. This was a change we made for Lands in Tibidabo (shared plug-in between Lands and VisualARQ), and we are swapping latitude and longitude by mistake.
As soon as the first build is finished I’ll post it here so you can test if the fix works.
Regards,
Enric