- mkgmap-dev - The mkgmap lists

Should inter tile routing still work when splitting Splitter results again?
by Lambertus 01 Oct '09

01 Oct '09

It's a bit difficult to specify a short topic title for this, so here it goes: Goal: Render the world with tiles that are as large as possible. Problem: If you split e.g. America in large tiles with e.g. 1.400.000 nodes then you end up with a lot of tiles that do not render. If you want everything to render then you need to use 400.000 nodes or so which results in more then 1000 tiles. You can get around this by manually defining the tiles sizes which is what I used to do (or use a density map, but afaik that doesn't work yet). So this time I've done something else: A solution: I created a PHP script that splits America with an high initial node count (of e.g. 1.400.000) and tries to render each resulting tile. If a tile render fails then that area is split again with an ever lower node count until at least two subtiles emerge which are then rendered. This process continues recursively until all tiles are rendered or the node count gets too low and splitting is aborted. The result: Neighboring tiles sometimes overlap because splitter seems to use a little larger bbox for splitting then what the source file contains. You can see the result of this on http://garmin.na1400.info/routable.php The question: Will routing be a problem because the result of recursively splitting and rendering results in tiles that apparently do not line up perfectly? I've done a few tests and it feels that routing has become worse, but I don't have a definitive answer. If so, what can be done about this? I'm curious if anyone (Chris?) has ideas about it. I can provide the script to anyone who's interested. Just send me an email off-list.

7 14

Mkgmap appears to hang on some split files
by Lambertus 01 Oct '09

01 Oct '09

While trying to get a new world map update out the door I noticed that Mkgmap sometimes hangs on an OSM data file produced with Splitter. When this happens the CPU is at 100% constantly for hours (e.g. all night) until I kill the process. The problem occurs in r1222 and also r1228. The following command was used for Mkgmap (I know the code-page is redundant): java -Xmx1792M -ea -jar mkgmap.jar --latin1 --code-page=1252 --name-tag-list=name:en,int_name,name --remove-short-arcs --add-pois-to-areas --make-opposite-cycleways --link-pois-to-ways --description='OSM World Routable' --route --series-name='OSM World Routable' Some problematic OSM files are below (created with Splitter r97 and max-nodes=1.200.000): http://planetosm.oxilion.nl/~lambertus/73240155.osm.gz http://planetosm.oxilion.nl/~lambertus/73240185.osm.gz

4 23

Suppressing or fixing zero-length arc warnings
by Marko Mäkelä 01 Oct '09

01 Oct '09

I have fixed some zero length arc warnings in the Finland extract. The count has gone down from 334 to 289. Most warnings are now for unnamed roads. Some of them are badly mapped cycleways or footways, but some are genuine zero-length arcs that I think should be silently dropped or merged by mkgmap. There are some cases that I am having trouble with: (1) steps and short ramps or paths around them, e.g., http://www.openstreetmap.org/browse/way/31345355 at http://www.openstreetmap.org/?lat=60.15495&lon=24.86515&zoom=17 Perhaps mkgmap should merge the highway=steps to highway=footway? Could this be done at the style-file level somehow? (2) short highways that end at some region boundary, such as this one: http://www.openstreetmap.org/browse/way/31359067 http://www.openstreetmap.org/?lat=60.15515&lon=24.88084&zoom=17 Could we introduce a tag for short arcs, similar to noname=*? It could be in the mkgmap namespace and renamed by a style file. For example, to suppress warnings about short steps, just add a rule like this: highway=steps { add mkgmap:zerolength=yes } (3) crossings on narrow city streets where the footway has been split into tiny segments due to a tram line crossing: http://www.openstreetmap.org/browse/way/28842855 http://www.openstreetmap.org/?lat=60.16600&lon=24.94182&zoom=17 See the Bulevardi/Yrjönkatu crossing. What to do about this? The same work-around as above? Marko

2 7

Issue with exits ref and possible patch
by Nakor 01 Oct '09

01 Oct '09

