- mkgmap-dev - The mkgmap lists

problem with mkgmap
by A Guertin 10 Nov '15

10 Nov '15

Hello, What can I do with this problem? Unable to split See attachement Andre --

3 3

feedback on sharp-angles-v4.patch?
by Gerd Petermann 27 Oct '15

27 Oct '15

Hi all, I am still waiting for feedback from Felix, but maybe other are willing to contribute? See http://gis.19327.n5.nabble.com/Patch-v4-sharp-angles-tp5854127.html Gerd

7 13

Commit: r3649: sharp-angles-v4.patch with small modifications
by svn commit 27 Oct '15

27 Oct '15

Version mkgmap-r3649 was committed by gerd on Tue, 27 Oct 2015 sharp-angles-v4.patch with small modifications - remove the code for --adjust-turn-headings which no longer worked - add code to fix sharp angles (enabled by default) Enlarge sharp angles at road junctions so that the time penalty is smaller. In OSM, junctions are often drawn without reflecting the exact angles of the roads, they are more symbolic. We assume that in most cases an angle below 45° doesn't really exist as such and therefor the heading values of the arcs are modified so that the Garmin routing algorithm "sees" a less sharp angle. If needed, the option --ignore-sharp-angles can be used to disable this.

1 0

Error message
by Bernd Weigelt 26 Oct '15

26 Oct '15

Hi what's wrong here? SCHWERWIEGEND (HousenumberRoad): /home/bernd/map_build/tiles/65020057.o5m: internal error, road links are not correct http://www.openstreetmap.org/node/2790241547 SCHWERWIEGEND (HousenumberGroup): /home/bernd/map_build/tiles/65020057.o5m: internal error, group check with houses on different roads? 4611686018443080889 2790241547 SCHWERWIEGEND (ExtNumbers): /home/bernd/map_build/tiles/65020057.o5m: internal error, house has wrong segment, road id=126612880, null house 498(0) http://www.openstreetmap.org/node/2790241547 SCHWERWIEGEND (ExtNumbers): /home/bernd/map_build/tiles/65020057.o5m: internal error, house has wrong segment, road id=126612880, null house 498(0) http://www.openstreetmap.org/node/2790241547 Bernd

2 4

boundary files
by Steve Sgalowski 26 Oct '15

26 Oct '15

it is still good to know gerd , if the boundary or sea files have been updated so is it possible somehow to just add as text when they were last updated .. Stephen

2 1

Commit: r3648: fix possible "internal error, road links are not correct " message
by svn commit 26 Oct '15

26 Oct '15

Version mkgmap-r3648 was committed by gerd on Mon, 26 Oct 2015 fix possible "internal error, road links are not correct " message This is related to addr:interpolation ways which connect addr:housenumber elements which specify a street name and the closest road doesn't have that name. Under certain circumstances the assigned road is changed, but another reference was not updated. The fix addresses two problems: 1) Only change the assigned road of such a housenumber element when the alternative road has the wanted name. 2) Always change both references. There is probably no golden rule here, as the data is wrong, and one has to decide if it is better to ignore the addr:housenumber element just because the addr:interpolation way is wrong.

1 0

Commit: r3647: construction_v3.patch: don't route through highway=construction
by svn commit 26 Oct '15

26 Oct '15

Version mkgmap-r3647 was committed by gerd on Mon, 26 Oct 2015 construction_v3.patch: don't route through highway=construction - use action setaccess no on these roads - revert unintended change on comment in build.xml

1 0

[patch v1] don't route the highway=construction ways
by Gerd Petermann 23 Oct '15

23 Oct '15

Hi all, attached patch implements the new internal tag mkgmap:add-to-NOD=false to handle the issue discussed here: http://gis.19327.n5.nabble.com/don-t-route-through-highway-construction-tt5… It shows how to use it in the default style. I've also added a rule to ignore highway=planned like highway=proposed If you don't like the rather technical name mkgmap:add-to-NOD, please let me know it, here are my ideas for alternatives: mkgmap:ignore-for-routing=yes mkgmap:routable=no mkgmap:address-search-only=yes Gerd

7 19

re Commit: r3644: add portugese spelling for Brasil / Brazil
by Mike Baggaley 21 Oct '15

21 Oct '15

Anyone know why the following lines are included in the LocatorConfig.xml under United Kingdom? They seem to me to be incorrect: <variant>Great Britian</variant> <variant>Gibraltar / United Kingdom</variant> Regards, Mike

1 0

highway=razed
by Gerd Petermann 20 Oct '15

20 Oct '15

Hi all, the lines file in the default style contains this rule: # Mop up any unrecognised highway types highway=* & highway!=proposed & area!=yes [0x07 road_class=0 road_speed=0 resolution 23] I've changed it to highway=* & highway!=proposed & area!=yes { echotags "mop up" } [0x07 road_class=0 road_speed=0 resolution 23] to see what it does and it "mops up" all kings of problem cases, e.g. mapping errors like highway=turning_circle or removed highways with the highway=razed I think the default style should not add these ways as routable, if at all. It also catches many highway=platform and highway=rest_area Most of these ways are areas, but don't have the area=yes tag. I am not sure why the "mop up" rule would ignore them when the area=yes tag exists. Gerd

5 7