New On This Ride
Increased longest ride: 41 miles, up from previous high of 35.
Metric units (so that’s 66 km, up from previous high of 56 km). It seems like cycling worldwide uses metric, and the world will come over to metric eventually, and 32 kph feels faster than than 20 mph.
This route is best ridden on weekends or super-early mornings. I felt like kilometers 18 - 25 and 50 - 56 would be uncomfortable with more traffic. Today, Sunday morning, I encountered nothing but courteous drivers.
Coffin Point doesn’t have much to see. There’s a government issue parking lot. Wrap around to the right and look for a break in the bushes to access the waterline. I didn't see access to the bridge landing pilings. It’s signed as though lots of commercial trucks come through there to Sparrows Point.
Fort Howard Park is closed for halloween festivities, reopening November 15th.
Cuckold Point doesn’t have much to see either. The end of the road is under construction, so there’s not a vantage point.
One portion of the route felt unsafe on the road, see below.
Power Saving Tests
I’m using an iPhone 7 as a cycling computer, navigation device, and emergency communication device, and camera. On this ride I tested a few strategies to increase battery capacity and reduce power consumption.
Bring More Power - Connected the iPhone 7 to the Apple Smart Battery Case. The phone draws power from the case first, then uses its internal battery. Power levels for both are displayed
Screen Off - Run without screen until km 9, then max brightness the rest of the way.
Airplane Mode - Enabled from km 40 to 48, when it became clear there would be plenty of power for the remainder of the ride. Disabled the remainder of the ride.
Power used during the ride was 57% of the case. So, remaining battery was 100% of the phone + 43% of the case. Plenty. Low battery level at the end of the previous ride may have been due to cold rather than excessive power draw.
Logging: RwGPS vs BikeGPX
I’ve been using BikeGPX for navigation and RwGPS for logging. BikeGPX can also do logging. Is it necessary to run both?
It looks like there are differences in the log files they generate. RwGPS is closer to the path I actually took, and smoother. I would guess they’re using different filter strategies to move from raw GPS data to a path the follows roads.
The power consumption numbers are less clear. iOS shows BikeGPX as consuming 40% while RwGPS only used 6%. However, BikeGPX was shown on the screen while RwGPS was in the background (except to grab the airplane mode screenshot above).
I’m suspect this is evidence that the screen uses more power than the location tracking features, rather evidence than that one app uses more data than the other. Maybe next time I ride a known route RwGPS can be shown on the screen with BikeGPX in the background and we’ll see if these figures are reversed.
For now, I think I’ll continue with the current strategy of using both apps.
How do BikeGPX and RwGPS behave without data?
For this test, I put the phone into airplane mode, and then rode a new part of the route (Cuckold Point, km 40 to 48).
RwGPS continued to show low-res map. Maybe it caches at least the area to be ridden. BikeGPX doesn't show a map, but does continue to provide the path and navigation. When a data connection is reestablished, both return to showing high-res maps.
I’ve heard that the cellular connection doesn’t consume much power (or much data, only 4mb today) when there’s a strong signal. However, if there are now cellular towers nearby the phone cranks up the radio power in hopes of making a connection. Airplane mode might be useful in these situations.