run_gms.py¶
GeoMultiSens preprocessing console argument parser. Python implementation by Daniel Scheffler (daniel.scheffler@gfz-potsdam.de)
usage: run_gms.py [-h] [--version]
{jobid,sceneids,entityids,filenames,constraints} ...
Named Arguments¶
- --version
show program’s version number and exit
Sub-commands:¶
jobid¶
Run a GeoMultiSens preprocessing job using an already existing job ID.
run_gms.py jobid [-h] [-jc [JSON_CONFIG]] [-DH [DB_HOST]]
[-DOO [DELETE_OLD_OUTPUT]] [-vid VIRTUAL_SENSOR_ID]
[-dsid_spat DATASETID_SPATIAL_REF] [--CPUs CPUS]
[-c [COMMENT]]
jobid
Positional Arguments¶
- jobid
job ID of an already created GeoMultiSens preprocessing job (must be present in the jobs table of the database)
Named Arguments¶
- -jc, --json_config
file path of a JSON file containing options. See here for an example: https://git.gfz-potsdam.de/geomultisens/gms_preprocessing/blob/master/gms_preprocessing/options/options_default.json
- -DH, --db_host
host name of the server that runs the postgreSQL database
Default: “localhost”
- -DOO, --delete_old_output
delete previously created output of the given job ID before running the job
- -vid, --virtual_sensor_id
ID of the target (virtual) sensor
- -dsid_spat, --datasetid_spatial_ref
dataset ID of the spatial reference
- --CPUs
number of CPU cores to be used for processing (default: “None” -> use all available
- -c, --comment
comment concerning the job
Default: “”
sceneids¶
Run a GeoMultiSens preprocessing job for a given list of scene IDs.
run_gms.py sceneids [-h] [-jc [JSON_CONFIG]] [-DH [DB_HOST]]
[-DOO [DELETE_OLD_OUTPUT]] [-vid VIRTUAL_SENSOR_ID]
[-dsid_spat DATASETID_SPATIAL_REF] [--CPUs CPUS]
[-c [COMMENT]]
sceneids [sceneids ...]
Positional Arguments¶
- sceneids
list of scene IDs corresponding to valid records within the ‘scenes’ table of the database
Named Arguments¶
- -jc, --json_config
file path of a JSON file containing options. See here for an example: https://git.gfz-potsdam.de/geomultisens/gms_preprocessing/blob/master/gms_preprocessing/options/options_default.json
- -DH, --db_host
host name of the server that runs the postgreSQL database
Default: “localhost”
- -DOO, --delete_old_output
delete previously created output of the given job ID before running the job
- -vid, --virtual_sensor_id
ID of the target (virtual) sensor
- -dsid_spat, --datasetid_spatial_ref
dataset ID of the spatial reference
- --CPUs
number of CPU cores to be used for processing (default: “None” -> use all available
- -c, --comment
comment concerning the job
Default: “”
entityids¶
Run a GeoMultiSens preprocessing job for a given list of entity IDs.
run_gms.py entityids [-h] [-jc [JSON_CONFIG]] [-DH [DB_HOST]]
[-DOO [DELETE_OLD_OUTPUT]] [-vid VIRTUAL_SENSOR_ID]
[-dsid_spat DATASETID_SPATIAL_REF] [--CPUs CPUS]
[-c [COMMENT]]
entityids [entityids ...]
Positional Arguments¶
- entityids
list of entity IDs corresponding to valid records within the ‘scenes’ table of the database
Named Arguments¶
- -jc, --json_config
file path of a JSON file containing options. See here for an example: https://git.gfz-potsdam.de/geomultisens/gms_preprocessing/blob/master/gms_preprocessing/options/options_default.json
- -DH, --db_host
host name of the server that runs the postgreSQL database
Default: “localhost”
- -DOO, --delete_old_output
delete previously created output of the given job ID before running the job
- -vid, --virtual_sensor_id
ID of the target (virtual) sensor
- -dsid_spat, --datasetid_spatial_ref
dataset ID of the spatial reference
- --CPUs
number of CPU cores to be used for processing (default: “None” -> use all available
- -c, --comment
comment concerning the job
Default: “”
filenames¶
Run a GeoMultiSens preprocessing job for a given list of filenames of downloaded satellite image archives!
run_gms.py filenames [-h] [-jc [JSON_CONFIG]] [-DH [DB_HOST]]
[-DOO [DELETE_OLD_OUTPUT]] [-vid VIRTUAL_SENSOR_ID]
[-dsid_spat DATASETID_SPATIAL_REF] [--CPUs CPUS]
[-c [COMMENT]]
filenames [filenames ...]
Positional Arguments¶
- filenames
list of filenames of satellite image archives corresponding to valid records within the ‘scenes’ table of the database
Named Arguments¶
- -jc, --json_config
file path of a JSON file containing options. See here for an example: https://git.gfz-potsdam.de/geomultisens/gms_preprocessing/blob/master/gms_preprocessing/options/options_default.json
- -DH, --db_host
host name of the server that runs the postgreSQL database
Default: “localhost”
- -DOO, --delete_old_output
delete previously created output of the given job ID before running the job
- -vid, --virtual_sensor_id
ID of the target (virtual) sensor
- -dsid_spat, --datasetid_spatial_ref
dataset ID of the spatial reference
- --CPUs
number of CPU cores to be used for processing (default: “None” -> use all available
- -c, --comment
comment concerning the job
Default: “”
constraints¶
Run a GeoMultiSens preprocessing job matching the given constraints.
run_gms.py constraints [-h] [-jc [JSON_CONFIG]] [-DH [DB_HOST]]
[-DOO [DELETE_OLD_OUTPUT]] [-vid VIRTUAL_SENSOR_ID]
[-dsid_spat DATASETID_SPATIAL_REF] [--CPUs CPUS]
[-c [COMMENT]]
Named Arguments¶
- -jc, --json_config
file path of a JSON file containing options. See here for an example: https://git.gfz-potsdam.de/geomultisens/gms_preprocessing/blob/master/gms_preprocessing/options/options_default.json
- -DH, --db_host
host name of the server that runs the postgreSQL database
Default: “localhost”
- -DOO, --delete_old_output
delete previously created output of the given job ID before running the job
- -vid, --virtual_sensor_id
ID of the target (virtual) sensor
- -dsid_spat, --datasetid_spatial_ref
dataset ID of the spatial reference
- --CPUs
number of CPU cores to be used for processing (default: “None” -> use all available
- -c, --comment
comment concerning the job
Default: “”
The argument parser offers multiple sub-argument parsers (jobid, sceneids, …) for starting GMS jobs. use ‘>>> python /path/to/gms_preprocessing/run_gms.py <sub-parser> -h’ for detailed documentation and usage hints.