Keywords: Google Earth, google earth, analytical results, xyz plot, hnm 30049
- Report Name
- Report Type
- File Name
- Input Parameters
- DB Type
- DB Schema
- DB Version
- Data Requirements
- Report Requirements
- Output Type
- Example Output
Report Name: Google Earth: Analytical Results (XYZ Plot)
Report Type: Standard
This Google Earth Report uses a saved Analytical Results Pick Report as the primary input parameter. The Analytical Results output is exported into to a *.kmz, and separated by chemical with each sampling date. Multiple sampling dates can be displayed in animation using Google Earth's time animation bar.
This report is computationally intensive, and interpolates a unique grid for each parameter and date. For example, a site may have only 100 different records, but 25 different dates. In this case the report would interpolate 25 different grids, and potentially consume vast system resources. Please also note that there are limitations to the size and complexity of KML/KMZ files supported in Google Earth. Selecting too many parameters and/or too large a date range may result in the following message:
"Report did not generate output. Please try again.
Please reduce the number of parameters and/or dates to be contoured (params=P,dates=D)"
where P = the number of input parameters, and D = the number of input dates.
File Name: EarthSoft.Interfaces.Google
Contact firstname.lastname@example.org for a direct file link.
Input Parameters: A selection you make to customize the output of a report.
|Input Parameters||Input Parameter Screenshot||Output|
|Saved Analytical Results Report||Google Map|
|Number of Palette Steps|
Note: * refers to hidden parameters.
DB Type: ORACLE and SQL
DB Schema: Standard (no custom or add-on schemas required)
DB Version: EQuIS 5.4.3 or later
Data Requirements: Coordinates in lat long
Report Requirements: Google Earth
Output Type: Google Earth or .kmz
View the following example or download the attachment.
Contact email@example.com for more information.