- mkgmap-dev - The mkgmap lists

Commit: r3221: merge the refactoring branch
by svn commit 22 Apr '14

22 Apr '14

Version mkgmap-r3221 was committed by gerd on Tue, 22 Apr 2014 merge the refactoring branch

1 0

additional checks in check-styles ?
by Gerd Petermann 22 Apr '14

22 Apr '14

Hi all, I think --check-styles should flag all rules that try to create a routable way with the wrong type. Sample: highway=track & surface=pebblestone [0x10411 road_class=0 road_speed=1 resolution 24] should produce a warning like "non-routable type is used with road_class or road_speed" Will that cause problems? Gerd

1 0

Different rendering
by demon.box 21 Apr '14

21 Apr '14

Excuse me, why this different rendering between Extreme Carver's Map (Open Mtb Map) and my map? ExtremeCarver: <http://gis.19327.n5.nabble.com/file/n5803738/Immagine2.jpg> My Map <http://gis.19327.n5.nabble.com/file/n5803738/immagine1.jpg> This are the only to lines of the style "lines" highway=footway & surface=concrete [0x10406 road_class=0 road_speed=1] highway=steps [0x0d road_class=0 road_speed=0 resolution 24] I rendered the map with the latest mkgmap release 3211. What can I do? Thanks! --enrico -- View this message in context: http://gis.19327.n5.nabble.com/Different-rendering-tp5803738.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 12

Commit: r3216: Rework access rules
by svn commit 21 Apr '14

21 Apr '14

Version mkgmap-r3216 was committed by wanmil on Mon, 21 Apr 2014 Rework access rules The access rules now fully use the access rule tree (e.g. access=>vehicle=>motor_vehicle=>motorcar). The default rules for highway types can now correctly work with access=no. Before this change the rules added foot=yes etc. to ways tagged with access=no only. The new file access_country contains some country specific default settings for highway types.

2 2

Commit: r3217: Avoid adding duplicate names for operator, brand and name tags
by svn commit 21 Apr '14

21 Apr '14

Version mkgmap-r3217 was committed by wanmil on Mon, 21 Apr 2014 Avoid adding duplicate names for operator, brand and name tags

2 1

Commit: r3215: WrongAngleFixer: ignore ways which already have less than two points
by svn commit 21 Apr '14

21 Apr '14

Version mkgmap-r3215 was committed by gerd on Mon, 21 Apr 2014 WrongAngleFixer: ignore ways which already have less than two points A few obsolete points on non-routable ways (e.g. railways) where not removed when they were shared with removed very short routable ways which are not connected to other routable ways, e.g. footways leading to tram platforms.

1 0

Commit: r3211: Merge from the sort2 branch. Index fixes.
by svn commit 20 Apr '14

20 Apr '14

Version mkgmap-r3211 was committed by steve on Sun, 20 Apr 2014 Merge from the sort2 branch. Index fixes. There are two main fixes here. 1. A problem with the size of section 29 of the index when the number of cities is near a critical number. Probably only affects the gmapsupp file. 2. When the files are not given in the correct sorted order on the command line. There was some code to deal with this, but not enough...

4 5

mkgmap.org.uk down
by Stéphane MARTIN 20 Apr '14

20 Apr '14

Hi, http://www.mkgmap.org.uk is unreachable :-( Just for me ?

2 2

Commit: r3200: Reapply 3198 as svn move
by svn commit 20 Apr '14

20 Apr '14

Version mkgmap-r3200 was committed by steve on Fri, 18 Apr 2014 Reapply 3198 as svn move prepare refactoring of access evaluation: move RoadNetwork from package uk.me.parabola.mkgmap.general to uk.me.parabola.imgfmt.app.net Note that you may have to adapt your logging.properties file! --- Also changed signature of addRoad() so that it takes a RoadDef and List<Coord> since MapRoad should not be referenced from imgfmt.

5 15

barriers on major roads
by Gerd Petermann 20 Apr '14

20 Apr '14

Hi all, I've just fixed a rare problem with barrier=* in r3206. Now I wonder if mkgmap should really process nodes with barrier=* that are at the start or end of one way. I found many cases in the past where this was a mapping error, e.g. If a small way is connected to a "major" road, and the connection node has barrier=gate, the current implementation will not allow cars to travel along the "major" road. The wiki recommends to avoid this situation: http://wiki.openstreetmap.org/wiki/Tag:barrier%3Dgate says "Avoid tagging highway intersections as that does not make clear which way has the impediment" I think mkgmap should print a warning if that is found and ignore the barrier. OK? Gerd

3 2