Hi Gerd,
I think I should have looked at the logfiles earlier,
but since I do not really understand the splitter log, I tend not to read it
carefully.
I found out, that the problem was gone even with the old parameter for
max-nodes.
The solution was just to splitt the area again.
I checked
Version mkgmap-r3993 was committed by gerd on Wed, 16 Aug 2017
don't create shop POI for shop=no or shop=none
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=3993
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
In the forum, there is a discussion on the enormous variety of values
for some tags, see
https://forum.openstreetmap.org/viewtopic.php?id=55541 (in Dutch).
There is also a link to a list showing the different values for the
"shop" tag:
Hi Walter,
another possible way to verify the data in your europe.o5m:
extract a node that is corrupted in 50100031.o5m, e.g.
osmfilter europe.o5m --keep="@id=1965123604" > test.osm
When I do this with 50100031.o5m I see
while the correct data should look like this:
Gerd
Hi Walter,
The data in 50100031.o5m looks very strange, maybe there is a special case in
splitter.
So if you still have the same europe.o5m file, it would be great if you could
try to reproduce the
problem. If you can, please send the splitter log and the areas.list.
Gerd
