Princeton

It's funny how one can do nothing for years and then suddenly turn into a total tourist. I lived for about 10 years in the Princeton area. Never felt the urge to take pictures. This weekend I happened to be visiting on a beautiful spring day and had my Olympus point-and-shoot with me. And I started snapping away for posterity...

Courtyard:

Juxtaposition of new and old:

Spring bloom of magnolias:

Well-placed trees:

Through an archway:

(Post-processed by Jim Montgomery.)

Late afternoon panorama of the garden at Prospect House (hence the light to dark transition):

Yes, it is a serene and gorgeous campus. Beautiful New Jersey.

the imprecision of measuring devices

Question: you have multiple measuring devices, which do you trust?
(Answer is none.)

Here's the story. Today was a beautiful day. 70F and sunshine.

I just ran the Charles River loop between the Museum of Science and River St bridges fully instrumented.

Full image here

This is the route recorded by my Garmin Etrex Vista Cx in my back pocket. I also had my Apple iPod Nano with the Nike+ kit.

The Nano computes speed/distance by measuring foot strike time. It overestimates my distance by about 5% usually. But I don't bother to recalibrate it because it would depend on the running surface: treadmill, grass, hard mud, gravel, tarmac, concrete all affect the foot strike time differently.

Clearly, there are some issues with the GPS data points recorded. I'm pretty sure I can't run at nearly 30 mph.

Zooming in at the Museum of Science reveals some oddities:

According to the tracklog, I've been doing some impossible zipping around. Of course, we need to delete those outlier points. Google Earth then reports:

The Nike+ kit doesn't record every footfall. It saves a reading every 2 seconds and performs lots of smoothing:

Finally, there is a well-known reference guide to this course (probably obtained by someone with a measuring wheel):

Summarizing, we have:

Source	Distance (miles)
Garmin tracklog	9.66
Google Earth	8.9
iPod Nano Nike+	8.13
My best estimate	7.6
Reference table	7.0

I didn't run the exact reference course, which is a good lower bound.

Additional mileage included running from the MIT Stata Center out to Memorial Drive. (Plus I had to double back at one point since a gate was locked.)

So I can't rely solely on the reference table.

Lesson? The GPS isn't too reliable in this urban environment. As it turns out, the lower tech device (Nike+ kit @ $30 + iPod Nano) is closer to the ground truth.

The possibility of bad track points (e.g. from interference) means that on a short run you have to inspect the GPS tracklog that's recorded. Wish there was filtering software built into the Garmin.

Springtime in New England

It really felt like Spring today in Boston. In the fifties (F) with sunny blue skies.

A quick opportunity to get a short and leisurely 28 mile loop before temperatures plummet again and the rain moves in.

Unlike out west (Arizona), New England has the advantage of having a dense network of backroads. Given local knowledge, it's possible to put together a beautiful and relatively traffic-free ride in a major metropolitan area. A friend, Pete Hausner, showed me one such route from his place in Newton.

With a Garmin etrex Vista GPS receiver in my jersey pocket, I recorded the route for posterity (here mapped on Goggle Earth):

(Click here for a larger view.)

The satellite imagery really gives a nice idea of the surrounding urban density and green areas. (Notice how we skirted around Needham.)

And despite near total unfamiliarity, I can use the recorded tracklog again. With the street level mapping capabilities of the Etrex Vista, I can now re-ride the loop and not miss a turn anytime I want:

Thanks Pete!