Mapping my journeys from sea to shining sea

An iPad screenshot shows a heat map from Google Photos indicating where photos had been taken based on geotagging or Google determining identifiable landmarks.

An iPad screenshot shows a heat map from Google Photos indicating where photos had been taken based on geotagging or Google determining identifiable landmarks.

With this year’s Independence Day celebrations fading into memory, I was thinking about the fact that I’ve had the opportunity to travel across great swaths of this wonderful and beautiful nation. In one sense, I’ve been everywhere (man) — from coast to coast to coast to coast. In another, I haven’t been to nearly enough destinations.

I’ve wanted to write about the map feature in the Google Photos app (Android and iOS) for quite some time, but it was hard for me to summarize why I feel this feature is so amazing. The Fourth of July celebrations brought this picture into focus as I realized that I’ve been able to visit so many different destinations, as specified in many of the songs about our nation.

The first song that came to mind was “This Land is Your Land” by Woody Guthrie. This song stands out strongly in my memory in part because we sang it every morning in kindergarten when I was living in Southern California.

A photo of the author in front of a pair of redwood trees at the Muir Woods National Monument in Mill Valley, Calif, on May 8, 2016.

A photo of the author in front of a pair of redwood trees at the Muir Woods National Monument in Mill Valley, Calif., on May 8, 2016.

For as encompassing as the song is, “This Land is Your Land” mentions only four specific destinations and they’re in the first verse — “From California to the New York island/From the redwood forest to the Gulf Stream waters.”

Of those four, admittedly broad locales, I realized that I’ve been able to either visit or live in all four over the course of my life. Unfortunately, the map feature in Google Photos doesn’t reflect this — my trips to New York and the coasts of Texas, Florida, Georgia and South Carolina all predate when we all carried cameras with us on a daily basis and where we could take endless numbers of photos without worrying about loading or developing film (so before the iPhone, basically).

Using the photos that are uploaded to the site/app, Google Photos generates a heat map based on the location data in the user’s photos plus whatever identifiable landmarks Google can identify in the images itself. The features is accessible under the search menu. It shows up as “Your map” (but it’s not available on the desktop version of the app).

A screenshot shows the Places map in Apple Photos.

A screenshot shows the Places map in Apple Photos.

I will note that Apple Photos also has the option of showing photos based on where they were taken, but I don’t find Apple’s solution as engaging or appealing as Google’s. Apple Photos shows thumbnails based on location. Zooming in will increase the number of thumbnails, but it seems clunky and inelegant compared to Google’s heat map.

The heat map evokes memories of past travels, family reunions and other adventures. I’m agog seeing some of the paths that I’ve taken over the past 39 years.

It evokes the spirit of roaming and rambling from Woody Guthrie’s song. There’s also some of the energy from the burgeoning lists of destinations called out in songs like “I’ve Been Everywhere” or “Living in America.”

The map displayed by Google Photos also reminds me of the map from “The Voyage of the Dawn Treader,” by C.S. Lewis. In that book from “The Chronicles of Narnia,” a magician gives the captain of the titular ship a map of the ship’s voyage to that point. The map was so detailed that when one looked closely with a magnifying lens, they could see accurate drawings of the actual place albeit at some distance. On the other hand, the map was incomplete in some areas because it could only depict where the ship had traveled.

The Google Photos map can feel like magic at times, even though it is simply a matter of technology and information (although Arthur C. Clarke did say something about technology and magic…). Zooming in on the map offers some joy as I can see the areas where I’ve been able to visit. Like the magician’s map from “Dawn Treader,” it can show documented locations in remarkable detail but be incomplete in areas lacking photos.

A screenshot from Google Photos shows a map indicating where photos were taken during a flight from Salt Lake City to San Diego in October 2016. Thumbnails of the photos from the trip are displayed on the right side of the iPad application.

A screenshot from Google Photos shows a map indicating where photos were taken during a flight from Salt Lake City to San Diego in October 2016. Thumbnails of the photos from the trip are displayed on the right side of the iPad application.

When one zooms in far enough, one can sometimes see individual points along a trip, which can be an interesting way to relive a past journey. At other times, the data can be a bit of a muddled mess — good luck sorting through the 2,800 photos I’ve taken over the course of six years around the venue where I curl, the Utah Olympic Oval in Kearns. The Oval is my most-photographed location by far.

