reg. https://forum.locusmap.eu/index.php?topic=9260.msg79024#msg79024
well it's a db and therefore not more complicated as it is by itself.
No doubt it makes sense to unite online and offline if different and grown structures have been in use.
It also makes sense to use a consistent structure if data of different sources get used, parsed, loaded, combined, and processed, and shown in a consistent way. If the community and userbase will bring additional content, like e.g. it is with Komoot, the more important this is, sure.
Well, noone expects a full db-documentation, plain information can be dropped at a dedicated github-page without big efforts as you know.
Even the same GUI-part, category-filter, mechanism could generally be used, though be separated to distinguish and better identify problems due to external database-files (offline), just in case. And back-loading of those can also generally be disabled to never bring those online, if building a LM-driven database is the goal.
I personally tried the old but now preserved LoPoint-part from time to time but decided not to use it consistently as it never was a satisfying experience, category ui in early design-state, poi loading awkward, search pois puh.., poi difficult to distinguish from the background, too small size and too small frame and no features like temporary switch map to bw, etc. It was a start.
Well, I suggest to rethink your view and to support with informations about the changed db-structure, consider 3rd-party sources like e.g. OAM, in my opinion this might better preserve community support and bring a better and more satisfying Locus-experience at all.
Quote from: Menion@T-mo
New LoPoints > I believe the profit of the change is quite big. No difference in online/offline work. A lot richer content of POIs, full compatibility of offline and online, better placement on the map and for use - very easy to modify both worlds at once.
Db documentation and support for 3rd parties > no, not planned and definitely not recommended. New system is a lot more complicated than the previous and we need to keep compatibility with the online and iOS world. That's why "Other POIs" will exist and will still be well supported.
well it's a db and therefore not more complicated as it is by itself.
No doubt it makes sense to unite online and offline if different and grown structures have been in use.
It also makes sense to use a consistent structure if data of different sources get used, parsed, loaded, combined, and processed, and shown in a consistent way. If the community and userbase will bring additional content, like e.g. it is with Komoot, the more important this is, sure.
Well, noone expects a full db-documentation, plain information can be dropped at a dedicated github-page without big efforts as you know.
Even the same GUI-part, category-filter, mechanism could generally be used, though be separated to distinguish and better identify problems due to external database-files (offline), just in case. And back-loading of those can also generally be disabled to never bring those online, if building a LM-driven database is the goal.
I personally tried the old but now preserved LoPoint-part from time to time but decided not to use it consistently as it never was a satisfying experience, category ui in early design-state, poi loading awkward, search pois puh.., poi difficult to distinguish from the background, too small size and too small frame and no features like temporary switch map to bw, etc. It was a start.
Well, I suggest to rethink your view and to support with informations about the changed db-structure, consider 3rd-party sources like e.g. OAM, in my opinion this might better preserve community support and bring a better and more satisfying Locus-experience at all.
