(assuming it's still there) are you going to undelete node/1833702708/history , or would you like me to? They also replaced way/59267532/history with node/3558188850 which has fewer tags.

Actually, I don't beieve that way/232185079 is all bridleway (I had a chance to check last week). There's a bit at the west end that is, and a bit at the east end that is (clearly signed at node/322713824) but in the middle at node/2405589357 the bridleway from the west goes north and a public footpath continues east. Similarly I suspect that the bridleway from the west turns north too. I'll update the map when I get a chance but there's still more to do - there's at least one partial public footpath that needs completing.

Also for info way/29213340/history and (in a different changeset) way/259211810/history

way/29213321/history has "layer=no isolated" on it. It's not one of the usual layer tags (which are usually just numbers). What does it mean?

way/190716622/history has mangled layer tags here. I'm guessing that you just split it from the way to the north, but do you know what the layer should be here?

way/183282998/history seems to have similarly merged way layer tags as the other changeset

Something's gone a bit wrong during the merge of ways here I think - way/188046153/history has layer="1; 2". I suspect you've merged items on multiple layers by accident.

node/2482524757/history has an odd layer tag on it "0;1". Maybe you were trying to say that Boyes has a ground floor and a first floor part? If so, I suspect building:levels=* or one of the pages linked from there may help (or maybe ask at help.osm.org).

Looks like something went wrong with way/262258996 here - it now has mangled layer tags of "2;1;2".

Did you mention the "problem" that you fixed here to either SK53 or will_p who were the previous mappers of the ways concerned? Given that they're both on-the-ground mappers I'd be very surprised if the previous situation was incorrect. Perhaps rather than diving in and trying to "fix" a problem (especially where, as in this case, it's really not clear from the imagery) it would be better to contact the previous mappers and ask them?

Here you've moved some information from way/48422187/history to way/48422187 , but what you've done was incorrect - it's not the whole part of the path that can get muddy, it's just where the drainage doesn't quite work properly. Please don't make changes like this in areas that you have never visited, especially without mentioning it to the previous mapper. By remotely editing like this you're devaluing the work of people who actually go out and survey stuff.

Did you upload the trace anywhere? How does it relate to the service road? There's no node where the two cross. At the north end it looks unfeasibly close and parallel to the service road - did you actually ride along the service road at all?

Also, what are the access rights there?

A quick note about the "tree" edits in Clipstone - dividing the area into smaller areas of different sorts of trees means that there's no single "Clipstone Forest" label currently. I'll add that back (probably as part of a larger "landuse=forest" area that includes parts that are used for forestry, but don't currently have trees on them).

I've not created a huge multipolygon partially because the cleared gaps are "land used for forestry", and partially to avoid the issue noted at http://worstofosm.tumblr.com/post/25633720207/just-in-case-there-was-any-doubt-this-is-the .

Have you actually surveyed way/351374184 or are you just relying on an external source of GPS traces? If the former, how does it relate to the service road - it just looks like a rogue GPS trace to me.

Just spotted this discussion and thought that it was perhaps worth mentioning that osmconvert (see osm.wiki/Osmconvert ) can easily extract centroids of OSM ways to make it easy to process. There's no need (in fact in most cases it's actually confusing) to add details both to a way and a separate node in the middle.

Hi - I'm guessing that this node was added by a BitcoinMaps user. The problem was, it was a duplicate of something that was already mapped (in this case, by me!). How does the BitcoinMaps "add" process help users avoid the addition of duplicates?

Best Regards,
Andy Townsend

(both a local mapper and a member of OSM's Data Working Group)

Hello and welcome to OpenStreetMap!

Just spotted that the phone number on your coffee shop way/278428791 might be missing a 6 - I'm guessing it's +441246 not just +44124.

Anyway, best of luck with the business - I might drop in for a coffee if I'm waiting for a pizza from next door.

Cheers,
Andy

Hello and welcome to OpenStreetMap!

As you may not have gathered (unfortunately OSM's documentation is open to improvement) there's "one map shared between everyone" so that your "planned walk" way/351419385 is viisble to everyone. What you probably want is something that allows you to create a map based on OSM data - something like http://umap.openstreetmap.fr/en/ might be what you're looking for here.

However - there's lots of useful information that could be added to this area of the map (gates and stiles, field boundaries, details of the surface of the paths, whether something is legally a public footpath ("designation=public_footpath") or not...

Is the use of Zillow's listings permissable licence-wise? Their main page says "© 2006-2015 Zillow". Their main terms page http://www.zillow.com/corp/Terms.htm would suggest not, unless we have some specific agreement in place (as with Bing imagery) to re-use their data?

When you say "altered to be a bridlepath" do you mean you changed the highway value, or the designation value?

Previously way/29334998/history was a highway=track with designation=public_footpath. Now it's part of a highway=bridleway (i.e. it's got narrower in the last couple of years and is no longer wide enough for e.g. farm traffic) but is designated as a bridleway. My recollection here was that the bridleway vs footpath signage was iffy in this area but part at least was definitely a track when I was last there (about 2 years ago).