A screenshot shows a heat map from the Google Maps app showing the approximate location of 2,700+ photos taken in and around the Utah Olympic Oval in Kearns, Utah.

A screenshot shows a heat map from the Google Maps app showing the approximate location of 2,700+ photos taken in and around the Utah Olympic Oval in Kearns, Utah.

The heat map of the Utah Olympic Oval also exposes some inaccuracies with the location data. GPS can give a good approximation of where a photo was taken (or where your phone is at a given point), but it’s not 100% accurate all the time. Some of the photos that the map says were taken outside the building were very much taken _inside_ the building (the ice is usually a giveaway, particularly in the summer).

It’s amazing that over 27,000 of my photos have been tagged — it’s probably about 95% of the photos that I’ve ever taken in my life. The vast majority of photos have tags because I took them with a smartphone with GPS. That era essentially started for me in September 2013 with an iPhone 5 issued for work (I bought a Samsung Galaxy SII in April 2013 but it didn’t have a data plan).

For the earlier era where photos were taken with a film camera, a digital point-and-shoot, a “dumb phone” or a feature phone, I’ve had to go back and manually map where I took the photos. That process is inevitably incomplete — there are some places that I don’t remember exactly where I was or there are photos where it doesn’t make sense to tag (including photos of loved ones taken by others but I was not actually present for).

Before tonight, I didn’t know how many photos were tagged by Google based on its ability to identify landmarks. When I first discovered that Google was attempting to locate photos way back in 2017, the process could be hit-or-miss. For example, I had taken a photo of a train car during a 2009 trip through California. For some reason, Google thought the photo was taken in Kunming Shi, China. It’s northwest of Vietnam — and nearly 7,500 miles from the nearest Amtrak stop.

Just a bit off the mark. in 2017, Google Photos thought this photo of an Amtrak train car was taken in China — about 7,500 miles from where it was actually taken.

Just a bit off the mark. In 2017, Google Photos thought this photo of an Amtrak train car was taken in China — about 7,500 miles from where it was actually taken.

Since then, Google has appeared to get better as guessing where I might have been. It’s been interesting to take photos or videos during plane trips (when the phone is supposed to be in airplane mode) and to later see that Google had apparently located where they had been taken (again assuming that I wasn’t a dummy and I remembered to put the phone in airplane mode during the flight).

For example, here’s a screenshot of a photo I took of the Salton Sea. Google Photos was able to correctly identify the location.

A screenshot shows a photo taken in September 2021 from an airplane showing the Salton Sea and an estimated location by Google Photos.

A screenshot shows a photo taken in September 2021 from an airplane showing the Salton Sea and an estimated location by Google Photos.

Apparently, Google Photos has estimated locations for about 6,200 of my images. Interestingly, it doesn’t include some of the aerial photos of the St. George area that I thought Google was able to place. That must mean that I was an insensitive jerk and didn’t use airplane mode during that trip. Whoops.

By the way — It may seem creepy for Google to have so much location data and it can be. Unfortunately, it appears that Google Photos only has an option to remove the estimated location data. As Google notes, “If the location of a photo or video was automatically added by your camera, you can’t edit or remove the location.” In that case, it seems that the best option is to disable location data on the phone/camera _before_ taking the photo.

I don’t necessarily mind saving location data because I find it to be a useful set of information. I do try to be selective in the images that I share, but if I needed to be extra careful, I would need to take additional steps to ensure that people couldn’t find geodata (or identifiable landmarks) in the images.

While I find this data useful, it seems like it would be difficult for a stranger to really root through the information. Google Photos presents the location data in a heat map that someone needs to interact with to learn any additional context (such as dates). The map also doesn’t appear to be shareable.

Google has taken the additional step of turning off location sharing by default in some common ways of sharing information like shared albums or conversations (it can be turned on by the user and was apparently on prior to 2021).

I also know that the heat map is woefully incomplete — as I mentioned earlier, the map can only show places that I’ve taken photos of. I’ve visited or traveled through 42 states, but the heat map can’t show that because there simply aren’t many photos from my time living in the Southeast or my lengthy trips across the Sun Belt, Midwest or the Northeast (or visits to Canada and Mexico, for that matter).

