Cycling Resources: Google Maps

One of the tasks that goes with cycling is sorting out routes to ride on. While it’s fun, at times, to simply pick a direction and see where the road takes you, much of the time it’s good to have an idea of where you are going, and how you are going to get there. This is especially true when you are trying to add distance to your regular routes. It’s pretty easy to use any mapping software or - if you still happen to have one about - a paper map - to sort out a five or ten mile ride. But as ride distances climb it becomes valuable to have a way to lay out clear routes that will work for the desired distance, and, particularly when riding on public roads, for safety purposes (it’s not fun to suddenly find that you’ve come to a point where your only choices are to either ride along a heavily traveled highway or backtrack).

Google Maps offers a free, readily available resource for this.

The first, simplest thing that it offers is cycling directions.

Usually this results in a route that avoids higher traffic areas, and it provides other information in a fashion that is specific to cycling - for example, travel times are at cycling speeds, and it gives a general impression of the terrain over the course of the route.

It also includes maps of biking trails and routes, identified in various shades of green lines on the map. The picture below shows biking trails in and around Rock Cut State Park in Rockford, Illinois.

Unfortunately, it doesn’t provide a key, so you are left to interpret on your own, but the Google blog says the following about the key:

• Dark green indicates a dedicated bike-only trail;
• Light green indicates a dedicated bike lane along a road;
• Dashed green indicates roads that are designated as preferred for bicycling, but without dedicated lanes

Some of the maps also show red, or perhaps brown, lines which were perhaps added in later (?). Based upon some familiarity with one of the areas they show up in, it appeared to me that these were either hiking or off-road trails, and that seems to be supported by this article on using Google maps for cycling on Lifewire.com. That article also offers step-by-step directions about how to use the cycling directions, though they appear to be specific to a desktop/laptop interface. In Google Maps for iOS, you tap the layers button in the upper right-hand corner:

Then select the cycling option in the menu:

This will turn on the cycling route overlay so you’ll see bike trails and such on the map. You also want to make sure you select "biking" for the directions when you punch in your destination. This means that your directions will be set for cycling rather than driving, so if you use Google Maps for driving directions, you’ll want to remember to switch it back when you are in the car.

That Google Maps offers cycling directions isn’t new - it’s been around as a feature since at least 2010 - but it’s one of those things that you only really notice when you have a use for it.

The cycling specific directions are a great feature when you are trying to determine how to get from one specific location to another, but Google Maps offers another feature that is extremely helpful when trying to add distance to routes: the Measure Distance mode.

To turn this on using Google Maps for iOS you want to find your starting point on the map, and do a long press to drop a pin. This will bring up a menu on the left that includes "measure distance":

(Note that, if you accidentally tap on a notable feature, it may not offer this option, so you may have to re-adjust your starting point slightly. I had to do that for this example, because I apparently tapped on just the right spot for Lock 2 of the Hennepin Canal for my first try).

Once you’ve selected this option, you’ll get a blue circle with a dotted line, and a distance readout at the bottom left hand corner. The trickiest part of this to get a handle on is that you don’t move the blue dot, you move the map under it. As you move the map the dotted line will extend. When you reach a turning point in the route you are exploring, you tap the "add point" button in the lower left-hand corner. This sets a marker and allows you to move the line in another direction (without it turns will get lost and the line will move at a diagonal direction - cool if you a traveling as the crow flies, but otherwise doesn’t work for the rest of us). This means that you’ll only need a few points set for a route with a few turns and mostly straightaways, but a lot more for routes that curve and turn. My example below marks out the distance for the Hennepin Canal Trail, which has a combination of straights and curves:

I’ve zoomed out a bit to give a larger picture here, but you can zoom in pretty close to make the map more precise as you are making it.

Ultimately, this lets you lay out a route for the distance you want. I find myself using it often to select routes for the distance I want in a way that avoids major thoroughfares, and takes me in a circular route from start to finish while avoiding re-covering the same territory as much as possible.

I don’t necessarily love Google products as a rule - I use Apple Maps on iOS for driving directions, don’t use their office software at all, and don’t generally use them for search. But I do generally try to use the best tool I can find for the job, all other things being equal. For cycling routes and directions, and for finding cycling trails, Google Maps is absolutely a step above.

