Canalplan Bug Tracker

Anonymous Login
2019-07-21 13:49 BST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000260Canalplan [All Projects] Data Maintenancepublic2019-05-18 22:30
Assigned ToNick Atty 
PrioritynormalSeverityminorReproducibilityhave not tried
Product VersionProduct Build 
Target VersionFixed in Version 
Summary0000260: Canal Plan CSV Output of Postcode for The Plough at Huddlesford is wrong
DescriptionCanal Plan CSV Output of Postcode for The Plough at Huddlesford is '60410'. I beleive it should be 'WS13 8PY'.
TagsNo tags attached.
Attach Tags (Separate by ",")
Attached Files




Stephen Atty (administrator)

It's wrong on the page too:

Latitude: 52N41'3"
Longitude: 1W46'37"
Postal code:60410
OS Grid:SK151096
Sunrise:6:16 AM
Sunset:6:15 PM
Date:17 March 2017


Shultzy (updater)

If you delete the post code in [Edit and Change] and refresh it automatically creates the correct code.


Stephen Atty (administrator)

Nick can probably force a rebuild of ones that are wrong...


Nick Atty (administrator)

The postcode is a text string in the database, so it will be the same on the gazetteer or the CSV output or anywhere else it appears. It's got by a lookup of a remote site, and very occasionally - for reasons I don't understand - it comes out wrong.

The best approach is - as Shultzy suggests - to visit the place in the gazetteer and delete the post code. It will do another lookup and hopefully get it right this time.


Beerbadger (reporter)

I looked at the entry again today and the Postcode has been updated to 'WS13 8PX', presumably because it has looked it up again. However, according to the Contact Us on its website it is 'WS13 8PY'. I couldn't find a way to edit it despite being logged in.


Shultzy (updater)

[Edit and Change] will allow you to change the postcode. Be aware that the postcode is calculated by long/lat so as the marker is in the canal it may be calculated as different than it actually is.


Nick Atty (administrator)

As with the other postcode/CSV bug, other changes have swept this away.


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
2017-03-17 15:57 Beerbadger New Issue
2017-03-17 17:16 user3 Assigned To => Nick Atty
2017-03-17 17:16 user3 Status new => assigned
2017-03-17 17:17 user3 Note Added: 0001026
2017-03-17 17:36 Shultzy Note Added: 0001027
2017-03-17 18:13 user3 Note Added: 0001028
2017-03-18 07:09 Nick Atty Note Added: 0001029
2017-03-18 11:27 Beerbadger Note Added: 0001031
2017-03-18 17:58 Shultzy Note Added: 0001033
2019-04-18 21:56 Nick Atty Status assigned => resolved
2019-04-18 21:56 Nick Atty Resolution open => fixed
2019-04-18 21:56 Nick Atty Note Added: 0002357
2019-05-18 22:30 Autoclose Note Added: 0002459
2019-05-18 22:30 Autoclose Status resolved => closed
+Issue History