And of course, the tag for that "cliff" would need to end up in the right place after the merge.

My inclination is to presume that whoever mapped it before got it right.

It seems possible that way/157329997 and way/625187013 could be merged with the tags transferred.

Since this is a geological feature, aerial imagery might not give us a good representation of the extent of the feature. (Some parts may not be apparent in the imagery, or might be obscured e.g. by sand.)

If I were trying to merge the ways, I would try to confirm the extent of the feature from one or more reliable external sources to decide which of the two ways more correctly defines the boundary of the feature.

Thanks for adding the Wikidata ID and link to the English Wikipedia article!

It may be that the Google translation isn't so good, but I found the English version to be a much better explanation of the feature.

I noticed that the natural=cliff tagging might not be right, but figured that whoever mapped it previously might have invested some time into figuring it out. So I wasn't going make guesses from aerial imagery without being able to confirm the profile of the feature from a definitive source. Topographic maps or elevation data might be helpful here.

Hi Krako73. Thanks for getting in touch by direct message as well. Let's continue the conversation there where it's easier to have a more detailed discussion.

Although the Downie Slide is a massive landslide, it is slow moving and it has been stabilized by BC Hydro so it is no longer a hazard. (See https://cgs.ca/pdf/heritage/Rev5-CGA24-Downie_Slide-EN.pdf) Shall we restore the geological=landslide tag to identify the nature of this landform?

How were you able to verify that this dike is not magmatic?

The oilfield at the center of this feature suggests that it would be a geological dome, since the majority of the worlds oil deposits are found in geological domes. What source did you use to determine that this is a volcanic caldera rim?

Based on the mature vegetation established at this location, the feature is clearly the landform established by a previous landslide. Can you explain why the geological tag is not appropriate in this case?

I am restoring the geological=endorheic_lake tag as the use of the lake=* tag is not documented and the values in use are not consistent.

I see that the geological=magmatic_dyke for osm.org/way/288479475 was recently reduced to geological=dike. If the feature is formed by magma, would it be appropriate to restore the more specific tag?

Nice work on the columnar jointing and glacial erratic Wiki pages, by the way!

Hi! I see you removed the natural=dry_wash tag and added a natural=sand tag. I put the natural=dry_wash tag here specifically as an experimental case to work out new tagging for this type of feature. Do you mind if I put it back?

Ah yes. It was that one extra node on the other continent. Sorry.

Nicely done! It's good to have the connectivity back. I plan to be out there when it gets a little cooler and will have an opportunity to survey current conditions.

I see that some of the sections of Steel Pass Road have been deleted. I know things got washed out pretty good last year (saw it myself) but recent reports are that the route has been reestablished. Did you have plans to restore those sections?

I saw your nodes and figured I'd see if I could find any info to help. GNIS has Burrows Park as a flat (i.e. natural feature) at the location of node/6635825602. Historical USGS Topo also has the same name in the same location.

https://edits.nationalmap.gov/apps/gaz-domestic/public/gaz-record/187418

Was there a ghost town by the same name nearby?

It doesn't really affect what I was doing. But I was curious so I did a little more searching, and while this is the only building mapped as a relation with admin_level=4, there are other buildings with the admin_level tag mapped as ways. So, I guess this is an appropriate tag for the building. Nice job with all the fancy levels, by the way!

That might be true for mapping in other parts of the world, but in the entire US, this is the only building with an admin_level=4 tag.

I was doing a query on admin_level=4 features in the US to collect some information about state boundaries and these relations ended up in the data set. At the very least, I might drop that tag from the relations.

Hi! I think the convention in the US is to reserve the admin_level=4 tag for the official state boundary relation. Mind if I remove it from this building so that it doesn't pop up in query results?