diff --git a/IntroPhotogrammetry/OpenDroneMap/03-ODM-georeferencing.md b/IntroPhotogrammetry/OpenDroneMap/03-ODM-georeferencing.md index da23dc5..9d50c7f 100644 --- a/IntroPhotogrammetry/OpenDroneMap/03-ODM-georeferencing.md +++ b/IntroPhotogrammetry/OpenDroneMap/03-ODM-georeferencing.md @@ -769,7 +769,9 @@ A practical strategy is to first **employ an automated filter to narrow down to ### ***Visual check of representative images for a marker*** -
+Ensuring that selected images are truly representative for each Ground Control Point (GCP) is a crucial step for accurate georeferencing. The `gcp_check.py` tool (from [Find-GCP repo](https://github.com/zsiki/Find-GCP)) offers a **user-friendly graphical interface to facilitate the visual check** of GCPs detected by `gcp_find.py`. + +
WARNING:
Proceeding with this section requires the use of Secure SHell (SSH) paired with X11 forwarding. X11 forwarding enables graphical applications run on the cluster to manifest visually on your local machine.

@@ -783,13 +785,11 @@ If the cluster doesn't permit the use of X11 forwarding and OOD also didn't work 3. Then continue with the subsequent steps of this section.
*Be sure to modify the paths to align with your local filesystem during this process.
-

- -Ensuring that selected images are truly representative for each Ground Control Point (GCP) is a crucial step for accurate georeferencing. The `gcp_check.py` tool (from [Find-GCP repo](https://github.com/zsiki/Find-GCP)) offers a **user-friendly graphical interface to facilitate the visual check** of GCPs detected by `gcp_find.py`. +
If you've followed this tutorial, you should have already cloned the Find-GCP repository (see section [Find-GCP Python utility: installation](https://geospatial.101workbook.org/IntroPhotogrammetry/OpenDroneMap/03-ODM-georeferencing#find-gcp-python-utility-installation)). As a result, the `gcp_check.py` utility would be included within your cloned repo, ready for use. -Check your SOFTWARE path on the Atlas cluster (for reference, see step 7 "Create the storage directory for custom software and GitHub repos" in section [Create env for geospatial analysis](#create-env-for-geospatial-analysis)): +Check your `SOFTWARE` path on the Atlas cluster (for reference, see step 7 *"Create the storage directory for custom software and GitHub repos"* in section [Create env for geospatial analysis](#create-env-for-geospatial-analysis)): ``` ls /project//SOFTWARE ``` @@ -803,8 +803,9 @@ FIND_GCP_PATH=/project//SOFTWARE/Find-GCP source activate geospatial ``` -**The output file of the** `gcp_find.py` **is the input file of this program.** -* `gcp_list.txt` file *(output from the gcp_find.py)* +**INPUTS:** +* `project-X` directory with the complete imagery +* `gcp_list.txt` file *(The output file of the* `gcp_find.py` *is the input file of this program.)* ``` EPSG:32611 @@ -818,14 +819,12 @@ EPSG:32611 523364.648 4779587.932 1395.735 4216 1930 R0036039.JPG 4 ``` -* `project-X` directory with the complete imagery -
WARNING:
Please be cautious: the script gcp_check.py can NOT be executed within the directory containing the input images. Instead, navigate one level up in the directory structure before running it. -

+ Let's assume you store your `gcp_list.txt` file along with your imagery at the `IMAGES/` path. If so, navigate one level up: ```