• On Second Thought

    Well, that didn’t take long…

    A few days of actually using the Input app, and I’m ready to throw it away and go back to QField, despite QField’s clunky data transfer method. The need to put my collected data into a PostGIS database (without too many hoops to jump through) is more important than I realized, and Input’s data entry UI had a few quirks that just became more unpleasant every time I used it — there was something just plain off about its text boxes and typing…

    It’s a shame too, because the Mergin update process was exactly what I wanted. (Input can also handle QR codes as data sources, something I have absolutely no use for — but hey, nerdgasm alert.) Well, QField is eventually supposed to get its own cloud service, maybe they’ll be able to upgrade their data transfer process once they have that in place. My luck, they’ll reproduce Mergin’s setup, and reproduce Mergin’s PostGIS problems along with it.


  • Data Collection II: Input

    Just picking up where I left off here

    I installed and started working with the other field geo-data collection app, called Input. It has a few drawbacks (so far) compared to QField, but it’s just as easy to use on the phone, and much easier to set up and transfer data back to the home computer.

    Input is basically a phone app front end for Mergin, a cloud-based data storage service built to integrate with QGIS. Mergin stores the data that then can be synch’ed with QGIS on the desktop, or with the app. Data collection does not need to be sent to the cloud in real time if you have no data connection, but can be done later, and is “just push the button” easy, as is synching between the cloud and QGIS. (This is the biggest advantage over QField, which has a pretty clunky update workflow.)

    The biggest problem I found so far has been that the data is not easily uploaded into a PostGIS table; the project relies on GeoPackages for data storage, even on the QGIS end. (Strictly speaking, there is a way to use PostGIS, but it seems involved, and needs to use another program that I have not yet tried.)

    There is also the issue of cloud storage: a free account is limited to 100 MB, and while the actual “location and description” data is usually pretty small, all the accompanying photos, at 5-10 MB each, will quickly bump up against that limit. If I could offload the data and photos, from the cloud-based project into something else (like my computer, and PostGIS), this limit wouldn’t be so pressing, but the workflow is starting to look unwieldy again…

    (Speaking of unwieldy, there is no direct way to store basemap tiles for offline use. Again, there is a way, but it’s not straightforward, and storing the tiles will also consume a significant portion of that 100MB limit.)

    None of these problems are deal-breakers (so far), and the single advantage of easy synchronization more than makes up for the lot of them. I’ll be playing with Input/Mergin some more, but I think it’s the one I’ll decide to keep.


  • Golem Unchained

    I’ve been using my handy, text-based “to-do” list for a while now, but my use of it was inconsistent, waxing and waning as it occurred (or didn’t occur) to me to use it, and I also didn’t like keeping a text editor open all the time whenever I did use it. So, the other day I added a “desklet” to my desktop, one that displays (the first lines of) a text file. I set it to display my to-do list, which I now can see any time, and open for editing with a click.

    Which is all well and good, but now I find that my to-do list is staring me in the face all the time, and I’ve been using it more, and more, and more… I guess I’m more productive now, as I write down all the things I need to do, then do them and mark them completed, but it seems that the tool I added to make my life easier is starting to get the upper hand, running my life instead of the other way around.

    I have to say that things get done, though.


  • Anabasis 2021

    So this weekend was our annual bike camping trip up the D&L to Jim Thorpe. A total of seven of us rode up, and our friend Predo, who was on “injured reserve,” drove to the campsite with our extra gear. It took us about six hours, with plenty of photo ops and snack breaks, and a few snafu’s…


    We (Bill M, Jared, Sara, Anna Z, Ed, and Anne and I) started at CAT, and took the roads until we got to Northampton, where we crossed the Lehigh and picked up the trail. Lunch was the “Diggity Dogs” food truck at the Slatington Trailhead, and then it was another fifteen miles to downtown Jim Thorpe. A trip to the supermarket, then the long climb from the river to our campsite, and we were done for the day. Predo met us at the campground, and Rick & Shari arrived not long after.

    Saturday we rode into town — which was a madhouse, the Fall Festival was in full swing — met Shari and Rick (they are NOT into camping) and continued north along the trail, picking up Matt & Diet at the Glen Onoko trailhead. We were now eleven strong…


    The trail was fairly quiet at the start, but it was a beautiful fall day if a bit drizzly, and things became pretty crowded after a while. We got to Rockport, which was another madhouse, with bicycle outfitters dropping off cyclists by the busload, and that’s where we ate lunch and did some very entertaining people-watching… Our goal and turn-around was Buttermilk Falls, just a half mile past lunch and always a good photo-op.

    On the way back we met up with Ben and Candace, which brought our group up to our full strength — 13 riders! One more photo session at the usual spot, and our excursion began winding down; we said goodbye to Matt & Diet at Glen Onoko, and rode back up to camp. Dinner was basically a pizza party, and we had one final addition: Gary L who was joining us for the Sunday return ride.

    Sunday was the return. Ben and Candace took off for Philly, and Rick and Shari had gone home the night before, so we were now down to eight. The ride was pretty uneventful, but we did switch things up by taking the Nor-Bath Trail from Northampton over to Bicentennial Park, before finishing on the road.


    …AND I finally got a photo of that spooky “house on the hill” at Lehigh Gap.

    And that was our trip up-country!


  • Background Obsession

    There have not been too many morning weigh-ins posted here lately, but that does not mean my obsession has abated. Far from it — I actually started keeping a log of my daily weights as a spreadsheet, and set up an R script to analyze and graph the results. Behold my weight loss since late June:

    The blue dots are my weight measurements, the black dotted line represents a “linear best fit,” and the red curve represents a smoothed, “LOESS best fit.” My target weight is 167 pounds, which is the weight I need for a BMI of 25, the highest “normal” BMI — I get to 167# and I am no longer overweight.

    I used the linear regression to figure when I’ll reach my target — it’s not shown here, but the black line is set to cross that green line on October 19th. The red curve is kind of showing me hitting a wall near 170# though, so we’ll see…

    Anyway, today was the group ride with Sights for Hope. Anne arranged for a bunch of tandem bicycles, and sighted captains to pilot them, to give sight-impaired people a chance to go for a bike ride. Scott S, Brian S and Ben (who came up from Philly with his sight-impaired friend William) were the captains, and one couple came with their own tandem, so there were four tandems in all. (Ann, Sara A and I rode our regular bikes in support.) We went around the loop of the Ironton Rail-Trail, about 5 miles or so, then had a lunch break before calling it a day. A very pleasant ride, and a very interesting group of people.


  • Data Collection

    Part of what I do, as a member of the D&L trail patrol, is document issues along the trail — down trees, washouts — that may need to be addressed by the land managers. There is a specific report form for this kind of thing, where we enter a description, location (GPS coordinates) and maybe one or two photographs; you can fill out the form on the trail if you have a data connection — a big “if” on the trail sometimes, so I usually do it at home on the laptop, where all things computer are easier anyway.

    My typical workflow: I stop and take a picture, and later at home I use the photo’s EXIF data to get the location. This can be a bit of a pain, so I was thinking that maybe there is some app where I could create an entry, with location data, photos and maybe a timestamp, all added on the spot without need for data connectivity; I can then call the note up and refer to it later at home. (I have a “notes” app, where I can add photos, and paste my location, from say Google Maps or whatever, into a note, but I want the whole thing to be more integrated than that, with less human intervention.)

    There actually are some “geo-notes” apps, but I started overthinking things as usual, my wish list expanded, and then I discovered that here are two apps that actually integrate with QGIS: QField and Input.

    I am currently working with QField. You build a data-collection project in QGIS, then you run the “Qfield synch” plugin to export the project into a format that the app can use. Move the exported files to your phone, do your data collecting, move the updated files back to your computer, and import the updated version back into the original project. This process (export, move files, get data, move files back, import) is tiresome, especially since every data collection effort requires you to go through that entire process — I would much prefer something like “build project, export to phone, then: get data, upload data, get data, upload data…”

    Actually using the app, however, is easy. I set it up to record a timestamp with every point collected, then add a description and optional photos, and it works flawlessly; the only limitation I found so far is from the phone’s GPS, which is sometimes inaccurate. Once the data is back on my laptop, I can massage it (mostly automatically) into the form I need for the trail report.

    Next up is Input. This looks like the more promising app (based on their website), but the grass is always greener on the other trail…


  • Garbage Town

    I did a ride and two walks yesterday. The ride really boosted my civic pride, but the walks, especially the second one, left me feeling deflated and outraged.

    The ride was in the morning, and was a collaboration between CAT and the Bethlehem Historical Society. We rode around town, visiting various historic places (the original Moravian residence halls, the Colonial Industrial Quarters, Sand Island, Burnside Plantation) while our guide Keith told us about what we saw at these places. Some of it I already knew, but plenty was new to me and all of it was interesting. All in all it was a pretty good way to spend an autumn morning.

    In the afternoon I decided to go get my flu shot, so I walked over to CVS on 8th Avenue. It’s just under a mile through our neighborhood, and a very pleasant walk, up until I had to leave the neighborhood and walk a short section of 8th Ave that’s basically a highway. What an unpleasant, noisy, and dirty mess! I almost got hit too, when I had to cross the road (at the walk sign) and someone making a left almost ran me down — his green light coincided with my walk signal, a classic WTF design, and I don’t think he saw me, or even looked, until he was practically on top of me.

    The second walk was with Anne, a longer version of our evening stroll: we went up Broad and down Main, then crossed the Fahy Bridge, walked through Southside on 3rd and returned to the Avenues via the Hill-to-Hill Bridge. There was a rotting garbage smell in all sorts of odd places, possibly from the most recent “WhateverFest” last week, and overflowing garbage cans (and public drunks) along Main Street from whatever the current circus is; we managed to see — and hear, from really far away — parties or concerts at several public and private venues. On the Hill-to-Hill Bridge we negotiated a gauntlet of broken auto glass, garbage and dog poop while dealing with the obnoxiously noisy traffic just yards away. (Meanwhile, the big bright animated billboard had an ad shining down on us, touting the Lehigh valley as a great place for happy farmers and cyclists.)

    It was all a bit much.

    Anyway, the quartet is getting together this afternoon, for the first time in maybe a year.


  • This Old Video

    Here’s the video I did of our memorial ride for Brian. I made this about eleven years ago and put it on Facebook, where it sort of languished ever since — FB “memories” just brought up some of that trip’s photos, and so I went rummaging for it. I just added it to my Youtube channel, where it will have a home — maybe a more accessible/discoverable one — with my other videos, if I ever actually make any.

    So anyway, there it is. I can’t say “enjoy;” it was a pretty somber moment but I sometimes like to look back at that day. I would love to know what happened to some of Brian’s own ride and vacation videos, he was a master at that sort of thing, and his videos were almost as much fun as the trips themselves.


  • Working Man’s Blues

    “Plans are worthless, but planning is everything.”

    Dwight D. Eisenhower

    I did another stint as a bicycle guide over this past week — this time, and rather unexpectedly, as the “ride leader”. I think I did well enough and liked it for the most part, and I think the riders got a pretty good experience out of it, but I also think I’ll not be doing that again anytime soon. Lesson learned: I like riding, and riding with other people, but I am not as comfortable schmoozing as I thought I’d be, and I absolutely hated feeling responsible for people and situations over which I didn’t have much control.

    What I did enjoy, strangely enough, is what I always enjoy: planning bike rides using map and database software. I started this particular ride-mapping project a few years ago. Rides, routes and alternate routes; points of interest and local trivia along the ride; ride logistics like bathroom locations and transportation times between the base and the start/finish — I stuffed it all into a database and managed the whole thing with QGIS. That was all well and good, but then it sat moribund over the COVID hiatus.

    As this new ride season approached I cleaned up and updated my project. Maybe this was really just the “fantasy football” or cosplay of the bike-guide biz, but it did come in handy after some local trails got wrecked by recent storms: I had backup rides already on deck, and enough information in my head to make plenty of other sudden changes “on the fly.”

    It seems a shame that I no longer have a use for my toy. We’ll see, maybe it can be the basis for some other project.


  • Ida, High And Mighty

    We went down to Sand Island, to look at the flooding we got after Wednesday’s heavy rain. This was the aftermath of Hurricane Ida, and though we got a lot of rain, maybe five inches or so, it was an all day affair — I’ve seen more shocking results from a heavy thunderstorm, at least in our neighborhood. The sheer volume though, of the rain that fell everywhere around here, made the situation with the rivers a very different story….

    The Lehigh, when we saw it at Sand Island, was running high; it was almost over its banks, and was running vigorously, almost angrily, and fast. The canal had overflowed onto the island and was pouring down into the river, but if the river were another foot or two higher that flow would have reversed. There was everywhere a sense of overwhelming power, unleashed and rushing past.

    (The Monocacy Creek was also flooding, but I’ve seen it worse — it goes up fast and comes down fast.)

    The last two photos are at the confluence of the Lehigh with the Delaware in Easton. Normally there is a 10 foot high waterfall at this spot, where the Lehigh goes over a dam, but yesterday it was invisible, except for a scary line of whirlpools that kept forming and disappearing.