Hi Probably the Garmin meaning has changed over time and it is now a display characteristic on some devices. oneway should continue to set it. {set mkgmap:has-direction=no} should end up with it not set (but correct routing). My eTrex has always shown this (looking back at an old map). I'd just never hovered over a one-way road and noticed. Maybe I'd seen something like "M3 (N)" and just assumed the carriageway was named as such. It is a bit of a rubbish way of showing one-way compared with putting an arrow on the road. Ticker On Sat, 2021-05-15 at 17:24 +0000, Gerd Petermann wrote:
Hi all,
what about routable lines with oneway? Should this force the direction flag in IMG format? I found no oneway road in Garmin maps where the dir-flag was not set, but Tickers finding reg. the Etrex HCx: showing compass directions for those roads seem to say that there is no clear rule about the meaning of this flag.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen@hotmail.com> Gesendet: Samstag, 15. Mai 2021 18:30 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Commit r4715: rework of options for reverse merge
Hi all,
OK, I'll try to change the code so that oneway=* has no effect on the dir-flag for non-routable lines. It's a bit tricky because of the overlays rule file. At least the OFM style still uses this and I forgot what it is good for.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Samstag, 15. Mai 2021 17:38 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Commit r4715: rework of options for reverse merge
I agree. The style can test "oneway" and set mkgmap:has-direction if appropriate for non-roads.
Ticker
On Sat, 2021-05-15 at 14:53 +0000, Gerd Petermann wrote:
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@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@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@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev