- mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] Misc documentation fixes
by Ticker Berkin 22 Jun '20

22 Jun '20

Hi Eugene I see. This is part of an automatic system that builds the release zip and web documentation when updates are committed to the svn repository. Parts of the release zip doc directory build are failing, but the web update of the same information are happening correctly I'll try and find out more. Regards Ticker On Sat, 2020-06-20 at 22:47 -0700, eugeny_burynin(a)mail.ru wrote: > Sorry for my English, this is Google translator. > > See the end of the file http://www.mkgmap.org.uk/download/mkgmap-r455 > 3.zip\mkgmap-r4553\doc\typ-compiler.txt > Polygon elements trimmed, missing Line elements, Points (POI), Icons > > Regards, Eugene > > <quote author='Ticker Berkin'> > Hi Eugene > > Yes - You're right, they are different. > > I hadn't noticed before, but the the versions of the files in release > download have been through a document processor. This is "asciidoc" > in > the case of the style manual, but I'm not sure about the others. > > Whatever it is, it fails for "tuning.txt", but the others look > reasonably like the resultant versions available from > > http://www.mkgmap.org.uk/doc/index.html > > Ticker > > On Sat, 2020-06-20 at 08:11 -0700, eugeny_burynin(a)mail.ru wrote: > > Thank you for your work. > > > > But compilation doesn't work correctly. > > I compare the documentation files located in the archive > > http://www.mkgmap.org.uk/download/mkgmap-r4553.zip > > http://www.mkgmap.org.uk/download/mkgmap-r4553.zip\mkgmap-r4553\doc > > \i > > ndex.txt > > http://www.mkgmap.org.uk/download/mkgmap-r4553.zip\mkgmap-r4553\doc > > \t > > uning.txt > > http://www.mkgmap.org.uk/download/mkgmap-r4553.zip\mkgmap-r4553\doc > > \t > > yp-compiler.txt > > with files of the same name located > > http://www.mkgmap.org.uk/websvn/l > > isting.php?repname=mkgmap&path=%2Ftrunk%2Fdoc%2F&rev=4553&peg=4553# > > a2 > > 008cef70b23f59cfd5d9cad5e05e6c8 > > > > They don't match. > > > > Sincerely, Eugene > > > > <quote author='Ticker Berkin'> > > Hi Gerd > > > > I didn't get the layout of one of my typ-compiler changes correct > > for > > when it appears here: > > > > http://www.mkgmap.org.uk/doc/typ-compiler > > > > so I've had another go - I'm still guessing at how the layout > > language > > works. > > > > Also fixed another couple of trivial noticed when comparing > > resultant > > page with: > > > > https://wiki.openstreetmap.org/wiki/Mkgmap/help/typ_compile > > > > Minor patch attached. > > > > Ticker > > > > > > _______________________________________________ > > mkgmap-dev mailing list > > mkgmap-dev(a)lists.mkgmap.org.uk > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > > miscDoc_v3.patch (2K) > > <http://gis.19327.n8.nabble.com/attachment/5968878/0/miscDoc_v3.pat > > ch > > > > > > > </quote> > > Quoted from: > > http://gis.19327.n8.nabble.com/Misc-documentation-fixes-tp5968452p5 > > 96 > > 8878.html > > > > > > _____________________________________ > > Sent from http://gis.19327.n8.nabble.com > > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > </quote> > Quoted from: > http://gis.19327.n8.nabble.com/Misc-documentation-fixes-tp5968452p596 > 8902.html > > > _____________________________________ > Sent from http://gis.19327.n8.nabble.com >

1 0

Re: [mkgmap-dev] Misc documentation fixes
by Ticker Berkin 20 Jun '20

20 Jun '20

Hi Eugene Yes - You're right, they are different. I hadn't noticed before, but the the versions of the files in release download have been through a document processor. This is "asciidoc" in the case of the style manual, but I'm not sure about the others. Whatever it is, it fails for "tuning.txt", but the others look reasonably like the resultant versions available from http://www.mkgmap.org.uk/doc/index.html Ticker On Sat, 2020-06-20 at 08:11 -0700, eugeny_burynin(a)mail.ru wrote: > Thank you for your work. > > But compilation doesn't work correctly. > I compare the documentation files located in the archive > http://www.mkgmap.org.uk/download/mkgmap-r4553.zip > http://www.mkgmap.org.uk/download/mkgmap-r4553.zip\mkgmap-r4553\doc\i > ndex.txt > http://www.mkgmap.org.uk/download/mkgmap-r4553.zip\mkgmap-r4553\doc\t > uning.txt > http://www.mkgmap.org.uk/download/mkgmap-r4553.zip\mkgmap-r4553\doc\t > yp-compiler.txt > with files of the same name located http://www.mkgmap.org.uk/websvn/l > isting.php?repname=mkgmap&path=%2Ftrunk%2Fdoc%2F&rev=4553&peg=4553#a2 > 008cef70b23f59cfd5d9cad5e05e6c8 > > They don't match. > > Sincerely, Eugene > > <quote author='Ticker Berkin'> > Hi Gerd > > I didn't get the layout of one of my typ-compiler changes correct for > when it appears here: > > http://www.mkgmap.org.uk/doc/typ-compiler > > so I've had another go - I'm still guessing at how the layout > language > works. > > Also fixed another couple of trivial noticed when comparing resultant > page with: > > https://wiki.openstreetmap.org/wiki/Mkgmap/help/typ_compile > > Minor patch attached. > > Ticker > > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > miscDoc_v3.patch (2K) > <http://gis.19327.n8.nabble.com/attachment/5968878/0/miscDoc_v3.patch > > > > </quote> > Quoted from: > http://gis.19327.n8.nabble.com/Misc-documentation-fixes-tp5968452p596 > 8878.html > > > _____________________________________ > Sent from http://gis.19327.n8.nabble.com >

