- mkgmap-dev - The mkgmap lists

support
by Steve Sgalowski 23 Mar '14

23 Mar '14

gerd p , i verry much appreciate the help you gave me and i am goeing to continue to run 24 hour testing here on caNADA file also i will help add more features to the brisbane maps in australia stephen \keep up the good work gerd p

1 0

[Patch v2] distorted lines with make-cycleway options
by Gerd Petermann 22 Mar '14

22 Mar '14

Hi all, this is version 2 of the patch for this problem: http://gis.19327.n5.nabble.com/link-pois-to-ways-tags-tp5800124p5800575.html Change: The options make-all-cycleways, make-opposite-cycleways and make-cycleways imply preserve-element-order. In fact, I'd prefer to change the code so that preserve-element-order is default and remove the option. Gerd

2 1

Commit: r3118: revert changes from r3117
by svn commit 22 Mar '14

22 Mar '14

Version mkgmap-r3118 was committed by gerd on Sat, 22 Mar 2014 revert changes from r3117

1 0

No sort description for code-page 1252 available
by News 22 Mar '14

22 Mar '14

Since checking out the latest version of mkgmap this morning I am getting the error No sort description for code-page 1252 available and mkgmap finishes immediately. I get this either with my normal command line or even if I strip it right back to just java -Xmx2048M -jar mkgmap.jar 00001*.pbf My previous version of mkgmap, r3111, works fine. Any ideas? Thanks Paul

3 5

link-pois-to-ways tags
by Gerd Petermann 22 Mar '14

22 Mar '14

Hi all, a few weeks ago we discussed the tags which should trigger the link-pois-to-ways option. The current implementation works like this: Each node with a tag access=*, barrier=*, or highway=* is handled as a POI (before style processing). Ways with such a node are tagged with mkgmap:way-has-pois=true. If the style assigns mkgmap:road-class=* or mkgmap:road-speed=* or one of the access tags (mkgmap:bicycle,mkgmap:foot,...,mkgmap:delivery) the node may change routing. WanMil suggested to remove access=* from the list of triggers, as it is too likely to be something like amenity=parking, access=private . This was forgotten during the merge of the mergeroads branch, so I've done it now with r3115. Gerd

5 19

mkgmap and route restrictions
by Gerd Petermann 21 Mar '14

21 Mar '14

Hi all, looking at the 4 node restrictions I think I found a general bug in mkgmap: Both with polish (.mp) format and with OSM data we compute the routing nodes for which the restriction shoud be applied. In a second step we compute the arcs between these nodes. In this 2nd step we ignore the information about roads given with TRAFFROADS in polish format or the from,via, and to roles in OSM data. In the mkgmap algo, we just select the first direct arc (means: peace of road) between the nodes. If the nodes are connected with multiple arcs on different roads, this probably is too lazy, although it will not fail very often. I have to rewrite most of the code reg. restrictions to correct this.. Gerd

5 8

weird behavior of contour lines
by Michał Rogala 19 Mar '14

19 Mar '14

Hi! I generated my map, merged with SRTM (using splitter) and my complilation has a lot of blank rectangles in contour lines: http://imgur.com/7zP0TNt Did anyone see something like that? Is it phyghtmap problem or something with mkgmap/splitter? Best regards Michal Rogala

2 6

Feedback on mkgmap r3111
by Thorsten Kukuk 19 Mar '14

19 Mar '14

Hi, during the last two days I had the chance to compare a lot of long distance routing of my Garmin 62s (Firmware 5.30, so newest one with activity routing) with my map generated with mkgmap r3111 and a commercial built in car navigation system. The routing on long distance between both devices was the same. The difference between the km the 62s calculated and we drove was about 1%, the time about 3%. Inside of cities on short routes the 62s did choose the better routes, but I think that's only because the OSM data was more up-to-date. So the "NOD127" branch was really a very good job! There were only two negative aspects: - the 5.30 firmware for the 62s is a nightmare in stability and usability :( - if you enable "avoid u-turns", the 62s will not only avoid them, but really never does them, even if it means there is no legal way to continue. Means in two situations we were suggested to use a cycleway or a footway. That's reproduceable with the 62s, but not with MapSource, so I think it's a firmware bug. (if somebody wants to try: Route to "Tigerpalast" in Frankfurt a. Main and continue with Routing to "Lange Strasse 30-36" with "avoid u-turn" enabled, car, fastest route). Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

2 1

Bogus roundabout warnings
by Marko Mäkelä 18 Mar '14

18 Mar '14

With the most recent mkgmap trunk (r3111) I am getting bogus warnings like these: 2014/03/14 22:07:19 WARNING (RouteNode): 63240008.osm.pbf: Roundabout (http://www.openstreetmap.org/browse/way/32502891) forks at http://www.openstreetmap.org/?mlat=63.830711&mlon=23.120524&zoom=17 2014/03/14 22:07:19 WARNING (RouteNode): 63240008.osm.pbf: Outgoing roundabout flare road (http://www.openstreetmap.org/browse/way/27506601) does not finish at flare? http://www.openstreetmap.org/?mlat=63.905483&mlon=24.516046&zoom=17 2014/03/14 22:07:19 WARNING (RouteNode): 63240008.osm.pbf: Roundabout (http://www.openstreetmap.org/browse/way/27506649) forks at http://www.openstreetmap.org/?mlat=63.905981&mlon=24.514913&zoom=17 I suspect that these are being triggered when there are nodes very close to each other, and they are being merged. I do not remember seeing these warnings yesterday, with r3110. Marko

2 5

Commit: r3116: reduce severity level of "very small shape near ... " message
by svn commit 18 Mar '14

18 Mar '14

Version mkgmap-r3116 was committed by gerd on Tue, 18 Mar 2014 reduce severity level of "very small shape near ... " message from warning to debug.

1 0