okay thanks I understand it now with the more detailed description. Strangely making sure direction is set to no following the section that should not be reversed led to an increase and not a decrease in file size - but that change was minimal. On Sat, 15 May 2021 at 17:55, Andrzej Popowski <popej@poczta.onet.pl> wrote:
Hi Gerd,
I understand, that mkgmap:has-direction=no takes priority over list and that oneway is independent of has-direction.
Next RoadMerger merges roads. It will not reverse roads with oneway flag true or direction flag true and it will not merge roads which have different oneway or direction flags. If it does that
Looks OK. I think that lines with and without direction flag could be merged, but this probably would be a rather rare case if not error in style.
Each line and road is converted to a MapLine or MapRoad object. Both have a dir-flag, MapRoad also has a pointer to further data for NOD which also contains the oneway flag. The dir-flag is set if the ConvertedWay says it is a oneway or has direction (or both).
I guess, that oneway flag in NOD is only set because of oneway description in data. I think has-direction value shouldn't influence routing.
-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Openmtbmap.org & VeloMap.org