Entries in geography (3)

Tuesday
May042010

Google Maps: View of Glen Canyon bridge (satellite images 3D models and street view)

The Earth view of the Glen Canyon bridge shows how the combination of satellite images and 3D “Earth” models work together. The satellite view can’t see underneath the bridge, and the 3D model of the bridge can’t repair the illusion that the road drops down the canyon walls and hugs the ground.


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

Unfortunately, the “street-view” vehicle doesn’t dynamically adapt to its context; it would be appropriate to raise the camera 10 or 20 feet here so as to get a clear view of the canyon. The scarcity of roads and the scarcity of “interesting views” from the road do suggest a different approach for mapping places like this. One wonders whether it’s desirable (and practical) for the vehicle operator to make a stop, get out and “bicycle-view” or “backpack-view” the pedestrian bridge seen here.


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

Tuesday
May042010

Google Maps Earth View: Observed Behavior (and a bug)

UPDATE: 20100801 The looping bug outlined below has been fixed.

 

First, it should be said that adding “Earth View” to Google Maps is a stroke of genius.

  • No need to install the Google Earth application 
  • Links and live embeds to Earth view maps work also

While testing Earth View in the context of my Little Colorado Fly-through Tour, I found a problem with the way Google Maps pans and/or zooms to make a selected place-mark visible. But first, here’s an Earth overview of my user map in progress. Earth tip: try moving the pointer while the button is pressed, and use the Control and Shift keys to change the behavior (rotate compass, tilt camera up, etc.)


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

In experimenting with “user maps” using the Earth View feature, it is clear that the Maps place-marks lack the control that the “micro-format” .kml provides — specifically, the view parameters specified in the “lookat” object.

<LookAt id="ID">
  ...
   
  <!-- specific to LookAt -->
  <longitude>0</longitude>            <!-- kml:angle180 -->
  <latitude>0</latitude>              <!-- kml:angle90 -->
  <altitude>0</altitude>              <!-- double --> 
  <heading>0</heading>                <!-- kml:angle360 -->
  <tilt>0</tilt>                      <!-- kml:anglepos90 -->
  <range></range>                     <!-- double -->
  <altitudeMode>clampToGround</altitudeMode> 
          <!--kml:altitudeModeEnum:clampToGround, relativeToGround, absolute -->
          <!-- or, gx:altitudeMode can be substituted: clampToSeaFloor, relativeToSeaFloor -->

</LookAt>

While the view details above can be captured with “link” and “embed,” they are not easily captured in a Map place-mark, except by placing a full Google Maps “permalink” URL inside the placemark. 

The default orientation for viewing placemarks in Earth View is due north, where the compass at top left has N at the top (a.k.a. “heading” or “yaw”) at the current zoom level (altitude), and the default camera angle is approximately 45 degrees “up” from straight down (“tilt”)

Casual URL decoding of Google Maps permalinks reveals

“&ecpose=36.18409487,-111.79393673,1482.19,-2.755,44.995,0”

which as expected seem to represent (most of) the six degrees of freedom:

  • latitude (X)
  • longitude (Y)
  • altitude (Z)
  • yaw (Z rotation)  “heading” i.e. rotation of compass
  • pitch (X rotation) “tilt” or camera angle measured from “straight down”
  • roll (Y rotation)  usually zero, i.e. the horizon is at an angle
  • the last parameter may or may not represent “range”

Problems with the Little Colorado river include the narrow canyon, steep walls, and the narrow body of water. Default behavior in Google Maps includes “automatic” view adjustment based on the user’s selection. In the case of the placemark below, many usage patterns leave the placemark invisible, and the algorithm for adjustment often loops and loops and eventually fails, with the view left as shown below.

The addition of Earth View means any place-mark may be invisible in a given view, and the automatic “pan/scroll/zoom” algorithm isn’t quite smart enough yet to handle a few odd cases.

  • terrain (elevation) data — a mountain comes between the view and the place-mark
  • zoom level of the view — at low altitudes (high zoom), elevation data starts to obscure things
  • “heading” (compass rotation) — The view may see the place-mark only if oriented properly 

 

Observing the long looping period it seems what is attempted by the algorithm includes coming closer to the placemark and changing the “pitch” or camera angle. Unfortunately, the “due North” default and maintaining the “zoom” (or altitude) are both problematic.


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

Other minor Earth View oddities include the “zoom level” indicator which is always in the center in Earth View, and the fact that “zoom in/out” via the embedded control behaves differently than scroll up/down (the “mouse” equivalents for zoom.) Using a scroll wheel maintains the camera tilt, even if you run into a wall. The zoom out control un-tilts as the altitude increases, and zoom in does the reverse, remembering the tilt that was in effect.

In the process of making many custom user maps, some quirks and deficiencies in Google map making are apparent. Here is a quick list of some pet peeves. 

  • There is no way to make a placemark that is specifically a “Street view” or “Earth view” flavor. Capturing the “map mode” and view details via permalink URL inside a placemark does work but has problems: there is no other way to switch modes or change the view, and there is no way to tell if you are looking at the exact thing described by the URL.
  • There is no way to specify a “place-mark” that includes view parameters other than latitude and longitude.
  • Map making is frequently tedious because the tools are unavailable in Street View and Earth View modes. Context is often lost when switching to “regular” map mode.
  • User photo icons are vanishingly small in the Earth view mode.

 

Monday
Apr122010

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