• Clean Bill of Health

    I got my colonoscopy today, a rite of passage I’d delayed for years. Fast and purge yesterday, then into the hospital for about two hours. I was pretty nervous, but the whole procedure was painless, even the “purge” part yesterday wasn’t as bad as people joke (though I wasn’t happy about the “fasting” part), and now I’m good for another 10 years.

    I just pounded down a turkey & cheese sub, and I think I’ll go take a nap.


  • Book Report

    Jonathan Strange and Mr. Norrell by Susanna Clarke

    I saw an extremely positive review in Vox of Susanna Clarke’s new novel (Piranesi) which made me want to read it, but I though I’d check out her original novel — for free, from the library — first.

    Jonathan Strange and Mr. Norrell is a honker of a book, weighing in at 782 pages, and tells the tale, set in an alternate-history version of early 1800’s England, of the two men who revived the practice of English magic. It’s written, perhaps somewhat ironically, in the style of the novels from that era — think Jane Austen or the Brontë sisters — which was fun and clever for the first half of the book, but that whole stilted “British landed gentry politeness” thing wears me down after a while (I sometimes joke that the one improvement Pride and Prejudice really needed was a guillotine), and it makes the story, which actually has a very active plot, seem like nothing ever happens.

    So the book rolled along just fine until the midpoint and then became a chore, but then it became interesting and readable again in the last hundred pages or so. I suspect that this is a result of my COVID anxiety: several longish books I read recently had the same effect on me — I liked them at first, they became tiresome as my attention span struggled, and then I enjoyed them again by the end. Like those other books, I am actually glad I read this one to the end.

    Since Piranesi is only about 200 pages, I’ll be adding it to my list.


  • Another Way To Look At It

    In my database of towpath-accessible amenities, my original definition of “accessible” was simply “within a half mile, by paths available to a cyclist, of an access point.” This seemed pretty reasonable — people don’t really want to travel more than a few hundred yards off the trail to get a bite or whatever, and beyond that point an amenity isn’t really part of the trail ecosystem anymore. This break-off point is more or less arbitrary, so I chose a half mile as a nice, round and fairly inclusive distance.

    As an example of what this might look like, here is a view of the Sand Island trailhead, with accessible amenities selected using this simple definition:

    map of bethlehem
    Amenities within a half mile of Sand Island

    You can see that there is not much available immediately near the trailhead, and then further north there’s a hotel (blue square) and a bunch of food/drink amenities (yellow circles) on Main Street’s “restaurant row.”

    I saw two issues with this. One is that people will probably be willing to go a bit further from the trail to get to lodging or a bike store, but these places are not shown, and the other issue is that the arbitrary break-off point comes in the middle of a dense clump of amenities — this is the case with “restaurant row” — and it seems silly to include one restaurant just under the half-mile cutoff while excluding the four next door, just beyond it.

    So (to address the second issue) I expanded my definition to include clusters: if there is a dense group of amenities, and at least one of the amenities in the group is within a half mile of the trailhead, all of them in the group are considered accessible.

    I also included any lodging or bike store within a full mile of the trailhead (to deal with the first issue), and now the map looks like this:

    map of bethlehem
    Amenities with a more expansive (ie “clustered”) definition of accessible.

    The map now includes the rest of the tourist/nightlife area near Broad and Main Streets, as well as several more hotels and two bike stores (the orange diamonds). This is the version of “accessible” my amenities map uses.

    But should I be even more expansive in my definition? What if someone wants to find a restaurant near their hotel, or near a bike shop, and the hotel or bike shop is one of the outliers, nowhere near the other “accessible amenities” even if there might be places nearby? (This actually happens in Bethlehem, where there is a separate business district on the south side of the river.) I decided to explore this possibility.

    My first approach to a more expansive definition of accessibility was to expand my definition of an accessible cluster: if a group of amenities contains anything considered accessible, like an amenity within a half mile of the trailhead, or a hotel or bike shop within a mile of the trailhead, then all amenities in the group are accessible. The new amenities can be seen in this map:

    map of bethlehem
    Sand Island amenities, including clusters near hotels and bike shops

    This was easy to implement, it just meant a tweak or two to the function I used for the original cluster definition. Now the Southside downtown is pretty well represented. By the way, here is the same map, but with clusters (accessible and inaccessible) shown:

    map of bethlehem
    Amenities near Sand Island, with cluster regions shown.

    The colored polygons in this map are the regions where clusters of amenities can be found. (Note the yellow polygon in the northeast corner. That represents a cluster where no amenity met any of my criteria, and no amenities are shown.)

    I worked out this definition of accessibility about the same time as the original clustered version, but didn’t use this definition for my map because it seemed a bit too expansive, with these second-order amenities — accessible not to the trailhead per se, but to other places that someone may want to visit — making the whole map too busy without adding much more value. After all, if someone wants dinner recommendations near their hotel, they can always ask at the front desk…

    But lately I’ve been thinking about a different approach to expanding my definition: what about the routes from the trailhead to the hotel (or bike shop), would it be useful to show the amenities along the way? Here is a map, just of the amenities that are within 50 yards of the shortest path to the accessible hotels and bike shops:

    map of bethlehem
    Amenities along the routes to hotels and bike shops.

    This seems to strike a happy medium, inclusive but not too inclusive. Here are those amenities along the hotel/bike shop routes, with the more expansive version of the clustered amenities superimposed:

    map of bethlehem
    Amenities near Sand Island, including those in clusters near, or along routes to, lodging and bike shops

    I kind of like this approach, though I wonder if it’s more a CYA reflex: I don’t want hungry people to pass restaurants on the way to the bike shop, and not see them on my map. After all, this is still a second-order set of amenities, and even if it’s not quite as busy as my first attempt at a more expansive definition, there is a lot of overlap. I’ll be thinking about this a bit more…


  • A Ride Up The Trail

    We did our semi-official, annual Fall Bike Camping Trip last weekend: up to Jim Thorpe via the D&L on Friday, exploring the Lehigh Gorge on Saturday, and home on Sunday. We had a pretty big crowd, and had three campsites reserved at Mauch Chunk Lake, and since some of us drove to Jim Thorpe we were able to have much of our camping gear carted up rather than bikepacking all of it — sweet! Except for some early morning sprinkles on Friday, we enjoyed perfect fall weather the whole trip. Here is our story in words, pictures and maps.

    Day One


    We started from Sand Island a little after 9:00 AM: Anne & me, Ed, Scott & Kellyn, and Julie, and picked up Rick and Shari at the prearranged location just north of Allentown. The day started with showers, but (as the weatherman had predicted) the rain stopped just as we got going, and the sky was clear by noon. We moved at a leisurely pace, with many stops along the way including a lunch break in Slatington. We got into town around 3:00, and were at the campsite by about 4:30. (We also bumped into Anne’s Aunt Kay at the supermarket, which was a pleasant surprise.)

    Day Two


    We didn’t exactly get up early on Saturday, but we managed to eat breakfast and hit the road by about 9:00. We met Rick & Shari in town — they’d stayed at the hotel — and picked up the day-tripper contingent of our crew at the Glen Onoko trailhead. After that it was north up into the Gorge.

    The day was really beautiful, though the leaves were only just starting to change. It was another perfect day, and we had plenty of company on the trail. We had a snack break (which turned into lunch) at Penn Haven Junction, then another feed stop at the Rockport trailhead. Most turned around there, but a few of us went just a little further, to check out Buttermilk Falls, another half mile or so up the trail.

    Day Three

    I didn’t take any pictures on Sunday, and since I forgot to stop the GPS before the ride’s end I managed to record some location data I don’t feel like sharing, so this section is a little sparse…

    We managed to have another great day on the trail, though it started a bit overcast compared to Saturday. We were a bit tired though, and maybe a bit sore in the nether regions, and our pace was definitely set at “mosey.” Still, before we knew it we were back in Slatington where I got the scrapple & egg sandwich — I got chili dogs from the same food truck on Friday, only to spot the breakfast sandwich menu immediately afterward, and I vowed to return someday…

    We had another nice surprise: I saw Chain Gangster Greg M at Slatington; he was doing a gravel bike ride and we all spotted the old team jersey he was wearing: bright yellow and still in good shape though it must be about 30 years old… I caught his attention and we had a nice chat before he continued on his way.

    Another few hours and we were home.


  • Infrastructure Fun

    I got in a few rides these past few weeks, and some good cello time too, but my major focus has been on “infrastructure” projects:

    Bike

    The Santa Cruz, after four years of that “new bike feeling,” is starting to show some signs of age. Nothing bad, just things like shifting problems in the highest gears, so I might need new cables and maybe housing, and some trouble with the tire valves: I’ve got a slow leak in the rear tire caused by a torn o-ring, and a gummed up valve up front.

    For the tires I got a “valve repair kit” from Saucon Valley Bikes. The tubeless tire valves are pretty easy to take apart and work with, so I was able to replace the rear o-ring — I can’t be sure if it worked perfectly, but it’s working enough for now — and have new valve innards on deck if the front tire becomes too annoying. The shifting seems sort of OK for the moment after I did some serious derailleur cleaning, but I can tell I’ll have to deal with those cables sooner rather than later.

    Meantime, I noticed a slight creak coming from the bottom bracket…

    SSL

    For my website I’ve been using an SSL/TLS certificate from Let’s Encrypt, which I obtained using SSLForFree, since Let’s Encrypt is pretty difficult on its own. These certificates need to be renewed every 90 days, but when I went to do it the next-to-last time, I found that SSLForFree had been bought out by ZeroSSL, who use their own certificates and who intend to charge for anything beyond a limited number of free ones. I used them that time, but spent the next three months looking into a better option.

    The ZeroSSL certificate expired a few days ago, but I had already replaced it with one from Let’s Encrypt, using a rather laborious process on yet another website. It’s very doable, but I think I’ll continue looking for a better method.

    Towpath Amenities

    This is a bit of old news, but I’ve added the amenities and access points along the towpath between New Hope and Morrisville. I have about 10 miles left to add, the section from Morrisville to Bristol, and I have all access points and amenities I could find added to my database. All that’s left is to ground-truth some of the info, then I can update the map. This last addition will make the map complete, but that won’t make the job done — this job will never be done

    I started thinking about my method of routing the other day: the routine finds the point on the road network closest to my access point (the start) and the point on the network closest to my amenity (the endpoint), then finds the shortest path through the network between start and end points. But what if the start and end points on the network are not particularly close to their respective access or amenity points?

    I originally assumed that this would not be an issue: access points were basically intersections of the D&L with the road network, and almost all amenities should be very near some road or path that customers use to get there. Then I figured out a way to check…

    Most amenities were within about 25 yards of their route’s endpoint, the distance being mostly open space like a parking lot or driveway. I figured that this was acceptable, but I also found a few amenities that were more than that distance, between say 25 and 50 yards from their endpoints. Again they were on the far sides of parking lots and such from the ends of their routes, but these distances seemed a bit too large to leave be, so I added service lanes and driveways as necessary — I’m not sure why these weren’t already a part of the network, but they are there now; I updated the routes to the offending amenities and all was well.

    There was a third group of amenities that I found, and these were the ones I had been worrying about: the ones where the database has a route, but in real life the route’s endpoint is nowhere near the amenity, and maybe the amenity isn’t even accessible from the endpoint. (One example could be a store along a roadway I’d deliberately excluded from the route network, such as a fast food place along a highway. The routing program would find a path to the closest point still on the allowed roads, and leave the cyclist to connect the endpoint and the amenity “as the crow flies,” crossing freeways or God-know-what, and I’m back to square one.)

    Luckily, I only found a few of these, and they all were total outliers: places that were in the database, but were too distant and isolated to be considered “accessible.” For now I’m leaving them in the database, but I guess I’ll eventually have to remove them. I’ll have to look more carefully at the relationship between new amenities and the road network in the future if I add any more, to make sure they actually connect.

    Network (the other kind)

    One last piece of infrastructure activity: we are switching our internet provider, from DSL on Verizon to RCN cable. I bought a cable modem and a wifi router, and called RCN the other day; the cable installers should be here this afternoon.

    I got us the slowest package, 10 Mbps, which is about four times faster than what we have now and costs about $20/mo less, before even considering the cost of the landline we’ll be abandoning when we get rid of Verizon. (If we need it we can upgrade our package, but we’ve been making do with DSL for so long that 10 Mbps will probably seem blazing fast.)


  • I Ply The Fire With Kindling Now, And Pull The Blanket Up To My Chin

    Weatherman says it’ll heat up again in a few days, but it’s been trending much cooler this past week — comfortable days, nights in the low 50’s. Good sleeping weather, as the saying goes.

    We went to a friend’s house for a porch visit yesterday evening, and I was actually chilly once the sun went down, and when we got home we closed some windows and put the comforter back on the bed. The temperature dropped into the 40’s overnight. Summer is coming to an end.


  • She Don’t Come Around Here Anymore

    There was a huge spider living under the eaves of our back door. I mean really huge, easily the biggest spider I’ve ever seen in the wild around here, maybe a quarter the size of a tarantula, with a big bulbous body (pregnant with eggs?), and legs that probably stretched almost an inch across. It would build a web every night from our rear door over to the clothes line, and every morning — until I figured things out — I’d go outside and walk into the web. The spider would then make a run for it, on semi-permanent strands a little higher up, back to its hidey-hole under the gutter, and from there it would stretch its arms out and make “I am scary spider!” gestures until I went back inside.

    The spider had a pattern: it would hide out in its spot during the daytime, then come out and rebuild its web once darkness fell. The web building process was quite fun to watch, and the spider was a very successful hunter, which is maybe why it liked that spot.

    A few days ago I noticed it had moved its daytime hiding spot to the inside of the screen door frame, then it seemed to disappear — no more spider, no more webs. Just yesterday I went looking, found its crushed body on the door, and felt bad for the rest of the day.


  • This Side Of The Mountain

    Well, we did it — Anne and I rode the century ride we’ve been working towards. We started with our friend Julie and her brother Peter, who were riding to their family cabin in NY just past the Poconos, but for COVID and logistical reasons we only went about halfway — we left them at Delaware Water Gap and continued from there on our own route, returning along Cherry Valley Road (one of our recent favorites) and picking up Mountain Road, an old favorite, just north of Wind Gap. This was a beautiful section, but it meant that we had to go over Blue Mountain at Little Gap. Luckily, the ice cream place was open at the bottom of the downhill side…

    We got home with about 98 miles and had to circle around the neighborhood a few times, but we finished with 100.1 miles. It seems funny, I used to do century rides on a fairly regular basis back in the day, but Garmin Connect tells me that this was my longest recorded ride. I’ve been using Garmin Connect since 2009, so that means that this was my first century in more than a decade.

    Reading

    I just finished David Mitchell’s latest, Utopia Avenue. I really liked it, which was good because I’d been thinking lately that I no longer had the patience or attention span to read a book under the current stressful circumstances. (I finally finished The Mirror and the Light, and was sorry to leave it behind, but in the moment the process seemed such a chore.)

    The story follows a British 60’s-era band, blues/folk/psychedelic amalgamation Utopia Avenue through its formative days, with plenty of references to the London music scene and cameos from all sorts of British musicians, but there were also connections to some of Mitchell’s other books like Ghostwritten, Cloud Atlas, and the books in the Bone Clocks universe. Apart from a few (relatively drama-free) supernatural passages, and a jarring ending, it just passed by in a smooth and pleasant flow, like a sort of “Forrest Gump of British Rock.”

    I just picked up where I left off in The Thousand Autumns of Jacob de Zoet, since it apparently is a bit of a prequel to Utopia Avenue.

    Happy Labor Day!