nslookup.dat give_way:direction=forward/backward stop:direction=forward/backward

[ProBackup-nl]

Highway=give_way

Not yet the default syntax for tagging direction of highway=give_way, is give_way:direction=forward|backward, see wiki.
Mainly Polish, Danish, Dutch, Belgian and London mappers use the more descriptive give_way:direction instead of just direction.
For small EU bbox the Mai 2025 overpass count = 1.8K

Highway=stop

Idem for tagging direction of highway=stop, see wiki.
stop:direction=forward and stop:direction=backward is used in The Netherlands, Belgium and less frequent in France, Portugal, Ireland, Germany, Poland, Switzerland, Italy, Czechia, Slovakia, London and Danmark.
For large EU bbox the Mai 2025 overpass count = 0.2K

Related to PR #458

This would profile developers that factor in direction of give_way and stop nodes, to give more accurate penalty results.

Note: for highway=traffic_signals the traffic_signals:direction notation is already standard practice for nodes, according to the wiki.

[emvee-osm]

OSM statistics for use in combination with higway=give_way/stop at this moment:

direction                     2732240
<none>                         598217
give_way:direction               1555
stop:direction                    989

So still minor but nevertheless good to cover.

lookups.dat support's already multiple values, for this it looks to me like a good idea to add also support for multiple keys, something like:

direction,give_way:direction,stop:direction;0000274642 forward
direction,give_way:direction,stop:direction;0000249637 backward
direction,give_way:direction,stop:direction;0000021634 both

would not bad to include also traffic_sign:direction but that is currently already separate values so that might give incompatibility problems if not done correctly.

[afischerdev]

@ProBackup-nl

lookups.dat support's already multiple values, for this it looks to me like a good idea to add also support for multiple keys

Hmm, that doesn't look very practical or clear to me.
The datastore logic is still tag=value
The 'multiple' values only substitute the first value, e.g.
smoothness;0000009837 horrible terrible
will be find later on only as horrible.

stop:direction=forward|backward
give_way:direction=forward|backward

I'll add that.