Re: [Tagging] Extremely complicated conditional values

2019-04-26 Thread Richard
On Thu, Apr 25, 2019 at 02:06:27PM +0200, Tobias Zwick wrote: > Even shorter, because if there are conflicting rules in the conditional, the > last one is taken, says the wiki. (Not sure if this is really implemented in > applications that work with that data though): just wondering, does

Re: [Tagging] Extremely complicated conditional values

2019-04-25 Thread Tobias Zwick
Even shorter, because if there are conflicting rules in the conditional, the last one is taken, says the wiki. (Not sure if this is really implemented in applications that work with that data though): maxspeed:advisory:conditional=37 mph @ (weight>=6 lbs);26 mph @ (weight>=65000 lbs);22

Re: [Tagging] Extremely complicated conditional values

2019-04-25 Thread Johnparis
I suppose, given that they all have the same tag, that the values would need to be concatenated with semicolons: maxspeed:advisory:conditional=18 @ (weight>=37.5);22 @ (weight>=35 AND weight<37.5);26 @ (weight>=32.5 AND weight<35);37 @ (weight>=30 AND weight<32.5) On Thu, Apr 25, 2019 at 10:28

Re: [Tagging] Extremely complicated conditional values

2019-04-25 Thread Johnparis
I'd try something similar to this example: access:conditional=destination @ (weight>5.5) So in your case you would have maxspeed:advisory:conditional=18 @ (weight>=37.5) maxspeed:advisory:conditional=22 @ (weight>=35 AND weight<37.5) maxspeed:advisory:conditional=26 @ (weight>=32.5 AND

[Tagging] Extremely complicated conditional values

2019-04-24 Thread Paul Johnson
Is there a condition value calculator that can help me come up with sane tagging for this? https://openstreetcam.org/details/955279/18672/track-info This is a chart of advised speeds in MPH for HGVs on a motorway in Oregon based on weight in pounds. I'm at a complete loss of how to tag for this