Hi, Truck-thin. Can you explain why you removed access=* and informal=* tags from trails here? One or more of them (e.g. way/1327258560) is on private property and is leading to trails that are not approved by the state park.

Thanks for the info. I was able to confirm and update name=* and ref=* for many buildings. The name was completely removed before since it did not seem reliable. It did not follow the correct naming convention described in the wiki for name=*, specifically under "Name is name only". Many of the names were descriptive. For example "Library LB 11" which was updated to the buildings name (i.e. Paul A. Elsner Library). With the info you provided I was also able to confirm the reference number (i.e. LB 11). I also see you recently added Mapillary imagery here. Thank you for that! That also helped me confirm many buildings ref=*. Some were not mapped before.

The info you linked to seems to confirm that many are descriptive names rather than an actual name of a building. But I have updated some with a name again. Some names on the site are the subject taught there, some are multiple offices within a building. A few are the actual name (e.g. Paul A. Elsner Library). A good example of how the "names" on that site are mainly descriptive is the one named "Vacant". But I was able to confirm from that site and with Mapillary that the building should have ref=26. The building number is on the side of the building like you said.

I'll take another look to see if there are any others I can update. If you have any questions, please take a look at name=* and ref=* in the wiki and let me know. Feel free to message me directly.

Naming both is redundant. Similar to giving buildings the same name as the surrounding way. If you feel strongly feel free to update as you see fit :-)

Learned some things. Including leisure=resort being a known issue (leisure=resort#Rendering)

Also with the site, I was able to tag the Retreat area at the south of the property. I am calling this good but I am on the fence about where to place the name now. Should I put the name on the campsite itself or leave it on the leisure=resort which is not rendered by some OSM's main renderer?

Well based on the info you provided, it definitely needs a little more fixing. :-)

But yeah, that is weird that leisure=resort is not rendered. The only reason I knew to point it out is because I remembered all of the similarly named things was confusing to sort out.

Thanks for letting me know. I'll take another look. It appeared to be a redundant name since it is within another way with a similar name (way/490782006). I'll take a look at the site and sort out what is what.

Thanks for catching. Fixed.

By the way, Its been a while since I read the wiki on turning loops. I should have done that before doing those edits. Sorry for the trouble.

It may not have been this changeset but most that I found today looked auto generated.

Sorry. Many turning islands were pretty messy. There were a few one offs that did not match the others. Be careful with reverting. There may be other edits in the mix. Are you cleaning up the messy ones here?

The note should have been "Fixes runway number format."

Thanks for asking. It is similar to a store number for a business. Except there are far less fire stations within a network.

There are some things that were imported from a large data set (e.g. GNIS) that do not follow what is described in the wiki. But the majority are named with whatever naming convention the source dataset had. Fire stations seem to be one of those features that were often imported from large datasets.

If I am missing or misunderstanding something, please let me know.

What is this building? The name "Pavillion" should probably be removed. It is currently tagged as a ranger station. Is that still the case? For more info on names, please see the wiki on names: osm.wiki/Names#Name_is_the_name_only

Please see the wiki on language-specific names (osm.wiki/Names#Language-specific_names). The correct way to tag this would be with name=*, name:en=*, and name:oj=*. Depending on the use of the language by the tribe, name=* may be Ojibwe (roman or syllabics). In other cases it may be English.

There are some tribes that have street signs in Ojibwe with English subtext. In that case, it would make sense to use the name that is signed.

In Cass Lake (as well as others in MN), English is the primary language. So signs are in English with a subtext of Ojibwe.

For Cass Lake, it would make the most sense to use name=Cass Lake with the respective language tags.

Thanks for the catch. I see you made an edit already. Since it is short for "Manhattan Parking Group", I will add a brand tag for context. That should avoid confusion in the future.

There are a couple of ways with invalid values The value for building:part=1 should be building:part=yes. But these are not mapped inside a building. Are they supposed to be building=yes?

way/1420428481
way/1420428482

The map has been updated. You are seeing the tile cache. It can take days to a week for the tile cache to be updated.

I used barrier=fence and fence_type=*. If barrier=fence should be a separate way, please let me know.

On a side note, I'm unsure where the gate would be. Otherwise I would add that.

Hey, GA_Kevin, here is another. I'll let you fix since I don't know much about mapping these. node/12944743366

I am guessing you are wondering why the parking lot does not have a name. If so, take a look at osm.wiki/Names#Name_is_the_name_only

Tagging with operator=* is helpful. It is very helpful when access=private or access=customers is used. Then it is easy to identify which business it is for.