I. Settings
A. Positioning/georeferencing: - Positioning mode: Use photo positioning dataB. Main settings: - Key point density: Normal - Pair selection mode: Default - Component construction mode: OnePass - Photo downsampling: 50%C. Estimation policies: - Tie points: Compute - Position: Compute - Rotation: Compute - Photogroup estimation mode: OnePass - Focal length: Adjust - Fisheye focal: AdjustFisheyeFocalSymmetric - Principal point: Adjust - Radial distortion: Adjust - Tangential distortion: Keep - Fisheye distortion: AdjustFisheyeDistortion_01xx0
II. Results
A. Global:- Errors
NB: Horizontal and vertical errors are given according to the following spatial reference system: WGS84- Connections
B. Per photo:- Automatic tie points
- Connections
C. Per point:- Automatic tie points:
Thanks Felix.But I do not understand what is the problem and the solution.The problem is the data set?Or is the program that makes the AT wrong?
When I have only photos without AT, and exported to KML, the photos are positioned correctly in Google Earth. So where the error is in the GPS coordinates?
How I can change corrected GPS tags if they are not correct?Is there any way to make a correct AT without using the GPS position of the photos? Only control points?
Thank you very much.
El 21 de julio de 2016 a las 12:25 Felix James <bounce-6CB05797-2EE4-4758-901F-687CA096CD6F@communities.bentley.com> escribió: Message from Bentley CommunitiesFelix JamesHi Asier, Thanks for sharing the images. We managed to reproduce the same issue using your dataset. The pose of the cameras after AT is far away from their initial position. We believe the issue comes from the GPS tags of the images. They were, in some way, interchanged or maybe they are just wrong. Because of this the Block-AT is not “correctly” positioned after AT. The AT is computed independently and adjusted on wrong GPS tags, these GPS tags must be corrected before being used. View onlineIf you encounter issues clicking "View online", check here. You received this notification because you are subscribed to the forum. To unsubscribe from only this thread, go here. To unsubscribe from a forum, please see this note.Flag this post as spam/abuse.
Hi Asier, Thanks for sharing the images. We managed to reproduce the same issue using your dataset. The pose of the cameras after AT is far away from their initial position. We believe the issue comes from the GPS tags of the images. They were, in some way, interchanged or maybe they are just wrong. Because of this the Block-AT is not “correctly” positioned after AT. The AT is computed independently and adjusted on wrong GPS tags, these GPS tags must be corrected before being used.
View online
If you encounter issues clicking "View online", check here.
You received this notification because you are subscribed to the forum. To unsubscribe from only this thread, go here. To unsubscribe from a forum, please see this note.
Flag this post as spam/abuse.
Hi Aisier
You say "When I have only photos without AT, and exported to KML, the photos are positioned correctly in Google Earth",
However, they are not. See the screenshots below:
2 photos (123 and 145) captured above the same area
A view of their relative GPS position before AT in Google Earth:
You can see here that these GPS tags are not correct.
They acquisition pattern may at first look ok in Google Earth but the tags are not correctly linked to photos and we have no idea of how the are wrong (nor how they can be fixed. The problem does not come from ContextCapture but, more likely from the acquisition system.
A workaround could consist of using a "fake" GCP derived from Google Earth (you would need to identify at least 3 GCP and their coordinates in Google earth before using them in ContextCapture for rigid geo-registration) however, this workflow is a bit inaccurate.
Answer Verified By: Felix James