Catching the Signs

It’s probably safe to say that riding a recumbent trike gives one a different perspective on the world. What I didn’t realize until I started was that this isn’t just a metaphorical difference.

Riding out on country roads things simply look different. Because of the position on the trike, one is at eye level with the long grass in the ditches, and a little extra care must be taken at the corners. It also means you get a different point of view on the wildflowers of summer:

I’ve also started noticing something that was hiding in plain sight, albeit a little lower than typical eye level. Riding out here in rural northern Illinois one encounters a sizeable number of small waterways. Some of these are natural, while others are man-made (you can often tell by the course that they take - natural waterways tend to meander, while the man-made ditches tend to flow in straight lines and sharp angles). Some flow year-round, while others are intermittent. However, they have a commonality when they meet the roadway - they require a bridge.

I’d ridden my bike all around the area when I was young, and since moving back I’ve literally ridden hundreds of miles on the local roadways. Between those two time periods I’ve crossed bridges over these streams more times than I can count. But a week or two ago I noticed something that I’d never seen before: some of the bridges have plaques on them.

The first one I noticed was a bridge over Willow Creek on Beemerville Road (and folks, let me tell you that, despite the name, I see no evidence of any "ville" along this path). Neither the bridge, nor the road itself, are a fancy affair, though both suit their purposes and location. But as I was riding along it I caught notice of the plaque:

Willow Creek (that’s pronounced "crick", incidentally) itself is an small, but ongoing affair:

And the bridge and road are relatively rustic affairs - most of Beemerville road is gravel. This is a fact which, incidentally, I think I’d known and actually forgotten, or I likely would not have chosen it. Gravel is easier to navigate on a trike than on a road bike, but it’s still not, you know, pleasant to ride on).

Of course, once one has seen a thing, discovered that it exists, has existed in the world despite one’s ignorance, one becomes primed to find it elsewhere. I had now begun looking for the plaques on the myriad other bridges I cross. And they are there, though certainly not everywhere. But they appear to have been present on a couple of bridges I have ridden across many, many times. I came across this plaque, which suggests the bridge it adorns has its own name:

This, then, is Faber Bridge (apparently). Faber is a common family name in the area, and the town of Mendota used to have a hotel by that name downtown, across from the train depot.

The hotel was still standing, albeit empty and unused, when I was a kid. Now only a gravel parking lot commemorates its location. But I digress...

The third plaque I came across is on one of the many bridges over Bureau Creek:

Bureau Creek is large and long enough to garner its own Wikipedia Page, running some 73 miles across at least two different counties. It is the creek that used to run under the Hennepin Canal aqueduct at Lock 12, on its way to empty into the Illinois River. There are times of the year where, depending upon the amount of rain, it would be navigable by a small canoe or kayak.

Given all of that, you can perhaps see why a bridge over this waterway might have a plaque on it. But the others?

The Faber Bridge covers the Little Vermillion River, a waterway that eventually empties into the Vermillion River), and then the Vermillion into the Illinois. Willow Creek looks, according to Google Maps, to flow into the Green River), which later feeds the Rock and that the Mississippi. And so one might think these plaques go on to bridges that cover more important tributaries. But no - there are at least dozens of bridges over Bureau Creek, for example. I’ve crossed more than a couple of them either by cycle or auto, and most of them are not similarly adorned. They do carry load ratings, so perhaps they were meant to be informative, but they are not placed in a location that would be easily read by a truck driver prior to crossing; and, again, you’d think if that were important, it would be marked on all of the bridges.

Ultimately, to me at least, their purpose remains a mystery. (There may well be a bridge engineer out there right now, reading this, saying "well actually" aloud as he comes across this section...).

What it does help reveal is the effect of that difference in perspective. Riding on my upright road bike the physical position places one’s body such that the head and eyes are oriented down, towards the handlebars and the road. The head is craned upward to see ahead unless leaning back into the seat (and often with the hands off the bars). Ion that machine my head is five to six feet up off the road, depending upon position.

Riding on the recumbent trike these plaques are at eye level, and one is comfortably able to look forward - indeed is oriented forward - the entire time. That I’ve not noticed these before I suspect is simply due to not having them easily accesssible. I’ve enjoyed years of riding my upright bike through the countryside - I’m certainly not trying to imply otherwise - but it is sometimes surprising how a relatively small change in approach can provide a very different point of view, and access to a different way of seeing things you’ve looked at many times before.

