September 12, 2017 um 19:44 #20088
Mapsforge POI specification will advance to version 2.
That will provide „proper“ multiple categories per POI and more efficient storage (as had discussed with Christian and Tobias).
– POI writer will produce only the newer v2 .poi files
– POI readers will be compatible with both v2 and v1 .poi files
Thanks to community work and more info is in Mapsforge forum announcement.September 12, 2017 um 22:54 #20097
Thanks Emux, great news (again). Lots of good developments at the mapsforge community at the moment, I’m looking forward to test it (when I have a bit more time at hand)…
Developer of Elevate mapstyleSeptember 19, 2017 um 15:47 #20167September 20, 2017 um 09:06 #20169
If I got this right – POI_V2 files will be compatible with (eg) Oruxmaps when the Orux will implement the new Lib in the App?
ChristianSeptember 20, 2017 um 10:31 #20171
Mapsforge poi reader(s) are compatible with both v1 and v2 poi files, so you’re right!Januar 25, 2020 um 15:57 #33468
I tried V2 Pois – yes I know, late very late – and got an error see attached logfile.
Pllease can you take a look at the poi-mapping.xml.
A tag that is assigned to more than one cat is (eg.) alpine_hut
Up to now I added one ore more blanks to the tags name to avoid this error, but that should’nt be the solution.
thanks ChristianJanuar 25, 2020 um 17:17 #33476
Do you have in poi mapping 2 same poi categories?
Is there some small poi mapping so can reproduce it easier?Januar 25, 2020 um 17:19 #33478
By the way please report such cases in Mapsforge forum so that anyone from the community can better help.Januar 25, 2020 um 18:51 #33482
Thanks for super fast answer, here are the files with only alpine_hut in two cats.
Anhänge:Januar 25, 2020 um 22:43 #33490Januar 26, 2020 um 16:37 #33499
What implemented in POI v2 is to support multiple categories per POI (see the related discussion / issue).
That is not hosting the same sub-category many times inside different parent categories in poi mapping tree.
I do think that having the same subcategory on several categories, like having ‚Alpine Huts‘ in ‚Hiking‘ and ‚Accomodation‘ categories, makes sense. This was possible on the first version of the POI spec, see below.123456[crayon-5e4c35582c421323129372 inline="true" ]SELECT * FROM poi_categories WHERE name LIKE '%Alpine Huts%' ORDER BY idid name parent16 Alpine Huts / Berghütten 2430 Alpine Huts / Berghütten 3759 Alpine Huts / Berghütten 65
So it looks to me like a regression in version 2
RegardsJanuar 26, 2020 um 17:25 #33501
This was possible on the first version of the POI spec
It was never designed or worked that way in any version.
See Christian’s answer above (uses a trick):
Up to now I added one ore more blanks to the tags name to avoid this error, but that should’nt be the solution.Januar 26, 2020 um 17:50 #33509
oh shit! I see now, there are spaces added to the second and third category names.
My understanding about the RTree stuff is that the index contains one entry for each record in poi_data table, unless I am missing something, it has nothing to do with categories.
Thank you for your quick response.
RegardsJanuar 27, 2020 um 16:26 #33515
Nevertheless I will use the new POI-Writer from next update of OAM on.
It provides smaler files…
Du musst angemeldet sein, um auf dieses Thema antworten zu können.