Google Earth Locations Report

<< Click to Display Table of Contents >>

Navigation:  EQuIS Library > Reports > Standard Reports > Google Earth >

Google Earth Locations Report

Report Name: Google Earth Locations (example)

File Name: EarthSoft.Interfaces.Google.dll

Dependencies: N/A

Software: EQuIS Professional

Source: EQuIS Professional install

Language: English

Output Type: Keyhole Markup Language (*.kmz)1, 2, 3

 

Description: This report generates a *.kmz file that will display the locations from an EQuIS facility. Each location is labeled with the DT_LOCATION.SYS_LOC_CODE value. Prior to using this report, review the Submission of Content Warning for Google Earth reports as well as the commercial license requirements.

 

Installation Instructions: This report assembly is part of the EQuIS Professional installation. No additional installation steps are necessary.

 

Overview:

The Places tree in Google Earth groups each location by type (i.e., DT_LOCATION.LOC_TYPE). The report output can also include DT_LOCATION.LOC_DESC in the 'callout box' when a location is clicked.

 

Another useful feature of this report is the ability to display documents and photos for each location. Associate documents or photos with a location using the Explorer Widget in EQuIS Enterprise. When uploading a document or photo, select the desired location from the drop-down. The Google Earth Locations Report will create a balloon popup for each location listing the documents and displaying any photos.

 

Note: Use 'Embed Files' for both images and documents in Google Earth Version 5.0+ as the 'Link File' parameter will not work in version 5.0 or newer.

 

For locations to appear in this report:

•DT_COORDINATE.COORD_TYPE_CODE must be like "*LAT*LONG*".

•DT_COORDINATE.IDENTIFIER MUST be "Primary".

•DT_LOCATION.LOC_TYPE  must be populated.

•DT_LOCATION.SYS_LOC_CODE must be populated.

•DT_LOCATION.LOC_DESC must be populated before locations are clickable. DT_LOCATION.LOC_DESC is displayed in the 'callout box' when a location is clicked, if this option is selected.

 

Use Personal Icons for Each Location Type

1.Use the Explorer Widget to upload the icon as an image (.gif, .jpg or .png).

2.Open the DT_FILE table and find the image file(s).

3.Set the PLACE_TYPE field equal to LOCATION_TYPE_CODE.

4.Set the PLACE_CODE field equal to the corresponding location type code for that image (such as Monitoring Well, Soil Boring, etc.).

 

The Google Earth output, which shows a table when clicking on a location, has been improved for readability by adding color to alternate rows.

 

Notes:

•EQuIS Google Earth Reports do not actually require or directly use Google Earth or any other Google service, the reports merely create KML (*.kml, *.kmz) files. Some of the charts are created using Google Charts (by sending individual data points for the chart).

•Other applications besides Google Earth (such as ArcGIS Explorer) can read *.kml files, although EQuIS reports have not been tested extensively with anything other than Google Earth.

•An EQuIS license does not provide legal license or permission to use Google Earth. Users are responsible to use Google Earth legally.

 

Report Parameters

Location


Individual

Parameter for selecting individual locations.

Group(s)

Parameter for selecting location groups.

Description

Choose which information to display for each location: loc_desc, Embed Files, Link Files

Name on Map

Choose the name source for the location display on map: sys_loc_code, loc_desc, loc_name

* Selecting a higher resolution will take longer to process.

 

 

Report Output

The report output is a *.kmz file that is viewed in Google Earth.

 

 

1Using Google Earth for commercial purposes requires a commercial license from Google which must be obtained separately by the end user.

2EQuIS Google Earth reports do not require Google Earth or Google Services to generate KML files. Charts may be generated by Google Charts.

3KML is an open standard that may be read or viewed in other applications. These reports have only been tested in Google Earth.