Issue with Custom Icons After Recent Route/Point Library Update
Hello Locus Map Team,
I'm encountering an issue with the display of my custom icons for points since the recent update that introduced the new route and point library. I have been a long-time user of Locus Map and have always used my own set of icons for my waypoints. My usual workflow involves regularly exporting my data as KMZ files, and in the past, these KMZ files consistently included my points with their associated custom icons.
Before the update, the icon style definition within the doc.kml file within my KMZ exports looked like this:
XML
<Style id="file:my_icons_v2.3.zip:sunrise_red.png"> <IconStyle> <Icon><href>files/file-my_icons_v2.3.zip-sunrise_red.png</href></Icon> <hotSpot x="0.5" y="0.0" xunits="fraction" yunits="fraction" /> </IconStyle> </Style>
However, after the update, the same icon style definition in the exported doc.kml now appears as follows:
XML
<Style id="file:///storage/emulated/0/Android/data/menion.android.locus/files/Locus/data/import/2025_05_05_0846_1554_Fotostandorte.kmz/files/file-my_icons_v2.3.zip-sunrise.png"> <IconStyle> <Icon><href>files/file-storageemulated0Androiddatamenion.android.locusfilesLocusdataimport2025_05_05_0846_1554_Fotostandorte.kmzfilesfile-my_icons_v2.3.zip-sunrise_red.png</href></Icon> <hotSpot x="0.5" y="0.0" xunits="fraction" yunits="fraction" /> </IconStyle> </Style>
To me, it seems like the path to the icon has changed from a relative path (in the first example) to an absolute path (in the second example)?
Consequently, with the new version of Locus Map, my custom icons are no longer displayed correctly.
Could you please investigate this issue and provide guidance on how to resolve it? My custom icons are an integral part of how I use Locus Map for navigation and organization.
Thank you for your time and assistance.
The same problem 
Hello Thomas,
I'm testing it on some custom icons and it works correctly.
If you look on absolute paths in the problematic export, it point to "Locus/data/import" directory. So it looks you are exporting any previously imported! points. Is it possible? App during import does not check, if imported icons already exist in custom icons and always copies them into the "import" directory. And this is the result.
What I've made now:
- there was a problem with the import of small KMZ files with icons included. App considered them as "custom icons", incorrectly. Fixed
- I've also improved the import of files with reference to custom icons, so it will in the next version use the custom icon file if it exists at the moment of import
Hope this helps.
Hello Thomas,
I'm testing it on some custom icons and it works correctly.
If you look on absolute paths in the problematic export, it point to "Locus/data/import" directory. So it looks you are exporting any previously imported! points. Is it possible? App during import does not check, if imported icons already exist in custom icons and always copies them into the "import" directory. And this is the result.
What I've made now:
- there was a problem with the import of small KMZ files with icons included. App considered them as "custom icons", incorrectly. Fixed
- I've also improved the import of files with reference to custom icons, so it will in the next version use the custom icon file if it exists at the moment of import
Hope this helps.
Hello Menion,
Yes, you're absolutely right – I do export already imported KMZ files again. Let me briefly explain my workflow:
I'm a photographer and I have a folder with POIs where I save all interesting photo locations, including related images. From time to time, I export this folder as a backup and then re-import it, overwriting all points in the folder. After that, I can delete the local image files because they are already embedded in the exported KMZ. I also use this KMZ file to synchronize my POIs across different devices.
Unfortunately, I can't use the online synchronization feature in Locus at the moment because it doesn't sync images in the POIs – only the description and coordinates. Maybe that will be implemented in the future.
Thank you very much for the fix and improvements – I really appreciate your work!
Best regards,Thomas
Hello Menion,
Yes, you're absolutely right – I do export already imported KMZ files again. Let me briefly explain my workflow:
I'm a photographer and I have a folder with POIs where I save all interesting photo locations, including related images. From time to time, I export this folder as a backup and then re-import it, overwriting all points in the folder. After that, I can delete the local image files because they are already embedded in the exported KMZ. I also use this KMZ file to synchronize my POIs across different devices.
Unfortunately, I can't use the online synchronization feature in Locus at the moment because it doesn't sync images in the POIs – only the description and coordinates. Maybe that will be implemented in the future.
Thank you very much for the fix and improvements – I really appreciate your work!
Best regards,Thomas
Hello Thomas,
understand. Sync of attachments is planned for this year. Hard to say for now, if it will be ideal solution for photographers as it will most probably reduce photo quality a little bit ... we will see.
Anyway, changes I made are now part of the 4.29.0.5 Beta version, so give it a try if you want to test it before the public version is on the Google Play (second half of May, most probably).
Hello Thomas,
understand. Sync of attachments is planned for this year. Hard to say for now, if it will be ideal solution for photographers as it will most probably reduce photo quality a little bit ... we will see.
Anyway, changes I made are now part of the 4.29.0.5 Beta version, so give it a try if you want to test it before the public version is on the Google Play (second half of May, most probably).
Hello Menion,
Thank you very much for the quick support! It seems to be working fine now.
Regarding the potential reduction in photo quality with the attachment sync: that shouldn't be an issue for me, as I usually resize my images to a maximum edge length of 1200 px before saving them into the KMZ file anyway.
Best regards, Thomas
Hello Menion,
Thank you very much for the quick support! It seems to be working fine now.
Regarding the potential reduction in photo quality with the attachment sync: that shouldn't be an issue for me, as I usually resize my images to a maximum edge length of 1200 px before saving them into the KMZ file anyway.
Best regards, Thomas
Replies have been locked on this page!