Thanks for the feedback, Phil. We've corrected the Australia map so the inset is now correctly recognised. Points placed on Tasmania have correct lat/lon, and vice versa - points with lat/lon in tasmania appear inside the map inset.

You'll need tonight's build of 2.5 (b196) or later for this to work. In older versions of Omniscope, the old behaviour will take effect as if the inset wasn't there.

Hi Steve
I downloaded b196 but still had the problem, i downloade the Austalian map agai and still had the issue
Is there anything i need to to to correct?
Cheers
Phil

Phil,

I've checked that b196 has the fix, and the map on our website has been updated. Can you try closing and restarting Omniscope before trying again?

Here's how I tested it:
* I chose "Open map" from the welcome screen, and chose Australia. The first test, I was prompted to download the updated map; you should only see this once, and never again.
* I added another map view, and changed it to the World map.
* I set both map views to be in "Mode: Place marker".
* I placed some markers in mainland Australia, on both maps, and each time verified they appeared on the other map.
* I did the same for Tasmania.

When placing markers on the World map in Tasmania, this creates valid lat/lon values for the problem case you are referring to. In my test, I saw them appear in the correct position on the inset map.

Note: placing markers in the small part of mainland Australia in the inset map won't work, as this area is duplicated in the main map.

Can you give some sample lat/lon values that are broken?

Steve