home again.

i'm back in boston. man, logan is just a clusterfuck every time i have to fly thru there. i think the past several times has been due to particularly bad timing on my part (once was the end of NH feb school vacation and the start of MA feb school vacation, and this past tuesday was the day after the marathon and i'm guessing that at least 20% of the morning travellers were somehow marathon-related). apparently, the baggage claim belts weren't working, because about 4 big flights were all clustered around one baggage claim area while the rest were idle. it was impossible to get close enough to snag my bag and then after waiting for it to come around again, we discovered that they were pulling bags off quickly to make room for more baggage. harrumf.

if there were a nonstop flight between providence and seattle or manchester and seattle, tho, i'd be a happy traveller.

the trip itself was great. i didn't get in as much socializing with ex-coworkers as i wanted, and i didn't quite get around to doing all the house-related stuff i wanted to do. but the happy couple got married, and that's the important part, i guess.

claudia and i did some geocaching in the couple of days before the wedding, but kept being thwarted. but three caches on our way to the airport on sunday morning (including a second attempt at one cache) got us to 4 finds out of 6 attempted caches. i particularly liked the cleverness of "urban cache: overdue"

another note about geocaching

i've got an older gps - it doesn't have a basemap, and it only gives distances down to 0.01 of a mile. which seems fairly precise until you're looking for something the size of a brick. so i picked up a simple compass and it's been fabulous. because even when the distance reads 0.00, it still gives me a bearing, and with the compass to accurately figure out where the bearing is pointing, i can get really impressively accurate. and it fits into my gps carrying case.