Some how migrating geo location images does not work as planned!?
After migration i can not turn off the first map, since it was moved to the untagged tag, while the new sat image was placed on its own tag inside the geolocate folder.

Any specific reason why this migration feature does this in sup2025?
PS yes i know, i could have used an older version like sup24, but i only want/have two instances of the program installed, stable 22 with discontinued geo location and the latest 2025 with issues 
Sorry to hear that the migration failed, i’m glad that it was relatively easy to fix on your end.
Thank you for the bug report, we will investigate the root cause of this and get back to you.
This migration should only occur if you have a geolocation import prior to the 3d buildings feature being released. So fingers crossed you won’t experience this issue again.
1 Like
@AnnoNiem Looks like we had a logical error during the migration which meant we weren’t assigning the tags correctly, which we did not catch during development/testing. A fix has been pushed to production to correct the behaviour.
Thanks again for bringing this to our attention.
1 Like
@matthew_rooney happy to read it was fixable!
You’re most welcome.
1 Like