Under Review
over 2 years ago

Fenix 7 series - MapView setMapVisibleArea doesn't zoom to the same map view like Fenix 6 series

Fenix 7 series - MapView setMapVisibleArea doesn't zoom to the same map view like Fenix 6 series.

Although the devices do have the same display resolution (e.g. F6X and F7X with 280x280 pixel) the setMapVisibleArea do behave different on each device series.

On F7 series devices the location/position coordinates have to be scaled nearly 100 time more to achieve the same zoom level on the map.

Please provide a common interface to avoid a device class filter in the app code.

Thanks for upcoming fix.

  • I was just looking to see if this is still an issue and on my Epix (Gen 2) running beta FW 17.14 this appears to now be fixed. Unfortunately, I did not test with the latest stable Epix 2 firmware (16.22) before installing beta 17.12 so I do not know if this was fixed in the 16.xx cycle or if this is fixed in the 17.xx cycle. But either way, this may finally be fixed.

  • to verify this bug it is realy simple

    - uder the interface of MapView setMapVisibleArea and scale to a defined area on the map

    - do the same scaling on a F7

    - do the same scaling on a F6

    => the visible area/zoomed map view is different on both devices

    the scaling is different for devices with similar screen resolution but should not.

    bug is still valid, but how cares...

    Hint: verify the bug with this widget/app: apps.garmin.com/.../ffcee43d-ef4f-4175-a55a-c46b6cc2918d

  • I do not have a Fenix 7 to confirm but given that the original poster (OP) experienced it on the F7 and I see it on the Epix (Gen 2) it would seem to be related to the entire F7 series codebase. Can I email you the source code I built out to replicate the issue? Perhaps you can confirm it and pass along to the Fenix 7 device team? I have already reported it here but they haven't actioned anything.

  • I have not seen this issue, if anything this will be a device side issue, CIQ do not control the scaling of the maps, it just passed the parameters for the native map module which renders it. Do you see any differences in the native map implementation across these devices?