A Brief Flirtation with Google Drive

As is true for most of us, I have my systems for doing things, and I get comfortable in those systems. Still, it is good to periodically check out other options to make sure one is not missing out on something better.

I've recently been exploring the possibility of changing my email service, and I was considering the option of using Google's email service - not basic gmail, but rather the email thru their G Suite service, which allows you to use email addresses based in your domain (e.g. that end with your own address rather than "gmail.com").

G Suite, as the name implies, doesn't just offer email, but an entire office suite of features, many of which present the option of potentially replacing systems I already use. They have a secure video conferencing service (Hangouts Meet), they have their suite of office software, and they have an online file storage service, Google Drive.

Some of these things are of interest to me, while others are not. For example, I'm open to exploring Hangouts Meet as an alternative to our current service, but prior experience leaves me with exactly zero interest in Google Docs, Sheets, or Slides. The feature set in Apple's iWork suite is perfect for me, and it's integration into iOS devices, particularly the iPad, makes it a solid winner for me every time. I also am well aware, both from personal experience and from the reports of others, that Google has historically been slow to update the iOS versions of their products to use the features available on the iPad.

Among the products in G Suite is Google Drive. Aside from looking up documents from my kid's school, I had very little experience with this service. I'm a long-term user of Dropbox, but as I said at the beginning, it's good not to let comfort keep one from exploring other, potentially better options. Since, like most of the free world, I have a personal Google account, I also technically have a personal Google Drive. I decided to play with it a bit and see what I thought.

I downloaded the app to my iPad and made a couple of documents to put into the drive for testing purposes. Some of what I found was what one might expect. It handled PDF documents just fine - you can render a preview of the document, export it to another location, etc, just as you might expect.

The iWork files were another story entirely.

I specifically made up a Pages document for the test. What I found initially was that there is no preview option for a Pages file - rather, Google Drive just tells you that it is an "unsupported file type".

This isn't entirely surprising in and of itself. iWork files, as I understand them, are actually packages, and in the past that has confused some file systems. But it is inconvenient if you want to take a quick look at the document before opening it to make sure it is what you want. Dropbox and iCloud (naturally) readily render previews of these files.

While this is inconvenient, it is not necessarily a deal-breaker. I'd prefer to be able to preview my iWork files, since I use them regularly, but there isn't that much confusion between one file name and another for me.

But then something else happened: The Pages document that I had entered into Google Drive started duplicating itself. The first time I tried the app it multiplied the file into some 40 or 50 copies, and I said to myself "well, that's that, then" and deleted the app from my iPad. After a few days, and a little bit of thought, I considered the possibility that the experience might have been a fluke, so I tried it again, this time bringing files into the app in multiple ways. When I sent a copy to the app directly from Pages using "Send a Copy", it did not appear to make duplicates (though it did, inexplicably, append "-1" to the file name, despite there being no other file with that name in the folder). However, when importing from Dropbox what I found was that, it after it was sitting in Google Drive for a few minutes, it began to make multiple copies of that file without being asked to do so.

I'm not sure why this would occur, but if I were to consider Google Drive as an option for me, it would be in place of Dropbox, which would mean that I'd be sending a lot of files from Dropbox to Drive. I love The Tick), but I certainly don't need a replay of the attack of Multiple Santa to occur in my file storage.

Of course, there is also iCloud Drive on the iPad. What I found there was that any attempt to import a Pages document into Google Drive from iCloud Drive caused the file to simply hang there, with its progress bar seeming to be finished, and yet never fully resolving. This was only true for the iWork file. I was able, for example, to import a PDF from iCloud into Google Drive just fine.

One could argue that I was functionally warned up front that Google Drive wasn't going to play well with my files with the indication that the Pages document was an unsupported file type. I suppose that is true, to some degree. It's worth noting, however, that the iWork suite - Pages, Numbers, and Keynote - has been around now for over a decade, and it comes free with the iPad - this isn't a new product, nor is it obscure, so it seems reasonable to ask why a product that presents as a general storage tool would not be prepared to support these file formats properly. One suspects, if one is conspiratorially minded (as one might be) that it is because Google would prefer one to use their office suite.

