Sorry why the revert? I did not change the ref from A516.

For the first two, the paths are continuous. There's no dead end for the public footpath/bridleway. They both go from a service road to a dedicated path. The fixmes didn't mention signage. For the latter, there is no visible trail on the imagery. If you think anything there is wrong then re-add the fixme tags.

It appears from the imagery that the paths are already connected and there are no stubs, so that's why I removed these fixme tags

You don't need to be arrogant. I shall add them back, but if I am told otherwise again then I shall mention this short exchange.

If you come to some sort of conclusion I will go over the area and add the missing tags, if required.

Then you need to speak to the StreetComplete team who's edits only add maxspeed:type tags for national speed limit roads in the UK. I'm confused what to do now. They say only one tag, now you say both. Who's right?

See the short discussion linked on the talk page. So long as the "maxspeed:type=GB:nsl_single" is there it should be fine.

Apologies. I only removed those as StreetComplete automatically has resurvey quests for construction areas

That tag signifies that a kerb of some type is there. Surveying on StreetComplete can provide the exact type on the ground (lowered, flush etc.)

Best to update to what is recommended by the editor with these branded shops.

I tested it myself and that is how they were removed. Re-added.

My apologies, but it seems the tag was removed automatically when I updated the platforms from 'train platforms' to 'tram platforms'

Is Portland Street pedestrianised now?

That's better. Just in my experience, road signs can be wrong or designed to not include certain road numbers. e.g. a sign may say 'M61' when it was meant to say '(M61)'

Do you have any other reference than "signs"? Signs can be wrong or sign the obvious route while ignoring the true road number

Hi, I believe it might be more appropriate to use 'kerb=lowered' ('Kerb ramp' on StreetComplete) for these, as 'kerb=flush' is more for kerbs where the pavement-road transition is almost completely level (according to the wiki), for example, crossings on speed tables where the road raises up to the kerb height.

Hi, please only use the PTv2 tag when the route is fully tagged as according. I have removed the tags for now.

Just so you know, last night I updated all of the City Red routes and converted them to the new Bluestar ones (though not all to PTv2). I see you have been redoing some routes, but they have not been up to the PTv2 standard. You can see details here about adding a bus route: osm.wiki/Buses#Adding_a_bus_route_to_OpenStreetMap

For examples, see the Unilink U2 route for a PTv2 setup.

I am not sure that is designated tactile paving. Could be perhaps something by the kerb manufacturer but even then it is not mentioned at all in the current tactile paving regs. Though saying that, nothing at all is mentioned for bus stops. All I will say is that this example is a clear tactile_paving=yes (I don't have a photo, so a google link will have to do): https://www.google.co.uk/maps/@50.9135746,-1.4902548,3a,48.9y,310.56h,70.09t/data=!3m7!1e1!3m5!1svNuQGJ-xTY7S4-UGT9sstg!2e0!5s20180501T000000!7i16384!8i8192

So for these cases I would recommend applying tactile_paving=no for these kerbstones. They don't look too resistant as well, so perhaps with time the textured surface would wear away.

Hi, can you confirm what the tactile paving looked like at these stops, just to make sure you've marked the tag as yes correctly?