April 2014 - mkgmap-dev - The mkgmap lists

Commit: r3188: fix NPE that occurs when relations style file removes the restriction tag
by svn commit 13 Apr '14

13 Apr '14

Version mkgmap-r3188 was committed by gerd on Sun, 13 Apr 2014 fix NPE that occurs when relations style file removes the restriction tag

1 0

restriction relations with wrong restriction text
by Gerd Petermann 13 Apr '14

13 Apr '14

Hi all, should mkgmap ignore if a no_left_turn restriction doesn't describe a no_left_turn? For example, look at this http://www.openstreetmap.org/relation/3414378 >From and to way build a straight line, but tag says restriction=no_left_turn. I think it is not clear what is meant, this might be an "only_straight_on" or the to way is wrong or the from way is wrong. In short: the restriction should be ignored after printing a warning. I've coded this check to be very tolerant , so this one is accepted: http://www.openstreetmap.org/relation/1394386 although the difference to a straight line is only 10 degrees. My test would complain if the difference would be less than 3 degrees. OK? Better ideas? Ciao, Gerd

2 2

Commit: r3186: improvements by Minko:
by svn commit 13 Apr '14

13 Apr '14

Version mkgmap-r3186 was committed by gerd on Sun, 13 Apr 2014 improvements by Minko: - don't open a new window for uninstall process - if map was already installed, use the existing past instead of the default c:\garmin\maps

1 0

natural=peak on the map
by Michel Amic 12 Apr '14

12 Apr '14

Hi, I would like see point natural=peak on the map and i go when i surch this point on the GPS . Have you Any ideas? Michel -- View this message in context: http://gis.19327.n5.nabble.com/natural-peak-on-the-map-tp5803032.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 2

Commit: r3184: correctiopn: make sure that isViaWay property is copied in Way.copy()
by svn commit 12 Apr '14

12 Apr '14

Version mkgmap-r3184 was committed by gerd on Sat, 12 Apr 2014 correctiopn: make sure that isViaWay property is copied in Way.copy()

3 3

Commit: r3185: fix possible NPE
by svn commit 12 Apr '14

12 Apr '14

Version mkgmap-r3185 was committed by gerd on Sat, 12 Apr 2014 fix possible NPE

1 0

"Grave (RestrictionRelation)" with mkgmap-r3181 and mkgmap-r3182
by Waxy 12 Apr '14

12 Apr '14

Hi, With mkgmap-r3181 and mkgmap-r3182 I got issues. This message, several times : Grave (RestrictionRelation): 63240003.o5m: Turn restriction (no_left_turn) http://www.openstreetmap.org/browse/relation/1172857 (at http://www.openstreetmap.org/?mlat=-21.007077&mlon=55.271317&zoom=17) way http://www.openstreetmap.org/browse/way/77065617 doesn't have required node An idea ? Need few tests or informations ? Files: http://tuxdomain.darktech.org/osm-garmin/view.php?file=R%C3%A9union/6324000… -> 8,5 Mo https://tuxdomain.darktech.org/osm-garmin/view.php?file=R%C3%A9union/632400… -> 1,8 Mo Regards.

5 10

Commit: r3183: work around to fix problem caused by copy of ways that is created when continue is used in style but no further routable way is added with
by svn commit 11 Apr '14

11 Apr '14

Version mkgmap-r3183 was committed by gerd on Fri, 11 Apr 2014 work around to fix problem caused by copy of ways that is created when continue is used in style but no further routable way is added with this copy. The code should to evaluate the restriction relation should be moved to RoadNetwork, this should reduce the complexity of the code.

1 0

special cases in restriction relations, r3178 still not perfect
by Gerd Petermann 11 Apr '14

11 Apr '14

Hi all, I found a few more very special cases, some can be easily fixed in the code, but one is maybe a problem in OSM: See http://www.openstreetmap.org/relation/1626132 The 'to' way starts and ends at the via point. In combination with the tag restriction=only_straight_on it is clear what this means, but the current implementation in mkgmap is not prepared for that. It would probable create a different result if the points of the 'to' way would go clockwise and not ccw. I think the wiki doesn't say that this is not correct, so to support this mkgmap has to interpret the restriction. Up to now it just checked if it is a only_xxx or an no_xxx restriction. It is much more complex to interpret the angle and find out what is meant. This seems too much work for that special case, so I prefer to print a warning and ignore the restriction. OK? Gerd

3 5

Commit: r3182: - don't ignore no_entry restriction relation if it has
by svn commit 11 Apr '14

11 Apr '14

Version mkgmap-r3182 was committed by gerd on Fri, 11 Apr 2014 - don't ignore no_entry restriction relation if it has multiple 'from' ways and one way is not routable or outside bbox, as long as one routable 'from' way remains - don't ignore no_exit restriction relation if it has multiple 'to' ways and one way is not routable or outside bbox as long as one routable 'to' way remains

1 0