February 2019 - mkgmap-dev - The mkgmap lists

WG: WG: mkgmap type file and posting to mkgmap.org
by Gerd Petermann 22 Feb '19

22 Feb '19

Hi Dave, I did not get a response from you but you wrote that you receive posts from the list. It seems neither Steve nor I are can send something to you? Gerd ________________________________________ Von: Steve Ratcliffe <steve(a)parabola.me.uk> Gesendet: Donnerstag, 21. Februar 2019 22:27 An: Gerd Petermann Betreff: Re: WG: mkgmap type file and posting to mkgmap.org Hi Gerd That is strange, I received a similar email from the same person a while back. I believed that I had fixed his problem and replied to him to try again. He never replied back though, so perhaps he did not receive my reply. I shall look into this some more. Could you reply to him to that effect as you may have more luck reaching him. There was a problem with one post that appeared to trigger a spam filter on gmail, but that was more recently. Steve > Hi Steve, > > please see below. > > Gerd > > ________________________________________ > Von: dave pitney <mappitney(a)gmail.com> > Gesendet: Donnerstag, 21. Februar 2019 22:04 > An: gpetermann_muenchen(a)hotmail.com > Betreff: mkgmap type file and posting to mkgmap.org > > Dear Gerd - > > I am unable to post to the mkgmap dev list using mappitney(a)gmail.com > although I can receive messages. I tried sending a message to > mkgmap-dev-owner(a)lists.mkgmap.org.uk in December? about this but did > not receive a reply. Can you check my settings and let me know if I > need to take any actions? Thanks. > > Also I am using mkgmap r4262 to make maps for Garmin GPS using the > default style and typ files from jorisbo (modified) which work well. > My problem is that when I add --precomp-sea=... to my script the map > displays a blue background covering Colorado which is not (currently) > in the sea. Without this option the map is fine. The typ? directions > mention setting a land polygon with a higher draw order than the sea > but without a clear example I cannot get this to work. Since I cannot > post I do not who to turn to for assistance. Any thoughts? > > I apologize if you are not the person to help with this, if you can > forward this to one who can help it is appreciated. > > Thanks, Dave Pitney, mappitney(a)gmail.com > > -- > pitney > > ----------------- end of message ------------------------ >

1 0

Commit r4278: correct code that checks for existing ovm_*.img,
by svn commit 13 Feb '19

13 Feb '19

Version mkgmap-r4278 was committed by gerd on Wed, 13 Feb 2019 correct code that checks for existing ovm_*.img, The old code might have removed an ovm_*.img file in the working directory instead of the output directory when processing non-osm input files. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4278

1 0

Commit r4277: partly revert r4276: don't print message
by svn commit 13 Feb '19

13 Feb '19

Version mkgmap-r4277 was committed by gerd on Wed, 13 Feb 2019 partly revert r4276: don't print message Don't say "nothing to do" when no input file was given. Options like --checkstyle, --version, --help etc. work without an input file http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4277

1 0

Commit r4276: Print useful message when no input file was given
by svn commit 13 Feb '19

13 Feb '19

Version mkgmap-r4276 was committed by gerd on Wed, 13 Feb 2019 Print useful message when no input file was given Without that check we may see nonsense like this: java -jar d:\mkgmap\dist\mkgmap.jar --gmapi Time started: Wed Feb 13 15:04:21 CET 2019 Options --gmapi and --no-tdbfiles are mutually exclusive Number of ExitExceptions: 1 Time finished: Wed Feb 13 15:04:21 CET 2019 Total time taken: 33 ms http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4276

1 0

Option handling with polish input (*.mp)?
by Gerd Petermann 13 Feb '19

13 Feb '19

Hi, with OSM data we provide options like family id, mapname etc. as program arguments. In *.mp files many of these options can be specified in the so called "IMG ID" section. In the past the polish reader in mkgmap didn't evaluate most of these parameters, there was no intention to replace the functionality of cGPSmapper. Now I learned about tools that create *.mp files as output and that mkgmap might be the better choice to process those files. So far so good. Problem: What is expected when the mkgmap options conflict with those in the *.mp file? My current understanding is this: 1) *.mp overwrites mkgmap builtin defaults 2) mkgmap options overwrite *.mp information Would that work? Gerd

3 2

Commit r4271: improve reader for polish (*.mp) format
by svn commit 12 Feb '19

12 Feb '19

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 level 0 TODO: SIGN section (exit hints) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4271

3 5

Commit r4275: improve reader for polish (*.mp) format:
by svn commit 12 Feb '19

12 Feb '19

Version mkgmap-r4275 was committed by gerd on Tue, 12 Feb 2019 improve reader for polish (*.mp) format: - handle ~[0x1d] in country name and translate labels in Numbers with decoder - evaluate and use POIZipFirst, POINumberFirst, and Transparent keywords in IMG ID section to set TRE header. Maybe transparent needs more work - evaluate CountryName and RegionName keywords in IMG ID (not yet used) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4275

1 0

Commit r4274: revert changes from r4273, not the right place to do this
by svn commit 12 Feb '19

12 Feb '19

Version mkgmap-r4274 was committed by gerd on Tue, 12 Feb 2019 revert changes from r4273, not the right place to do this http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4274

1 0

Commit r4273: improve reader for polish (*.mp) format: handle ~[0x1d] in country name
by svn commit 12 Feb '19

12 Feb '19

Version mkgmap-r4273 was committed by gerd on Tue, 12 Feb 2019 improve reader for polish (*.mp) format: handle ~[0x1d] in country name http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4273

1 0

Commit r4272: improve reader for polish (*.mp) format: Don't make assumptions about inner or outer roles of multipolygons, use the logic in MultiPolygonRelation to find out.
by svn commit 12 Feb '19

12 Feb '19

Version mkgmap-r4272 was committed by gerd on Tue, 12 Feb 2019 improve reader for polish (*.mp) format: Don't make assumptions about inner or outer roles of multipolygons, use the logic in MultiPolygonRelation to find out. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4272

1 0