A quick check of the weather finds that Hell has not, in fact, frozen over yet, so that won't be happening on my iPad.

So, as the title says, this was a brief flirtation with the product. I might have been able to live without the ability to preview my iWork files - though in retrospect, I do use that feature quiet frequently. Not being able to reliably import my files, and finding them duplicating like bunnies, however, largely seals (or, rather, breaks) the deal.

This Place is Permanently Closed

I've come across an interesting and somewhat troubling bug in google maps. For some reason, there are locations coming up as being "permanently closed", even when this is not the case.

How do I know this? My Lovely Wife and I were vacationing in Manitou Springs, Co, after the ABAI Conference this year. Manitou Springs is a lovely little tourist town that sits on the doorstep of the Garden of the Gods and the Manitou Cliff Dwellings - just down the road from Pike's Peak. We were looking for a place to have dinner on our first night in town, so MLW fired up her Yelp app and discovered a place called PJ's Bistro that served variations on polish food - pierogies, in particular, were what sparked her interest (she's half-Ukranian on her mother's side - you don't want to get in the way of a Ukranian on her way to a pierogie).

That decided, I looked it up on the Maps app on my iPhone. It was there, but the flag over the pin listed it as "permanently closed". Afraid all hopes of potato pocket heaven were lost, MLW called to ask if PJ's was open. She received a mildly confused "yes" from the woman on the other end of the line. (Incidentally, the food was delightful, and the restaurant offers a bit of balcony seating that offers views of the main drive in Manitou Springs, with the Rocky Mountains as a backdrop).

Ordinarily I might have written it off as a fluke, but the following day we decided to rent a car to cover the distance to the Colorado Wolf and Wildlife Center. We had the rental company pick us up. I didn't know the actual street address of our motel, so I just gave the name - The Dillon Motel - to the young man on the phone. Later he told me that they were confused because when they looked the Dillon up on Google Maps it was listed as - wait for it - "permanently closed".

I was aware that the Maps app that comes on the iPhone uses Google Maps as its source material, so it wasn't surprising to find the same indication when I looked it up on my iPad. The situation brings up a couple of troubling questions. The first is whether our entire trip has been some sort of feverish delusional experience brought on by too many days of behavior analysis seminars, or whether we've been sucked into some sort of alternate reality (staying at the the Dillon Motel does make me feel like I'm in a Quentin Tarantino movie - and I can't find either my gun or the drug money, making me very, very nervous as to who might come through the door).

The second, perhaps more salient question is: how many businesses are inaccurately listed as being "permanently closed" on Google Maps? It appears that this is one of Google's crowd sourcing features, so just about anyone can list a business as "Permanently Closed" - including competitors and prior customers with an axe to grind. Given that Google maps - either directly or through the plethora of other applications that rely upon it - is a primary source of information for a growing number of people looking for a hotel, a restaurant, an all-night bikini waxing spa, this could likely be a large source of lost business and revenue for such places. This would be particularly true for those businesses run by less tech-savvy folks, who are likely to be completely unaware of such a listing - after all, the legions of people not stopping into a store can't inform the owners of the problem.

Furthermore, even when a business owner is aware of an innacurate listing, who does she contact? There are no "report a problem" links that I could see on the iOS Maps app, nor on the mobile version of the Google Maps site. There is one on the desktop version, but I could not get it to allow me to enter information from my iPad. It might - probably would - from a desktop computer. But even if that's so, once the issue is reported it's up to Google to decide whether or not to correct the issue. And even then, this would be one correction at a time.

And that's somewhat beside the point. The reality is that these sites and applications are designed to be used by people who are out and about. The mobile versions - apps and mobile websites - are what people are going to be seeing and using more and more. Business people already contend with competition and the other stresses of the open market. They can be reviewed by anyone and his uncle for any reason. The business owner should not also have to worry about whether he or she is unknowingly losing business because Google has identified a business as "permanently closed".

Update: We had let the owner of the Dillon Motel know about his status on Google Maps, and he was able to have it corrected. He also indicated that he would get in touch with the owner of PJ's Bistro and make them aware. So - a happy ending for them, but how pervasive this is remains an open question.