The map can also exaggerate single trips across great distances. This can be seen with my single trip aboard the Empire Builder train across the Upper Midwest in 2009. It was memorable, but my only trip through North Dakota and Montana is depicted as a giant blue ribbon on the map.

The map is ultimately a fun look at where I’ve been. It is truly amazing that we have so much freedom to travel about the country. It’s a right that has sometimes been denied to Americans (and regrettably still is to some extent today). I certainly don’t wish to take this right for granted.

The map also indirectly shows places where I haven’t been. Even in areas where it looks like I’m well traveled, there are destinations that I haven’t yet been able to visit such as national parks in Utah.

I don’t know if I’ll get to some of these locales — such expeditions depend on time, money and planning. If I do, I’ll make sure that photos from those trips are added to my Google Photos map.

A map of Provo and Hobble Creek Canyon

On Thursday, law enforcement officials disclosed that the body of Elizabeth Elena Laguna-Salgado was found in Hobble Creek Canyon on May 18 — about 10 to 15 miles from where she was last seen in downtown Provo on April 16, 2015.

As part of the Daily Herald’s coverage of Salgado’s disappearance, I created a map showing both Provo and Hobble Creek canyon. The print version of the map includes additional detail.

Hitting 11 million image views on Google Maps

My profile on Google Maps.

My profile on Google Maps.

Just a year ago, I passed 2 million views on Google Maps. Imagine my surprise when my images surged past 10 million views just a couple of months ago. The 190 images I’ve published on Google Maps has been viewed 11.1 million times as of this writing.

I wish I could claim total responsibility for this accomplishment, but it seems like it’s more a matter of being in the right place at the right time.

Since I started uploading photospheres to Google Street View, none of them had exceeded 1 million views (although one was close at 970,000 views). Following the Oroville Dam crisis in February, I had two photospheres reach past the one million mark, with one reaching past two million.

In my experience, the most successful spheres are those that are featured in Google’s search results. I don’t have definitive proof that this is the case, but I’ve found the images that featured in the search results seem to perform best. The example that came to mind was my photosphere for Bear Hole in Bidwell Park. I was surprised when I saw it suddenly surge beyond 100,000 views. I wasn’t sure why it was performing so well.

The most plausible explanation was that it was featured on the search results on Google Map. When I searched for Chico, CA in Google Maps, the search engine returns a map of the city, but there’s also a card showing useful information — and photos of the city. Often times, these are popular pics of major landmarks or the like. Google also includes photospheres. This is often from its own Street View service, but it increasingly appears to include photospheres taken by its users.

A Google Maps card for Oroville, California on Monday, May 29, 2017. The top image is from one of my photospheres.

A Google Maps card for Oroville, California on Monday, May 29, 2017. The top image is from one of my photospheres.

I think this is behind my most “popular” photospheres, including ones taken at regional parks, train stations or other landmarks likely to be searched by people.

Adding credence to my theory was another photosphere of Bear Hole taken by another user. I saw that it too was featured at times in the Google Maps search results and it had a view count similar to mine,

That brings me to the incident that brought my views surging to new heights. In early February, there was a natural disaster that prompted the evacuation of more than 200,000 people in Northern California. Although the emergency spillway at Oroville Dam didn’t breach, I imagine there were a lot of people interested in learning the location of Oroville Dam and the surrounding area.

Indeed, the most popular photospheres featured the now-destroyed main spillway at the dam. It’s interesting that my most popular image is something that no longer exists.

The second most popular image for me was a photosphere of sculptures at Centennial Park in Oroville. It’s not associated with the park because there’s no entry for the park on Google Maps, but it is the first thing that comes up on Google Maps when someone searches for Oroville.

Several other images from Oroville have jumped following the Oroville Dam crisis, but those are by far the most popular.

I don’t know if a view is counted merely because someone sees it on a search result or if someone actually clicked through to see the full image. I would like to think it’s the later, but information on Google support forums indicates that merely seeing an image in a search result counts as a view.

Ultimately, I would like to think that people are viewing my images — it’s nice to think that millions of people are seeing my work. If it’s true, these images are the most popular thing that I’ve ever done.