Processing Options
Contents
Processing Options#
Define Job ID#
Expected value: (optional) an alpha-numeric string
The job ID is used to manage a processing task. It is an optional field, however, if you choose not to define a job ID yourself one will be automatically generated for you. If you do provide a value, it must only contain letters and/or numbers.
The Job ID will be used to name the workspace folder where intermediate processing steps are stored, and it will be used for the folder name where the processing outputs are finally stored.
Results Handling#
During the processing task, Geona Hyperspectral will produce a series of files required to arrive at the final outputs; this option allows you to define which of these files you would like to be transferred to the final output location. If you are not sure, we advise that you retain all files initially, at least until you have performed several processing runs and are more familiar with the outputs generated and which ones you are interested in.
For each processing task, all input, intermediate, and output files are retained in the workspace directory.
The following table describes the all the intermediate and final output files, and which are retained for each of the
options. In this context, *
is replaced with the filename of the raw input file minus the file extension,
and <job_id>
is replaced with the job ID
Filename / Description |
Final mapped files |
3-band mapped intermediate |
Unmapped calibrated & intermediate |
All files |
---|---|---|---|---|
|
✓ |
✓ |
✓ |
✓ |
|
✓ |
✓ |
✓ |
✓ |
|
✓ |
✓ |
✓ |
✓ |
|
𐄂 |
✓ |
𐄂 |
✓ |
|
𐄂 |
✓ |
𐄂 |
✓ |
|
𐄂 |
✓ |
𐄂 |
✓ |
|
𐄂 |
𐄂 |
𐄂 |
✓ |
|
𐄂 |
𐄂 |
𐄂 |
✓ |
|
𐄂 |
𐄂 |
𐄂 |
✓ |
|
✓ |
✓ |
✓ |
✓ |
|
𐄂 |
𐄂 |
✓ |
✓ |
|
𐄂 |
𐄂 |
𐄂 |
✓ |
|
✓ |
✓ |
✓ |
✓ |
|
✓ |
✓ |
✓ |
✓ |
|
𐄂 |
✓ |
✓ |
✓ |
Processing Completion - Webhook URL#
Expected value: any valid URL starting http
or https
This setting is provided as a method to integrate Geona Hyperspectral processing into external workflows to allow for onward steps to commence without the need for manual intervention. Once a processing task has completed, the status log file for the job is posted as a JSON object to the webhook URL provided. The webhook call is made regardless of whether the job completed successfully or failed. The status code from the webhook call is recorded in the job’s log file, but no further details of the response is stored.