I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

When more specific tags contain accurate information, please do not revert to more vague methods.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

When a more specific key is available and the information in it is valid, then that takes precident towards more general tagging schemes. Please don't iterate backwards.

I'm intimately familiar with the intersection in question, and if this is the case, then nobody on your team is qualified to map in the United States.

Sorry, my mistake, looks like a third one was added but you only changed the last one and did not add a placement value.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139071591

There's clearly only two lanes here.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139071591

Please stop tagging destination:lanes until after you've driven in the US; these values aren't accurate.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139076821

Please stop changing destination:street to destination. There's no reason to do this.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139082121

OK, for destination:lanes tagging, it's fairly obvious that you need someone who knows how to drive in the US to get the correct values. As for destination:street bulk retagging being a part of the workflow, please make it not part of your workflow and fix your data consumer.

Is there a specific reason why you're bulk-retagging the entire country for your specific data consumer instead of changing your data consumer to accept an already in use data model?

I think you can square right angle corners with the Q key in iD. You might check its help for hints.
---

Published using OSMCha: https://osmcha.org/changesets/139064384

Don't worry about adding access=yes unless it's someplace that you wouldn't normally expect everyone and everything to go through.
---

Published using OSMCha: https://osmcha.org/changesets/139064981

Not sure about the lanes there but thanks for the other part!
---

Published using OSMCha: https://osmcha.org/changesets/139065011

You added a lane where there is no lane.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139022474

We would have also accepted:

noname=yes
ref=CR S205
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/139047744

Please don't change destination:street to destination. Your destination:lanes tagging doesn't match what the signs say or on the ground.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/138177682

Incorrect destination:lanes added.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/138092578

Please don't fabricate values for destination:lanes; the ones supplied in this changeset are not accurate. Please don't change destination to destination:street.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/138325529