Please don't use abbreviations; these are made automatically by data consumers when desired. Computers can't tell if "N" means "North" or "Normandy" or if "St" means "Saint" or "Street" or "Strasse".
---

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

Instead of "fixme=continue" it might be better to be slightly more descriptive, like "fixme=Stream continues."

I'm in this mall regularly, and these driveways are definitely not residential streets.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/163320975

Names should only be the name, not also the branch.

osm.wiki/Names#Name_is_the_name_only

There's a seperate branch tag for branch information.

branch=*
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/163311841

Semi-detached house is what you're looking for with duplexes.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/163299590

This should use address tags instead of a name.
---

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

"Avenue" works better than "Ave" as it removes all potential ambiguity while allowing data consumers to accurately create abbreviations if desirable.
osm.wiki/Abbreviations
---

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

You can map terraced buildings faster without overdrawing existing lines by using relations.
osm.wiki/Relation:multipolygon
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/163266118

Kinda sorta. Helps to look around the wiki and the map a bit to figure out what's going on. The lanes page is outright wrong and some people puppyguarding the wiki keep trying to insist bike lanes and permanently closed lanes aren't "lanes", so you have to take what you're reading with a grain of salt and apply common sense in such cases.

I re-terraced these buildings to try to help you out.
---

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

Yes, that's correct, I intended to remove that wheelchair description.

Could be broken down a little more precisely. Check out the landuse work around Colony, OK for some examples.
---

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

Looks like that would be street_side. If that space is a travel lane when cars aren't parked in it, then it'd be lane.
---

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

You're looking for capacity:disabled=1
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/163187805

The name should only be the name. osm.wiki/Names#Name_is_the_name_only
Please consider lifecycle tags. osm.wiki/Comparison_of_life_cycle_concepts
Street names shouldn't contain abbreviations.
access=yes means anybody can use it at any time without restriction, which isn't the case with Tesla.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/163186306

Yeah, you're right. I forgot to swap the tag as I drew north and you are correct at the location of the split.

When a value is unknown, it's best not to set the key. No operator tag would suggest that the operator is not known, but operator=unknown suggests the operator is named "unknown".
---

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

True, though the spirit of "don't map for the renderer" is also "don't break it" since the only real difference between forest service networks and non forest service networks is the network. That's where my head's at on it at least.

Fair enough, though I'm not sure that really went anywhere in practice and could be a bit of a "don't break the renderer" moment? I'm certainly on team semicolon when multiple refs apply (though ultimately I think this information doesn't belong on the way, it belongs on the route relation).

All three just use "ref=", nothing even consumes ref:usfs or ref:blm...I was on that thread.