Images in kmz
Answered
How to show the missing images ? The kmz is attached.
Files:
BOM_KMZ - Orang...
How to show the missing images ? The kmz is attached.
The same question
More on this subject. By Locus map Pro 3.70.4 Classic.
Current import of both kmz and gpz files by attached images are added into both folders:
/storage/emulated/0/Android/data/menion.android.locus.pro/files/Locus/data/import/....
/storage/emulated/0/Android/data/menion.android.locus.pro/files/Locus/data/media/photo/.....
Problem 1.
The handling after the import of both gpz or kmz files are different.
For gpz imports a path is given while for kmz the path is not complete.
Suggestion 1.
Add the paths in an identical way to the folder import that should be cleared after closing Locus map.
As image file names can be identical in both gpz and kmz files optimally is to use the folder import.
Problem 2.
A. Import SET: Display only (= no save in database)
B. Import UNSET: Display only ( = save in database)
The folder import is NEVER cleared and keeps growing for ever !
Suggestion 2.
- The folder import should automatically be cleared when closing Locus map app.
- By A. > no save in database > the folder photo must not be filled.
- By B. > save in database > the folder photo can be filled. Q: Same named files can cause conflicts ?
Clear the folder photo by the Locus map function delete temporary items.
Problem 3. General.
- Before A13+ A check in Locus data by file explorers is allowed.
- After A13+ A check in Locus data by file explorers is forbidden.
Suggestion 3.
Locus should offer to set the Main directory into.
- Private folder in Android data. (not accessible)
- Private folder in Android media. (accessible)
To know.
Select internal memory to use all Locus features.
More on this subject. By Locus map Pro 3.70.4 Classic.
Current import of both kmz and gpz files by attached images are added into both folders:
/storage/emulated/0/Android/data/menion.android.locus.pro/files/Locus/data/import/....
/storage/emulated/0/Android/data/menion.android.locus.pro/files/Locus/data/media/photo/.....
Problem 1.
The handling after the import of both gpz or kmz files are different.
For gpz imports a path is given while for kmz the path is not complete.
Suggestion 1.
Add the paths in an identical way to the folder import that should be cleared after closing Locus map.
As image file names can be identical in both gpz and kmz files optimally is to use the folder import.
Problem 2.
A. Import SET: Display only (= no save in database)
B. Import UNSET: Display only ( = save in database)
The folder import is NEVER cleared and keeps growing for ever !
Suggestion 2.
- The folder import should automatically be cleared when closing Locus map app.
- By A. > no save in database > the folder photo must not be filled.
- By B. > save in database > the folder photo can be filled. Q: Same named files can cause conflicts ?
Clear the folder photo by the Locus map function delete temporary items.
Problem 3. General.
- Before A13+ A check in Locus data by file explorers is allowed.
- After A13+ A check in Locus data by file explorers is forbidden.
Suggestion 3.
Locus should offer to set the Main directory into.
- Private folder in Android data. (not accessible)
- Private folder in Android media. (accessible)
To know.
Select internal memory to use all Locus features.
Hello Willy, thanks for the complext report!
Firstly, negative part: since October 2023 (half of 5 year maintenance mode), I'm doing mainly/only critical fixes and maintenance in the Locus Classic, that affect functionality for most of users. Code for both versions are now separated and it require a lot more work to do some modifications in the Classic as well.
Possitive (probably not for you, sorry)
Problem 1
Should be identical, agree. Updated. Also copy of files into "data/media" directory was not ideal solution, so I've removed this and all data remains in the "data/import".
Problem 2
This one is in the app since day 1 and was already reported many times. I do not have easy solution for it for now, sorry.
Problem 3
Also complicated to solve. I do not trust "media" directory. There is no clear info from Google, that this directory is stable and will remain available also in the future Android versions. If there is need to access internal app data directly, there is always solution over so-called AFA version.
Thanks for understanding,
Jiří M. aka Menion
Hello Willy, thanks for the complext report!
Firstly, negative part: since October 2023 (half of 5 year maintenance mode), I'm doing mainly/only critical fixes and maintenance in the Locus Classic, that affect functionality for most of users. Code for both versions are now separated and it require a lot more work to do some modifications in the Classic as well.
Possitive (probably not for you, sorry)
Problem 1
Should be identical, agree. Updated. Also copy of files into "data/media" directory was not ideal solution, so I've removed this and all data remains in the "data/import".
Problem 2
This one is in the app since day 1 and was already reported many times. I do not have easy solution for it for now, sorry.
Problem 3
Also complicated to solve. I do not trust "media" directory. There is no clear info from Google, that this directory is stable and will remain available also in the future Android versions. If there is need to access internal app data directly, there is always solution over so-called AFA version.
Thanks for understanding,
Jiří M. aka Menion
Replies have been locked on this page!