I’d agree that wheelchair=yes doesn’t help here, and it’s certainly not appropriate for access tags (there’s been no change to the legal status), so I’d just tag what you see - width, surface, smoothness, tracktype etc.

Other things to think about are the incline along the path (which sometimes is tagged in OSM) and the (here, lack of an) incline perpendicular to it, which can make paths challenging for mobility scooter users, which may have a narrow track and relatively high center of gravity.

You can also add some sort of description or note. That won’t get picked up by routers but might very well be by a human vetting the results that a router returns.

With regard to translation - pages now seem compatible with Google Translate, so for example https://translate.google.ca/?sl=en&tl=de&text=https%3A%2F%2Fcommunity.openstreetmap.org%2Ft%2Ftagging-help-for-osmose-error-untagged-named-object%2F99233%2F11&op=translate now works as is. Obviously that’s just an anonymous view of the page, so you can’t reply from there, but it’s much less clumsy to use than Discourse’s built in one-post-at-a-time-but-not-the-thread titles translation.

I’ve no idea whether this was a change at Discourse or at Google, or when (it might have been working for ages and I haven’t tried it).

Changeset comments for info: https://resultmaps.neis-one.org/osm-discussion-comments?uid=550560 .

Re the “hashtags” part of your question - no-one is stopping you from using hashtags. However, please do follow the advice at osm.wiki/Good_changeset_comments and use good changeset comments as well to help other mappers understand what changes you are making.

Suggesting that other mappers should resort to using things like chatgpt to decode your gibberish is a ridiculous suggestion.

You were asked before at osm.org/changeset/123219182 but you ignored the request.

In osm.org/user_blocks/7082 you were therefore sent a message that you had to read before continuing to edit.

You were at no stage blocked from editing OpenStreetMap.

@SaltyKimchi I’ve hidden the crypto spam comment that you were referring to and reported the user

Sometimes the people creating these accounts have a sense of humour, like with the picture here: osm.org/user/Ranah%20Medle .

I’ve just tried the Nokia 6.1 with an incognito Chrome tab - 4 seconds. The Nokia X10 with Chrome, about 3 seconds. Maybe it’s slightly faster than Firefox, but 4 seconds to do anything in 2023 is just too slow. An iPhone 8 Plus of about the same vintage as the Nokia 6.1 (but obviously much more expensive new) is about 2.5 seconds.

I’ve saved a recording from the “performance” tab of firefox on a Chromebook to https://map.atownsend.org.uk/tmp/c.osm.org.profile.json . From me pressing return in the address bar to the page appearing took about 8 seconds.

@Firefishy - Re the speed issue, I suspect that this is mostly due to just how bloated the site is. I’ve just tried a couple of times, each time in a new Firefox private window on a mobile phone.

On a Nokia 6.1, Android 9 on 3 (4G with 31 Mbps down) I got a 5 second delay before the front page https://community.osm.org loaded.

On a Nokia X10, Android 13 on O2 (4G with 26 Mbps down) I got a 3 second delay before the front page https://community.osm.org loaded.

On a PC, Windows 10 / Chrome Incognito (FTTC “broadband” with 16 Mbps down), the delay was about 2 seconds.

If there’s anything I can do to test this locally, let me know. I’ve also got a chromebook and a couple of old laptops here that might show the same issue and show what is “eating all the pies” in the site itself.

@Firefishy - Re “virtual categories” I added them into the “good” part of the list just before your comment, but as an example, “Garmin” is still a bit hidden. Search for the text on https://community.openstreetmap.org/ and you won’t find it. Typing it into the search box finds 6 items - one is a tag (but it does not say that it is a tag) and 5 are users (but it does not say that they are users).

Of course, the decision not to have a Garmin category (just a tag) is a local deployment decision, and I’ve steered clear of talking about those above to avoid muddying the waters between “Discourse the software” and “how we have deployed it”.

I’ve been a bit naughty in tagging these with disused=yes rather than using a life cycle prefix

FFS - you’ll be adding “(closed)” after the name next :)

(It would be very nice if one of the OSM renderers offered a disused windmill icon

Ahem:

https://map.atownsend.org.uk/maps/map/map.html#16/53.1671/-8.0244

A visualisation of the deletion is https://overpass-api.de/achavi/?changeset=101625624 .

osm.org/way/842886190 was mapped as “informal=yes; surface=gravel; trail_visibility=intermediate”. It doesn’t have a “foot” access tag; I guess that would still be “yes”, even though it’s informal?

Various options exist for undeleting the trail exist, such as the undelete plugin in JOSM. However, even if it makes sense to do that it might be useful to review the route - there are a couple of river crossings either side of osm.org/node/7863138316 that might benefit from looking at.

However, I’d also suggest reviewing it in the light of osm.wiki/United_States/Trail_Access_Project and especially osm.wiki/United_States/Trail_Access_Project#Trail_Tagging_Chart within there. It’s definitely worth discussing the status of it with other mappers in the area (if there are many others - this is a bit of an out-of-the-way location) so that everyone’s on board with any change of status. In particular, I’d expect the current state of the trail to be discussed - it was informal a couple of years ago; if local land managers are advising against access, it may be effectively disused now.

Places for discussion include OSM US’ Slack instance - there’s a “#trails” channel there. More public options include the forum community.osm.org (there are plenty of US mappers there) and the talk-us mailing list.

Andy

PS: For technical help with undoing edits and reverts you can always contact OSM’s Data Working Group via data@openstreetmap.org (I’m a member of that group). However, the first thing we’d try and make sure happens is that all interested parties talk about it together.

I see you’ve found osm.org/way/527242637 :)

I can hide the diary entry if you want…

(I don’t think there is a “delete” option is there?)

There are various “Ubuntu” options in the Windows app store. From memory, it used to be needed to download “Ubuntu” from there, but it looked like it it might have been removed, hence the notes above.

Go into powershell, and type “wsl -l -v”.

If that does not list anything, install “Ubuntu” from the Microsoft App Store. If you get a choice of 20.04 and 22.04, choose 22.04 because more OSM tools are built-in there.

Ah - so it’s a HOT thing. Thanks for that.

What is the “Asia Pacific Hub”?

@4004 I’ve tended to use something like was:highway (or some other lifecycle tag) when I can see a bit of the history. Here, though, there’s really nothing left on the ground at all - I’ve had a few goes at looking in different weather conditions. It is present as a “bridle road” on an 1852 OS map that the NLS have in their collection, as actually are a large number of other no-longer present paths.

On IRC SK53 suggested that the usage change to full-time grouse moor probably initiated the path change, and that does make sense - I’m pretty sure that that resulted in creation of the wide vehicular access track that you can see in the pictures above.

(answering my own question) - roads not know to be paved or unpaved are shown the same as before, which is how paved roads are now. This tile, the area around here, shows that.