Wrong source comment. Local knowledge and website as tagged.

Nice work! I'd not expected to find an internet source specifically documenting a "roundabout... known as" and appreciate you looking out for your home state.

Oh. I see you did this with CoMaps which probably forces you to pick one and only one of these tags. Anyway, fixed now.

Good job with your first edit.

I've added amenity=cafe since this place seems to sell prepared drinks not captured by the shop=coffee tag alone.

shop=coffee

While I see eastbound was quickly corrected as the road had already been opened before this changeset, the westbound lane was accidentally left close for over two weeks
way/1395759020

Changing the permanent access controls on an OSM element to reflect short term road closure, even if anticipated to be a week is a poor idea. Many downstream uses take snapshots of the OSM data and use it for months.

Thanks as well for your good work. This import and the after consideration to the edge cases have been very well handled.

It's now fixed, but here is an example of where this edit has duplicated an element already on the map.

note/4827069

OK. If the land users and managers have names for the trails, I appreciate your efforts to get that information. I myself got into this project to map a local forest in my town. For future edits, I'd recommend a more specific source comment such as "discussions with land users and managers" to make this clear.

You've cited "knowledge" for many edits in this area. Can you elaborate on how your knowledge of trail names was acquired? Are they signposted? Has someone published a trail guide or map?

For these names to be is scope for OSM, they need to be verifiable.
osm.wiki/Verifiability

added

changeset/166543323

... and add website to Aldi. Sorry for long geographic area--it was a mistake.

Source: ... and ESRI imagery

Hi TucsonIsFor[]ers:
Can you confirm having seen this in person?

While I appreciate your interest in citing an internet source we can all see, that one is not one we use for intellectual property reasons. If you've seen it, you're the source--problem solved.

Welcome to OSM o0elMira0o.

I'm glad to see someone citing local knowledge fill in the track. I was not comfortable doing it from imagery alone having not seen it.

I've changed the tagging from narrow_gauge to miniature and marked the track gauge=184 (mm) based internet sources saying its 1/8 scale. Do correct that if you have more precise information, as it appears 190 is also an option, such as here.

way/613631580

Yes, I see what you are talking about now and doubt doubt there may have been very small bridge that escapes my memory. Thanks for checking!

Greg Rose:
Have you seen this bridge?

way/978314272
I hiked this about 11 months before you marked it. The fords are real. If there's a bridge here, I've forgotten it.
It seems odd to have a bridge over a small creek that can only be accessed by four fords of a bigger creek.

Unfortunately, my one photo is of the cabin taken with the creek to my back.

been fixed by SuzanneTF1

changeset/141140150#map=17/35.680372/-80.477890&layers=N

I've removed the name tags from individual buildings as the complex has been tagged on the landuse element. This is an instance of "One feature, one OSM element" practice.

osm.wiki/Good_practice#One_feature,_one_OSM_element

Thanks for your contributions.

It looks like this was intended as a joke. We really don't appreciated people messing with the integrity of our data. However, if you'd like make some constructive edits here, I'm sure we can find things for you to contribute.

You've added names to many nodes within the Memphis airport taxiways. Can you leave a comment on the following note about what these are?

note/4592305