organicmaps/organicmaps-tmp

Archived

Fork 1

Too much information in navigation mode #1656

New issue

Open

opened 2021-12-04 18:58:36 +00:00 by arnaudvergnet · 9 comments

arnaudvergnet commented

2021-12-04 18:58:36 +00:00

(Migrated from github.com)

When navigating, we do not need all this information. Magic earth does this very well by only showing information around the bottom of the viewport, where the gps position usually is. So when navigating we see useful information around our position, and if we pan the map we can still see information away from our position. In OM, every POI in the viewport is shown, but as the camera is tilted, it can be very far away.

In my opinion, OM could benefit a lot from following the same approach as Magick Earth. Maybe also make the few information visible bigger, as when navigating we are usually far away from the phone and only give short glances.

OM Car mode	OM Bicycle mode	Magik Earth

OS: Android 9
Organic Maps version: 2021.11.04-2-F-Droid
Data Version: 211022

Navigation mode shows way too much information, it looks really cluttered and can get very poor performance in some dense areas. It is the most visible in bike or foot mode, where nearly every POIs are shown. Car mode is a bit better as it hides most of them, but it still shows every house number and road names. When navigating, we do not need all this information. Magic earth does this very well by only showing information around the bottom of the viewport, where the gps position usually is. So when navigating we see useful information around our position, and if we pan the map we can still see information away from our position. In OM, every POI in the viewport is shown, but as the camera is tilted, it can be very far away. In my opinion, OM could benefit a lot from following the same approach as Magick Earth. Maybe also make the few information visible bigger, as when navigating we are usually far away from the phone and only give short glances. | OM Car mode | OM Bicycle mode | Magik Earth | |-|-|-| | ![Screenshot_20211204-182941_Organic_Maps](https://user-images.githubusercontent.com/80701113/144720692-aaa6bd4a-0bb5-40d1-9612-87c7cf2c913c.png) | ![Screenshot_20211204-193112_Organic_Maps](https://user-images.githubusercontent.com/80701113/144720696-53fc0873-4040-499b-8997-b5aecf314480.png) | ![Screenshot_20211204-192617_Magic_Earth](https://user-images.githubusercontent.com/80701113/144720710-9d742b57-c6a3-4f3f-b842-be42941a09f1.png) | - OS: Android 9 - Organic Maps version: 2021.11.04-2-F-Droid - Data Version: 211022

👍 2 👎 1

biodranik commented

2021-12-04 23:34:34 +00:00

(Migrated from github.com)

It is related to #1577

👍 1

arnaudvergnet commented

2021-12-23 13:19:39 +00:00

(Migrated from github.com)

Toulouse is not even that big of a city, it must be even worse in capital cities and such. I am using a Fairphone 3, which does not have the best hardware but should be decent enough to run a map application without issues.

https://user-images.githubusercontent.com/80701113/147245092-71f63bf0-fdbe-484d-8ca6-3cdf859661ad.mp4

I really think this issue should be top priority. It makes using navigation modes other than car unusable in cities. In the end, I always en up working only with the route preview and never starting the actual navigation.

To insist on how important this issue is, here is a recording of me trying to move the camera while navigating on bike in the city of Toulouse. There is so much information on screen the phone struggles to keep up. If you look closely, you will notice it lagged so much it even locked me in perspective view when I stopped the navigation. Toulouse is not even that big of a city, it must be even worse in capital cities and such. I am using a Fairphone 3, which does not have the best hardware but should be decent enough to run a map application without issues. https://user-images.githubusercontent.com/80701113/147245092-71f63bf0-fdbe-484d-8ca6-3cdf859661ad.mp4 I really think this issue should be top priority. It makes using navigation modes other than car unusable in cities. In the end, I always en up working only with the route preview and never starting the actual navigation.

👎 1

biodranik commented

2021-12-23 13:46:30 +00:00

(Migrated from github.com)

This should be fixed by a proper "navigation" style. There are already several style-related issues in GH.

👍 1

vng commented

2022-02-06 19:23:01 +00:00

(Migrated from github.com)

@arnaudvergnet Since you can reproduce the issue, please try to turn off 3D buildings in settings, restart the app and try again.

arnaudvergnet commented

2022-02-06 21:36:32 +00:00

(Migrated from github.com)

No 3d buildings

https://user-images.githubusercontent.com/80701113/152702147-1bc60ab7-2cd1-46d3-9f26-d677ad383cdc.mp4

No perspective

https://user-images.githubusercontent.com/80701113/152702150-63587a9d-f262-4a34-a234-6e5a65bd21f9.mp4

Disabling 3d buildings helps especially on low zoom levels. But the more you zoom in, the more perspective gets applied and performance starts to get worse. As expected disabling perspective fixes the issue. **No 3d buildings** https://user-images.githubusercontent.com/80701113/152702147-1bc60ab7-2cd1-46d3-9f26-d677ad383cdc.mp4 **No perspective** https://user-images.githubusercontent.com/80701113/152702150-63587a9d-f262-4a34-a234-6e5a65bd21f9.mp4

arnaudvergnet commented

2022-02-06 21:40:37 +00:00

(Migrated from github.com)

For comparison, here is the same view in perspective, without 3d buildings but in car mode instead of foot. You can see it is a bit better but there are still some freezes when moving the camera.

https://user-images.githubusercontent.com/80701113/152702460-3ee72cb7-87bb-4b51-9fad-4b50d43b8743.mp4

For comparison, here is the same view in perspective, without 3d buildings but in car mode instead of foot. You can see it is a bit better but there are still some freezes when moving the camera. https://user-images.githubusercontent.com/80701113/152702460-3ee72cb7-87bb-4b51-9fad-4b50d43b8743.mp4

vng commented

2022-02-07 06:24:52 +00:00

(Migrated from github.com)

Well, I suspect that the performance problem is not in styles or visible POIs here. I will check.

Note for me. Investigate viewport (rect) cells covering in perspective mode. Limit cells size/count with some reasonable values according to the reasonable horizon line.

Well, I suspect that the performance problem is not in styles or visible POIs here. I will check. **Note for me**. Investigate viewport (rect) cells covering in perspective mode. Limit cells size/count with some _reasonable_ values according to the _reasonable_ horizon line.

vng commented

2022-02-08 07:04:42 +00:00

(Migrated from github.com)

@arnaudvergnet One more thing to clarify. Do you use SD-card or internal memory to store map files? We had a bunch of performance issues before, related to bad/cheap/old SD-cards.

arnaudvergnet commented

2022-02-08 07:46:23 +00:00

(Migrated from github.com)

I use internal memory (I do not have a SD card)

This repo is archived. You cannot comment on issues.