[mkgmap-dev] Commit r4715: rework of options for reverse merge
From Gerd Petermann gpetermann_muenchen at hotmail.com on Sat May 15 15:53:45 BST 2021
I think the important question is if the oneway tag should be evaluated for non-routable lines. Felix already said no, I agree with that. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk> Gesendet: Samstag, 15. Mai 2021 16:04 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Commit r4715: rework of options for reverse merge Assuming that the output device shows the direction on lines with direction and doesn't on lines without: Another example is, say, [intermittent] water using type [0x26] 0x1f. stream/river will have a direction and canal/ditch won't. There will be others, under the control of the Style/TYP, so I don't think mkgmap should check/warn of this situation. Ticker On Sat, 2021-05-15 at 12:59 +0000, Gerd Petermann wrote: > I only thought about non-routable lines and LineMerger. For roads it > is normal to have different flags because of the oneway tag. > Maybe I make too many assumptions about the possible usage of > types... > > Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev at lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
- Previous message: [mkgmap-dev] Commit r4715: rework of options for reverse merge
- Next message: [mkgmap-dev] Commit r4715: rework of options for reverse merge
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list