Names of maps are sometimes getting the same name, despite different file name
PROBLEM:
Sometimes, two maps with the different file name, have the same name in Locus.
EXAMPLE:
I have these maps in Locus/maps folder:
Radom.Ruski42.sqlitedb
Radom.39-51.sqlitedb
Radom.1943.AerialPhoto.v09.sqlitedb
Radom.Compass.UTM34.sqlitedb
Radom.M-34-019-3.S.sqlitedb
Radom.M-34-19-c.N.sqlitedb
but instead of seeing their full names (with ".sqlitedb" cut off) I can see:
Radom
Radom
Radom.1943.AerialPhoto
Radom.Compass
Radom.M-34-019-3
Radom.M-34-19-c
It looks like Locus is cutting off the last (.*.) part. Which is crucial for distinguishing between different maps.
PS. Small question, is there any way to add additional information to .sqlitedb file, which will be showed in the "Information/Overview" screen for a map? It would be cool to add some copyright info, or a special icon or thumbnail ( which will be showed under "Overview" section)
The same problem 
I may confirm this. It`s directly implemented in this way so it`s not a bug.
In times I created this "map manager", some maps I used for testing had two endings, like x.osm.sqlite, so I was removing both.
It`s not a problem to remove this, question is just how many people will write after next update - "hey, now I see ... " ... etc. you know :)
so "fixed", or better "changed"
about extra data in database - yes this should be useful. Currently locus use info table in database where are additional data included, so it`s not a big problem, to add there some extra fields ...
maybe insert metadata table as has MBTiles https://github.com/mapbox/mbtiles-spe... where is not needed to add extra columns, because all is much clever in just key/value table
I may confirm this. It`s directly implemented in this way so it`s not a bug.
In times I created this "map manager", some maps I used for testing had two endings, like x.osm.sqlite, so I was removing both.
It`s not a problem to remove this, question is just how many people will write after next update - "hey, now I see ... " ... etc. you know :)
so "fixed", or better "changed"
about extra data in database - yes this should be useful. Currently locus use info table in database where are additional data included, so it`s not a big problem, to add there some extra fields ...
maybe insert metadata table as has MBTiles https://github.com/mapbox/mbtiles-spe... where is not needed to add extra columns, because all is much clever in just key/value table
Thank you for solving that.
Thank you for solving that.
sure, you`re welcome!
sure, you`re welcome!
Replies have been locked on this page!