[mkgmap-dev] Line direction flag, merging etc
From Ticker Berkin rwb-mkgmap at jagit.co.uk on Tue May 18 14:53:06 BST 2021
Hi Gerd The code in low-res-opt looks like ignore-oneway-for-lines.patch. The disadvantage of this, as I see it, is that has-direction can't be forced false for one-way roads. I think my version is clearer. Considering substitute lines from /overlays: I had intended that they all (first and duplicates) have the same has -direction value as the original. An alternative is that the first has the original has-direction value and the duplicate set has-direction solely from lineTypesWithDirection. I don't know which is better. Ticker On Tue, 2021-05-18 at 12:35 +0000, Gerd Petermann wrote: > Hi Ticker, > > in the branch I found a solution which doesn't set the direction flag > for overlay lines when the OSM way is a oneway and a road with > overlay type is created. > With your patch still ALL lines created from the overlay type have > the direction flag set in that case. > Tested this with the unchanged OFM style without any new options. > > Do you see something wrong in the current branch version r4723? > I think it's clearer. > > Gerd
- Previous message: [mkgmap-dev] Line direction flag, merging etc
- Next message: [mkgmap-dev] Line direction flag, merging etc
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list