There were a number of other issues in changeset/132100886

Hi, please remember to square the corners on buildings. The imagery layer you used is somewhat oblique, so the shapes you see are very skewed compared to reality.

Good catch. I meant to use leisure=pitch sport=equestrian in these cases, though you’re right that some of them look more like paddocks.

The translations are fine but I still got confused. Vietnamese has very similar words for “riding arena” (“sân cưỡi ngựa”, literally “horse riding field”) and riding centers (“khu cưỡi ngựa”, literally “horse riding area”). “Khu” and “sân” can both refer to something as small as a playground or basketball field, but “khu” can also mean a neighborhood.

I think I fixed up the horse farm and mapped another one nearby. Please feel free to make corrections as necessary.

Thanks!

See service=driveway#Pipestems . I’ve been avoiding the term “pipestem” because it’s jargon and it only describes a subset of shared driveways.

This changeset was reverted in changeset/131583380. A quick Internet search turned up https://www.nm.org/about-us/history/northwestern-medicine-lake-forest-hospital-history , which mentions that the hospital was built on the former Dick family farm. This makes it much more likely that A. B. Dick was the lake’s real namesake, not profanity or vandalism as your profanity detector claims.

Hi, I see that Vid the Kid’s old essay about abbreviation was mentioned above. For context, Vid wrote it in 2009 when they and I were among a handful of mappers in the Midwest. Back then, there was serious debate among the U.S. community on the merits of expanding the abbreviations that TIGER used throughout the country. By 2012, those in favor of expansion won out and we expanded all of TIGER’s abbreviations by bot.

Vid used to be very active in the vicinity of Columbus, Ohio. Some of the surrounding counties’ road names indicate the quadrant (e.g., Mink St. SW), and indeed the names can feel pedantic at times. But as you can see from the current map of Fayette and Licking counties in Ohio, we did end up expanding the abbreviations and haven’t looked back.

With the benefit of hindsight, I would say with confidence that the essay no longer reflects consensus and that its conclusion about official names was simply incorrect. However, I very much appreciated Vid’s approach to gaming out the pros and cons of each approach. I hope folks here can coolly arrive at a workable solution.

Hi, please refrain from changing streets and parking lot aisles into golf cart paths. OpenStreetMap needs to remain usable to the general public, not just golfers. The changes in this changeset could have prevented some people from getting routes to this neighborhood by car, or prevented delivery services from reaching its residents.

To indicate that golf carts are allowed on an ordinary street, expand the “Tags” section in the left sidebar and add a new tag: “golf_cart” on the left side, and “yes” on the right side.

changeset/129761521 restores the streets around Beckett Ridge. If you have any questions about how to edit OSM, please don’t hesitate to ask me or join the chatroom at slack.openstreetmap.us for help from the broader community of mappers.

That’s fair. If the local(s) in Redding would like just the SHU boundary restored – tagged correctly – I don’t think there would be much of a fuss about it. It’d be a different story if someone wanted the whole dataset reimported or wanted to add organizational unit boundaries for many other state agencies.

It reminds me of how there was such a kerfluffle when someone imported the whole nationwide EPA contamination site dataset and it had to get reverted, but I convinced the importer to keep them in my area (Cincinnati) so I could use it as a starting point for mapping industrial sites. The data is still in OSM many years later in an improved state, harming no one.

I only chimed in later, after the deletion. (It isn’t possible to comment on a changeset before it gets uploaded.) Gus later reached out to me privately, but I haven’t had the time to explore options with them.

These boundaries were added systematically across California, so it isn’t surprising that it garnered the attention of mappers across the state. If it had been an addition of just the unit covering your part of California, I think it would’ve been a longer time before anyone would’ve flagged it as an issue that Shasta College was now located in CAL Fire Shasta Trinity Unit, California, instead of in Shasta County.

If I remember correctly, it was actually another mapper who asked Gus to remove these boundaries; it came up in Slack and Discord at some point.

In any case, if anyone does decide to restore the CAL FIRE units as boundaries, they would need to be tagged as something other than county boundaries. For example, one mapper has experimented with mapping the Fort Bragg Unified School District as a boundary=school relation: relation/9992727

I was just making an observation about an alternative that’s currently in use, not laying down the law. 🤷‍♂️

Thanks for documenting where these no cruising signs are in effect. As of this changeset, by far the most common value of cruising=* contains conditional restriction syntax. Did you mean to use cruising:conditional=* instead?

Ah, OK, to indicate that snowmobiles are allowed, expand the Tags section at the bottom of the sidebar and set “snowmobile” to “yes”. Here’s some documentation about the snowmobile key: snowmobile=* . It doesn’t have a dedicated row in the part of the sidebar that you used because it’s a little rarer worldwide.

Here’s some documentation on mapping townships in Ohio: osm.wiki/Ohio/Boundaries/Townships

Hi, it looks like you’ve been setting “Motor Vehicles” to “designated” on footpaths and bridle trails. This would mean that the trails are mainly intended for cars and other motorized vehicles. It actually causes some routing engines to route people over these trails in some cases:

osm.org/directions?engine=fossgis_osrm_car&route=41.3400%2C-80.7788%3B41.3510%2C-80.7675#map=15/41.3452/-80.7743

Did you mean to set it to “no” instead?

Thanks for the details, I stand corrected. This is very recent construction. Lately I’ve been feeling confident about the Bing Streetside imagery in the area, which is current to last year, but this construction is even too new for that. Among the publicly available layers, some road construction is apparent in Esri, but I didn’t realize that led to a road diet.

I realize you’re normally unable to share the proprietary imagery as you’ve done here (thanks!). But perhaps when you’re making a change that’s very new and only available in this proprietary imagery, you could note its age in the changeset comment. This would give another mapper like me a heads-up that you know more than I do. :-)

I restored your suggested tags in changeset/127316900. Thank you for patiently explaining the situation to me!

By the way, I’ve also introduced lane connectivity relations to this intersection, since some lanes before the intersection lead to two lanes after the intersection. This isn’t always required, but as you’re updating lane counts, if you see any lane connectivity relations, it would be great if you could keep them up-to-date also. osm.wiki/Relation:connectivity

Hi, this changeset and others such as 119657559 introduced errors rather than fixing them. Vine St. has two more lanes than you may have recognized in street-level imagery – these can be parking lanes during some times of the day, but these are the exception rather than the rule. Also, the intersection of 5th and Vine has two more lanes, as shown by overhead signs and pavement markings. Finally, these changesets connected the roadway to bridges and tunnels, creating impossible routes. These issues have been fixed in changeset/127223264.

Several downtown Cincinnati intersections, including 5th and Vine, are staggered and therefore have unusual turn lane arrows. There isn’t an established tag for these arrows, so slight_right is the most compatible option at the moment: osm.wiki/Talk:Key:turn#Unusual_arrows

The intersection is correct now, but I’d welcome advice on how to keep it from generating a false positive in validation tools such as the one you’re using.

Also updated the address in changeset/126968013

Most of the overconflation affected Confederate flags, which, well, are problematic for other reasons anyways. But node/4718501937 is an example of a historical flag of the United Kingdom and Ireland – same flag, different country represented. I’m not sure if it’s worth creating a separate entry; maybe the validator should be more lenient about subject differing, or NSI should omit subject altogether.