Here’s the thing: a few days ago I realised the tracking information wasn’t being displayed. Initially I thought it might be due to limited connectivity or bandwidth – I was in Peru, at the time – but I then realised it was probably due to the volume of points being queried and overlaid… we’ve come far enough now that this has become a problem. I haven’t checked to see whether the problem was on Garmin’s side or on Google’s – whether the issue was querying the points or processing/displaying the overlay – but the below solution worked well enough for my immediate needs.
To fix the situation, I simply went and split the queries into 6: one for each month of our journey. I might have done this automatically (and I may yet do this in a future post, we’ll see) but the basic manual implementation works well. Basically this means that instead of 2 overlays – one for the planned journey, one for the “actual” one – we now have 7 (i.e. 1 + 6).
<html>
<Read more