April 2009 - mkgmap-dev - The mkgmap lists

[PATCH v1] Add --no-sort-roads option
by Mark Burton 05 Apr '09

05 Apr '09

The attached patch adds an option (no-sort-roads) to turn off the generation of sorted road data. Hopefully, that process can be made more efficient (if that is indeed where the time is going) but in the meantime this option can be used to restore the performance to it's previous level. Cheers, Mark

2 3

Performance of mkgmap.jar and splitter.jar
by Felix Hartmann 05 Apr '09

05 Apr '09

I think during the last weeks the increased feature set of mkgmap is really nice, not so nice is the performance though..... I made some tests - see below. I think with the current versions performance really has gone by the wayside. It takes 4times as long against austria.osm compared to rev 937. I will check against some other versions to find out if there was one specific patch that fucked up the performance or if it increased slowly.... Compiling austria.osm (from geofabrik) with my custom style-files (6layers) takes 788 seconds with rev. 937, but 3519 seconds with rev 988. 1. Performance Tile Splitter. Split austria.osm with already established areas.list (4 areas) takes 120sec, the same but austria.osm.bz2 took astonishing 312 seconds. The tile splitter works significantly faster on unzipped sources. 2. Performance mkgmap rev 988 .gz zipped: The bigger the tile size you try to get done in one step, the better the performance. For tryout style1 calculating the 4 tiles took 6 minutes (about 1:30 minute for tiles 1-3, and *3 minutes* for the last and biggest tile (which still works fine in Mapsource though). The same tiles trying to calculate with a bit more heavyweight (only lines though, no Polygons or POI) style2 - the first 2 tiles took a bit less than 1 minute each, the third (and only second biggest tile) took *15 minutes,* and the forth took 2:30 minutes. I don't know what causes mkgmap to fuck up here on the third tile. If someone wants to have a look at the exact configuration, I can send the configuration files (including batch to run it through). In total it took from *04:45 for the first style, but 20:21 *for the second style. 2b) the same again this time from unzipped sources: The first 3 tiles on stylefile1 got done in about 2 minutes, the fourth one took again 3 minutes. That's 04:42 compared to 04:45 zipped, so no significant difference). The first 2 tiles on stylefile2 got done in about 1:20, the third now took 17 minutes and the fourth 2 minutes.(so even worse than before; thats 20:35 unzipped compared to 20:21 zipped) The filesize of the resulting tiles with style1 is: 2.54MB 4.70MB 4.31MB 8.03MB The filesize of the resulting tiles with style 2 is: 2.78MB 5.87MB 5.90MB 8.96MB 2c) trying to run the two styles on the whole austria.osm without splitting results in: Stylfile1: 3:36:48 (so thats about a full minute quicker than the the country split into 4 tiles). Stylefile2: 16:48 (that's about 4 minutes quicker, 4 tiles took 20:35). 2d) Speed of processing Austria.osm with mkgmap rev 937 Stylefile1: 2:52 Stylefile2: 3:17 *My whole mapset: 788 seconds (compared to 3519 seconds with rev 988)* P.S. on a related note, in case the style-file is not found there should be an error message, and not a defaulting to the default mkgmap style. P.P.S: see stylefile2, it's really short an simple - nothing else (no POI or Polygons), I have no clue why it takes so long on Austria.osm respectively tile three (having run splitter jar with 25000000)..... mtb:scale:uphill=0 [0x1d resolution 22] mtb:scale:uphill=1 [0x1e resolution 22] mtb:scale:uphill=2 [0x26 resolution 22] mtb:scale:uphill=3 [0x29 resolution 22] mtb:scale:uphill=4 [0x2b resolution 22] mtb:scale:uphill=5 [0x1b resolution 22] highway=primary [0x04 road_class=0 road_speed=3 resolution 19] highway=primary_link [0x04 road_class=0 road_speed=2 resolution 19] highway=secondary [0x05 road_class=1 road_speed=3 resolution 16] highway=tertiary [0x06 road_class=1 road_speed=4 resolution 20] highway=residential [0x07 road_class=1 road_speed=3 resolution 22] highway=living_street [0x07 road_class=1 road_speed=3 resolution 22] highway=unclassified [0x07 road_class=1 road_speed=4 resolution 22] P.P.P.S - the commandline for mkgmap: "start java -jar -Xmx1184M d:\garmin\mkgmap_svn\dist\mkgmap.jar --description=02_Austria --style-file=2 --route --net --country-name=AUSTRIA --country-abbr=AUT --country-name=AUSTRIA --ignore-turn-restrictions --mapname=63260001 austria.osm"

3 14

Commit: r995: Fixed syntax errors.
by svn commit 05 Apr '09

05 Apr '09

Version 995 was commited by steve on 2009-04-05 14:26:00 +0100 (Sun, 05 Apr 2009) Fixed syntax errors.

1 0

Commit: r993: Improve efficiency by only checking points that are nodes for equality.
by svn commit 05 Apr '09

05 Apr '09

Version 993 was commited by markb on 2009-04-05 09:49:38 +0100 (Sun, 05 Apr 2009) Improve efficiency by only checking points that are nodes for equality. Bug fix - node ids start at 1 not 0.

1 0

Commit: r992: Added no-sort-roads option to suppress generation of the sorted road data.
by svn commit 05 Apr '09

05 Apr '09

Version 992 was commited by markb on 2009-04-05 09:49:27 +0100 (Sun, 05 Apr 2009) Added no-sort-roads option to suppress generation of the sorted road data. Also, fixed default country name/abbr + general tidying.

1 0

Restaurant+hotel not appearing in nuvi
by Carlos Dávila 03 Apr '09

03 Apr '09

Hello I have a node tagged as follows: amenity=restaurant name=some_name tourism=hotel If I search for it in my nuvi, it appears under Food, but not under Accommodation. Shouldn't it appear in both sections? Cheers Carlos

6 11

Restaurant+hotel not appearing in nuvi
by Felix Hartmann 03 Apr '09

03 Apr '09

Some month ago I proposed the feature to "double" elements already. Right now I have to use 6 style-files for each map tile to get all the elements I want. We would need a seperate file in the style-file where you can write in all features that should be checked for independantly whether or not an object has already be included (for the example this file is called "doublecheck"). i.e. imagine a street object with the following attributes: highway=track; bridge=yes; tracktype=grade1 In the style file "lines" we search for: highway=track [0x30 resolution 18] In the "doublecheck" file we search for: bridge=yes [0x31 resolution 20] tracktype=grade1 [0x33 resolution 20] In the typ we now define (for simplicity 9=transparent, 0 =yellow, 1=red, 2=black) 0x30: 11111111111111111111111111111111 0x31: 22222222222222222222222222222222 99999999999999999999999999999999 22222222222222222222222222222222 0x32: 00009999000099990000999900009999 00009999000099990000999900009999 99999999999999999999999999999999 99999999999999999999999999999999 99999999999999999999999999999999 99999999999999999999999999999999 99999999999999999999999999999999 The highway=track; bridge=yes; tracktype=grade1 Mapsource or on the PNA would now look like the following: 00009999000099990000999900009999 00009999000099990000999900009999 22222222222222222222222222222222 11111111111111111111111111111111 22222222222222222222222222222222 99999999999999999999999999999999 99999999999999999999999999999999 There is one thing to notice however. the file "doublecheck" needs to be run AFTER the file "lines" and after the file (For Polygons this doesn't matter as we have to define a "draw order" in the typfile determining what is shown on top). POI are not possible to be shown with transparency on top of each other. I would propose having the file "doublecheck" only for lines and for Polygons. The "points" file should by default allways make one POI per found indicator. So a POI with amenity=restaurant; amenity=hotel should always be put as two points into the resulting map. The order of operation in the style-file "points" will determine what shows up on the map. On Mouseover however we can see all POI - and also searching for restaurant as well as hotel we are able to find the amenity=restaurant; amenity=hotel. Inside the "points" file we would need a "break" command however. Imagine a POI, amenity=restaurant;cuisine=thai;amenity=hotel. in the points file we define: cuisine=thai [0x1012 resolution=20 break amenity=restaurant) So that after finding we have a thai restaurant, we don't get the entry amenity=restaurant, but we would still get a dedicated POI for amenity=hotel. Of course I could right now achieve all this by running several style-files on each input file (objects from higher mapnames will show above objects from lower mapnames), but this takes much more time (the data has to be read to memory each time) and you end up with many more (many very small tiles, e.g. a tile showing nothing but bridges and tunnels) tiles than needed.

1 0

[PATCH v10] - patch to support road find by name (now thinking about putting this in trunk)
by Mark Burton 03 Apr '09

03 Apr '09

v10 - based on r987. Functionally, should be identical to last version. If no one has any problems with either v9 or this version, I would like to commit this within the next few days. So please speak up if you have any issues with it. ----------- Hi, The attached patch is for the current SVN trunk and it generates the sorted road data that is required by the gps to find roads/intersections by name. As for the number field, I haven't thought yet how that would get its data. Please test this patch and report success/failure. If it doesn't break anything for anyone, I would like to commit it fairly soon as I think that quite a few people will be happy to have street finding added to the trunk. Cheers, Mark

6 13

Some weird route results
by Lambertus 02 Apr '09

02 Apr '09

I encountered some strange things while testing routing using the maps built by Mkgmap-r991 on the GPSmap 60CSx and MapSource: * A long bicycle route used a service ramp for busses to get on the motorway rather close to the starting point and stayed on the motorways until close to the endpoint. The service ramp is tagged: highway=service oneway=yes access=no psv=yes * The same long bicycle route in MapSource was 200km long, did not use any motorways but made a huge detour in the first section of the route (going in the southeast direction instead of northeast) The latter part of the route was OK though. Yournavigation.org calculates a route between the same endpoints of about 120km. This is the tested route: http://yournavigation.org/?flat=52.159151&flon=5.968067&tlat=52.995343&tlon…

1 0

[PATCH] minor change to motorway exits
by Carlos Dávila 01 Apr '09

01 Apr '09

I've added colon to exits ref to separate from name, because IMHO current format may be a little confusing with some exit names. I'm not developer, just guessing, so check if it's right (works for me) and doesn't break anything. Cheers Carlos Index: resources/styles/default/points =================================================================== --- resources/styles/default/points (revisión: 991) +++ resources/styles/default/points (copia de trabajo) @@ -46,10 +46,10 @@ highway=bus_stop [0x2f08 resolution 21] -highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } +highway=motorway_junction { name '${ref}$: ${name}' | '${ref}' | '${name}' } highway=motorway_junction [0x2000 resolution 16] -highway=services { name '${ref} ${name}' | '${ref}' | '${name}' } +highway=services { name '${ref}$: ${name}' | '${ref}' | '${name}' } highway=services [0x210f resolution 16] historic=museum [0x2c02 resolution 20]

2 2