This object is in archive! 
Tiles only drawn partially for some zoom levels for vector maps
Not a Problem
Hi,
Unfortunately Locus is currently unusable for my holiday destination island Föhr in Germany
When using offline maps from openandromaps.org.
Please see attached Screenshot.
(The same file is rendered OK in Orux and Cruiser)
Map used is Schleswig Holstein from 2.3.2016
With other render themes the problem is less visible, but still exists (e.g. roads not shown in some tiles)
Any plans for fixing this issue?
Regards Michael
Files:
Screenshot_2016...
Good day Michael,
interesting. I'm not sure if I'll be able to help in this case as no such problem happen with own LoMaps from Locus Store. I'll anyway check it tomorrow with my colleague.
Good day Michael,
interesting. I'm not sure if I'll be able to help in this case as no such problem happen with own LoMaps from Locus Store. I'll anyway check it tomorrow with my colleague.
Hello Michael,
I've checked your image and I have to say that we're limited in this situation. Openandromaps (OAM) are not created by Locus team so We don't know how are these maps created. Locus uses customized renderer of vector maps that works with internal LoMaps that are available via Locus store.
The green borders are probably caused because map was not generated with custom attribute that force OSM elements to lines. It seems that official renderer is able to process such data but Locus isn't. Please try to contact provider of OAM if would be possible to generate maps in older way.
We could focus on it only in case that you would find similar issue in Locus LoMaps
Edit: of course it also suggested to use OAM themes with OAM maps
Thank you for understanding
Best regards
Petr
Hello Michael,
I've checked your image and I have to say that we're limited in this situation. Openandromaps (OAM) are not created by Locus team so We don't know how are these maps created. Locus uses customized renderer of vector maps that works with internal LoMaps that are available via Locus store.
The green borders are probably caused because map was not generated with custom attribute that force OSM elements to lines. It seems that official renderer is able to process such data but Locus isn't. Please try to contact provider of OAM if would be possible to generate maps in older way.
We could focus on it only in case that you would find similar issue in Locus LoMaps
Edit: of course it also suggested to use OAM themes with OAM maps
Thank you for understanding
Best regards
Petr
Replies have been locked on this page!