It might need updated satellite imagery to get this all accurate, but I get the felling you might have realigned it a bit now.

I have extended the temporary oneway on Dock Rd a little further south after passing there today.

Near the Cycle Shuttle bus stop, I suspect
way/893713893 might be the intended shared use path for the new cycle route. At the moment it's just all very under-signed with the shared paths (and speed limits too) , but hopefully some more signs will come here.

I've an inkling that Dock Rd might open at some point tomorrow.

Should the traffic signals now be removed from node/1683288283?

I spotted it yesterday. Possibly will still get a few more adjustments between here and the roundabout before Monday.

I passed there today. Still closed. Could be at least a few more months before it could open.

Thanks. Was a partially deleted source=" tag.

Now fully deleted.

Regular problem with ID unfortunately.

Would be very tricky to get the right order using ID!

I discovered osm.wiki/Relatify yesterday. It could be particularly useful for mapping new bus route relations although I didn't test it too much.

Hi, as it appears that cyclists entering the circular junction don't have to give way to cyclists who are already on the junction, the junction=roundabout tag isn't correct.

junction=circular could be used instead.

I have readded the is_sidepath* tags, although I've also changed this tagging from the (former) tertiary to secondary.

A lot of geometries will have to be estimates.

I've made a guess based on how it looks that they will use some of the new Dock Rd as part of a temporary access road into the back of the Expressway car park so that they can complete the works/kerbing on the NE side of the current dead end to Dock Rd.

I passed around there yesterday. Apart from the mid-section of Beaconsfield, almost all of the roads are constructed, and where relevant include oneway arrow markings and contraflow cycle logos.

They remain mostly unopened but they are well beyond being changeable. Alignments can always be adjusted later on using GPS or aerial imagery.

Well, there are no actual lanes (including cycle lanes) at these 2 crossing points.

It's not impossible that the temporary crossing on Manor Rd near Pond Rd could get relocated before the diversion begins.

Also I wouldn't be surprised if the advertised cycle route diversion changes to use the full length of Leywick St.

I'll be away when the diversion starts so if you're going to be surveying the diversion, OSM might need some adjustments to get things accurate.

I was told the ramp to the Greenway from Manor Rd is to get widened before the closure begins. I suspect its width won't actually change though. They have cleared the vegetation already which might be the 'widening', but it will be interesting to see if they do move the handrails further apart. (The steps nearby will remain open.)

The 18 month closure will be to the east of Canning Rd. This is the major work involved in this scheme.

The closure to the west of Canning Rd will only be for 2 or 3 months, possibly Dec 2024-Feb 2025.

Yeah, and the new signallised crossing on the northern arm is also for cyclists.

At this rate, Cycleway 2 might eventually get to Ilford by 2054!

It looks like you may have extended a couple of walking routes along way/801938376 that presumably should not continue beyond the crossing on the main road.

I just did updates here and noticed the problem that got introduced. Someone had wrongly extended the currently open cycleway to permit pedestrian access.

I've rectified this now and added pedestrian access round the works at this spot.

Hi Bernard, they are currently realigning some of the old cycleway here and constructing new cycle tracks to create a continuous cycleway on both sides of the roads.

Mapping-wise it a bit fiddly at the moment, but I do check on the works more or less weekly.

I completely agree with with not using the longer "opposite_*" tags, but I can't see any reason to deprecated the simple "cycleway=opposite" where there is no contraflow lane.

It does at least hopefully deter StreetComplete from applying tags for a fantasy "shared_lane".