StephenA

We've removed and repacked with the boat in the water. You pre-cut your packing to the right length. Remove the old squished packing and put the new stuff in and re-seat the packing bush, making sure you tighten up the two bolts evenly. Yes some water will come in - but that's what you have a bilge pump for, and if the amount coming in round the shaft whilst you have the packing out is enough to get anywhere near to overwhelming the pump then you've got a serious problem. As for packing - we've picked up a small length and as when we've needed it. Most chandleries sell it - but as has been pointed out there are different sizes so you need to make sure you get the right one.

We were there about 3:30pm - beer was good and quite a good number of people sitting round outside soaking up the sun.

Nick might know - it might be from a specific source or it could just be caused by internal calculations when things have been added and moved round. I've adjusted it but I had to guess at what the actual distance is.

If you could provide a diagram showing what is where that would be helpful and we could look at tweaking things in canalplan

Are you censoring the word or is it like that on the notice. If you're the censor then I'd be onto CRT about it.

Which is why we use the emails as the starting point.

You'd have to ask Nick. I have a feeling that similar discussions have taken place in past

No problems with co-ordinates as I use geospatial logic (using POINT storage in the DB and ST_Length and ST_GeomFromText in the code) to return the nearest canalplan location to the co-ordinates from CRT. So after that we're just using Canalplan IDs If you click on Plan Round it will find a route that does not include the stoppage. So for my test : Middlewich big lock to Wigan Pier First attempt - bridgewater stoppage. Click Plan around Second attempt - two on Macc, Click Plan around Third attempt via trent and Huddersfield which has stoppages. Plan around Fourth attempt via L&L - success. Those last two I'm ignoring the issue at Vazon bridge as that would kill it dead I'm quite sure we could make it so it did all of that automatically (due to how canalplan generates its routes for you) and basically because I've got the MSC as an excluded waterway it would stop and say it's not possible. But as Canalplan isn't Tom-Tom we don't

We would have got those names from other data sets (possibly Edwards)

Correct - it simply says your route is impacted and do you want to plan round it and you can then choose to do so. Nothing to do with 365 network maps. Canalplan knows the start and end dates of closures and the locations. If you plan a route that goes through those locations with dates in the start to end date range it flags it up. CP tells you that your route is impacted and offers you the choice to plan around it. This is because I might be planning a route with no specific dates set and if I plan it today canalplan will point out the currently active closures. but I might not actually care.

Yes they did - luckily I already had code to check for stoppage updates on their website so I just repurposed a pile of the code to handle the closure emails. The stoppage was there but 1) It's a tree down. If we put every tree down stoppage in canalplan then planning anything would swamp people with notices that their chosen route was impossible 2) It came in on Friday morning when I was at work. There is a manual step in stoppage processing which is to check that it's actually right, which it often wasn't due to the way CRT sent stoppages - the new format is a lot better in getting things like places right. After work I went boating and didn't get back until late Sunday afternoon. Planned a route from Middlewich to Wigan Pier. At the bottom is The canal open is because that is how CRT sent it out - the CRT stoppages have a status for canal and towpath. They sent it out as open but we flagged it as a stoppage and canalplan uses that designation (and not the CRT navigation status) to determine if it needs to display a message Trust me it doesn't : Emails arrive. Background process takes the email and gets the CRT URL Background process parses the JSON data buried in the CRT webpage to get all the details and the start end locations (as co-ordinates). Background process then either inserts a new record for a new message or updates an existing one with the new details After work a poor bugger who has spent all day working on commercial databases sits down and checks each "closure" and "approves" the ones that are relevant. Tree downs are not usually put in because there are too many of them and they'd make planning a complete pain. CRT actually published the bridgewater closure so it's in there. https://canalrivertrust.org.uk/notices/01968ad7-992f-7513-9460-52ca6d9dde2f

What do CRT say on their stoppages list? Not that there is a Peartree Lane bridge on the Staffs & Worcs

In Cheltenham they sit in the trees and pull the acorns and conkers off and throw them at you. Squirrels that is, not rats...

I brain cramped - I meant either fully through the DHWT and back to the boiler or round the rads and back to the boiler.

' Or do you just pump the whole lot through the 22mm line in the calorifier on the way to the rads like you do in a Domestic set up.