This object is in archive!
The problem of vector maps (Garmin IMG)
Solved
Since the last update, the application is very slow reads vector maps that are placed on the SD card. Vector maps are typically the Garmin device but until recently seamlessly in Locus.
It is a pity that the problem I noticed during the trip in the Jizera - a lot of hours too late. So far there was no problem: (.
I hope you are working on the improvement / restoration speed, because I lose both confidence and desire to advertise the application of Friends of cyclists.
Sample map GPS Wielkopolska -> http://www.gpswielkopolska.pl/files/slady_gps/gpswielkopolska_mapa.zip
Device: Samsung Galaxy S3
OS: Kitkat 4.4.4 (ArchiDroid 2.5.1 based on CM11)
The same problem 
Good day bobiko,
1. Garmin IMG maps are not officially supported and it's support may change from version to version
2. I'm checking a code and around Garming vector maps was not done any changes for last few months
3. I'm testing your map and it's speed is same as for other img maps I have for testing purpose and it's also same as was versions before. I see no significant different.
4. Becuase you use alternative rom which is based on another alternative rom, I should rather check if there is not any decreased performance in reading data from your SD card or any problem with card itself.
Good day bobiko,
1. Garmin IMG maps are not officially supported and it's support may change from version to version
2. I'm checking a code and around Garming vector maps was not done any changes for last few months
3. I'm testing your map and it's speed is same as for other img maps I have for testing purpose and it's also same as was versions before. I see no significant different.
4. Becuase you use alternative rom which is based on another alternative rom, I should rather check if there is not any decreased performance in reading data from your SD card or any problem with card itself.
I can confirm there's been a significant regression with Garmin .img maps in 3.1.
I'm using this map (sorry, huge file) and after the update some tiles refuse to render at all, no matter how long I wait.
Same behavior with both Moto G and Nexus 7, both using stock firmware, and the same map works just fine with OruxMaps so there's definitely nothing wrong with the file or mass storage systems on the devices.
Attached screenshots of the same view from 3.0.2 and 3.1.3.
I can confirm there's been a significant regression with Garmin .img maps in 3.1.
I'm using this map (sorry, huge file) and after the update some tiles refuse to render at all, no matter how long I wait.
Same behavior with both Moto G and Nexus 7, both using stock firmware, and the same map works just fine with OruxMaps so there's definitely nothing wrong with the file or mass storage systems on the devices.
Attached screenshots of the same view from 3.0.2 and 3.1.3.
Interesting,
Weird is that I did not do any changes to rendering of Garmin IMG files. Anyway thanks for a file, I'll check it!
Interesting,
Weird is that I did not do any changes to rendering of Garmin IMG files. Anyway thanks for a file, I'll check it!
Juha,
sorry, but no problem on my device also. Everything works
fast as usually and without any missing tiles. I suggest to give locus a
while or if you want, you should try to create me a log by this method
http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log .
But I cannot promise there will be something useful ...
Juha,
sorry, but no problem on my device also. Everything works
fast as usually and without any missing tiles. I suggest to give locus a
while or if you want, you should try to create me a log by this method
http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log .
But I cannot promise there will be something useful ...
Really strange. I tried removing all addons, uninstalled and reinstalled and deleted all data and cache, no difference.
The unresponsive tiles are apparently not random, but always the same across restarts, etc. Zoom level matters too, on some no tiles at all seem to work, and on some most are okay but it seems there's always a couple missing.
Both of us with the problem seem to be using Android 4.4 devices, could this be OS related, any chance your test device happens to use older version?
I sent some debug logs to the support e-mail address (issue #5277), both android-generated and those created by Locus when using the miscellanous setting for that.
Really strange. I tried removing all addons, uninstalled and reinstalled and deleted all data and cache, no difference.
The unresponsive tiles are apparently not random, but always the same across restarts, etc. Zoom level matters too, on some no tiles at all seem to work, and on some most are okay but it seems there's always a couple missing.
Both of us with the problem seem to be using Android 4.4 devices, could this be OS related, any chance your test device happens to use older version?
I sent some debug logs to the support e-mail address (issue #5277), both android-generated and those created by Locus when using the miscellanous setting for that.
Ah gotcha ... with published version I have same problem. Issue was caused by Proguard app (if you know). Thank you! It's fixed now and will work as expected in next version.
Maps were slow also because of this problem, because on background was quite a lot of errors that dramatically slowed whole rendering.
Thanks guys for a help!
Ah gotcha ... with published version I have same problem. Issue was caused by Proguard app (if you know). Thank you! It's fixed now and will work as expected in next version.
Maps were slow also because of this problem, because on background was quite a lot of errors that dramatically slowed whole rendering.
Thanks guys for a help!
Please, kindly advise how to install these maps on Locus so as they apper on the website with the elevation contours:
http://garmin.opentopomap.org/#download
Thanks
Please, kindly advise how to install these maps on Locus so as they apper on the website with the elevation contours:
http://garmin.opentopomap.org/#download
Thanks
After downloading a map from OpenTopoMap in Garmin IMG format, it includes a file with the following information:
OpenTopoMap Garmin Edition
==========================
Topographical vector map for Garmin devices from OpenStreetMap data
Under the free, non-commercial license CC-BY-NC-SA
http://garmin.opentopomap.org
## Installation Guide:
# For etrex 20/30 etc:
Copy the two image files (OpenTopoMap country map and treble lines) to the SD card in the "Garmin" folder.
# For etrex Legend / Vista etc:
Rename the OpenTopoMap country map to "gmapsupp.img" and copy it to the "Garmin" folder on the SD card. Unfortunately, the old Garmin devices can only load a single card file, so no additional heights.
I may be wrong but I believe neither Locus Map or OruxMaps supports the "second file" which contains "treble lines". I think "treble lines" is translated from German and refers to (in English) contour lines.
After downloading a map from OpenTopoMap in Garmin IMG format, it includes a file with the following information:
OpenTopoMap Garmin Edition
==========================
Topographical vector map for Garmin devices from OpenStreetMap data
Under the free, non-commercial license CC-BY-NC-SA
http://garmin.opentopomap.org
## Installation Guide:
# For etrex 20/30 etc:
Copy the two image files (OpenTopoMap country map and treble lines) to the SD card in the "Garmin" folder.
# For etrex Legend / Vista etc:
Rename the OpenTopoMap country map to "gmapsupp.img" and copy it to the "Garmin" folder on the SD card. Unfortunately, the old Garmin devices can only load a single card file, so no additional heights.
I may be wrong but I believe neither Locus Map or OruxMaps supports the "second file" which contains "treble lines". I think "treble lines" is translated from German and refers to (in English) contour lines.
Replies have been locked on this page!