Richard Welty <rwelty@averillpark.net> writes:
On 11/24/12 10:07 AM, Carlos Dávila wrote:
El 24/11/12 03:08, Richard Welty escribió:
$ java -jar ../mkgmap/mkgmap-r2379/mkgmap.jar capitaldistrict-2012-11-23.osm --index --gmapsupp
From mkgmap help: "Note that option order is significant: An option only applies to subsequent input files." So you should put your *.osm file last in the mkgmap call ah, i missed that. the change seems to have done it, address lookups in the nuvi now work.
There's something else that I think is highly non-obvious to new people: there are a ton of options (no surprise), but the defaults are not really useful. The norm among mkgmap users is to give a large number of options, but for some reason (perhaps trying to keep behavior consistent) these options are not default. In the --remove-short-arcs case, I don't understand why anyone wouldn't want it. Another point is that you probably want --route in addition to --index. FWIW, here are the options I use that I suspect everyone should use (or mine are off from the consensus and I should change): --tdbfile \ --reduce-point-density=4 \ --reduce-point-density-polygon=8 \ --merge-lines \ --route \ --check-roundabouts \ --check-roundabout-flares \ --remove-short-arcs=6 \ --adjust-turn-headings \ --report-similar-arcs \ --report-dead-ends=2 \ --add-pois-to-areas \ --index \ (Actually, "everyone should use add-pois-to-areas" is perhaps controversial.) I think it would be good for all options to have a --no-option variant, and then to default each option to what the group consensus is in terms of "what should a user (who doesn't really understand all the subtleties yet) who just wants to take OSM bits and make a map for their device for general use want".