[mkgmap-dev] Commit r4271: improve reader for polish (*.mp) format

2019-02-10 Thread svn commit
Version mkgmap-r4271 was committed by gerd on Mon, 11 Feb 2019 improve reader for polish (*.mp) format - fix restriction handling (various errors, esp. NPE and "can't locate arc from 'via' node..." error messages - make sure that route nodes are only calculated for POLYLINE nodes given for

[mkgmap-dev] documentation improvement patch

2019-02-10 Thread Mike Baggaley
Hi Gerd, I have attached a patch to improve the documentation of the command line. I did it some time ago and had forgotten about it, but the discussion on whether to change default options prompted me to come back to it. The change is purely to the documentation, no code changes. Please review

Re: [mkgmap-dev] Commit r4270: improve reader for polish (*.mp) format

2019-02-10 Thread Andrzej Popowski
Hi Gerd, doesn't mkgmap support multiple points restrictions from OSM data? Anyway, removing 4-point restriction prevents mkgmap from crashing, but errors still remains: SEVERE (RoadNetwork): 8001.mp: 1 can't locate arc from 'via' node 1 to 'to' node 171 on way 431744 SEVERE

Re: [mkgmap-dev] Shouldn't both options --gmapi and --nsis imply --tdbfile?

2019-02-10 Thread Mike Baggaley
>I still don't dare to change the option handling in mkgmap completely. My understanding is that we have two groups of users: >- One large group uses mkgmap since long and has all kinds of scripts which expect exactly the current behaviour. >Thus I consider backward compatibility very important.

Re: [mkgmap-dev] Commit r4270: improve reader for polish (*.mp) format

2019-02-10 Thread Gerd Petermann
Hi Andrzej, besides the mixed case problem mkgmap also cannot handle 4 node restrictions in polish input. Will take a while ... Gerd Von: Gerd Petermann Gesendet: Sonntag, 10. Februar 2019 09:26 An: Gerd Petermann; Development list for mkgmap Betreff:

Re: [mkgmap-dev] Commit r4270: improve reader for polish (*.mp) format

2019-02-10 Thread Gerd Petermann
Hi Andrzej, I found an older example with restrictions and I can reproduce the problem. It seems that our reader is too restrictive regarding the spelling of key words. For example, the parser understands "TraffPoints" but not "TRAFFPOINTS" I can try to change the parser so that it always uses