Going up in the world

There’s a new Strider out, with the next of my articles. I see there in the ‘Contents’ that I’m no longer listed under ‘News and Features’. I’m now under ‘Regulars’, so I must be doing something right!

Strider, Number 145, December 2019

To make the article legible, simply click on the photo. If that doesn’t work, here’s the text.

“So you’re a go-it-aloner planning your next long-distance walk. It’s to start here and end there, and, for whatever reasons, it’s to go through these particular parts of the country. That was easy, wasn’t it? Thinking of the idea always is. Now, however, you’ve got to develop that idea into a walk that you can realistically carry out given the constraints you have, for instance of time and money. That’s nowhere near as easy.

There are three questions you’ll find yourself asking again and again as you develop the idea – as you fit the possible paths together, as you set up the logistics, as you arrange the stops, and so on. The first is ‘Where do I go next?’; the second is ‘How do I best get there?’; the third is ‘What will it be like?’ The answers to the first two questions come obviously from maps and from tools such as Google Earth – I dealt with these in previous articles. The third question is different, completely, for it deals with what is commonly termed ‘ground truth’. You’re seeing some feature on a map or on Google Earth – or indeed on any type of remotely sensed image – and you’re asking yourself ‘What is that really like, on the ground?’

This question is critically important for go-it-aloners. Just think of some of the possibilities: a footbridge that’s marked on a map as passable but turns out to be gated, a river crossing that’s suicidal except at the lowest of flows, a hillside track that crosses some clearly unstable landslips, a winding country lane with high embankments and no footpaths. It’s certainly better to find out about things like these as your walk is being planned, rather than to stumble across them during the walk itself. Fortunately for the go-it-aloner there are well-established sources of ground truth. These don’t by any means provide ground truth everywhere, nor are they ever a substitute for being on the ground yourself; they are nevertheless better than nothing.

The conventional – dare I say old-fashioned? – approach to ground-truthing is to ask an expert. This can mean searching through guidebooks and walk reports for the area concerned, or it can mean contacting someone who’s actually been there. Using guidebooks and walk reports is a sensible strategy provided (a) that these are available for the area you want and are written in sufficient detail, (b) that they are up-to-date, and (c) that you can easily get hold of them. This strategy is unlikely to be successful if the walk you’re planning goes through areas that are not usually walked. The strategy of contacting someone who’s been in the area begs the questions ‘Who can that be, and how do I contact them?’ Firing off emails to people you think may be able to help may produce helpful answers; then again it may not. It’s worthwhile remembering that other people – even other go-it-aloners – have priorities too, and that these won’t necessarily include answering what seem to you to be thoroughly reasonable questions. But don’t give up! I think back fondly to the time when I was looking for a way around the broken-down bridge on Ca na Catanach. The obvious person to contact was the RSPB Ranger at Forsinard, who duly told me about the alternative. Thank you, Paul!

The more modern approach to ground-truthing involves searching on the web for geographically located photographs. There are specialist websites that help you do this, the best known probably being http://www.geograph.org.uk/. There are also geographically located photographs on mapping websites and on many walk-related blogs. What is impressive about the specialist websites – and this is what makes them the preferred source of ground truth for many go-it-aloners today – is the density of their photo coverage. Geograph, for instance, has an average inter-photo spacing of about 200 metres over the whole of Britain. It would seem, at least at first sight, that somewhere out there there must always be photos of the places you want to go and the paths you want to walk.

Of course there is a down side. Firstly, the only photos on websites such as Geograph are ones that people want to take; there tend therefore to be lots of photos of famous and/or visually attractive subjects. Secondly, there is excellent coverage on these websites only in areas that are well visited; the coverage in areas where fewer people go – and this may be exactly the sort of area that you’re planning to walk through – is often mediocre at best. Thirdly, the photos on these websites are indexed by the locations from which they were taken, not by the areas that the photos themselves show; it can therefore sometimes be remarkably difficult to get an adequate feeling for what the index location of a photo really is like. Fourthly, there is no guarantee that the given photo locations are correct, or that the given photo directions are correct, or that the photos are correctly captioned and dated. The rule when using websites such as these as ground truth for a walk has to be ‘be cautious’.

