Not adding missing Slow Way but removing Slow Ways instead
There are some problems with Slow Ways settlements and thus routes in the Haverfordwest area in Pembrokeshire. There is a multibranched and extensive estuary with only one crossing which means lots of routes overlapping, and many from A to C actually passing through or just tens of metres from the meeting point of Settlement B. Having so many ABC routes seems unneccesarily confusing and makes planning a walk which joins several routes togethr much more difficult than it needs to be. The current website configuration doesn't make this duplication obvious and indeed it's not easy to discover which of the overlapping lines correspond to which Slow Way.
An example: The map view looks like there are two PembNar routes and two PemPem routes, but when you click on the common factor, Pembroke, that definitely isn't the case. It takes a bit more digging to figure out that what you were seeing was actually one each of PemNar, PemPem and PembNar, with an extra layer of confusion that sometimes Pembroke Dock is Pem and Pembroke is Pemb, but occasionally it is the other way.
There is quite a lot more of this going on with neighbouring SlowWays too. It'd be a shame to leave it because Pembrokeshire is very attractive to walkers and also has a lot of very meandering and circuitious stretches of the Wales Coastal Path. The confusion could put them off using Slow Ways to supplement that.
I could propose a number of SlowWays that should be removed altogether. And as for those actual routes, either discard them or split them from AC into AB Two and BC Two. Also Pembroke Dock could then be removed too as only one route going north and one south makes it a point on a line instead of a useful node.
If these changes are acceptable in principle could they happen before any reviews or surveys are done? If yes then I could I figure out quite what is needed and what is not. Making gpx files for the AB and BC split routes gpx files would be pretty easy too if it would help.
Please sign in to leave a comment.
Comments
0 comments