Hello, I have noticed that in case an exit node is linked to several highways (maybe this is bad mapping practice but it exists) and one of them does not have a ref tag, mkgmap issues a warning that the exit was not assigned a ref (see nodes 62152165 and 61852851 for an example). Below is an patch that tries to fix this: Index: src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java =================================================================== --- src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java (revision 1246) +++ src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java (working copy) @@ -432,19 +432,21 @@ for (Node e : exits) { String refTag = Exit.TAG_ROAD_REF; if(e.getTag(refTag) == null) { + String ref = null; for (Way w : motorways) { - String ref = w.getTag("ref"); if (w.getPoints().contains(e.getLocation())) { - if(ref != null) { - log.info("Adding " + refTag + "=" + ref + " to exit" + e.getTag("ref")); - e.addTag(refTag, ref); - } - else { - log.warn("Motorway exit is positioned on a motorway that doesn't have a 'ref' tag"); - } - break; + ref = w.getTag("ref"); + if(ref != null) + break; } } + if(ref != null) { + log.info("Adding " + refTag + "=" + ref + " to exit" + e.getTag("ref")); + e.addTag(refTag, ref); + } + else { + log.warn("Motorway exit is positioned on a motorway that doesn't have a 'ref' tag"); + } } } Thanks, N.

2 2

Commit: r1246: Impelent mdr 4 and 9 as best as we know.
by svn commit 30 Sep '09

30 Sep '09

Version 1246 was commited by steve on 2009-09-30 10:54:40 +0100 (Wed, 30 Sep 2009) BRANCH: mdr Impelent mdr 4 and 9 as best as we know. The unknown byte in mdr4 is set to a constant, we still don't know what it is there for. Plenty of things appear to work still. mdr10 is grouped based on the primary type and this grouping is indexed by mdr9. The categories menu is now useful and will restrict the things returned. Note that it is not perfect yet, no matter what category you select you always get a couple of pubs and a bus stop included in the results. This is probably down to type/subtype confusion which I will try to fix next.

5 6

Re: [mkgmap-dev] Commit: r1198: Merge in the sea polygon patch from
by Du Plessis, Bennie 30 Sep '09

30 Sep '09

Tomas I used your advice and built a map of SA with sea successfully. When building SA from one tile, the sea is correct with only some islands drowned, (I download Africa from geofabrik and extract southern Africa from it with splitter because geofabrik SA cuts the coastline at the country border and not at the tile border.) When I build SA from 4 tiles (Windhoek; Jhb;Durban;Capetown) the sea and land is reversed in some tiles, and correct in some. I guess some splits in the coastline made by splitter does not get merged again / correct by mkgmap? BennieD ##################################################################################### Scanned by MailMarshal - Marshal's comprehensive email content security solution. Download a free evaluation of MailMarshal at www.marshal.com #####################################################################################

5 6

Commit: r1245: In mdr10 the top-bit flag is to indicate that the name
by svn commit 30 Sep '09

30 Sep '09

Version 1245 was commited by steve on 2009-09-30 08:26:15 +0100 (Wed, 30 Sep 2009) BRANCH: mdr In mdr10 the top-bit flag is to indicate that the name is not repeated - ie if it is unset, then the name is the same as on the previous POI. The type field is the subtype, unless there is not a subtype, when it is the type - that last part is true for cities anyway.

1 0

Commit: r1244: Fix sorting of records in MDR 4.
by svn commit 29 Sep '09

29 Sep '09

Version 1244 was commited by steve on 2009-09-29 14:46:30 +0100 (Tue, 29 Sep 2009) BRANCH: mdr Fix sorting of records in MDR 4. Doesn't appear to have any effect, so perhaps they do not actually need to be sorted.

3 2

Problem with special Garmin label codes
by Gert Münzel 29 Sep '09

29 Sep '09

Hi, i would like to use also other special Garmin label codes like ~[0x1f] not only the highway shields.. I could manage modifiying the "HighwaySymbolFilter.java" of mkgmap by adding a symbol. The usage also works if i only use one special code like in: highway=secondary {name '${ref|highway-symbol:stname} ${name}' | '${ref|highway-symbol:stname}' | '${name}' } where "stname" is the new symbolentry for ~[0x1f]. But i would use a action like: highway=secondary {name '${ref|highway-symbol:oval} ${name|highway-symbol:stname}' | '${ref|highway-symbol:oval}' | '${name}' } which should be give me as result e.g. a ~[0x06]B51~[0x1f]Hauptstrasse if ref=B51 and name=Hauptstrasse But this doesn't work. The second code always is ignored by mkgmap. How can i get to work? cheers Gert

1 1

Commit: r1243: Now includes all POIs.
by svn commit 29 Sep '09

29 Sep '09

Version 1243 was commited by steve on 2009-09-28 22:48:16 +0100 (Mon, 28 Sep 2009) BRANCH: mdr Now includes all POIs. There is no categorisation however. You can find everything when All points of Interest is selected, but if you select any of the drop down boxes such as attractions, food & drink etc, then nothing will be found.

2 1