While Google continues to add great new features and tons of new imagery to Google Earth, they want to be clear that they’re not forgetting about some of the basic layers such as the Mountains and Water bodies.
A few days ago they pushed out an update to the Mountains layer which includes some powerful new features, including a detailed information window, Panoramio photos, cross-section views of the mountain and tours that they’ve created for every mountain. For example, here is a video showing the tour of the Matterhorn:
For this feature to work, you need to enable the “Mountains” layer on the left-hand panel in Google Earth. Of course, an increasingly difficult challenge is finding the proper layers as Google continues to add more of them. For the Mountains, you’ll find it under “Borders and Labels” –> “Labels” –> “Mountains”, as shown here:
In addition to the mountain layer changes, they’ve added thousands of new labels to the “Water Bodies” layer, which can be found just below the “Mountains” layer in the image above.
Hopefully Google will continue to finesse the organization of the layers section and make it easier to find the hidden gems like this one.
Today, Peter Batty from Ubisense updates us about how their product, myWorld, is using Google Maps API Premier to make sense of complicated GIS data.
The data for these network maps is stored and maintained in a Geographic Information System (GIS). These systems have been around a lot longer than Google Maps, for 30 years or so, and tend to be powerful but complex to use. We have focused on working with data from GE Smallworld for utility GIS, but can also work with data from ESRI and others. We render the network data from the GIS to raster map tiles to create an image map overlay that is displayed on top of the Google Maps basemap. The advantage of this approach versus using a vector data format is that it is much easier to match the cartographic design of the network maps used in the GIS, and the users expect consistency between the systems.
All features on the map need to be clickable so that users can display information about any of the network items such as cables, poles, transformers, etc. To handle this we just define a click event that queries a server to find items close to that point. We use a system called Arc2Earth Cloud, which stores spatial data in Google App Engine.
One cool feature of our application is its tight integration with Google Street View. You can click on an object on the map, such as a pole or a building, and see a Street View of that object. This gives the user additional information that they can’t get from their existing GIS database. We calculate the right bearing for the Street View automatically, and this works surprisingly well, given the potential for mismatches between the Street View and GIS location data. When necessary, the user can adjust and save the view, over-riding the automatic view. We can display markers in the Street View and click on them to display attributes of poles or other characteristics – this is a great feature of the V3 API.