| Info |
|---|
NOTE: Google has decided to retire the Google Earth API. Per their deprecation policy, the API will be turned off on December 12, 2015. http://googlegeodevelopers.blogspot.com.au/2014/12/announcing-deprecation-of-google-earth.html |
| Info |
|---|
Cohga is not a registered partner of Google nor is Google associated with Cohga or Weave. |
...
On existing sites it seems to work best with a true 3D model of the area. If just looking at an image on the ground it does not have the same impact. The down side of 3D models is that they generally consume large amounts of memory and consume considerable bandwidth.
| Gallery | ||||||
|---|---|---|---|---|---|---|
|
Architecture
The Google Earth Integration has been implemented using the JavaScript API described in the Google documentation. It is designed to reside either in a tab or inside a floating window within the Weave client interface. The Google Earth plugin communicates with the Google servers for the main datasets and with other servers for sourcing KML and images.
...
The plugin and the data that is exposed to Google Earth needs to be considered. Since the Google Earth plugin renderers all content on the client side, it needs to have access to the data sources provided. e.g. any KML dataset needs to be externally accessible for Google Earth to consume it. Depending if the KML source data is intended for both internal and external browsers.
| Gliffy | ||||
|---|---|---|---|---|
|
Advantages
- Licensing is still unknown at this stage. Several attempts by Weave sites to contact Google about licensing have not been successful. You can run the Google Earth plugin on external sites however internal use requires that the organisation purchases an Enterprise License.
- Allows visualising 3D data. However Weave does not support exporting 3D data.
- Adds another dimension to the interface.
...