Finally, there is one special source of photographic ground truth that is invaluable in some circumstances – Street View. Street View is one of the controversial features of Google Earth, and in some countries – for instance here in Germany – its use is deemed to be a violation of personal privacy. There’s no such problem in Britain, however, which is fortunate for go-it-aloners who walk there, especially as Google appears to have sent its camera-cars down even the remotest country lanes. What do you get from Street View? Firstly – this is relevant wherever your route involves road walking – you get an idea of how pleasant or unpleasant that walking is liable to be – or how dangerous. Secondly, you get to look sideways from the roads: you get to see the adjacent countryside, to look down the paths and the entryways, to read the signs and the fingerposts. What don’t you get from Street View? Obviously you see nothing that isn’t visible from a road.”

The answer that wasn’t and the answer that is – or at least I think it is

I thought I’d solved that blog readability problem. Changing the ‘Number of posts’ control seemed to be the answer. I therefore put up a post to tell everyone about it (‘I really am very annoyed – WordPress please take note!’), logged out of the WordPress system, then went downstairs for a well-deserved cup of coffee.

But of course that wasn’t the answer. The following morning, because there was still something niggling in the back of my mind, I tried the blog again, this time without first logging in. The problem was still there. I therefore logged in and went to the ‘Settings’ page for the blog. Sitting there at the bottom was this notice: ‘Infinite Scroll Behavior. This option has moved. You can now manage it here.’ Clicking on here led me to a completely separate ‘Settings’ page, one that otherwise isn’t readily reachable. On this page there is a button to enable or disable infinite scrolling, i.e., to let you scroll down through the blog as far as you want. Infinite scrolling was already enabled, so I should have been able to start at the top and scroll continually down. I checked and I could. Great! I logged out and checked again. Lo and behold, I couldn’t. Not so great.

Clearly the problem had something to do with whether or not I was logged in. The WordPress forum was the obvious place to go to for an answer. Sure enough, someone else (http://wooskieatstvrestaurants.wordpress.com/) had reported the same problem, and only a few days earlier: https://en.forums.wordpress.com/topic/infinite-scroll-works-logged-in-but-not-as-a-visitor/. The answer, according to WordPress, was that an ad-blocker on my browser (Firefox) might be interfering with the infinite scrolling. The only difficulty with this – yes you’ve guessed – was that I don’t have any ad-blockers installed! So that couldn’t possibly be the answer. Back to the drawing board.

To cut a long story short, the answer turns out to be in the ‘Browser Privacy’ settings in Firefox. If you have them on ‘Standard’, infinite scrolling works; if you have them on ‘Custom’, as I had, it doesn’t. Of course you can always use another browser.

I think another cup of coffee is in order.

I really am very annoyed – WordPress please take note!

Every so often I refer someone new to this blog. Sometimes it’s because they’ve shown an interest in the walking I do; sometimes it’s because I think there’s a post on the blog – or posts – that would be of interest to them. In every case I hope they’ll be able, if they wish, to read what I’ve written. Seems logical, doesn’t it?

But what if they can’t?

Earlier this week I referred Brian to the blog. He’s a former colleague from Canberra, and I hoped he’d be able to shed some light on the landscape problem I described in ‘The Bourne Question’. This was posted on 13th June and referred to an earlier post from 8th May. Unsurprisingly, I wanted to read through those two posts again to make sure there wasn’t something I’d overlooked. I therefore scrolled back through the blog, starting off at the top – August, July, June, etc. No problem, until 27th May. I was blocked; I couldn’t get back any further. I tried clicking on ‘May 2019’ in the blog Archives on the right-hand side panel. This started me off earlier, at 31st May, but once again I got blocked, this time at 24th May. I’d never had this difficulty before. What on earth was going on?

It turns out that WordPress have, unbeknown to me and presumably also to most of their other users, inserted a control in their blog settings that limits the number of posts visible from any given starting point. The default value they’ve chosen is 10, meaning that anyone trying to read the blog, as I was, would see only the ten latest posts counted back from wherever the start point was. I’ve now reset this value to 150, which is the maximum WordPress will allow. This should make all of the blog readable again, because there are never even close to 150 posts in a month.

Needless to say, I won’t be sending WordPress a Christmas card this year. I can see why they would want to limit the number of visible posts in this way: it reduces their server load. But if you’re going to change your product substantially – and making most of a blog unreadable certainly is a substantial change – then you have an obligation to notify your users.

No argument.