That’s great, thanks a lot, and happy editing! It’s nice to see someone putting effort into the map around Cockermouth

Hiya, thanks for your helpful contributions around Cockermouth recently. When editing access tagging for things, can you please read the OSM wiki for guidance on the tagging though? osm.wiki/Access_provisions_in_the_United_Kingdom

access=no specifically means that no physical access is possible to anyone, regardless of whether they have permission.

The correct tagging here is access=private. I have corrected it in changeset/153085001

Thanks! I’ve linked the NT to this on changeset/150437359

Another user has come up with a query to show all gates which are tagged as locked=yes on a footpath: https://overpass-turbo.eu/s/1Nb7

It seems that this tagging affects a number of the gates on NT routes which have been edited recently. Is this tagging definitely correct?

See further discussion on changeset/152889219

Thanks!

Heya, further to discussion on other changesets: was this edit made based on an in-person survey of the access situation, or is it an attempt to get Komoot to route along this way?

If it’s the latter then would access=private foot=designated be more correct, bearing in mind the tagging guide for footpaths/etc? osm.wiki/Access_provisions_in_the_United_Kingdom#Public_footpaths

Hiya, thanks for your helpful reply. Sorry I was abrupt earlier, I was rushing and I shouldn’t have.

You’re right that it was motorcar=no before. I looked into it a bit more closely and this road is a bit odd. It’s on the Wainwright C2C long-distance footpath, so needs some form of public foot access, but it’s not part of the council’s definitive highways network. So on reflection, motorcar=private seems more appropriate than access=private.

I’ve changed it to that in changeset/152990451

Thanks!

I’m so sorry, I completely failed at checking this when I wrote my comment. Trying to do too many things at once. The relations/route master relation hierarchy look good to me, and were already like that before I wrote my comment. Sorry for wasting your time!

Heya, thanks for adding this. Should the northbound and southbound routes be in a route master relation for T3 as a whole?

osm.wiki/Relation:route_master

Fixed in changeset/152982224

This road is private, not public. Removing access=no without a survey is not helpful. Please don’t change access permissions without doing a survey.

Heya, just a reminder to please osm.wiki/Keep_the_history.

way/331366453 and way/331366455 were both deleted and recreated quite similarly in this changeset, losing the record of other people’s contributions to the area.

Thanks :)

Hiya @Olivia Ragone. There’s been some discussion recently on changeset/152889219 about the change of node/262689051 from a stile to a gate, and the addition of locked=yes to it.

Even though it’s tagged as foot=designated, the addition of locked=yes means that software like Komoot no longer wants to route walkers along the path.

Is there still a stile next to the gate? Is the gate actually locked? I’m guessing the answer is yes to both, and the gate is locked to prevent vehicle access? If so, I wonder if the stile needs to be re-added to the map and a little path forked off the track, over the stile and joined up with the path on the north side again, to fix Komoot routing.

I worry there might be other cases like this where gates have (correctly) had locked=yes added to them, but this inadvertently breaks hiking routing.

Interested to hear your thoughts on it! I hope I haven’t misinterpreted the situation, though there’s a good chance I have. :)

Nice to know about that technique for debugging Komoot, thanks @JassKurn.

I’ve reverted the access changes as changeset/152933272, since they made the access tagging less correct.

@Dan12345678 if you have walked this path recently then please edit the offending gates to mark them as locked=no, if that’s correct.

Looking at node/262689051, up until version 6 it was tagged as a stile. I wonder if there’s a stile next to the gate, and routing a footpath over the stile would overcome the problems of the gate being tagged as locked=yes. Presumably it’s been tagged that way because it’s locked to vehicles.

The addition of locked=yes was made by a National Trust GIS officer. I’ll comment on their edit and query the locked=yes, because it might be part of a wider pattern of changes which stop Komoot from working in other places.

Hiya, what was your intention with this edit? That footpath was already marked as a public footpath with the correct tagging (foot=designated and designation=public_footpath). foot=yes is less definitive than foot=designated. See osm.wiki/Access_provisions_in_the_United_Kingdom#Public_footpaths

Thanks for taking the time to survey it Artasen!

For anyone following along, the updates were done as way/938862878, and the way is now amenity=parking (with other appropriate tagging) rather than amenity=yes.

Hiya, just a hint: you can press ‘Q’ when a building is selected to automatically square its corners. It makes for a neater map :)

Heya, thanks for your recent surveying and edits in Windermere!

Regarding the fixme here, I don’t think this defibrillator should be removed from the map. It’s listed on The Circuit (https://osm.mathmos.net/defib/progress/LA/), and even if the wall box is in poor condition, the defibrillator inside should hopefully still be working.

OSM is here to map what’s visible on the ground, which in this case is a visible defibrillator box. We’re not here to test and maintain defibrillators! If it subsequently gets removed from The Circuit due to not being maintained, then it will be straightforward to automatically remove from OSM due to the ref:GB:the_circuit tag linking the OSM object to the database.

Where did this data come from? It looks like it’s been badly copied and pasted into OSM. The new addr:housename= and website= for a couple of these pharmacies contain a full address and something which is not an URL.

addr:unit= should be used instead of addr:housenumber= to specify commercial property unit numbers.

Please also split large changesets so they don’t span multiple countries, as that makes them hard for local mappers to review. See osm.wiki/Changeset#Geographical_size_of_changesets

Super, cheers :)

Why remove the name?