Another case of the mysterious unprintable characters in this changeset. I've cleaned up osm.org/way/24196266 which maybe was the only one. 7f, which I guess is delete.

Reverted in osm.org/changeset/58565004

It probably doesn't make sense to change these away from site relations (using 2 tags, type=site and power=plant, is not ambiguous), but in any case it should not be done unilaterally.

Hi-

Here you've changed commerce road osm.org/way/16135250 from a minor road to a residential road. In general, it's an improvement to change this sort of road that isn't in a residential area away from residential.

Separate from that, I've adjusted the tagging of a couple hospital buildings that you added so that the buildings don't repeat the main "hospital" marking. That way a search for hospital features will just return 1 result for each hospital (the buildings are associated with the areas just by being inside of them).

I've adjusted the hospitals but not done anything with the streets.

Max

Just considering population, place=city (in the US) probably starts somewhere around 40,000.

A county seat with a smaller population can be a town.

There's basically 3 labeling hints, village,town,city. If a population of 3238 is place=city then they won't really ever convey any information, because every vaguely notable place will be a city.

All I did in this edit was change the boundary relation to match the place node.

I just didn't delete the existing tag. Feel free to go ahead and fix it.

I didn't make any changes.

I was simply encouraging you to be accurate rather than expansive in your use of tags, because if everything is a park then nothing is a park.

Checking the imagery, it looks a lot more like a nature area with a nice trail than a landscaped recreation area. Oh well.

Hi-

I'm reviewing edits by new mappers, that's how I got here.

Anyway, OpenStreetMap has it's own meanings for things that are often more specific than the common usage. For example, parks. In OSM, a park is an area that is developed for recreation. This meaning is at odds with a the area also being a reserve (which in OSM would be an area that limits human use). So often things that are called parks in day to day usage end up not being parks in OSM. There's some discussion of the issue on the wiki OSM uses for documentation: osm.wiki/Tag:leisure%3Dpark

Happy Mapping,

Max

Watch out for the editor helping you out and setting the building=yes tag on areas that are closer to property boundaries.

It's not a serious problem, but the map style doesn't account for it so things inside the area end up looking a bit strange, like here, the small building disappears: osm.org/changeset/55533836#map=18/37.14300/-93.26780

Max

Finally fixed the remaining uses by me. Mostly in osm.org/changeset/58339773

Hi-

Make sure to check out the various different background layers. I think in the area you've been editing that the Mapbox background is quite a bit clearer and more accurately lined up than the Bing layer.

Max

Shouldn't an address added from Bing aerial imagery make sense with the context?

Neither of the cross streets here are Medical Center Parkway.

Hi-

For development sites, a tag like landuse=construction, landuse=brownfield or landuse=greenfield is better than putting a note in the name (I've adjusted the hospital land here). There's more info about the tags at osm.wiki/Key:landuse

Thanks,

Max

Hi, there's a specific tag for an ambulance station, emergency=ambulance_station.

I've gone ahead and retagged the station you marked as amenity=hospital here.

Max

Hi-

OpenStreetMap is a database for features that exist in the real world. Please keep this in mind when mapping.

I've deleted your pokemon lures.

Thanks,

Max

I think it is a poor use of the highway= tag to assign it based purely on physical features rather than using it to provide context. Short upgraded segments have better physical features but really are part of a lower priority road. Sometimes a road plays a role that it is underbuilt to perform; it should still get a higher priority tag if it is a more important road.

Changing the road classification for a single bridge (like on US 24 south of here) is a bigger issue to me than whether this particular segment is a motorway or not.

Please look at the edit history of the page. There's no group of people behind it, it's mostly what one person said 9 years ago.

The way I understand 'wiki', instead of discussing my proposed changes at length, I can just make them and then if there is too much disagreement they can be removed. That's part of why there is a history feature.

In any case, the 5 people that have edited the page in the past do not have more say over US highway tagging than the broader US community.

I wrote it because I believe it. It's not an attack on anybody. No, I didn't discuss it with anyone, but no one who wrote anything there previously bothered to discuss it with me either.

It may seem absurd that I'm pointing at my unilateral change to the wiki as an argument to justify a particular way of mapping, but that's pretty much the situation with any use of the wiki as justification for a particular way of mapping, it's likely to reflect the views of whoever last edited the page.

I've upgraded the wiki:

osm.wiki/United_States_Road_Classification#Motorway

Hi, you accidentally overwrote the value in the 'address' tag here with the text 'addr:full'.

I've fixed it.

Max

Hi-

When two ways have the same corners, they should usually use the same nodes.

This is especially true for something like a building:part where one object is adding detail to the other.

Max