Table in GCP/MTP Manager | Table in Basic GCP/MTP Editor |
The following actions can be performed in the table:
The table has as many rows as points in the project (GCPs / Manual Tie Points / Check Points). Each row displays information for one point.
- Number of marked images
- Label
- Type
- First coordinate
- Second coordinate
- Third coordinate
- Accuracy Horz
- Accuracy Vert
Actions on the table
This column displays the number of images on which each point is marked. The number can have the following colors:
- Black: For points that have been marked on less than 2 images.
- Green: For points that have been marked on 2 or more images.
- Red: For Manual Tie Points that have been marked on less than 2 images and for which no 3D position has been estimated. This is the case for Manual Tie Points that are added using the GCP/Manual Tie Point Manager.
This column displays the label of each point. The label column is filled:
- When importing the label from the GCP file.
- When pressing the Add Point button.
- When drawing an object in the rayCloud.
- When manually editing the label: Double click on the corresponding cell and enter the new label.
There are four possible point types:
- 2D GCP: A 2D GCP is a point that has a known 2D position in the scene and is used for the project's AAT/BBA.
- 3D GCP: A 3D GCP is a point that has a known 3D position in the scene, and that is used for the project's AAT/BBA.
- Check Point: A checkpoint is a point that has a known 3D position in the scene and is used for checking the accuracy of the reconstruction. It is not used for the project's AAT/BBA.
- Manual Tie Point: A Manual Tie Point is a point that is manually identified in several images. Its position in the scene is not known. Manual Tie Points are also created by drawing an object on the 3D View of the rayCloud. Each vertex of the object corresponds to one Manual Tie Point.
When GCPs are imported from a file, the GCPs type is automatically set to 2D GCP or 3D GCP depending on how many coordinates the points have in the imported file. When a new point is added by clicking Add Point, then the type is by default Manual Tie Point.
The point type can be defined manually: Double-click on the corresponding cell and choose the desired type from the drop-down list that appears.
The first coordinate is:
- Latitude [degree]: If the coordinate system of the GCPs is a geographic coordinate system.
- X [m]: If the coordinate system of the GCPs is a projected coordinate system. The unit is given in meters.
- X [feet]: If the coordinate system of the GCPs is a projected coordinate system. The unit is given in feet.
- Arbitrary X [m]: If the coordinate system of the GCPs is defined by the user (local coordinate system). The unit is given in meters.
- Arbitrary X [feet]: If the coordinate system of the GCPs is defined by the user (local coordinate system). The unit is given in feet.
The coordinate columns are filled:
- When importing the coordinates from the GCP file.
- When manually editing the table: Double click on the corresponding cell and type the coordinate.
The second coordinate is:
- Longitude [degree]: If the coordinate system of the GCPs is a geographic coordinate system.
- Y [m]: If the coordinate system of the GCPs is a projected coordinate system. The unit is given in meters.
- Y [feet]: If the coordinate system of the GCPs is a projected coordinate system. The unit is given in feet.
- Arbitrary Y [m]: If the coordinate system of the GCPs is defined by the user (local coordinate system). The unit is given in meters.
- Arbitrary Y [feet]: If the coordinate system of the GCPs is defined by the user (local coordinate system). The unit is given in feet.
The coordinate columns are filled:
- When importing the coordinates from the GCP file.
- When manually editing the table: Double click on the corresponding cell and type the coordinate.
The third coordinate is:
- Altitude [m]: If the coordinate system of the GCPs is a geographic coordinate system.
- Z [m]: If the coordinate system of the GCPs is a projected coordinate system. The unit is given in meters.
- Z [feet]: If the coordinate system of the GCPs is a projected coordinate system. The unit is given in feet.
- Arbitrary Z [m]: If the coordinate system of the GCPs is defined by the user (local coordinate system). The unit is given in meters.
- Arbitrary Z [feet]: If the coordinate system of the GCPs is defined by the user (local coordinate system). The unit is given in feet.
The coordinate columns are filled:
- When importing the coordinates from the GCP file.
- When manually editing the table: Double click on the corresponding cell and type the coordinate.
The GCP horizontal accuracy defines the horizontal accuracy value (Accuracy Horz). The horizontal accuracy refers to the first and second coordinates (latitude, longitude, or X, Y).
- Very accurate GCP horizontal coordinates have lower accuracy values. e.g. 0.02m
- Less accurate GCP horizontal coordinates have higher accuracy values. e.g. 1.23m
GCPs with very accurate, lower values will be given more influence over less accurate, higher value GCPs during step 1. Initial Processing. The accuracy is a value between 0.001 and 10'000 meters.
To edit the horizontal accuracy of one GCP, double-click on the corresponding cell and enter the new value. For more information about editing the horizontal accuracy for multiple GCPs: Select multiple points.
The GCP vertical accuracy defines the vertical accuracy value (Accuracy Vert). The vertical accuracy refers to the third coordinate (altitude / Z).
- Very accurate GCP altitude coordinates have lower accuracy values. e.g. 0.02m
- Less accurate GCP altitude coordinates have higher accuracy values. e.g. 1.23m
GCPs with very accurate, lower values will be given more influence over less accurate, higher value GCPs during step 1. Initial Processing. The accuracy is a value between 0.001 and 10'000 meters.
To edit the vertical accuracy of one GCP, double-click on the corresponding cell and enter the new value. For more information about editing the vertical accuracy for multiple GCPs: GCP / Manual Tie Point Table.
Article feedback (for troubleshooting, post here instead)
0 comments