Hello,
Should way/1329335285 perhaps be "operator=SSE" rather than building=sse"?
Best Regards,
Andy

Hello,
What is a "building=barb"?
way/644918873#map=20/54.1568336/-2.1386904&layers=H
Cheers,
Andy

I've set it back to yes :)

You didn't add it originally, but have you any idea what sort of building way/51583113 is? It does match OS OpenData but doesn't match Bing imagery, suggesting that something might have been rebuilt in its place?

Hello, and welcome to OpenStreetMap!
You've set way/1272898465/history to "building=closed". If it's still a pub building but the pub is closed, more appropriate would be "building=pub" and "disused:amenity=pub".
Best Regards,
Andy
PS: Any other questions, please don't hesitate to ask!

I'm guessing that "building=yesrunning_or_walking_while_listening_to_some_music_or_a_podcast_can_get_you_into_a_great_rhythm_-_please_just_be_careful_that_it_doesn’t_end_up_distracting_you._when_crossing_the_road,_temporarily_remove_your_headphones_and_avoid_interacting_with_your_ph" was an accident here?
I've changed that in changeset/165089530

Thanks!

Oops - I think that this might have created a gap in the Thames Down Link path - you can see that at relation/115934#map=20/51.2696199/-0.3117511 .
Are you OK to fill in the gap, or would you need any pointers to help doing that?
Cheers,
Andy

I was just looking at the rare values at https://taginfo.geofabrik.de/europe:britain-and-ireland/keys/building#values .

For example, for semidetached_house100752, a regular worldwide overpass query https://overpass-turbo.eu/s/22pe will work - you can zoom in and review the data and, if a simple "replace the value with something else" makes sense (as it does here) you can use that same query for input to Josm.

It looks like something has gone a bit wrong here - the merge of the building and the roof has created relation/13505281/history which is "building=roof;yes".

Hello recrayon,
You might like to join the discussion about naming oceans etc. at https://community.openstreetmap.org/t/looking-for-the-pacific-ocean/128699 .
You've said "as per wiki page", but which page, and where was the public discussion around that?
I can see arguments on both sides here, which is why a "big change" like this has hopefully already been widely discussed.
Best Regards,
Andy

@NFZANMNIM What some wikipedia project does is irrelevant here. In fact, many data projects do link to wikidata's various language names via wikidata links - that is a perfectly sensible approach.

The OSM wiki is clear: osm.wiki/Names#Transliteration .
There are a couple of languages (such as Punjabi) where there are multiple orthographies for the same words - in those cases, and in only those cases, transliteration makes sense - both versions are real, local names.
What Korean names have to do with Persian names in Vietnam I have no idea.

Hello - please do not make up names by transliteration in this way. Only map names that actually exist.
If a data consumer wants to transliterate names, they can.

Thanks - these things do sometimes get forgotten.

Hello,
Andy from OSM's Data Working Group here. We've often worked with land managers about helping understand why "just deleting the data" may not be the best approach.
The first and most obvious reason is that someone who doesn't know the history might just "re add" it based on aerial imagery or even something like Strava. The best thing to do might be to leave something there that accurately reflects the situation on the ground. That might be:
* highway=path with access tags set to "no" if there is something physically there but it is not open to the public.
* informal=yes if what is there was created informally
* Instead of "highway", set a tag such as "disused:highway" if nature is being allowed to reclaim what was there.
If you've got any more questions you can email us at data@openstreetmap.org with a subject line of "[Ticket#2025040410000312] kjm1511". Another set of people who may be able to offer advice is the OSMUS Trails Working Group - osm.wiki/Foundation/Local_Chapters/United_States#Trails_Working_Group .
Best Regards,
Andy

I think everything that was expected to reappear did, thanks.

Hello,
Thanks for this. I'm guessing that the gap at relation/69312#map=18/51.828983/-2.215376 is just "awaiting survey following completion of new housing estate" or similar?
The view of the ROWmaps data (green lines at https://map.atownsend.org.uk/maps/map/map.html#18/51.82841/-2.21512/H/P ) I don't think has been updated for ages, but the path round to the south looks new, so presumably that may end up being joined and (and perhaps even signed).
Cheers,
Andy

It looks like way/1376867539/history was accidentally created as a duplicate way of way/366119186 in this changeset and as well as fixing some invalid relation that created others ("5446375 | Miltonsfields" fell out of the database last night).
I've deleted the duplicate and re-added the missing relations to way/366119186 . The relations I've edited in changeset/164846491 , changeset/164847085 and changeset/164847214 now verify in JOSM as valid polygons, so hopefully all is geometrically OK now.

Also a bit of cycleway near York college

Hello,
I've filled in a gap in the National Forest Way at relation/3748275#map=17/52.667166/-1.311819 . Does that look OK?
Best Regards,
Andy