Most fire stations have a reference number assigned either by the department itself or by a larger district or county. I think it’s entirely appropriate to use ref=* for that reference number.

Or are you commenting on the inclusion of the number in the name? I didn’t add that. It came from node/3040281233/history and I just converted it to an area.

Anyhow, I disagree that a store receipt name is equivalent. People don’t refer to stores by number in normal conversation, but they often do for fire stations, especially in technical contexts. In this case, the sign just says the fire department’s name, but I’ve mapped many fire stations that have the station name on the sign, including the number.

Hi, thanks for making this golf course so detailed! changeset/92923787 fixes some issues with this golf course. Specifically, if it’s OK to drive a golf cart along a road, add the golf_cart=yes tag to the road instead of drawing a new golf cart path that overlaps with it. Also, the various parts of this golf course were tagged as golf courses in their own right, which resulted in lots of golf course icons. It’s enough to add a golf=* tag plus the appropriate natural=water or landuse=grass tag. Software that uses OSM can figure out that these things are inside the golf course. Thanks again for your diligence, and let me know if you have any questions.

Thanks for indicating that there was a bogus road here. I deleted the road in changeset/92800276 . You can select a road and delete it by pressing Ctrl+Backspace in Windows or Cmd+Delete in macOS. (You may need to zoom out a bit so the whole road is visible first.)

This change didn’t have the effect you probably intended. Multi-use paths in the U.S. are most commonly mapped as bike trails or walkways depending on what they’re more widely known as. iD has a separate section to indicate specifically whether pedestrians, cyclists, and horseback riders are allowed. In this case, by changing the trails to paths, no router can be confident that either pedestrians or cyclists are allowed.

Oh! That was a typo – thanks for catching it. Fixed in changeset/92454686.

changeset/92454266 reverts this changeset along with changesets 92260890 and 92260895. I’ve once again restored the payment:i-pass=* key to distinguish the similarly named iPASS and I-PASS payment methods. See also this discussion: osm.wiki/Talk:Key:payment#Ambiguous_subkeys

The “yes” is because the street-level imagery was just clear enough to tell that it was a relative “Weight Limits Reduced” sign, but not clear enough to see the actual percentage that the weight limit was reduced by.

It’s quite strange, but true: @Minh%20Nguyen/diary/394347

Hi, should the weight limit on this bridge be expressed in short tons (U.S. tons), as indicated by the maxaxleload tag on way/223438984? (If not, metric tonnes would use the “t” suffix or no suffix at all.)

…idges; reclassified alleys

Thanks, changeset/91562371 reverts some smaller segments that had also been mistagged.

Named landuse=residential areas are the best way to map these residential developments, since they have well-defined boundaries and usually well-known names and are predominately given over to a single kind of land use.

However, I’m not sure I’d go so far as to say place=neighbourhood is never warranted for an American-style planned development. These developments can vary in from a few houses to the size of a small city and can be further subdivided into named sections. Some subdivisions have corresponding census-designated places (boundary=census) due to their population or relative isolation.

(By the way, note that these signposted subdivisions are usually distinct from the legal subdivisions tracked by county tax authorities. Typically a developer combines multiple legal subdivisions to create a marketable subdivision. These legal subdivisions have names that a resident would only see when looking at their title. I don’t know if anyone has mapped them systematically, but that might also be a poor candidate for place=* nodes.)

…ion from abandoned railroad; LMST is a bike route

Thanks for sprucing up this scattered set of neighborhoods in Southwestern Ohio. Note that sometimes you need to split a way before deleting it. While you were correct in identifying way/168816847 as having been reconfigured, the deletion also affected the ability to turn left from way/432841207 onto way/431577087. Not the end of the world, but something to keep in mind for the future. Also feel free to add anything that you see replacing the roads that got demolished.

Thanks for making the route relation more manageable. Breaking up these massive relations means a lot to me, as someone who uses Web-based editors.

changeset/90897098 changes the Little Miami Scenic Trail back to highway=cycleway. The North Country Trail and Buckeye Trail happen to traverse the Little Miami trail, but the it’s more well-known as a bike trail. Access tags are sufficient for conveying that the trail is also designated for hiking and horse-riding.

Yup, back when I added cuisine=boba here, we still had a mess of four or five equally common tags for the same thing. I later settled on cuisine=bubble_tea and documented it in cuisine=bubble_tea so I could start adding some boba chains to NSI. If you spot older tagging like this, please feel free to correct it. In this case, there aren’t that many occurrences of the older tag, but in cases where there are, it might also be worth asking editors to flag it as a deprecated tag.

Hi, thanks for your attention to this part of the map. This is related to https://www.wdam.com/2020/06/08/lamar-county-intersection-be-rerouted-driver-safety/ , correct? It sounds like the changes haven’t been completed yet, so changeset/90780773 temporarily undid the changes. But please feel free to redo the changes once they’re complete. When you do, please consider using Sentence Case rather than ALL CAPS and choosing the Residential Road preset instead of Primary Road. Your edits are less likely to be mistaken for vandalism that way.

I don’t think disused:building=* (including disused:building=retail) is appropriate. building=* tags refer to the building’s original purpose when built, not what it’s currently used for. For example, way/498357508 is still building=retail despite having been convert to a church. It’s counterintuitive, but the idea is apparently to give renderers a hint about the architecture of the building. You can use building:use=* to indicate the current use of the building if it differs and isn’t obvious from other tags like amenity=* or shop=*.

Once the building is demolished, then it would become demolished:building=retail.

Once the buildings are demolished, then demolished:building=* would be appropriate. But until then, the buildings are still standing, so an unprefixed building=* is correct. You could add end_date=* if you know when they plan to demolish the buildings.

A lot of the shops are already tagged disused:shop=* and shop=vacant, which seems adequate. I didn’t retag any of the businesses that were still tagged as being in operation, because I’m unfamiliar with this mall. But if you know that additional businesses have closed, feel free to update them too.

Thanks for making these corrections. changeset/73976526 is part of a pattern of fictional editing that multiple mappers have complained about lately in both Indiana and Ohio.