Intro
Having spent our first day wandering around Newcastle and getting the train everywhere we finally set off on the actual hike. Our plan today was to get to Corbridge where we had a bed & breakfast reserved for the night. I looked it up on Google Maps and it said that the entire journey would cover about fifteen miles, a long but not impossible stretch. Since there was basically nothing to see for this part of the journey (and certainly no stretches of wall) this didn't seem like a bad idea at the time. Do the serious walking on the days when there were few places to stop at and save the slow days for areas where there was a lot to see. There were only two problems. First, the distance calculation was based on road miles in a direct line to our destination. Google Maps doesn't include walking paths in its directions. I figured that the actual distance would be less than the road miles since the path could cut corners which roads would have to circle around. Boy was I wrong. The trail heads along the river for a while, but then it goes sharply north up through Heddon and then keeps going along a north-westerly direction whereas Corbridge is right on the river about two miles south of the wall. So our strenuous fifteen mile hike turned into a draining twenty mile slog that took up the entirety of the day. Second, I didn't factor in the terrain. Google Maps doesn't show the terrain and while Google Earth does it's very hard to get an idea from it of just how steep it really is. The hills weren't too bad (at least today) but once the trail goes off road all time calculations get thrown off. I'm used to hiking wilderness trails or along roads, not cutting across fields and climbing over fences. Progress is slow and painful, and it doesn't help when you're tired from having walked ten miles already and then up a steep hill. By the time we arrived at Corbridge at about 9 PM we were too tired to move.
Having spent our first day wandering around Newcastle and getting the train everywhere we finally set off on the actual hike. Our plan today was to get to Corbridge where we had a bed & breakfast reserved for the night. I looked it up on Google Maps and it said that the entire journey would cover about fifteen miles, a long but not impossible stretch. Since there was basically nothing to see for this part of the journey (and certainly no stretches of wall) this didn't seem like a bad idea at the time. Do the serious walking on the days when there were few places to stop at and save the slow days for areas where there was a lot to see. There were only two problems. First, the distance calculation was based on road miles in a direct line to our destination. Google Maps doesn't include walking paths in its directions. I figured that the actual distance would be less than the road miles since the path could cut corners which roads would have to circle around. Boy was I wrong. The trail heads along the river for a while, but then it goes sharply north up through Heddon and then keeps going along a north-westerly direction whereas Corbridge is right on the river about two miles south of the wall. So our strenuous fifteen mile hike turned into a draining twenty mile slog that took up the entirety of the day. Second, I didn't factor in the terrain. Google Maps doesn't show the terrain and while Google Earth does it's very hard to get an idea from it of just how steep it really is. The hills weren't too bad (at least today) but once the trail goes off road all time calculations get thrown off. I'm used to hiking wilderness trails or along roads, not cutting across fields and climbing over fences. Progress is slow and painful, and it doesn't help when you're tired from having walked ten miles already and then up a steep hill. By the time we arrived at Corbridge at about 9 PM we were too tired to move.