Thanks. I have corrected tagging here now.

Thanks. I've now done some rough realignments based of the imagery.

There's still a bit to be done at the Greenway end. The riverside path is done at that end and has steps to get up to... basically nothing, for now.

I heard someone ask the police, but they weren't giving any info about the incident.

I passed there again today and the bridge was open + was being well used. There's also a connection open between the towpath and Hepscott Rd (passing beside the north end of the bridge.)

You might also be interested in checking out Bridgewater Bridge which has also opened up.

More on these at https://bsky.app/profile/maclondon.bsky.social/post/3mkbkrvv3yk2i

Apparently the bridge opened on Thursday... but was completely cordoned off by police this afternoon. Police say it 'hopefully' will be open again on Saturday.

Thanks. Yeah, has been opened for a while. I've removed the access=no tags now.

Ah, I hadn't spotted that. I've changed the route relation to "disused".

https://www.thurrock.gov.uk/ferry-services/tilbury-to-gravesend mentions theat it "will not operate until further notice" so it might potentially reopen in the future.

Yes, it does look like the BM5 line only needs 2 relations.

Bus routes in NYC have definitely needed some attention as in general not many bus stops have been added to route relations. (Like most of the world, I suspect a lot of routes are also over-mapped beyond where the route actually starts or ends.)

The one big advantage with having ALL public transport routes converted (properly) to PTv2 is not having to worry about foward/backward roles - a benefit for all OSM mapper.

If for example a junction gets remapped, it can get very confusing if there's a mix of routes on a section of road where some routes need a role set to forward, some need backward and others (including all PTv2 relations) should have neither.

It becomes much easier to identify gaps introduced into valid PTv2 bus routes as OSM Inspector highlights them as invalid. However there are other causes for an 'invalid' route, including bus routes in the wrong order.

Non-PTv2 routes would be almost impossible to keep accurate in NYC.

Hi,
It takes a bit of effort to make a route relation into (usually) 2 PTv2 relations - one for each direction of the route. It also need knowledge of where each direction of a route begins + ends.

The relation doesn't need to perfect, but there should at least be some degree of effort to 'convert' the route relation before (mis)tagging it as being PTv2.

Routes do need ongoing maintenance on OSM due to introduction of gaps/errors. One of the advantages of PTv2 is with identifying routes that need (often only minor attention) using e.g. https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=-73.93171&lat=40.71787&zoom=12&baselayer=Geofabrik%20Standard&overlays=ptv2_routes_invalid%2Cptv2_error_ways

Currently with OSM Inspector the QM15 route demonstrates how one relation mistagged as PTv2 can pollute the map. If a large number of routes were similarly mistagged, it would made this valuable OSM Inspector tool into 'finding needles in haystacks'.

Ideally all bus/train routes would be converted to PTv2, but only those that have been converted should be tagged as PTv2. Improvements can be made later.

(Some bus routes can have different variants that require separate relations, so it is possible that the BM5 line does need more than 2 relations.)

Some info on the delays at https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Froach-point-bridge-any-update-v0-fhwaful4hmtg1.jpeg%3Fwidth%3D1240%26format%3Dpjpg%26auto%3Dwebp%26s%3Da89ea20027da7b77ad6e8db179bf8e477257f13f

Seems it might open anytime from tomorrow (council inspection) to after the electrical works on the 14th.

Possibly needs to pass a safety check first. I'd be hopeful it might get opened up as soon as tomorrow... but I might be overly optimistic.

One grumble... the placement of the 'no entry' signs at the end of Wyke Rd do officially 'block' the intended future cycle route via the footbridge.

I had a look yesterday, half-expecting that it might have opened the previous day.

There's still a small gathering of railing + handrails on the ground for the steps at the southern end of the Fish Island side.

Looks like it might 1 works day away from opening.

The changeset descriptions seemed to suggest there was an intention to map the Greenway 'consistently' (rather than accurately) and wasn't based on any obvious knowledge of it.

Hi. Any reason why you reintroduced the section of C22 that will be closed for the next 3 years back into the relation for the open route?

Thanks Pascal. Now removed.

I tend to use that name=zz for temporary use to ensure I'm adding ways to the correct route. I try to remember to delete the name before I save the changeset, but every few days I do a search for instances where I'd forgotten to delete it.

The LCN+ links in London were continuous (numbered) corridors that were used to plan the entire intended cycle network in London. These included existing + aspirational alignments for cycle routes. Numbering would change whenever a line crossed a borough boundary.

The idea for these links was that individual boroughs could strategise long term towards delivering missing sections of the cycle network and ensure that neighbouring boroughs were 'singing from the same hymn sheet'. The forward planning could include e.g. that future buildings might need to have an arch to enable a cycle route.

The numbering used was completely separate to actual cycle route numbers and was never meant to be used on any route signs but was basically for 'administrative' purposes.

However the LCN+ links that did get mapped on OSM were initially wrongly tagged as being actual lcn cycle routes, with numbers like +166 and +205.

I only changed the name at + to the SE of the Manor Rd junction. If you think the street name has also been wrong further up (i.e. NW of this junction), feel free to correct it.

Yeah, I'd intended it to changed to highway=path.... but instead changed the surface tag by mistake.

I've corrected this now.

Now corrected. A separate node for Superdrug had become merged with the subway exit.

Thanks Andy. This gap is now fixed.