Canalplan Bug Tracker

Anonymous Login
2019-07-21 14:12 BST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000038Canalplan Route Planningpublic2019-06-04 14:30
ReporterNick B 
Assigned ToNick Atty 
Product VersionProduct Build 
Target VersionFixed in Version 
Summary0000038: Lock Transit Times and other known delays
DescriptionMore a request. Is it possible to amend an individual lock transit time? Some are well known to take longer than others and it would be handy to make an allowance for these in the route planning rather than adjust the average time for all locks.
TagsNo tags attached.
Attach Tags (Separate by ",")
Attached Files




Nick Atty (administrator)

I think the ability to add a delay to any place or feature would be a good idea - we could add an average of 30 minutes to Harecastle Tunnel, say, as well as a delay for big slow locks etc.

Of course it will not always be accurate, but there are certainly places where something longer would be closer to the median time than the default.

Will look into it - it feels a relatively easy addition to the data.


Nick Atty (administrator)

This turned out to be quite a bit of work, but you can now add an extra time for passing through any place, or any link between two adjacent places.


Autoclose (administrator)

Closing automatically, stayed too long in feedback state. Feel free to re-open with additional information if you think the issue is not resolved.

-Issue History
Date Modified Username Field Change
2015-10-17 21:05 Nick B New Issue
2015-10-19 08:10 Nick Atty Note Added: 0000123
2015-10-19 08:10 Nick Atty Assigned To => Nick Atty
2015-10-19 08:10 Nick Atty Reproducibility random => N/A
2015-10-19 08:10 Nick Atty Status new => assigned
2015-10-19 08:10 Nick Atty Summary Lock Transit Times => Lock Transit Times and other known delays
2019-05-05 13:47 Nick Atty Status assigned => resolved
2019-05-05 13:47 Nick Atty Resolution open => fixed
2019-05-05 13:47 Nick Atty Note Added: 0002416
2019-06-04 14:30 Autoclose Note Added: 0002525
2019-06-04 14:30 Autoclose Status resolved => closed
+Issue History