1 0

Commit r4553: doc: improve formatting (miscDoc_v3.patch by Ticker Berkin)
by svn commit 20 Jun '20

20 Jun '20

Version mkgmap-r4553 was committed by gerd on Sat, 20 Jun 2020 doc: improve formatting (miscDoc_v3.patch by Ticker Berkin) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4553

1 0

Misc documentation fixes
by Ticker Berkin 20 Jun '20

20 Jun '20

Hi Gerd Here are some documentation fixes & improvements + a change to build.xml to use 4 chars for the unknown version number so that offsets match the typical 4 digit svn version number. This minimises noise when comparing the display of internal structures. I can't tell if I've got the layout in typ-compiler.txt correct until it appears on http://www.mkgmap.org.uk/doc/typ-compiler If it looks bad I'll do another patch. Ticker

5 7

Commit r4552: miscDoc_v2.patch by Ticker Berkin:
by svn commit 20 Jun '20

20 Jun '20

Version mkgmap-r4552 was committed by gerd on Sat, 20 Jun 2020 miscDoc_v2.patch by Ticker Berkin: "Here are some documentation fixes & improvements + a change to build.xml to use 4 chars for the unknown version number so that offsets match the typical 4 digit svn version number. This minimises noise when comparing the display of internal structures." http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4552

1 0

Nearby poi feature
by Joris Bo 19 Jun '20

19 Jun '20

Hello, I'm struggling with the nearby poi rules. As far as I understand from the manual there are 3 options named: triggered if the type code and the name is the same unnamed: triggered if the type code is the same and the name is empty no specification: triggered if the type code is the same regardless of the name being the same But if I use 0x3002:10 on a docters clinic with 9 doctors all having different names, obvious closer together then 10 meters nothing happens When adding multiple rules for the same typ-code I get a SEVERE error message (which is correct and proofs the correct nearby - config-rules - file is in use) When hiding trees next to the doctors (just to be sure the correct code is triggered) the unnamed trees are hidden as expected When rendering the doctors as typ-code trees, again nothing happens. So it's not in the the typ-code used and I can only assume that I just can't hide poi's when the name is different? Maybe somebody could help explain what can be expected If interested in the test area: https://www.openstreetmap.org/#map=19/49.75947/6.64167 https://www.openstreetmap.org/#map=19/49.75841/6.64698 Kind regards, Joris

3 15

Commit r4551: Report type(node, way, relation) of original element in "generated from" messages (slightly modified generated-from.patch)
by svn commit 19 Jun '20

19 Jun '20

Version mkgmap-r4551 was committed by gerd on Fri, 19 Jun 2020 Report type(node,way,relation) of original element in "generated from" messages (slightly modified generated-from.patch) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4551

1 0

possible echotags enhancement?
by Ranko Jaksic 19 Jun '20

19 Jun '20

Hello, echotags style command displays the element type and original OSM-Id (as in "Node generated from <OSM-Id>"). Would it be possible to additionally display the original element type for all such "generated from" elements? (Something like "Node generated from Way <OSM-Id>" or "Way generated from Relation <OSM-Id>") Background: At the end of my style file I use echotags to log elements left unhandled and then process this logfile to generate a html file with direct links to offending elements in OSM. This way I can click and easily correct the data in OSM if needed. A href tag generated this way looks like this: <a href="https://www.openstreetmap.org/way/688658542">OSM link</a> To do this I need to detect the (original) element type from the echotags message (is it a node/way/relation), but for "generated from" elements there is no way to detect this properly from the echotags message text. For example: with the "--add-pois-to-areas" option a node is generated for each polygon or multipolygon. However, the message is the same for both and there is no way to detect if the original element was a polygon ("way") or a multipolygon ("relation") :( regards, Ranko

3 8

Tiles missing
by Pierre Brico 17 Jun '20

17 Jun '20

Hello, Sorry my mail format is not as expected but this is the first time I send an email to this mailing list. Be indulgent... A few months ago, I bought a Garmin GPSMAP 66s (I've already other Garmin devices). I would like to get maps for it without using illegal maps. So, I had a look at OpenStreetMap. The project has made a lot of improvements since the last time I've seen it. So, I'm now contributing to my region. I was looking for maps for biking but didn't find anything to my taste. That's why I've decided to generate my own maps. I started from OpenTopoMap script which generates maps very close to what I would like. I've generated a map for Belgium and with some adjustments, I get what I want. Now I would like to generate a map for my next holiday in France but I have issues with missing tiles. Indeed some tiles aren't displayed on my GPSMAP 66s. Whatever is the scale. I've tried the maps from OpenTopoMap and their maps don't have this kind of problem. All tiles are correctly displayed. I'm using splitter (r597) and mkgmap (r4525). That's not the version used by OpenTopoMap ( https://github.com/der-stefan/OpenTopoMap/blob/master/garmin/tools/generate… ). My question is: how can I proceed to find the issue ? I tried to download the same version as OpenTopoMap used but it is not available anymore... I've verified the final france.img file and the missing tiles are well packed in the image. Thanks, Pierre Brico [image: 191.bmp]

6 14

Commit r4550: refactoring, no functional change
by svn commit 16 Jun '20

16 Jun '20

Version mkgmap-r4550 was committed by gerd on Tue, 16 Jun 2020 refactoring, no functional change rename variable fmt to sb cause it's a StringBuilder, not a Formatter http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4550

1 0