[mkgmap-dev] parameter no-trim
From Thorsten Kukuk kukuk at suse.de on Fri Nov 30 09:29:01 GMT 2012
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)
- Previous message: [mkgmap-dev] parameter no-trim
- Next message: [mkgmap-dev] splitter maximum tile size
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list