Hello!
Thank you very much for your contributions to OpenStreetMap!
I reviewed your changeset on OSMCha and found some errors or elements
that could be mapped in a better way. Feel free to message me
to know more about it or visit http://learnosm.org/ to get started.
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/55370233

Hello!
Thank you very much for your contributions to OpenStreetMap!
I reviewed your changeset on OSMCha and found some errors or elements
that could be mapped in a better way. Feel free to message me
to know more about it or visit http://learnosm.org/ to get started.
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/55370163

Hello!
Thank you very much for your contributions to OpenStreetMap!
I reviewed your changeset on OSMCha and found some errors or elements
that could be mapped in a better way. Feel free to message me
to know more about it or visit http://learnosm.org/ to get started.
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/55370218

Hello!
Thank you very much for your contributions to OpenStreetMap!
I reviewed your changeset on OSMCha and found some errors or elements
that could be mapped in a better way. Feel free to message me
to know more about it or visit http://learnosm.org/ to get started.
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/55370195

Hello!
Thank you very much for your contributions to OpenStreetMap!
I reviewed your changeset on OSMCha and found some errors or elements
that could be mapped in a better way. Feel free to message me
to know more about it or visit http://learnosm.org/ to get started.
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/55370139

FYI, this import contained some degenerate areas:

osm.org/way/544942627
osm.org/way/544945260
osm.org/way/545115869
osm.org/way/545382318
osm.org/relation/7800945
osm.org/relation/7800997
osm.org/relation/7805002
osm.org/way/546469413

I fixed these cases, but you might want to run JOSM’s validator on the data again just in case. Let me know if you have any questions.

Source should be San José Public Works Department, not Bing.

Plugged several gaps in the imported data around street corners and where walkways through apartment complexes met sidewalks on public streets. Added noexit=yes, barrier=wall where appropriate to satisfy near-but-not-connected validator. Deleted a sidewalk segment that was actually a hedge.

Thanks for your recent contributions to the map along Beechmont! Regarding the area you mapped as “Current site of Dewey's Pizza and Silver Ladle”: the default aerial imagery from Bing is a bit outdated, as you’ve noticed, but you can click the Backgrounds button on the right side of the editor to switch to more recent imagery from DigitalGlobe that reflects the construction of these two restaurants. Feel free to send me a message if you have any questions about mapping.

And colour:lanes while we’re at it. :-P There’s more information about lane-specific tags at osm.wiki/Lanes

Since there’s no physical separation, a single way would be more accurate. But you could use bicycle:lanes and foot:lanes tags to say which side to walk or bike on.

Also, this changeset moves the beginning of many turn:lanes tags to where the turn lane begins to be demarcated, as opposed to where the road only begins to widen.

…updated buildings

This changeset introduced a speed limit expressed in miles per hour without an explicit unit, so it was interpreted as kilometers per hour. Fixed in changeset 54297467.

https://github.com/openstreetmap/iD/issues/3625

Yikes, sorry about that! I’ve been manually entering these in iD, and unfortunately, iD silently adds the _1 instead of forcing me to notice the existing tag. I’ll double-check my edits for this error in the future. Thanks for noticing!

I made a few corrections in changeset 54210692. Of note, it isn’t necessary to collapse a segregated intersection (such as at Red Bank and Duck Creek) down into one highway=traffic_signals node; mainstream routers are capable of treating it as one intersection despite having multiple intersecting nodes.

Also, I was unaware of the crossing=pedestrian_signals tag – thanks for that!

Also added emergency crossovers, advisory speed limits, height restrictions, and hazardous cargo designations.

Stale changeset comment. The real comment should’ve been: Added sidewalks #osmus-project-127 #c4sj #South-Bay-OSM

Rushville doesn’t meet the criteria for place=city. Based on its population, it should be place=village, though place=town is better since it’s a county seat and thus is more prominent than any other place in the county. I demoted the POI in changeset 53703346.