- mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] residential area processing switch
by Mike Baggaley 14 Mar '17

14 Mar '17

Thanks Gerd (and ArndtAm who sent me the same suggestion). That worked a treat. Cheers, Mike -----Original Message----- From: Gerd Petermann [mailto:GPetermann_muenchen@hotmail.com] Sent: 14 March 2017 20:59 To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] Severe Error in mkgmap (that does not disturb at all) Hi Mike, you can use option --x-residential-hook=false. I can also try to disable the hook when the style doesn't use mkgmap:residential . Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen(a)hotmail.com> Gesendet: Dienstag, 14. März 2017 21:50:39 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Severe Error in mkgmap (that does not disturb at all) Hi Jakob, thanks for reporting. The error means that the housenumber algorithm went nuts at some point, thats why it reports a severe error. I'll try to find out what is happening... Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Jakob Mühldorfer <mail(a)jmuehldorfer.de> Gesendet: Dienstag, 14. März 2017 21:42:09 An: 'Development list for mkgmap' Betreff: [mkgmap-dev] Severe Error in mkgmap (that does not disturb at all) Processing some map, it told me: > SCHWERWIEGEND (ExtNumbers): ./splitmap/63240077.osm.pbf: internal > error, distance to road too large, road id=184899623, SS12 Strada > Nazionale del Canaletto Nord house 1070(47) > http://www.openstreetmap.org/node/4712532420 Does not actually seem to be any problem at all, but wanted to report it in case it helps Version 3846 Commandline to reproduce > mkgmap.jar --housenumbers 63240077.osm.pbf And the tile in question https://dropfile.to/rdEAQV7 Best Jakob _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

1 0

Is anyone creating a Database of Linetypes and Points that will not show up on specific Garmin GPS's?
by greg crago 14 Mar '17

14 Mar '17

My GPSMAP 276c will not display LINETYPE: 0x20 My Montana 600 will not show display the following POINTS: 0x3001,0x3002,0x3008,0x5904 POINTS This info can be helpful if you cannot see data on your GPS and your CODE is correct. Greg

2 2

Severe Error in mkgmap (that does not disturb at all)
by Jakob Mühldorfer 14 Mar '17

14 Mar '17

Processing some map, it told me: > SCHWERWIEGEND (ExtNumbers): ./splitmap/63240077.osm.pbf: internal > error, distance to road too large, road id=184899623, SS12 Strada > Nazionale del Canaletto Nord house 1070(47) > http://www.openstreetmap.org/node/4712532420 Does not actually seem to be any problem at all, but wanted to report it in case it helps Version 3846 Commandline to reproduce > mkgmap.jar --housenumbers 63240077.osm.pbf And the tile in question https://dropfile.to/rdEAQV7 Best Jakob

2 2

residential area processing switch
by Mike Baggaley 14 Mar '17

14 Mar '17

Hi is there a switch to turn off the new residential area processing (I can't see one in the documentation or in the code)? If not, can one be added? This new bit of code is causing difficulties in my (slightly patched) version of mkgmap, and I have no need of its functionality. Thanks, Mike

1 0

[Patch v1] differet Coord implementation
by Gerd Petermann 14 Mar '17

14 Mar '17

Hi programmers, After writing my findings here http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2017q1/026317.html I did some cycling and decided that I might still be better to use the attached patch. It works better with 32 bits and is probably a bit easier to understand. The major difference is that it calculates the Garmin position of a point from the already rounded 30 (or 32 bit) value. In some cases this means that points in the map move by one, e.g. one with 52.2452629, 21.0833536 appears on the right grid point instead of the left (it is very close to the middle). Gerd

3 3

Overview map
by Mike Baggaley 14 Mar '17

14 Mar '17

Gerd's comment about looking at the overview map, prompted me to look at mine, and I realised I didn't have one (or it is empty), despite me having --tdbfile specified - the help for this option says an overview map will be created. I assume I am not getting an overview map because I don't have --overview-levels specified. Would it be better if the default for --overview-levels is not an empty string when --tdbfile is specified? The documentation for --overview-levels is not very clear. From inspecting the code it looks like the format expected is similar to the format expected by --levels and that the overview level numbers should be greater than the normal levels. Can the documentation for this be improved? Also, what is the benefit of specifying something like --overview-levels=5:15,6:13,7:11 over the much simpler --overview-levels=15,13,11 and have mkgmap work out the next free levels. Could we simplify this? Regards, Mike

2 3

generate-sea: behaviour
by Ticker Berkin 14 Mar '17

14 Mar '17

Hi I've been using --generate-sea rather than --precomp-sea for a few weeks and there doesn't seem to be an obvious performance penalty and the img size is slightly better (but I have been changing other things along the way). However - It doesn't seem to know about the rule that land must be on the left of the coastline and sea on the right. Taking the geofabrik download of UK/Hampshire, the Isle of Wight is (correctly) mostly excluded - just 3 bits of coastline that don't meet each other or the bottom edge of the tile. With --generate-sea=multipolygon, I sometimes get the top half, which is correctly defined land, ie has coastline to the tile edge, as sea and the sea as nothing. The bits of disconnected coastline sometimes have a triangle of sea where it should be, sometimes where the land is! With extend-sea-sectors,gap=350 it is much better behaved. Maybe the default behaviour should be to ignore these disconnected bits of coastline (with a warning), hence both sides will show as sea. The coast of the requested area should behave correctly. Ticker

2 1

x-residential-hook missing tile
by Arndt Röhrig 13 Mar '17

13 Mar '17

2 3

Commit r3846: prevent another possible ArrayIndexOutOfBoundsException in BoundaryLocationPreparer
by svn commit 13 Mar '17

13 Mar '17

Version mkgmap-r3846 was committed by gerd on Mon, 13 Mar 2017 prevent another possible ArrayIndexOutOfBoundsException in BoundaryLocationPreparer tag value may contain a single comma http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3846

1 0

Commit r3845: prevent possible ArrayIndexOutOfBoundsException in BoundaryLocationPreparer
by svn commit 13 Mar '17

13 Mar '17

Version mkgmap-r3845 was committed by gerd on Mon, 13 Mar 2017 prevent possible ArrayIndexOutOfBoundsException in BoundaryLocationPreparer tag value may be an empty string after style processing http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3845

1 0