Osmand is now almost perfect, but for me the rendering is one of 3 weakest points. The other 2 are route calculation (mainly it's speed) and lack of online services (for example collecting data from drivers and using them for routing).
Regarding routing, it is not just the speed which is bad also the lack of any 3D visualisation. For example look how good maps look in this navigation: https://play.google.com/store/apps/details?id=com.generalmagic.magicearth or buildings rendering here: http://osmbuildings.org/ Switching to Qt is the right choice IMO. They even have ready to use map solution (at least as an inspiration). Some sources for information are here: http://blog.qt.io/blog/2017/03/09/provisioning-openstreetmap-providers-in-qtlocation/ and http://blog.qt.io/blog/2016/10/04/customizable-vector-maps-with-the-mapbox-qt-sdk/ Another advantage I can see is the fact, that the developers won't have to care which 3D rendering engine must be used. Qt will automatically pick OpenGL, Vulkan or whatever else is available. -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
