Continuing the discussion from https://github.com/openstreetmap/iD/issues/9565 , access=official is officially deprecated, and the value “official” actually meant the same as “designated”. In other words, you’re saying the service roads are designed to be used by all traffic (except air traffic). Changeset 134243656 retags them as access=private private=maintenance, as they aren’t even for airport employees. Lyft editors have previously tagged similar nearby access roads as access=no, which is another option.

FYI, the local community has been discussing this issue on OSMUS Slack: https://osmus.slack.com/archives/CCV2P9QET/p1679802276162459 https://osmus.slack.com/archives/C2VJAJCS0/p1679826643887899 (You’re welcome to join the workspace by visiting: https://slack.openstreetmap.us/ )

The lake is very complex in reality; I would think OSM should reflect that fact to the extent possible. It seems like you’ve identified a gap in the tagging model. Splitting up this lake is at best a workaround. After all, not every editor or data consumer would be impacted by the issue you mentioned.

The tagging was discussed on OSMUS Slack: https://osmus.slack.com/archives/C2VJAJCS0/p1677722616750459

Even though this isn’t a vet facility that would accept walk-ins, it is a veterinarian who makes house calls.

Yes, I corrected the buildings in changeset 132948807. I used the same imagery as you but interpreted it differently. It’s important to understand how oblique or offset imagery can distort the shapes you see, especially with a pitched or gabled roof.

In this case, try comparing Esri and Maxar imagery to see how the rooflines differ – that’s the effect of photographing the building from a different angle in the sky.

Yep, I’ve got thousands of these buildings in the area that I’m slowly going back and cleaning up – not just squaring but in many cases complely redrawing, because I often mistook one building for two.

There’s also the osm.wiki/Hamilton_County_Building_Import which went on hiatus for years after the first phase was complete. I’ve started on the second phase, replacing geometries with the better geometries that come with heights and addresses. I’ve done the northern reaches of the county and plan to work southward over time. However, I can only bear to use JOSM so much at a time. If you’re interested in helping, I can send you a shapefile or set up a tasking manager project.

Hi, this changeset unfortunately had several major issues. I tried to manually repair most of the tagging problems in changesets 133062695 and 133064894. However, some things may need your attention:

* I restored all the road names you deleted. However, I was unsure about Johnnie Doolittle/Johnny Doolittle/Townsend-Ballard. Note that OSM doesn’t abbreviate words in names.
* I removed the network=* tags you added to roadways. network=* tags belong on route relations. I created route relations for all the numbered parish roads. If a parish road has a number but it isn’t posted anywhere, the ref=* tag should be replaced by unsigned_ref=*.
* I removed tags from nodes such as osm.org/node/116032755 that were were tagged as roads. Perhaps you misclicked?
* I undid every instance of highway=road, which is essentially never supposed to occur. However, I wasn’t very thorough in reclassifying residential roads as tertiary roads etc.
* I undid every instance of highway=path, which is for non-vehicular usage. Most were highway=track, but some were driveways (highway=service service=driveway).

My guess is that most of these problems arose when you accidentally edited the tags on a large selection or a find-and-replace operation. We’ve all been there. In case you haven’t tried it, I highly recommend using the iD editor, which has a less confusing interface. iD labels everything with everyday words instead of the jargon in JOSM that may have misled you into using these tags incorrectly. It’s just harder to make a mess. I myself use iD and only use JOSM in extreme circumstances.

Regardless of the editor you prefer, you can find help by joining the U.S. community’s Slack chat server at https://slack.openstreetmap.us/ . There’s a #local-louisiana room there with a bunch of locals and expats who know how to say bayou. ;-)

There were a number of other issues in osm.org/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 osm.wiki/Tag:service%3Ddriveway#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: osm.org/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?