After examining street-level imagery and researching further, I’ve determined that the name isn’t dependent on the side of the street after all. “Columbus-Cincinnati Road” (with the hyphen) is preferred by the Ohio Department of Transportation, which posts all the street name signs along this road. However, “Cincinnati Columbus Road” (without a hyphen) is preferred by the West Chester Township Road Division, which posts periodic address signs along the road.

Since both names are equally prevalent, I’ve included both in the name tag, using reg_name and loc_name to clarify the situation. I put “Cincinnati Columbus Road” first in the name tag because that’s the name that most businesses along the road use in their addresses. I also mapped traffic_sign=US:D=3 and advertising=sign nodes for all the signs I could find that name this street.

Awesome, I’m glad there are local eyes on this part of the map, especially given the online attention that https://onezero.medium.com/how-googles-bad-data-wiped-a-neighborhood-off-the-map-80c4c13f1c2b brought this neighborhood.

My edits were only ever intended to be a starting point for further refinement. If you can determine the neighborhood’s boundaries independently using local knowledge, there’s no need to cite city-data.com as a source. Aligning or joining to the streets that form the boundaries would be worthwhile, to avoid incorrect geocoding on the other side of the affected streets.

Even if Buffalo neighborhoods aren’t formal enough to have administrative boundaries, we could still add a non-administrative boundary relation. Do you agree with Wikipedia’s claim that the neighborhood is “centered on” the High/Jefferson intersection? If so, maybe we should put a place POI there and add it to the non-administrative boundary relation with the label role.

This changeset moved node/6338689283 from the corner of High and Jefferson to a location along the edge of the neighborhood as it replaced the node with a place=neighbourhood area. This change is problematic for two reasons: the geographic centroid of this area is not the commonly acknowledged center of the neighborhood (as stated by Wikipedia), and place areas per se aren’t rendered by most renderers. If we were to map the neighborhood as an area, we would need to map the boundary as a boundary=administrative admin_level=10 relation, with the place=neighbourhood node being a member of that relation with the label role.

Apart from that, city-data.com says the neighborhood boundary data is copyrighted by urbanmapping.com. So I don’t think we should rely on it as a source, unless you or someone else has secured permission from urbanmapping.com under terms compatible with the ODbL.

I would favor reverting this changeset, though I thank you for deleting the other POI someone later added in the middle of the fruit-themed streets – that seemed to be a misunderstanding too.

This changeset removed important turn lane information. The ramp should begin where the physical separation begins, not where the lane change restriction begins. Turn restrictions should be mapped as relations, not as incorrect geometry.

To the team at Amazon Logistics: if you see that a road has already been mapped with turn lanes, please refrain from editing it as part of turn restriction mapping. Thank you.

Hi, I undid part of this change in changeset/68122862. changeset/53221067 was correct to move the Costco gas station canopy to the rear of the parking lot by the tire center. In the Bay Area, none of the available aerial imagery layers have been updated since late 2017, shortly before the gas station moved. If you need help determining whether something has changed on the ground in this area, I’d be happy to help; just let me know.

Hi, I undid this change in changeset/68086436. Please be careful about keeping bus routes intact and lane counts accurate when reconfiguring intersections.

In this case, I think making part of Vine two-way is preferable. Even if your router doesn’t understand maneuver relations like the ones you deleted, it’ll say “turn right, then turn left” to go straight through to E. Court St., which is still intuitive. And to turn left onto Vine, it’ll say “turn left”, instead of “make a sharp left”.

changeset/68037062 replaces these nodes with barrier=block nodes. As far as I know, noexit=yes is only used by QA tools, not by routers.

Please do not replace circular roadways with highway=turning_loop nodes. highway=turning_loop is less detailed than the ways you deleted. Thank you for your attention.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/60154559

This school had been retagged as a park in changeset/51441572 – and renamed to include the word “park” – to disguise the fact that it was intended to optimize for Pokémon Go gameplay.

Thanks for these edits. Retagged Miro Towers as a construction site in changeset/67572097.

Hi, it looks like you’ve been very manually building up a contiguous U.S. boundary relation. You may find it more convenient to use the Ctrl+Shift+{ and Ctrl+Shift+} shortcuts in iD (⇧⌘{ and ⇧⌘} on a Mac), which jumps directly to the first or last node along a way. You can also use the list of members of the main U.S. boundary relation to jump to pieces of the border.

The contiguous U.S. is something people might want to search for, so you’re right to add it to the map. However, it isn’t an administrative boundary in the usual sense. It’s probably better to leave off the boundary=administrative tag and give the relation a place=* tag of some sort. Perhaps place=region? osm.wiki/Tag%3Aplace%3Dregion

Hope this helps!

Note that osm.wiki/United_States_Road_Classification hasn’t gotten much attention from the community. osm.wiki/Ohio/Map_features is specific to Ohio and is what most of Ohio is consistent with.

Thanks!

Hi, you may be interested in the discussion in osm.wiki/Talk:Indiana#SR_for_state_roads , where I’ve proposed that we standardize on the “SR” prefix for ref tags on state roads in Indiana.

demolished:building=yes should be used in place of building=yes, not in addition to it. Thanks!

Also corrected tagging of channelized turn lanes.

Oh, never mind, I found 15 mph speed limit signs further up the road. Fixed.

Are there any signs for the speed limits inside Creekside Village? I noticed that the speed limits are tagged as 12 km/h, but I can’t find either 12 km/h or 7½ mph speed limit signs in the complex, just “slow down” signs.

These references may be helpful:

highway=stop
maxspeed:advisory=*
traffic_sign=*
osm.wiki/Tagging_for_the_renderer

This changeset has been reverted fully or in part by changeset/66870047 where the changeset comment is: Reverted changeset/66869945: JOSM mangled the upload after a network connection error