Thanks again for helping to improve the map. I commented on this node a while after it was added: changeset/101416787. We now have two nodes node/448899243 and node/8542013793 in the same place, but both attempt to represent the same thing. The older node is more established and has more detail associated with it, such as the trig point's reference code, so I suggest deleting the newer one that you moved. What do you think?

Cool, I've changed this in changeset/116751052 - I hope that looks correct to you.

Thank you for helping to improve the map. Although there's a trig point here, I wouldn't describe it as a "peak" - it's quite a flat area. I'd suggest tagging it with man_made=survey_point instead of natural=peak - what do you think?

Thanks for that: I've not got round to using Streetcomplete yet, but if I do I'll look out for surprises like this.

Thank you for helping to improve the map. I notice the new car park you added at way/1014066261 overlaps one that already exists at way/235098934 - I've combined them both into one car park and added tags in changeset/115988981

Also I notice the platform you added at way/235098931 overlaps the Pullman Buffet at way/235098927 - you might want to tidy up the boundaries between these.

I'm puzzled by this change: there's a noticeboard here, but nothing that I'd consider an office that you can go inside for tourist information.

Thank you for this helpful improvement to the map. I notice that Bollington FP 41 way/101827164 is marked as both "designation=public_footpath" and "access=private". It doesn't seem right that both these things can be true: if it's a public footpath, at least "foot=yes" should be set and I wonder if other forms of access are also permitted.

Hi, I noticed this is tagged with the name "Woolsone" but I suspect it should be "Woolstone"

Thank you for your helpful improvements to the map. I noticed you had tagged with way/896022405 "name=footpath" which seems weird: it is a footpath, but that's not its name. I've removed that name and added a "designation=public_footpath" to match way/109670819 which seems like one end of the path. I also removed a "fixme" from that end of the path and the other end at way/109667913

I think all this makes sense, but please let me know if I've made any mistakes.

Hi, John. Thank you for all your helpful improvements to the paths around Cromford and Black Rocks. I've been meaning to improve them for a while, so it's good to see you getting round to it.

Hi, thank you for these useful improvements to the map. In this changeset you altered the name of node/245941740 from "Alport Heights" to "Alport Height". This makes sense and matches the title of its Wikipedia and Wikidata articles. However, "Alport Heights" is a commonly used name for this place, so I've added it back as an alt_name in changeset/114068834 to help searches for osm.org/search?query=alport heights return useful results.

That's great - thank you for fixing this so quickly.

It looks like you've mapped an industrial area at way/956597519 in the water of the River Tame at way/217703929 - the extent of the river as currently mapped also covers Camden Street.

I've removed the towpath tag in changeset/109358696

Thank you for improving the map. I notice Winterford Lane way/83641001 has the tag "towpath=yes" which seems like a mistake given that it doesn't run alongside the canal.

Good point: I didn't check the way's history carefully enough. Thank you for fixing the tags.

It might also be worth restoring the "foot=yes" tag you removed to make it clear that pedestrians have a legal right to use this route.

If there's a gate there, that doesn't mean nobody can pass. Many footpaths pass through gates that pedestrians must open and close.

I see you've removed the "access=private" in way/112575179 which is good, but to improve your future mapping I encourage you to read designation=public_footpath and osm.wiki/Access_provisions_in_the_United_Kingdom as well as checking the existing tags on objects before editing them.

In this changeset you have marked way/112575179 as "access=private" even though it also has "designation=public_footpath". As foot access is permitted to public footpaths, it seems you have mistakenly marked this as private. Can you explain the reason for this change?

In this changeset you have marked way/112587247 as "access=private" even though it also has "designation=public_footpath". As foot access is permitted to public footpaths, it seems you have mistakenly marked this as private. Can you explain the reason for this change?