- mkgmap-dev - The mkgmap lists

ANNOUNCE: Free Garmin MapSource installer available
by Ævar Arnfjörð Bjarmason 23 Sep '09

23 Sep '09

I've written a free installation program for Garmin's MapSource. It's aimed at the people who are maintaining Garmin map exports of the OpenStreetMap database. A lot of these exports[1] don't have a MapSource installer, some suggest proprietary solutions and some have a unconfigurable BAT file included or ask end-users to manually edit their registry after installation. I'd like to improve upon that, so I've written this: http://wiki.openstreetmap.org/wiki/Garmin_Mapsource_installer Here's blog post about it on the OpenStreetMap site: http://www.openstreetmap.org/user/%C3%86var%20Arnfj%C3%B6r%C3%B0%20Bjarmaso… Like it says in the blog I'm interested in getting feedback / testing from users & map distributors on how it fits their needs. So please download the installer for Iceland (or make your own!): http://osm.nix.is/latest/default/OSM_IS_default.zip And tell me how installing it in MapSource goes. Whether you can install the map from there onto your Garmin device. And what could be improved about the whole process. 1. http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Download

4 6

Commit: r1221: Avoid making unwanted nodes when --link-pois-to-ways is active.
by svn commit 23 Sep '09

23 Sep '09

Version 1221 was commited by markb on 2009-09-23 12:07:17 +0100 (Wed, 23 Sep 2009) Avoid making unwanted nodes when --link-pois-to-ways is active. When linking pois to ways it makes sense to consider the poi to be a node for the purposes of short arc removal. Unfortunately, this was done in a buggy fashion that would cause nodes to be created when they should not have been. Now, it just notices that a point could possibly become a node but it no longer increments the point's highway count so it won't become a node unless it really is shared by more than one way.

1 0

mkgmap, sendmap and family-name oddities
by Charlie Ferrero 23 Sep '09

23 Sep '09

Hello list, Can anyone explain the following discrepancy? 1. I invoke mkgmap with java -Xmx1500m -ea -jar ../mkgmap/mkgmap.jar -c UK_test_options.args (see attached file for options) 2a: I use sendmap to upload the file to my GPS 2b: I copy the file manually to the memory card Result of 2a: In the GPS, map tiles are listed as [description], [family-name], [date of creation] Result of 2b: In the GPS, map tiles are listed as [description], Area 6324999X, [date of creation] Obviously I'd like the maptiles to be listed as in 2a, but don't want to have to use sendmap because it's much much slower than using a card-reader. Any ideas on what's going on? -- Charlie # Set mkgmap options # # java -ea -Xmx1500m -jar mkgmap.jar -c thisfile # all paths have to be relative to the folder from which the batch file is running # ------------------------------------------------ # GENERAL OPTIONS # ------------------------------------------------ style-file:../mkgmap/resources/styles/charlie family-id: 134 product-id: 1 series-name: Charlie's maps (UK) family-name: Charlie's test map route remove-short-arcs latin1 max-jobs gmapsupp tdbfile #lower-case location-autofill=2 # Assign the region of the nearest city to each place, if the is_in tag doesn't already stipulate where it is # ------------------------------------------------ # TILE-BY-TILE OPTIONS # ------------------------------------------------ mapname: 63249998 description: Battersea country-name:UK country-abbr:GBR region-name:Greater London region-abbr:G London input-file: clapham.osm mapname: 63249999 description: Wimbledon country-name:UK country-abbr:GBR region-name:Greater London region-abbr:G London input-file: wimbledon.osm

5 6

--add-pois-to-areas and adress problems
by Christoph Wagner 22 Sep '09

22 Sep '09

Hello list, I just want to produce a garmin map, where you can see all adresses tagged in osm, even the adresses on a building polygon for example too. So I used the --add-pois-to-areas option and wrote just one line in the points style file: addr:housenumber=* {name '${name} (${addr:street} ${addr:housenumber})' | '${addr:street} ${addr:housenumber}'} [0x7100 resolution 24] I hoped that there would be nodes at the place of building-polygons tagged with adresses but it isn't so. I can see just the nodes that were tagged as nodes. What is the problem? Does the --add-pois-to-areas option ignore adress information? Is it possible to change that in a way? Thanks and sorry for my bad english... Christoph

