- mkgmap-dev - The mkgmap lists

Exclude POIs from index
by Dave Swarthout 25 Aug '15

25 Aug '15

When I search for All POIs on my Garmin Montana I get many useless unnamed POIs, even power poles, barriers, houses, etc. Is there some way to tell mkgmap to exclude such POIs from its search results? -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com

6 6

Commit: r3633: correction: don't ignore the no-u--turn restrictions that are generated by an only* route restriction
by svn commit 25 Aug '15

25 Aug '15

Version mkgmap-r3633 was committed by gerd on Tue, 25 Aug 2015 correction: don't ignore the no-u--turn restrictions that are generated by an only* route restriction

1 0

patch for omitting nearby POIs with the same name and type
by Mike Baggaley 24 Aug '15

24 Aug '15

Hi, please find attached a patch that adds two new options: --max-same-poi-distance=distance and --include-nearby-poi-types=type[,type...]. These options are used to determine whether nearby POIS are duplicates and should be omitted from the map, extending the existing check for duplicates at the exact same location. They help to reduce the problems cause by OSM data frequently having an area such as a building tagged with the same information as a point or where multiple areas are given the same name - this is most problematic if the --add-pois-to-areas option is used. It may be valid for some named POI types to be found close together hence the option to omit certain types of POI from the nearby processing. I have the distance set to 50 with bus stops and cave entrances always included and this seems to work well for me (I don't use the default style). If --max-same-poi-distance is omitted or set to 0, the check works as previously. Please try and if OK, commit. Thanks, Mike

2 2

[Patch v0] fix sharp angles to optimise bicycle routing
by Gerd Petermann 24 Aug '15

24 Aug '15

Hi all, attached is a first working version of the patch, please test it with your style. I've also uploaded a binary: http://files.mkgmap.org.uk/download/277/mkgmap.jar It implements two new options: --x-fix-sharp-angles (I plan to remove this option when the code is ready, I now think the fixing should always be enabled) Is needed to activate the new code. --x-cycle-map Should be used when the map is only usable for cycling and walking, means, all vehicles (except foot) are treated like bicycles. (like with styles from Minko or Felix) The patch also removes the code for the option --adjust-turn-headings. The important code is in a new class AngleChecker, when you want to see what it does you should enable logging on info level like this: uk.me.parabola.imgfmt.app.net.AngleChecker.level=INFO When you find a message like ... sharp angle 28° at 38.343434,-0.770673 headings 40° 68° speeds 2 2 dest nodes 311 2103 followed by ... sharp angle 28° at 38.343434,-0.770673 changing arc with heading 68° -> 85° angle is now 45° you may want to compare the routing results for that location, once with and once without the option. (In Basecamp and Mapsource you can use Ctrl+T to jump to the location printed in the msg) While testing the code I found one problem in OSM data: Sometimes roads are duplicated, means, one road (or a part of it) hides the other. I consider this as a potential error in the OSM data, so a warning like this is produced: WARN: uk.me.parabola.imgfmt.app.net.AngleChecker 63240007.o5m: sharp angle < 1° at 38.355308,-0.483420 ,maybe duplicated OSM way with bearing 359° The message doesn't contain any OSM Id because often the available Ids are missleading due to the merging of roads. I use JOSM to fix these errors: Use Ctrl+J to jump to the given position (38.355308,-0.483420) and download a small area around the point. Next, use Alt+left mouse click multiple times on the node to see the connected roads. Gerd

3 3

What's the meaning of the 'has no region' warnings?
by Carlos Dávila 24 Aug '15

24 Aug '15

What is supposed to be wrong regarding warnings of type '(MapBuilder): 55114001.o5m: Highway EX-A2 has no region (define a default region to zap this warning)'

5 9

[Patch v1] fix sharp angles to optimise bicycle routing
by Gerd Petermann 24 Aug '15

24 Aug '15

Hi all, I just noted that v0 was not complete (source for AngleChecker missing). Attached is the new patch based on r3632, no functional change, but with less noise in logging. Binary: http://files.mkgmap.org.uk/download/278/mkgmap.jar Some more remarks: - The current code considers angles <= 45 as sharp. I am not sure about this value, maybe it should depend on the combination of road class/speed values that appear in the two arcs. I am working on this. - In some cases the log will show e.g. ... sharp angle 24° at 53.152893,8.711292 don't know how to fix it I think they are good candidates for an algo that adds an arc as suggested by Felix. For the node at 53.152893,8.711292 I would want to add an arc between the nodes 3305128837 and 2902056869. Maybe I find a way to code that... Gerd

1 0

question about ignored no_u_turn restriction
by Ben Konrath 22 Aug '15

22 Aug '15

Hi everybody, I recently noticed a bunch of warning messages about ignored no_u_turn restrictions. Here's an example: 2015/07/04 18:12:50 WARNING (RestrictionRelation): 17244023.o5m: Turn restriction (no_u_turn) http://www.openstreetmap.org/relation/4630872 (at http://www.openstreetmap.org/?mlat=41.890540&mlon=-87.805101&zoom=17) no_u_turn with equal 'from' and 'to' way and via node is ignored Looking at the rules for restrictions and the relation itself, I can't see what the problem is. https://wiki.openstreetmap.org/wiki/Relation:restriction http://www.openstreetmap.org/relation/4630872 Does anybody know why this particular restriction is being ignored? Thanks, Ben

5 15

sharp angles and routing
by Gerd Petermann 22 Aug '15

22 Aug '15

Hi Felix, please check: you said that sharp angles also have an effect on pedestrian routing, I was not able to reproduce that. Can you give an example? Gerd

3 8

Warnings about correct ways produced by --check-roundabout-flares
by Carlos Dávila 21 Aug '15

21 Aug '15

Option --check-roundabout-flares produces a lot of warnings about ways that are correct IMHO, like the following examples: (RouteNode): 55114001.o5m: Incoming roundabout flare road (http://www.openstreetmap.org/browse/way/22974731) points in wrong direction? http://www.openstreetmap.org/?mlat=39.476332&mlon=-6.340242&zoom=17 (RouteNode): 55114002.o5m: Outgoing roundabout flare road (http://www.openstreetmap.org/browse/way/53537671) does not finish at flare? http://www.openstreetmap.org/?mlat=36.471647&mlon=-6.207968&zoom=17 (RouteNode): 55114001.o5m: Incoming roundabout flare road (http://www.openstreetmap.org/browse/way/183666800) points in wrong direction? http://www.openstreetmap.org/?mlat=40.026175&mlon=-6.096136&zoom=17 (RouteNode): 55114001.o5m: Outgoing roundabout flare road (http://www.openstreetmap.org/browse/way/55608338) points in wrong direction? http://www.openstreetmap.org/?mlat=39.430758&mlon=-6.365738&zoom=17 (RouteNode): 55114002.o5m: Outgoing roundabout flare road (http://www.openstreetmap.org/browse/way/226321374) points in wrong direction? http://www.openstreetmap.org/?mlat=37.234124&mlon=-7.250831&zoom=17 Code for this check was written long ago now and perhaps could be improved some way to avoid such noise. I can supply more examples if needed, my log is full of them.

2 4

Wierd routing problem
by John Aldridge 19 Aug '15

19 Aug '15

I'm having a weird routing problem! I'm using CreateIMG (which uses mkgmap to do the work) to create a Garmin compatible map of the UK. I've installed this map into BaseCamp, and I'm trying to create a route. There's a point on a local minor road which BaseCamp refuses to route through *unless* the route options permit the use of 'Interstates'! There is no node in OpenStreetMap at this point, although BaseCamp, displaying the map I've created, does show a black dot at the point in question. I don't know what this black dot signifies. The problem point is at the centre of http://www.openstreetmap.org/#map=16/52.1631/0.2473 and the BaseCamp view of this area is http://www.jjdash.myzen.co.uk/temp/routeproblem.png This problem has only recently started happening, though I both have updated BaseCamp and built a new map from current data, and don't know which of these might be responsible. I am using a slightly customised set of stylesheets, but these have not changed since the last time this worked properly. I also know CreateIMG uses rather an old version of mkgmap, but again this has not changed. Any ideas? Or is there a better place to ask for help? Thanks in advance! -- Cheers, John

4 8