Little Colorado Fly-through Tour (early Google Earth experiment)

UPDATE: Corrections, clarifications and attributions

Photo by Philippe Pellen

Little Colorado fly-through tour (Google Earth Community post)

Note: a FFriend told me the color of the water comes from Rock flour

A fly-through tour of the Little Colorado River, from Blue Spring to where it joins with the main Colorado River. The water really is bright blue unless runoff makes it muddy. It seems the elevation (GIS) and satellite image data don’t always match, because at points the river goes up the side of the canyon. The Grand Canyon is unique and strange in many ways, but water still flows downhill.

There is a “play folder” control in Google Earth; or the tour can be opened up and stepped through. You will notice the program doesn’t like it when one hits the wall, which I do several times. Toward the end of the tour in the bright sunlight you see the color of the water vividly.

If I were to do it again, I would zoom out quite a bit and use fewer “placemarks.” The extreme close-ups aren’t always attractive, especially when the water isn’t in direct sunlight. Since the satellite image data gets updated, the shadows will move depending on the time of day the satellite passes over (assuming sunny weather.) I would stay well above the canyon until late in the tour, and drop down close to the ground as you approach the confluence, where there are some spectacular user-contributed photos such as the one above. I have not re-constructed the tour in Google Maps; instead, I started a companion map for this tour.

I wonder if a “river/donkey/boat/hiker view” is planned for images captured a la “street view”? It seems a good idea to risk a camera setup mounted on a boat. I recommend the Portuguese fishing boat (Dory) expertly manned by the Grand Canyon Expeditions company in small tours, providing one rower and four passengers maximum per boat. This could be a fantastic way to bridge Earth, Maps, and Street view, in a place not easily accessible and undeniably fascinating.

The Whistler by snowmobile project is nice but implies much more is possible. A river expedition is more difficult to arrange and requires more personal risk… and would be much more interesting. Imagine the view from a cresting wave on the Diamond Creek rapids. A consolation: the food provided by the guides is really good.

Download Google Earth here. Screen capture below linked to View in Google Earth (.kmz download)

View Little Colorado (Grand Canyon) Tour in a larger map

Twitter needs geo tools (location filtering)

The twitter conversation below occurred this morning. I’m very sympathetic to Stephen’s complaint, and often don’t post stuff because the content is geo-limited or time-limited. If Stephen hadn’t complained, I wouldn’t have been prodded into offering a possible solution. It’s up to the geniuses who design these services to decide when to adopt @ or officially allow a feature such as described below.

I was much more vocal about my disappointment in twitter when pr0n-sters and spammers were winning the battle. I applaud twitter for progress in that area, and I would do some digging to offer old tweets, especially one where I really lost my temper. I would do that, but access to older tweets is still unavailable. Try searching your own tweets; they have still not fixed search. My point is… lost now.

Notes: “geo” is short for geographical, or “location-based.” Twitter here is shorthand for whatever micro-messaging platform wins, with @ (at-replies) and # (hashtags) being just one example of how to express such things. Unstated in the conversation is that there is no way for me to geo-limit my sphere of interest, or geo-limit the sphere of single tweet. In my profile, I could say I’m interested in #usaonly and any tweet could limit its sphere appropriately. In this case, I would add #usaonly to all Netflix ad Hulu tweets, and Stephen wouldn’t see them if he said he was interested in #canadaonly. Geo-unlimited tweets and profiles act as they do currently. Each image linked to its tweet.

 

A more expressive dialect is to either #include #usaonly (inside joke for all C and C++ programmers there) or #exclude #usaonly. This allows Stephen to register his disgust with all Hulu tweets by saying #exclude #usaonly, rather than artificially limit his sphere of interest to #canadaonly.

#canadaonly should not be needed, since Stephen is not only interested in Canadian issues… he is merely tired of being notified of content that he cannot access. I will not address the question of whether geo-limiting content is wise; it’s a very unfortunate fact.