Continued the discussion on changeset/74378574.

Hi, would you mind double-checking the tags you used on these bike share stations? They aren’t tagged correctly and won’t render on the map as a result. Bike share stations should be tagged like this:

amenity=bicycle_rental
name=* (not station=*)
network=Kaupunkipyörät
network:wikidata=Q28129102

In general, if you want to indicate the city and country that a given feature is located inside, you would use the “is_in:city” and “is_in:country” tags. The “country” tag is reserved for things like embassies and flagpoles that are associated with a particular country.

Anyways, for bike share stations, there’s no need to tag the city and country, because the “network” tag is more specific and a data consumer can detect that these features lie within the Helsinki administrative boundary.

Thank you for your help in keeping the map tidy!

Thanks for spotting this error. I had intended to tag it as highway=turning_circle. Most likely I used the R key (repeat) but previously mistagged another node due to an overreliance on Potlatch 2’s autocompletion suggestions. Sometimes my keystrokes got inserted out of order due to asynchronous keystroke handling in the Flash plugin.

Fixed in changeset/74320023. Hopefully there aren’t too many more instances where I made this error.

The source for the boundary changes was CAGIS: https://data.cincinnati-oh.gov/Thriving-Healthy-Neighborhoods/Cincinnati-Community-Council-Boundaries/6aci-7ivg

(Typo: I’ve gone ahead and reverted this changeset in changeset/73733859.)

US 52 follows Central Parkway and Central Avenue rather than I-75, as seen in Mapillary street-level imagery dating back years and right up to a few hours ago:

https://www.mapillary.com/map/im/h-IatpGTq5GIAe8bWxlquw
https://www.mapillary.com/map/im/C0n9JFishlW1iCgKayLVQw
https://www.mapillary.com/map/im/NnEwrjmD1XKZoxCi90nC2Q
https://www.mapillary.com/map/im/UEMqcorPlIHdTdTAosmFZA
https://www.mapillary.com/map/im/gjt3_UldwJH7iRt4ZrlZmw

I’ve gone ahead and reverted changeset/73733859 until there’s evidence that the route has actually changed.

You may want to double-check the other edits you’ve made across Ohio. The name and ref tags should be consistent with route relations and should reflect what’s signposted on the ground. There are other ways to indicate proposed or scheduled changes. If you have any questions, please reach out to me or ask in the #ohio channel of slack.openstreetmap.us.

This road already had “SR 56” in the ref tag. There’s no need for a name tag in this case. Reverted in changeset/73733044.

Thanks!

It kind of does look like that from aerial imagery. However, it’s probably less rigorous in terms of traffic education, meant more for exercise. There’s also a little parking lot within it that’s cleverly patterned as a ruler. If I knew for sure that the school uses tricycles there, I’d tag it as a cycleway, but for all I know they could be using https://en.wikipedia.org/wiki/Cozy_Coupe or electric kiddie cars (which are similar to golf carts).

This way was originally added in changeset/61515999 by another local mapper who may have more context.

Oh that’s even better. By the way, do you know how far this preserve extends? I tried to guess based on any clear property lines I could see from aerial imagery, but I came up quite short compared to the official acreage.

Hi, thanks for your edits in the area. When aligning roads and other features, please switch the background imagery to OSIP 6in Most Current Available, which is newer, higher-resolution, and better aligned. Thanks!

Fixed in changeset/73561163.

Hi, I reverted this edit because it looked like you were practicing editing. It’s OK to practice editing, but please avoid saving in that case, because your test edits end up affecting the live map that everyone sees. If you’re interested in mapping schools, there are plenty of schools in the area that could use more detail. :-)

Reverted in changeset/73560487.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/67566162

Hi, this is nowhere near the old CooKoo’s Coffee Shoppe on Whetsel. If the garden does exist, can you place it in a more accurate spot and also move “Broccoli” to a more suitable tag, like “crop”? Thanks!

By the way, the OSIP 6in background imagery layer is almost as up-to-date as DigitalGlobe/Maxar imagery but much higher-resolution and better aligned.

Queen of Peace has a new church building; the one tagged here is actually the rectory and parish office. Fixed in changeset/73452007.

Thanks for cleaning up GNIS nodes, but please be careful when combining them with buildings. Most GNIS entries since 2009 have very accurate locations, but older entries’ locations are only approximate.

In this case, the engine house is next door at 1654 Marlowe. You can tell from OSIP imagery because it has a façade wide enough to accommodate two fire trucks. (Incidentally, a separate GNIS entry for the relocated fire station also indicates 1654 as the previous address.)

In a previous case, I noticed that you had untagged a village hall as being possibly nonexistent, but actually it was across the street.

If in doubt, please leave the POI alone and skip to the next Maproulette task. Thanks!

These changes largely seem OK to me, but for the future, please note that highway tags in OSM aren’t intended to correspond one-for-one with HFCS. HFCS can be a starting point, but it would be better to look at its criteria and evaluate these roads on your own, perhaps taking those characteristics into consideration.

Whenever you reclassify roads based on an external source, please double-check the roads in any available aerial or street-level imagery to make sure you aren’t propagating errors from that source.

Also, please ensure good connectivity within each highway classification. When possible, avoid making a secondary road terminate at a tertiary road, as with State Line Road in Bright.

Thank you for the care you’re putting into this aspect of the map. If you have any questions, please feel free to reach out to me directly or stop by the #indiana channel in OSMUS Slack.

Hi, these ways lead into a parking garage. If you were trying to resolve a validator warning about inaccessible ways, the proper fix would have been to add an amenity=parking_entrance tag to the node that connects the ways to the building.

Removing the oneway tags is incorrect, because traffic is only allowed in one direction on this entrance and exit. A lot of garage entrances in this region are missing amenity=parking_entrance tags, so I appreciate your help in adding those tags.