Hello Corsec,
There are several golf cart paths in your changeset that duplicate existing golf cart paths. See the larger parking lot for an example. Can you remove all of your newer paths and make whatever tag updates are appropriate to the older paths? Thanks.

Hi Topcats, I noticed you made a lot of changes in the area of way/934480913 about a month ago and a lot of errors were introduced with nodes being dragged around creating sidewalks and other ways that zigzag and cross over themselves. Any chance you could go back in and make corrections? Thanks.

I've changed it. I just wanted to make sure I wasn't stepping on any toes first and I appreciate the discussion on the topic. Thanks.

CTVL has private rooms and private baths. That's just about what everyone in the US would consider a hotel to be. On a scale of 1-10 where 1 is a hostel and 10 is a hotel, I'd rank this place an 8. It certainly isn't something a hiker taking a college gap year from college would be able to afford.

Can you give some more information about this hostel? I can't find anything about it and the neighborhood seems to be residential and not zoned for something like a hostel.

What was the reason for labeling Christmas Tree Vineyard Lodge as a hostel? Was that a typo of hotel, or was there some reason to label it a hostel? I'm not sure that is accurate.

Yup, that was my guess. Thanks for confirming.

I'm guessing you meant "hotel" for way/631622350 and not "hoStel", right? I'm going to change it, but please let me know if I'm doing this in error.

There are three adjacent places that are all natural=wood that should be combined into a single area. However, they are visibly different and maybe should have different tags. But if not, there probably shouldn't be three separate areas with the same tag.

Hey Ian. We (speaking for the rest of the OSM community) really appreciate your attention to detail and desire to do things the best way that you can and we like to see desire to learn and improve. If you ever have questions, feel free to reach out and we'll help.

With that said, I came across the errors with a tool called OSM Inspector (http://tools.geofabrik.de/osmi/?view=geometry&lon=-83.37559&lat=33.95658&zoom=18&overlays=long_ways,self_intersection_ways,self_intersection_points,single_node_in_way,duplicate_node_in_way) that show two things I'm interested in: two nodes at the same exact point in space, and ways that cross over (or "intersect") themselves. So that's the first thing that tipped me off to the problems.

I was cleaning up some of them with the editor that like named "JOSM". It is a little "advanced" and can scare people off, but if you plug away at it, you can learn more and more and be very productive with it over time. One of the advantages of JOSM is some very robust QA verification tools and one of the things it warned me about was identical ways (same exact nodes) having identical tags.

Hope that helps a little bit.

If you want more interactive help, there is a Slack server where you can discuss OSM with hundreds of others that are happy to help. Feel free to join here: https://slack.openstreetmap.us/

Hi IanVG, I was correcting some minor errors in this building and noticed that several rooms have the exact same nodes, but also have the same tags. I'm assuming the rooms are meant to be on different levels. Could you double check and correct these problems? way/970103798 is an example that shares the same path as another room with the same tags.

I'm guessing you meant to tag way/968934754 as something other than natural=wood. Can you take another look? Thx.

Can you please explain the fence at way/965617338 ? I've never seen a fenced area like that. Was this a ground survey or did you map this from aerial images. If the latter, can you indicate which image set you used?

No worries. If you look at my history, you'll see I fix a dozen or so similar errors a day. It gets to be old hat.

Hi there ExecutableFiles. Thanks so much for asking about the change and how you can improve in the future. That's awesome.

Basically what I did was removed one node (5908972688) from the area because the way went out to that node and then immediately double back on itself, which isn't "topologically correct" since that doubling back part is zero width. I believe that it went along a wall or something. If you want to indicate that there isn't grass because there is a wall there, it really isn't necessary and you'd have to draw around the wall for the width of the wall. That's just overkill IMO and unnecessary.

I hope this explains things. If not, happy to engage with you some more.

Hi VLD178. I noticed there are overlapping buildings in this changeset that you might want to look into. Maybe there is a problem with your dataset that you are working with that should be addressed?

Hello. Can you take a look at way/30802924 ? I think it got messed up in your edit.

Can you take a look at way/824663804 and see if it can be cleaned up? It currently is all over the place and crosses over itself and that just doesn't make any sense. Thanks.

Can you take a look at way/957610299 ? Something must have happened to it because the way goes all over and crosses over itself. I'd like to fix it, but I'm not sure what was intended. You can probably fix it better than I can. Thanks.

Hey 1T. Something went very wrong with way/837278306. I think it might have been part of your change. Can you take a second look? Thanks.