OpenStreetMap logo OpenStreetMap

Changeset When Comment
137186343 over 2 years ago

Out of interest, why change way/100817341 from highway=cycleway to highway=path?

137042934 over 2 years ago

Hiya, has the signage for this changed very recently? Last time I passed the turnings for this it was signed as maxwidth=6'6" and no special speed limit.

136796251 over 2 years ago

Thanks for the explanation, I can see it does strictly make sense.

However, given how few people use post towns in addressing any more (since their purpose is fully covered by the first half of the postcode), and how the ID editor doesn’t provide any guidance about esoteric UK addressing rules, you might be fighting a losing battle to change all addresses to use post towns.

I don’t mean to be negative, but would it be a more productive use of time to ensure that postcodes are present (and correct) everywhere in OSM in the UK? They convey more information than the post town, fit in nicely with the ID editor defaults, and are more understood by people.

136796251 over 2 years ago

Hi, is there some documentation of the tagging scheme you're applying here?

Helwith Bridge definitely isn't a suburb of Settle, for example.

And having both addr:city= and addr:suburb= set to Settle for addresses within Settle seems odd.

136587322 over 2 years ago

I created note/3714103 so this can be resolved at any point in the future without risking being forgotten about.

136609944 over 2 years ago

I’ve made the fixes on your behalf in changeset/136735002

136609944 over 2 years ago

building=farm_auxiliary, farm_auxiliary=mushroom_farm would work as far as I’m concerned, and be more machine-readable than using the description= tag.

136609944 over 2 years ago

@jmarchon Do you have any better suggestions for how to tag these buildings, while retaining the information that they are specially designed and constructed for growing mushrooms?

136609944 over 2 years ago

Hi, please don’t change these, they are correct and more specific than farm_auxiliary. These are specialised buildings for growing mushrooms in.

136587322 over 2 years ago

Heya, thanks for your StreetComplete work around Galgate, it’s made the map a lot better!

I was just wondering whether way/838572591 is definitely number 8, or whether that’s a typo and it’s actually number 6?

Ta :)

136464916 over 2 years ago

Why have you added this footpath back again? Has something changed which means the discussion from changeset/135290950 is no longer valid?

If something has changed, you should explain it in your changeset comment. As it stands, this looks like an under the radar effort to revert the consensus for how this path should be tagged.

136268773 over 2 years ago

It looks like you reverted it successfully in changeset/136326948 :)

I’ve changed the tagging to disused:highway=footway in changeset/136354219 so I think this is all sorted now. Thanks very much for taking the time to improve the map!

The disused: prefix is documented here if you’re interested as well: osm.wiki/Lifecycle_prefix

Cheers

135425997 over 2 years ago

Are you sure there’s nothing to give way to? There’s all the traffic on the A580, and I don’t think it’s going to be stopping for someone on a bike!

There might not be give way signs, but are there dashed lines painted where the cycleway meets the road? That indicates a give way too.

136202043 over 2 years ago

As you say, I think whether/how to display the label is a rendering question, not an issue with the dataset itself, although I see your point. The Lake District is very heavily labelled.

I can see your point about it being a collection of hills rather than an area. The tagging as natural=mountain_range doesn’t seem wrong to me, but I guess an alternative would be to add a relation containing all the relevant hill tops and label that instead. Perhaps a type=site relation would be appropriate?

136268773 over 2 years ago

If it does, I suggest reverting this changeset to restore the geometry, then re-editing it to change the tagging.

Changesets can be reverted using http://revert.osmz.ru/ (in case you haven‘t come across it before) :)

136268773 over 2 years ago

Heya, is it definitely this whole path which is closed off? The northern segment of it was marked as a public footpath, so it seems a bit odd (although definitely not impossible) that it would be closed for conservation reasons rather than being fixed/improved.

In any case, it’s quite possible that someone may come along and re-add the paths in future, from sources such as MapThePaths or Strava Heatmap. To avoid that happening, the recommendation* is to retag closed paths as disused:highway=footway rather than highway=footway, and add a note= explaining why the path is closed. That way, if someone comes to re-add the path in future they’ll see it’s already there and is explicitly closed.

* See osm.wiki/Talk:Organised_Editing/Activities/National_Trust_Paths#Closed_routes_(e.g._for_safety)

Does that fit in with what you surveyed on the ground?

Thanks!

136202043 over 2 years ago

I’ve reverted these changes (as changeset/136248127), since the area is definitely referred to as the Langdale Pikes, and there needs to be some way on OSM to reflect that.

If you have ideas for how to improve the tagging please go ahead, but I think the way needs to stay there to associate the name ‘Langdale Pikes’ with the area.

Cheers

136202043 over 2 years ago

Hi, can you perhaps go into a bit more detail about why this is a good change and why the previous mapping was incorrect?

If people now search OSM for “langdale pikes”, they won’t find this area, despite that being a commonly used name for it and it being a popular area to visit. That feels like a loss to OSM.

Thanks

136128234 over 2 years ago

Did you see the latest discussion from the National Trust and the OSM’s Data Working Group (DWG) on changeset/135290950?

The National Trust (via AWMapper) have said that path restoration has taken place for this path, and that they are looking into signage.

That does not stop you from walking along this path if you really want to, but it does make it pretty clear that the path should not be on a public map. Putting it on a public map effectively encourages people to use it.

Do you have any response to their points or the discussion as a whole?

136123001 over 2 years ago

This basically re-applies the changes to the path from changeset/135904623 after reverting it (in changeset/136122957) to restore the position of the trig point.

The trig point (node/7685964297) had a note saying its position had been calibrated for calculating imagery offsets, so moving it is probably going to break things.