way/663291700 got all messed up recently and zig zags across itself. Can you take a look?

A double sided tag seems like the right answer to me. In the meantime, maybe they can be represented with parallel lines separated by a small distance?

I'm guessing these aren't really curbs, but more appropriately very short walls, right? The fact that the way doubles back on itself (ie. nodes A-B-A) leads me to think this was done on purpose to indicate it is "lower" on both sides. But this triggers various Q/A tools like OSM Inspector since that is invalid topology (as I understand it). So wouldn't a wall be more appropriate here? Or maybe there's another way to keep the Q/A tools happy?

Awesome. Thanks for contributing.

So the sign says "http://www.jersey.police.uk/" and you are unhappy that the bot changes it to "https://jersey.police.uk/". Do I have that correct? I can add some code to skip this one particular node since it seems to upset you, but I won't be able to get to it in the next week, which means that it will switch it back at least one more time. Sorry.

I'm not sure what change you're going to make to make us both be happy. If it has already happened, it isn't correct IMO. Ways shouldn't cross over themselves. They should be split and the layer attribute should be set appropriately. I don't consider this a false positive for QA tools. And if it is, I think the right thing to do would be to go ahead and split it so that even if it was a false positive, it wouldn't clutter up the output of such tools so that work can be focused on other areas without the clutter.

Hey Stereo, the pedestrian stairs from street level up to bridge level need to be split so that the way doesn't cross over itself, which is topologically incorrect. If you look at my changeset (changeset/111830687), you'll see what I'm talking about. Can you please revert your change? Thanks.

Hello there. You broke one of the outer members of the national forest multipolygon. It doesn't enclose anything now as it's just two nodes. Is that something you know how to fix?

@pnorman, probably time you assist with a revert as the importer doesn't appear to be responding in a timely manner.

Looks like someone else has deleted it.

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/