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] Commit r4270: improve reader for polish (*.mp) format

2019-02-10 Thread Gerd Petermann
: AW: [mkgmap-dev] Commit r4270: improve reader for polish (*.mp) format 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 "TraffP

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

2019-02-10 Thread Gerd Petermann
that it always uses method String.equalsIgnoreCase() instead of String.equals(). Gerd Von: mkgmap-dev im Auftrag von Gerd Petermann Gesendet: Sonntag, 10. Februar 2019 06:42 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Commit r4270: impro

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

2019-02-09 Thread Andrzej Popowski
Hi Gerd, I have tried to compile some more complicated mp. First problem is, that restriction placed on the beginning of the file give multiple warnings, like: SEVERE (RoadNetwork): 8001.mp: 1 can't locate arc from 'via' node 1 to 'to' node 171 on way 431744 SEVERE (RoadNetwork):

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

2019-02-09 Thread Andrzej Popowski
Hi Gerd, I would rather have mkgmap compatible with real compiler than manual, but in this particular case, both options are reasonable. I'm using the latest version of cGPSmapper 100d. The earliest version I have is 74 from 2004. It behaves the same. -- Best regards, Andrzej

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

2019-02-09 Thread Gerd Petermann
: mkgmap-dev im Auftrag von Andrzej Popowski Gesendet: Samstag, 9. Februar 2019 19:55 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Commit r4270: improve reader for polish (*.mp) format Hi Gerd, I have compiled this example. cGPSmapper doesn't work like in quoted description. When

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

2019-02-09 Thread Andrzej Popowski
Hi Gerd, I have compiled this example. cGPSmapper doesn't work like in quoted description. When EndLevel is present, cGPSmapper uses only lowest DATA and ignore any other. See description of EndLevel, this one is true: Endlevel=# - The coordinates in the lowest numbered Data# line apply up

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

2019-02-09 Thread Gerd Petermann
ldn't. " Gerd Von: mkgmap-dev im Auftrag von Andrzej Popowski Gesendet: Samstag, 9. Februar 2019 12:44 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Commit r4270: improve reader for polish (*.mp) format Hi Gerd, I think GPSMa

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

2019-02-09 Thread Andrzej Popowski
Hi Gerd, I think GPSMapEdit does it correctly. Each line should be extended up to EndLevel, so it means that first line should be present on levels 0-2 and second on levels 1-2. Multiple DATA in a statement is not a typical case. I think these statements are created usually by GPSMapEdit. I

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

2019-02-09 Thread svn commit
Version mkgmap-r4270 was committed by gerd on Sat, 09 Feb 2019 improve reader for polish (*.mp) format Fix handling of repeated DATA lines with different levels Sample from manual: [RGN40] Type=22 Label= EndLevel=2 Data0=(51.562624,-1.070283),(51.561637,-1.070592),(51.561272,-1.069878),