August 2009 - mkgmap-dev - The mkgmap lists

Routing with the default style
by Nop 14 Aug '09

14 Aug '09

Hi! I am just having my first look at creating a routable map. It appears that the default style completely disregards the access tags access=no, vehicle=no, motorvehicle=no and motorcar=no. Naturally I'd like to exclude these from routing, but there seem to be no rules evaluating them in the default style. Is this really the case or are those tags somehow hardcoded in mkgmap? bye Nop

3 3

splitter: small patch and wishlist
by Valentijn Sessink 14 Aug '09

14 Aug '09

Hello list, A small wish list for splitter: - honour "action='deleted'" in the input file. Rather trivial to write, but I don't send a patch because you would be horrified by my code. - make it possible to use hex data in areas.list (trivial patch, see below). Best regards, Valentijn

2 4

best practice in adding address info for enhancing POI address search in Garmin units
by maning sambale 13 Aug '09

13 Aug '09

Hi, Perhaps not entirely appropriate here, but just the same here goes. I am planning to finally incorporate address search in my Philippine garmin map. Currently, I always use --no-poi-address switch because we lack address info in our data for the Phil. There are several ways to add this for mkgmap, Karlsruche schema and the is_in tag. What would be the best and more efficient way to enable address info in the POIs? My previous attempts to use the is_in tag as a proxy to address info yield showed inaccurate results. My guess would be the full Karlsruche schema in liue of the is_in tags. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 2

Commit: r1133: Rounding fixes when placing points on lines
by svn commit 13 Aug '09

13 Aug '09

Version 1133 was commited by steve on 2009-08-13 23:57:39 +0100 (Thu, 13 Aug 2009) Rounding fixes when placing points on lines within a subdivision. Also a small fix to rounding in the subdivision width/height calculation. -Elrond

1 0

Commit: r1132: Documentation update for overview-mapname.
by svn commit 13 Aug '09

13 Aug '09

Version 1132 was commited by steve on 2009-08-13 21:13:32 +0100 (Thu, 13 Aug 2009) Documentation update for overview-mapname. - Valentijn Sessink

1 0

Multipolygons
by Steve Ratcliffe 13 Aug '09

13 Aug '09

Hi I am going to merge all the multipolygon fixes. Including, if appropriate, the sea polygon changes. In addition to the patches sent to the list I also have permission to use the attached patch from Olaf Kähler which he describes as follows: > I guess, mkgmap has a bug with "vanishing islands" in case of > multipolygons. The major problem seems to be, that in the polygon > splitting process (PolygonSplitterBase.java), the Java awt methods mess > around with the inner polygons, that were previously merged into the > outer polygons. I included a patch, that somewhat works, but still seems > to have a few issues. I've also included sample .osm files to explain > these issues: I'd appreciate it if anyone who understands the polygon issues takes a look at the patch. Also if you have an test cases which don't work with the current trunk but might be fixed by the outstanding patches let me know. ..Steve

3 5

[PATCH v3] - min arc length fixes
by Mark Burton 13 Aug '09

13 Aug '09

v3 This patch is getting serious! To reduce the number of short arcs that are being generated at tile boundaries, this now clips the ways before the short arc removal is done. However, it isn't a perfect solution because some map data is very hard to deal with: a - If a way crosses a tile boundary right in the corner such that both ends are clipped and the resulting sub-way is less than 5m long, it will fail to fix that. A possible workaround could be to introduce extra points to elongate the arc. b - a much more common problem is where a way forks very close to a tile boundary and more than one of the connected ways cross the boundary so you end up with several boundary nodes that should be merged to remove the short arc(s) but they can't be moved as they are boundary nodes! I believe that this could be fixed by not merging the forking node but, instead, moving it away from the boundary such that the ways connected to it that do cross the boundary are not less than 5m long! Alternatively, adding extra points to elongate the forking arcs could be done. With this patch, I processed a 14 tile map of the Netherlands and it produced 21 of these short arc errors (all due to forks close to the tile boundaries). I then tested the routing at 5 of these positions (using mapsource) and only 1 of the 5 showed any sign of breakage, the other 4 all routed happily in all directions. The one that was broken was a junction of three ways and one pair of the ways had no connectivity but the others were ok. On the upside, the patch removed 147 short arcs introduced by the clipping. So more work is required here to fix the corner cases (ha ha) but please test this patch anyway as I expect it to have problems due to the big change it has introduced. As usual, all feedback is appreciated. ---------------- v2 of this patch not only enables remove-short-arcs by default when routing is in use (as previously discussed on ML) but it also fixes some problems in the way splitting code. I would be grateful if people could test this patch because it could possibly cure some routing failures. Cheers, Mark

1 1

Garmin Nuvi asks province
by Valentijn Sessink 13 Aug '09

13 Aug '09

Hi, A bit of a strange thing: my Garmin mkgmap maps ask the "provincie" (Province? State? County? Whatever you guys call it over there ;) when I want to route to an address. I normally build my map with country="Netherlands" and country-abbr=NL, I also tried no country and abbrev, but it keeps asking for a "Provincie". Whatever I enter, Garmin can't find it and this makes routing to an address pretty much infeasible. On the regular map, it just asks me if I'm in the Netherlands and then I can enter street and city names. java -enableassertions -Xmx1800m -jar ~/garmintest/mkgmap/dist/mkgmap.jar --country-name="" --country-abbr="" --family-name="Openstreetmap Netherlands `date -I`" --latin1 --remove-short-arcs --lower-case --preserve-element-order --location-autofill=1 --gmapsupp --route --net --tdbfile -c template.args What am I doing wrong? I guess this is just a wrong option somewhere? Valentijn

7 8

inverse oneways
by Chris-Hein Lunkhusen 13 Aug '09

13 Aug '09

Good Day, is mkgmap able to handle inverse oneways (oneway=-1) correctly (routing opposite to the ways direction) ? Chris

2 1

Putting the DP code under the microscope
by Mark Burton 13 Aug '09

13 Aug '09

Hi, As today's topic is the DP code, I thought I would take a close look. Not sure, but is the i-- on line 93 erroneous? As i will be decremented at the end of the loop anyway, it seems to me that the extra decrement will give rise to the possibility that a Coord won't be tested to see if it's a CoordNode and so it will get zapped if it's not outside the error tolerance? Do we care? Cheers, Mark

5 18