[Patch] Add optional direction tag to cycleway=asl preset

[Woazboat]

cycleway=asl should also be tagged with the corresponding direction unless it's a oneway street (similar to highway=stop/give_way)
​osmwiki:Tag:cycleway=asl

[Woazboat]

Add optional direction tag to cycleway=asl preset

[taylor.smock]

From the wiki page:

If it is not a oneway the a direction tag is needed. Use key direction=* for this. Values are forward or backward. Example: direction=forward

Why do you have N,E,S,W,0,90,180,270,forward,backward as possible values for direction in the patch? It looks like it should just be forward,backward.

[Woazboat]

I added those in order to be consistent with the josm presets for highway=stop and highway=give_way which have the same semantics as cycleway=asl. (Although I'm not sure why exactly those additional values are defined there. They should all be removed tbh.)

[skyper]

direction=forward/backward is a complete mess. I consider both values as tagging for a router. Many of the asl I know are the end of a cycle lane and the highway needs to be split at the asl.
If we change the values, we should add more cardinal values like NE or 45.

[Emvee]

See ​taginfo, cycleway=asl is currently only mapped with direction=forward/backward

Also for ​highway=stop and ​highway=give_way you can do the math and see that only 1.8 and 2.7% is mapped as not forward/backward and very likely that remaining percentage is "both" but that makes no/much less sense for cycleway=asl.

What is messy about direction=forward/backward? Yes, it is tagging for the router but is that bad? The only problem I know is that direction on a node does not make sense without looking at the way context. That can be a problem if the node is part of multiple ways and josm is warning for that. It is no problem if direction of the ways are consistent and my guesstimate is that this is often the case so I think the problem is small.