Hi Gerd Yes Ticker On Tue, 2021-05-18 at 15:56 +0000, Gerd Petermann wrote:
Hi Ticker,
which "existing behaviour" do you mean? That before r4703?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 18. Mai 2021 17:51 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Line direction flag, merging etc
Hi Gerd (& Minko?)
overlay files are undocumented and probably unused except in OpenFietsMaps. It is a very restricted way of doing what is now done with [... continue {with_actions}] or, even simpler, something like:
tourism=camp_site [0x2b03 resolution 24] [0x2b05 resolution 24]
[continue] allows for different resolution ranges, routing attributes etc and now, with {set mkgmap:has-direction= }, explicit control of this for each generated line (although see following).
Thinking about my previous suggestion of looking up each overlay copy linetype to set has-direction, this could be very dangerous in allowing different merging/filtering behaviour/filtering between all the copies, so the lines might not overlay each other.
I don't think overlays should be allowed to add any ugliness. The lineType as given in the rule should be the one that is checked against --line-types-with-direction. The replacement and all copies should have the same value for has-direction.
My implementation preserves the existing behaviour. I think it is quite tidy and it doesn't need another flag in MapLine.
Ticker