Hi Nate_T,
I replaced node/5359363756 since it got moved in such a way that the fairway became an invalid polygon (intersected itself). I also moved the park boundary, because it looked invalid both before and after the change. Is that an area you know well enough that you can fix up the boundary? It cross a lot of things that I'm guessing shouldn't be crossed (like a putting green).
Thanks!

Hi Brian@Brea. Does way/625187729 really cross over itself? Is it a boat ride on a track or a free-floating motorboat just tooling around the body of water?
I'm trying to make sure ways don't cross over themselves without proper intersection or grade separations. Can you help clear up this path? Thanks.

Hi there @Btlalum. Your tracks for Ridgewood and West View look much better than the previous ways that were there. I went ahead and deleted the old version since it was confusing to have two similar ways on the map at the same time. I also did some editing of the way to remove places where you doubled back over the same nodes/points that you had drawn going out to the end of the loop. In general, a way should never be drawn on top of itself. Thanks again for improving the map with your contributions.

Good evening kartler175. I'm guessing from the "reverter" in the "created_by" tag in the changeset that you reverted some change? You might want to take a look at what your change did to node/185937622 since it moved it far away and broke the ferry route and made a service road travel across water.
I'm not sure if the revert broke anything else, but this is something that I noticed.

thanks!

Thanks for cleaning it up. If I spot another case of it, I'll let you know.

It looks like whatever change you made to the boundary has created 100+ duplicate nodes. For instance, check out node/6152983910 which sits at the same location as two other nodes. If you look at that boundary, there are 110 duplicate node errors according to JOSM. Should this changeset be reverted?

I stumbled across one of your edits and found that some waterway nodes got moved to a boundary and made some big errors in the path of the river. I'm fixing node/470159145, and a couple more in the immediate vicinity, but you might want to take a broader look at your revert and clean it up if there are others in the same situation.

FYI, I reverted this changeset as it made a huge mess around Pathways High.

I was thinking maybe it could just be marked `amenity=parking` since I did see a couple of cars parked there in one of the satellite images.

Hi there @Digiranger. I've noticed a few of your edits and wanted to share a tip with you so that you can make better paths. I have a golden rule of OSM that says something along the lines of "paths shouldn't overlap other existing paths". If you need to overlap another path, or cross an existing path, you should terminate it at the crossing point and start a new path. It's very common to use many many paths when mapping out a sidewalk structure. It is best not to try to do it all with a single path, because that results in some validation errors.
Let me know if this doesn't make sense and you need some clarification.
Thanks!
@b-jazz

Thanks for your first (and second) contribution to OpenStreetMap! If you ever need help, feel free to reach out to me. I do a lot of mapping a couple hours North of Ashland.

FYI, I deleted one of the Big Turtle Park since there was already another one at pretty much the same location/boundary. Is there a reason for adding the second park?

Deleted the mishmash of service roads in changeset/65557596. I can't imagine why they were there in the first place? Mapping for the renderer maybe?

Hi @Melase,
Just so you know, I deleted way/646011493 since there was already a way drawn for those roads. If you feel this is a mistake, please let me know.

Hi Brian@Brea. Can you help me out with way/625187729. There is a pretty hard and fast "rule" of OSM that ways can't cross over themselves without an intersection. If this boat ride is on a flat body of water, I'm wondering if a way is the best way to represent the path. If so, I'm guessing the way should be broken up into pieces and "intersections" put into place, right? If it is more of a ride (like a log ride), then the way should be broken up and layer=N tags put into place. I can't tell from imagery what the path actually is. So I'm hoping you can lend a hand.

Thanks,
b-jazz

Hi there. I'm curious to know why you are adding things like swimming pools and why someone else added a stereo store to a US census statistical area relation. Was this an accident? If not, please clear it up for me. Thanks.

Oh man. I'm really sorry about that. My change was trivial and can be reverted if that makes it easier for you to to resolve the conflicts.
I'll make sure I wait several days before editing any of your work in the area again.

Welcome to OpenStreetMaps, Janet. We appreciate your contributions.

Hi there Robert Lamm. Are you aware that the nodes that make up some of these boundaries are stacked on top of each other at least 6+ times? At least for way/652979075, there are many nodes that occupy the same centimeter of space. Is that something you can clean up?