Hi all, I want to change the behaviour of splitter: If no bounding polygon is given, we can have two situations: a) the input file contains no bounding box. In this case splitter calculates a bbox that is automatically trimmed. b) the input file contains a bounding box. In this case splitter should - by default- try to trim this bounding box (and not more). If --no-trim=true is given, splitter should not trim the bbox. Trimming singular tiles doesn't make much sense, esp. not with keep-complete=true. We risk holes in the map and gaps in ways crossing the tile, eg. ferry lines OK? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/parameter-no-trim-tp5738361.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
On Fri, Nov 30, GerdP wrote:
Hi all,
I want to change the behaviour of splitter: If no bounding polygon is given, we can have two situations: a) the input file contains no bounding box. In this case splitter calculates a bbox that is automatically trimmed. b) the input file contains a bounding box. In this case splitter should - by default- try to trim this bounding box (and not more). If --no-trim=true is given, splitter should not trim the bbox.
Trimming singular tiles doesn't make much sense, esp. not with keep-complete=true. We risk holes in the map and gaps in ways crossing the tile, eg. ferry lines
OK?
Sounds good to me. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
participants (2)
-
GerdP -
Thorsten Kukuk