1 1

Commit: r1198: Merge in the sea polygon patch from the multipolygon branch.
by Du Plessis, Bennie 22 Sep '09

22 Sep '09

Generate-sea does not work for me on Southern Africa. I use: 1)JRE 1.6 2)Source file GeoFabrik Africa 2009-09-04 extract with Southern Africa extracted from that with splitter 3)Splitter options: java -Xmx900m -jar splitter.jar^ GeoAfr.osm.bz2^ --mapid=11090906^ --max-nodes=3000000^ --overlap=0^ (also tried with default) --split-file=SuiderAfr.list 4)SplitFile # List of areas 11090906: -1644587,605843 to -885464,1677722# : -35.289,12.99998 to -19,36 5)MakeIt java -ea -Xmx1300M -jar Latest\mkgmap.jar^ (r1210) --name-tag-list=name:af,name^ --route^ --remove-short-arcs^ --road-name-pois^ --tdbfile^ --style-file=MyStyle^ --description=11090906SdAf^ --product-id=0906^ --overview-mapname=12090906^ --mapname=11090906^ --family-name=GeoSAfr0906^ --series-name=11090906^ --generate-sea^ --ignore-osm-bounds^ (also tried without) --gmapsupp^ 11090906.osm.gz Groete BennieD ##################################################################################### Scanned by MailMarshal - Marshal's comprehensive email content security solution. Download a free evaluation of MailMarshal at www.marshal.com #####################################################################################

2 1

Polygon offset too large - what does it mean?
by Nop 22 Sep '09

22 Sep '09

Hi! mkgmap r1196 quits with an error "polygon offset too large". When I use mkgmap r1163 with exactly the same data and parameters, no error occurs. What does this message mean? bye Nop

2 3

Commit: r1219: Fix null pointer exception, during creating extra rules.
by svn commit 22 Sep '09

22 Sep '09

Version 1219 was commited by steve on 2009-09-22 17:38:18 +0100 (Tue, 22 Sep 2009) BRANCH: style Fix null pointer exception, during creating extra rules. The teststyle/main style altered to excersize that code.

1 0

Commit: r1218: Add sections 4 and 9 with hard wired contents as they
by svn commit 22 Sep '09

22 Sep '09

Version 1218 was commited by steve on 2009-09-22 15:28:17 +0100 (Tue, 22 Sep 2009) Add sections 4 and 9 with hard wired contents as they are not fully understood by me... or at all in the case of 9. Searching works with these sections.

1 0

[PATCH v1] - Reduce number of Table A entries required
by Mark Burton 22 Sep '09

22 Sep '09

Reduce number of Table A entries. Previously, Table A entries were unique for each combination of start node, end node and RoadDef. But no information from the start and end nodes goes into Table A so we can ignore the start and end nodes and all roads within a given routing centre that use the same RoadDef can now share a Table A entry. This reduces the number of entries required which makes the .img files smaller and, hopefully, also improves the routing because routing centres can now cover a larger area. I have tested this with mapsource and on a Nuvi and it appears to work OK but it really needs more testing before it could be considered for committing. So, all feedback is welcome regarding the effect this patch has on routing performance. With the patch, the routing changed and I thought it was more sensible but perhaps that's just wishful thinking. My GB map shrunk from 180 to 174 Mb with this patch. The Nuvi calculated a route from Lands End to Thurso (800+ miles and quite a few tiles) in no more than 10 seconds. Cheers, Mark

5 7

Commit: r1217: Give route centre boxes a label that reports the size of its contents.
by svn commit 22 Sep '09

22 Sep '09

Version 1217 was commited by markb on 2009-09-22 12:21:05 +0100 (Tue, 22 Sep 2009) Give route centre boxes a label that reports the size of its contents. The label lists the number of nodes, the number of bytes taken up by the nodes and the number of entries in the a and b tables.

1 0