Hi Ticker, sounds good. I'm making progress with a better ShapeMerger that produces less jitter, but so far it still produces some. Will try it later..
Gerd ________________________________________ Von: mkgmap-dev <[email protected]> im Auftrag von Ticker Berkin <[email protected]> Gesendet: Donnerstag, 27. Mai 2021 12:49 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] special case where splitting fails without a log message Hi Gerd I think this can cope with any number of lines, in either/both directions, following the same path. Also it should give better output if same number of lines in both directions. With debug, if it notices a problem, it generates a GPX trace of the original and traces of all the resultant bits individually in a subdirectory relevant to the split line. I've tested it on a few examples, but I'll stress-test GBR again and check the shapes where it detects problems. I probably need to tidy up some message levels and comments. Ticker On Wed, 2021-05-26 at 11:17 +0100, Ticker Berkin wrote: > Hi Gerd > > I have to design a shape that does this and think what it means. With > the extra handling needed for identical opposite lines it will be > easy > to detect. Maybe possible to just chuck it. > > I'm out for the rest of the day so can't do anything until tomorrow. > > Ticker > > On Wed, 2021-05-26 at 08:46 +0000, Gerd Petermann wrote: > > Hi Ticker, > > > > OK, I think your patch improves some cases. I've also fixed another > > potential cause for these problems with r4744. > > > > I think I have to find a way to avoid those segments which are > > visited multiple times in the same direction. There's probably > > always > > an alternative merge order that avoids this. > > > > Gerd > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
