[mkgmap-dev] new option --add-boundary-nodes-at-admin-boundariesFrom Gerd Petermann gpetermann_muenchen at hotmail.com on Wed Aug 1 12:30:01 BST 2018
Hi Greg, my understanding is this: The additional nodes (only) help when you create multiple maps. For example, if you have a script that creates a map for a given geofabrik extract by executing splitter and mkgmap. If you feed that script 1st with Maine and 2nd with New Hampshire you get two different maps with overlapping tiles. If you use osmconvert to merge the two extracts before using the script there are no overlapping tiles and thus there is no need for the additional nodes. Gerd ________________________________________ Von: Greg Troxel <gdt at lexort.com> Gesendet: Mittwoch, 1. August 2018 12:36 An: Gerd Petermann Cc: mkgmap-dev at lists.mkgmap.org.uk Betreff: Re: AW: [mkgmap-dev] new option --add-boundary-nodes-at-admin-boundaries Gerd Petermann <gpetermann_muenchen at hotmail.com> writes: > seems the description is not clear enough. The default of this option > is "2", that means it is switched on by default. It has no effect > unless --route is also on. Thanks. Having it on by default if --route is on sounds good. (Separately, I wonder why --route isn't default. Does anybody really want a non-routable map these days? But that's a separate, very old question.) I am glad to see this option. I have been avoiding the issue by using the geofrabrik US northeast option. I wonder if it should be using states (admin=4) in addition, in the US.
- Previous message: [mkgmap-dev] new option --add-boundary-nodes-at-admin-boundaries
- Next message: [mkgmap-dev] new option --add-boundary-nodes-at-admin-boundaries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list