I find that while using many levels the overall map size increases, each zoom level is a bit better. So I use all resolution from 24-18 for the map, and 11-17 for the overview map. levels = 0:24, 1:22, 2:21, 3:20, 4:19, 5:18 overview-levels = 6:17, 7:16, 8:15, 9:14, 10:12, 11:11 For contourlines of course no overview map, and starting later.
As for highways - they usually are inside a highway relation, but without specifying which is which direction or anything. In general each direction has a oneway=yes/1/-1/reverse tag. but yes that relation will not help at all I feel. There is no way inside osm data to directly tell that it goes two ways and be able to say from resolution 18 or 19 onwards only to say show direction=forward vs direction=forward and direction=backward lines. On Tue, 4 May 2021 at 20:33, Gerd Petermann <[email protected]> wrote: > Hi Felix, > > it probably depends on the --levels option, means, how many levels you put > into a gmapsupp. > > And yes, I don't have a clear idea how to detect parallel lines which will > / should collapse into one line. > > Gerd > > ________________________________________ > Von: mkgmap-dev <[email protected]> im Auftrag von > Felix Hartmann <[email protected]> > Gesendet: Dienstag, 4. Mai 2021 13:19 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution > 23 raster problems > > Wow - looks really good. The main problem I feel is now that sometimes > highways you can see both directions apart - while before this was less > rare - or lost in the jaggedness. > > --x-simplify-filter-line-errors=23:3.6,22:4.2,21:5.4,20:6,19:7,18:7.5,16:8,15:9 > --x-simplify-filter-polygon-errors=23:4.6,22:7,21:8,20:9,15:10 > --polygon-size-limits=24:16,23:14,22:12,21:11,20:10,19:9,18:8,17:7,16:6,15:5,14:4,13:3,12:2,11:0,10:0 > seems to give pretty nice results - and much faster on my Garmin 600 at > lower resolutions. > > I guess those highways with dual directions are much harder to solve... > > On Tue, 4 May 2021 at 17:24, Gerd Petermann < > [email protected]<mailto:[email protected]>> > wrote: > Hi Felix, > > OK, I am happy to hear feedback regarding the latest changes the branch. > Next planned step is to check if the simplify4.patch still improves things > and maybe improve it further. > > Gerd > > ________________________________________ > Von: mkgmap-dev <[email protected]<mailto: > [email protected]>> im Auftrag von Felix Hartmann < > [email protected]<mailto:[email protected]>> > Gesendet: Dienstag, 4. Mai 2021 11:03 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution > 23 raster problems > > well I never got the merge-more patch actually running as together with > simplify v4 it did not change anything for me. I'm waiting for updates on > the new branch to test things. > I still feel level>=1, the higher the level the less exact it needs to be. > It just needs to be small and beautiful from resolution 21 and lower. While > actually driving/riding/walking you will always use 24-22 (even 22 only in > car I feel. Maybe 21 on highways). > > Those levels are important on PC and GPS device for orientation. And while > actual switchback turns on a road would be quite worthwhile, those zig zag > things aren't. > > > _______________________________________________ > mkgmap-dev mailing list > [email protected]<mailto:[email protected]> > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > -- > Felix Hartman - Openmtbmap.org & VeloMap.org > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > -- Felix Hartman - Openmtbmap.org & VeloMap.org
_______________________________________________ mkgmap-dev mailing list [email protected] https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
