Fixed - It was just a typo.

Personally, I would have classed it as an obvious typo and just corrected it myself - would have been quicker :)

Sure, happy to do that if it helps.
I would have done it sooner but wasn't aware of that property.

Go ahead and update based on your latest survey.
There is some work being done on this road but I thinks it's just pavement work at present and not affecting road lanes.

I may have made a mistake and thought it was only a section of road.
I can't see which change you are referring to (i find it really difficult to see specific change history within OSM, i must be missing something)

@someoneElse
I'm sorry for the mess I made. It wasn't intentional I must have got confused with the task and the attributes.
TBH I found Maproulette more trouble than its worth so have stopped using it - much safer sticking with StreetComplete and Direct edits.
I did get muddled by the task and did think the place name was weird for a town, although I thought that would also apply for a township (having the date range mixed in with the name, but there are some odd places names in the world and i didn't want to edit that).
Thanks for reverting - as I say, it was a genuine mistake and nothing malicious.

Thanks, that is useful - I wasn't aware of taginfo.osm.org.

I'm happy to change the values for this area and now feel it may be best just to retain the previous value (I assume if there is a mix, then put the primary item first so the various apps can take that as the single value if they want and its mostly correct).

Thanks - I am genuinly keen to help improve the map . I have hit exactly that scenario you describe. The MapRoulette task shows a sequence of rare values for surfaces - most of which are typos or obvious mistakes and then you encounter a value which could be a mistake, or missing something and its so hard to tell, especially whne in the headspace that most previous entries were errors.
I'm pleased the other changes have been useful (As i hoped).

Ok, should I change it back to the previous value (I tihnk it was something like "safety surface")
Or try a different generic value?

Perhaps this is a more fundamental principle on whether values should aim to fit within the default values or be hyper tailorered.

I was using MapRoulette which suggest that rare values maybe less useful (presumably for different apps that consume the data).

What would you suggest? i'm happy to be guided.

No, i didn't survey in person. i was using images where i oculd.
I was tryngot replace the previous value of "Safety surface" with something generic and the guidelines (osm.wiki/Key:surface#Special_(sports,_etc.))
suggest that "Tartan" can be used as a generic name.

Thanks for asking -I was trying to remove mixed values so either "dirt" or "sand" could work. I was told its often better to clear ambiguous values so other could complete.
Do multiple values work? I was trying to follow the guidance for surface area and it wasn't clear if multiple values can be used (I guess different apps present the data differently)

I did leave a comment within MapRoulette saying that I couldn't "fix" this item and why (area is not clearly identified). I can only assume these change notes get saved in MapRoulette rather than OSM itself.
TBH, i'm finding MapRoulette more trouble than its worth so may just stick with my local area! :)

Sorry, i've just realised how bad I have been at that. Often I complete the MapRoulette task and sometimes do some other tweaks whilst there (Usually if the system highlights something that needs resolving).
From now on I will ensure that my comments reflect any additional changes I make.

Hi, I was using Map Roulette which had a task to update nodes to areas for Basketball courts.
In this location there is a node but I couldn't change to an area because its not clear where the area is ( there was a footpath cutting through what looked like the likely basketball ground).
It's odd that the Maproulette task it links to is incorrect and not the one that showed this site. Not sure what's happened there - Will flag with Maproulette.

Hi, I was using MapRoulette and a task was to convert nodes for "Basketball court" into Areas.
It showed a basketball court at Church Road Recreation Ground. (Node ID 9079069745). The latest imagery shows a car park. Perhaps this has changed?
Thought you may be local and could update more accurately than me.

Hi, thanks for your helpful comments.
For this area marked as cork, I did check some photos of the area and I was trying to apply the best fitting value. I have been looking at the wiki (osm.wiki/Key:surface?uselang=en) but couldn't find any mention of Cork.

Similarly for the slip way - I was trying to use the values in the drop down so changed "Rails" to "Metal" as Rails was not on the wiki.

For the path that was "partly asphalt" I felt this was less useful than simply "asphalt". However, I did consider removing the value entirely but felt this would be losing some information. If this is better practice, I will happily do that.
I'm sorry if I've accidentally degraded the map - it certainly wasn't my intention. I'm still learning the conventions so any guidance is appreciated.

If this is not correct, because it is not officially prohibited for pedestrians, i'm happy to change it to a disabled quest.

Have another look at the section I marked. It is a very small stretch where cars cross to choose a different fork.
There is no pavement or anything here.
In the Bing street view you shared, turn to face South and you can see the blue car heading up the right hand fork (Wells Road) this is the section in question.

Hi,

Yes, the area is called "Zone N" - Its a strange name but is left over from when the area was demolished in the 1970s and then zoned for redevelopment. You'll see another green area SE along the Wells Road, called "Zone A".

The path is across the grass through the area, rather than a concrete path. so it often blends with the surroundings - I can remove it if required. It is only semi-formal....in that it gets mown but I guess someone could walk anywhere on the grass.
Simon