Hello Felix,
... Ups too fast. if I use: /highway=* & copy=99 { set oneway=no } [0x01 road_class=0 road_speed=0 resolution 24 continue] highway=* & copy=98 { set oneway=no } [0x01 road_class=0 road_speed=0 resolution 24 continue] highway=* & ( copy=99 | copy=98 ) [0x02 road_class=2 road_speed=2 resolution 24] /Then it does work as expected, however Mapsource puts out error =3 when I try to route along 0x01 against 0x02 direction.
I'm missing something here - where are you setting oneway for 0x02?
If I use however the highway=* & copy=99 { set oneway=-1 } [0x01 road_class=0 road_speed=0 resolution 24 continue] highway=* & copy=98 { set oneway=yes } [0x01 road_class=0 road_speed=0 resolution 24 continue] /highway=* & ( copy=99 | copy=98 ) [0x02 road_class=2 road_speed=2 resolution 24]/
then oneway=-1 is also set for 0x02, instead of 0x02 being oneway=1. and vice versa. I am unable to have opposing oneways. On top of this at some places Mapsource creates an error when I route over the way (- the critical point being where ways are joined to simple oneway=no ways).
Again, I don't see how 0x02 would be given oneway=1. I shall look again at where the way is being duplicated, I don't understand how with that patch, setting oneway=-1 in 0x01 also sets it in 0x02. Cheers, Mark