I’ve changed it to monitoring:photosynthetically_active_radiation=yes. Hopefully expanding the acronym will make it a little clearer. I’ve also added wind speed, wind direction, relative humidity and global radiation by comparing the photos from the peatland-es-uk website with the manufacturer’s website (Skye Instruments).

Adding things to the wiki doesn’t really interest me, sorry.

Thanks for your efforts on this :)

It’s a sensor for photosynthetically active radiation (https://en.wikipedia.org/wiki/Photosynthetically_active_radiation), see https://peatland-es-uk.york.ac.uk/field-measurements/climate

Hi, thanks for your edits to improve the centre of Lancaster. I’m not sure this edit is correct though — Gillison's Lane is a covered passage inside the shopping centre, not a cutting (like a railway cutting). What was the issue with City Strides?

What was incorrect about the foot= tagging here?

It was a typo of highway=footway, which I’ve fixed in changeset/96730493. Thanks for pointing it out.

I didn’t make it a linear feature or join it to anything else because I was trying to make as few changes as possible in changeset/93505061, given that I was fixing up the tagging of someone who’d done an on-the-ground survey, and I have not done an on-the-ground survey. In particular, I didn’t want to fiddle with their geometry.

If you have strong feelings about how it should be done, though, and know how the paths/areas are layed out on the ground, please go ahead and correct things further. :)

Thanks for your continued edits! The Lyth valley’s starting to look quite detailed. Just a note — I think building=barn or building=cowshed would be more appropriate for these farm buildings. building=shed is intended for garden sheds! See the wiki: building=cowshed and building=shed
Happy Christmas :)

Hi, thanks for your edits around Lyth recently, it’s good to see someone taking an interest in the area :)

Hi, thanks for your recent edits. What’s your reasoning for changing this from highway=track to highway=bridleway? On the ground, this is a track. Its legal designation as a bridleway is already tagged separately as designation=public_bridleway. To my eye, the map now contains less information about the type of highway on the ground. Were you making this change to highlight the bridleway in the rendered map tiles? Ta
---

Published using OSMCha: https://osmcha.org/changesets/95738482

Hi, unfortunately we’re not allowed to use modern OS data in OpenStreetMap, as their licensing terms are incompatible with OSM’s, so I’ve reverted this changeset (in changeset/95803026).

See osm.wiki/Ordnance_Survey for more details.

Please do continue to contribute to OpenStreetMap using other, freely licensed sources of data! In particular, your own local knowledge of an area is invaluable.

Thanks

Hi, thanks for your edits.

I’ve reverted this changeset because it looks like you accidentally dragged a node of the fence so it crossed the railway line and joined Park Road Gardens. There didn’t seem to be any other changes in this changeset.

Can you please use more informative changeset comments in future, as it lets people know the intent behind your edits, and quickly find ones which are relevant to their interests. ‘details’ is not very informative! See osm.wiki/Good_changeset_comments

Ta!

Oh dear! Sorry that’s going to be more work for you. I think the map will be better for it in the end though. Thanks for your efforts :)

I was using this tagging proposal, which suggests using diet:vegetarian=limited when there are very few vegetarian options available: osm.wiki/Talk:Key:diet#add_.27limited.27_value

They have few vegetarian options on the menu, and from local knowledge, typically they are out of stock of one of those options at any time. I think that qualifies as ‘limited’. I was certainly pretty disappointed when I ate there (IIRC there was exactly one option available to me).

When doing maproulette quests, please don’t overwrite potentially-correct tagging values which already exist, just because the wiki page is more constrained than reality.

It could be tagged as diet:vegan=limited too, yes.

I’ll make those changes.

Hi, have you visited the Toll House Inn recently? At least earlier this year their vegetarian menu was quite limited (I surveyed it). What’s your source? Thanks!

Hi, what’s your source for this edit? From its name, I would expect Chapel Close to be a no through road, and from the Bing satellite imagery it looks like the service road off Langdale Crest is actually just a driveway for one house, which potentially doesn’t connect to Chapel Close. I might be wrong, though. Do you have driver feedback for this edit? Thanks

Sure, feel free to make that change (bear in mind that the path is split into 4 or 5 segments).

> Do byways normally list every type of transport in this way, rather than just use the access to represent the same group?

I did think so, since the access=* tag applies to every possible mode of transport (foot, bike, lunar buggy, hovercraft, …). Looking at the definition of a BOAT, and the UK tagging guidelines (osm.wiki/Access_provisions_in_the_United_Kingdom#Byways) though, it does look like access=designated is the preferred tagging. I’ll change that, thanks for the pointer.

No, I don’t agree with the removal of those. For better or worse, there is a legal right of way for all traffic (pedestrians, bikes, cars, etc.) on this route, and the tagging for that is *=designated.

It really is the case that this route is explicitly designated for use by cyclists (and others).

If there’s a problem with cyclestreets.net picking up and recommending these routes to people, then perhaps there’s another tag it could factor into its decisions which could discourage that?

(I’ve fixed the tagging in changeset changeset/93592748)

Hi, thanks for your detailed edits to WGC on OpenStreetMap :)

Tagging the car park as golf=cartpath is incorrect tagging (it’s a car park, not a cart path) and an example of osm.wiki/Tagging_for_the_renderer which we try to avoid. While it potentially makes the rendered map look nicer, it makes the underlying map data inconsistent and confusing, and OpenStreetMap data is used in many more contexts than just the static rendered map.

Thanks, and happy editing :)

Fixed in changeset/93591577