Exporting to Google Drive

Exporting to Google Drive (GDrive) is controlled by the boolean flag export_to_drive in the config file delineator/heet_config.py.

1. Exporting to GDrive automatically

If export_to_drive is True, the results will be exported to Google Drive automatically.

2. Exporting to GDrive later

If export_to_drive is False, the results will not be exported to Google Drive automatically. To export the results to Google Drive at a later time, use the utility script heet_export_cli.py as follows:

> python heet_export_cli.py [path-to-results-folder-on-ee] [destination-folder-on-gdrive]

Attention

Only a single top-level folder can be specified as the destination folder on GDrive

Hint

To read about other configuration options, please refer to Configuration Options.

Example usage:

> python heet_export_cli.py users/tjanus/XHEET/MYDAMSD22_20230107-2140 XHEET_MYDAMSD22_20230107-2140

will export the calculation outputs from the job folder MYDAMSD22_20230107-2140 residing in the users’ working folder users/tjanus/XHEET on Earth Engine and save the data to the folder of the same name in GDrive.

Note

Please note the following Earth Engine documentation describing where in Google Drive the data will be written to. “The Google Drive Folder that the export will reside in. Note: (a) if the folder name exists at any level, the output is written to it, (b) if duplicate folder names exist, output is written to the most recently modified folder, (c) if the folder name does not exist, a new folder will be created at the root, and (d) folder names with separators (e.g. ‘path/to/file’) are interpreted as literal strings, not system paths. Defaults to Drive root.”

Export Settings and Outputs

We provide a setting that is given as an argument in the command-line call - see [output-option] in the Syntax section of Running the GeoCARET Script for details. The output options are provided as columns in the table below: standard, extended, diagnostic, diagnostic-catch, diagnostic-res, diagnostic-riv. They control the amount of data that is calculated and saved to the Earth Engine folder during the analysis, as illustrated in the table below.

file_prefix	title	st and ard	ex ten ded	di agno stic	diag nostic -catch	diag nosti c-res	diag nosti c-riv
user_inputs	User inputs	X	X	X	X	X	X
P_*	Raw dam location		X	X	X	X
PS_*	Snapped dam location	X	X	X	X	X	X
WCPTS_	Watershed candidate points			X	X
WDPTS_	Watershed detected points			X	X
CX_	Catchment pixels			X	X
C_ c_	Catchment boundary	X	X	X	X	X	X
WBSX_	Waterbodies pixels			X		X
WBS_	Waterbodies boundaries			X		X
R_ r_	Reservoir boundary	X	X	X	X	X	X
rbz_	Reservoir buffer zone	X	X	X	X	X	X
sr_	Simplified reservoir boundary						X
S_ s_	Inundated river reaches (streamline)						X
MS_ ms_	Main indundated river channel	X	X	X	X	X	X
N_ n_	Noninundated catchment	X	X	X	X	X	X
output_parameters	Calculated Parameters	X	X	X	X	X	X