Hi,
I have a problem in Pix4DCloud. After processing the GCP’s are not in the right position or ortho image is not in the right position, I don’t know.
I attached the Quality report and processing_task.
Thank you.
processing_task.log (2.9 MB)
Hello @sdprelipceanu,
Thank you very much for your patience and for sharing the information along with the dataset’s log file and quality report.
The reconstructions of PIX4Dcloud dataset 1755179, which has since been deleted, are not aligned with your ground control points because PIX4Dcloud’s GCP detector did not identify any of the ground control points in any of the images. Since none of the GCP targets were identified in any images, all of the reconstructions, i.e., point cloud, 3D textured mesh, digital surface model, and orthomosaic, are all georeferenced with the meter-grade geotags measured by the drone.
We are still working on identifying the root cause of the unexpected behavior. However, you can count on us to share more information as soon possible after the investigation has progressed to its next stage.
As of this message, given the success of your one of your most recent PIX4Dcloud datasets that represent the same project area, how PIX4Dcloud’s GCP detector is expected to behave, and the state of the investigation, we recommend that you continue to fly your drone and capture images in practically the same way. Kudos on the flight plan, image quality, GCP targets and distribution; they struck me as top notch.
The images and dataset consumed by PIX4Dcloud dataset 1755179 have been returned to your PIX4Dcloud balance so you can use them to generate another set of reconstructions.
Please let us know in the meantime if you have any questions or additional information to share about the misalignment of PIX4Dcloud dataset 1755179.
Hi @sdprelipceanu,
Thanks again for waiting.
To make sure you have a reconstruction of the project area from Friday, February 9, a new set of reconstructions were exceptionally generated and georeferenced with the images and GCPs of PIX4Dcloud dataset 1755179.
The new set of more accurately georeferenced reconstructions is avaialble in PIX4Dcloud dataset 1760356. You can also access the dataset at PIX4Dcloud when you log in with the same Pix4D account you used to create the original dataset.
We are still investigating the root cause of why the ground control point targets were not automatically identified. You can count on us to send you another update as soon as possible after the investigation progresses.
As I already mentioned, we recommend that you continue to fly your drone and capture images in practically the same way.
Please let us know in the meantime if you have any questions or additional information to share about the misalignment of PIX4Dcloud dataset 1755179 or the newly created dataset, i.e. 1760356
Hi @sdprelipceanu,
The root cause of why the orthomosaic and other reconstructions of PIX4Dcloud dataset 1755179 were not aligned with your ground control points has been identified.
In the meantime, to make sure your orthomosaic is aligned with your ground control points the next time you process a dataset with PIX4Dcloud, please enable PIX4Dmapper compatibility in the project creation wizard.
Please let us know if you have any questions about creating and processing a PIX4Dcloud dataset that is similar to 1755179 and has ground control points.
Thanks again for your patience and for sharing the information.
Hi Andrew,
Thank you very much for your response.
Clear for me.
I’ll follow your advices
I saw the your email now, but I want to please help me with another project to fix it, if it’s possible
Here you have the project no
189572-Project-2024-02-28T00_47_39.714Z
Next time i’ll check the box for Pix4DMapping, probably this is the issue from what I saw in your email compared with my work.
Thank you very much, I’m waiting for your response about the last project.
Sebastian Prelipceanu
processing_task (1).log (2 MB)
Sorry,
Forgot to mention that in the last project pix4DCloud did read the GCP for points 529,530,533
If you can help me with that, it will be great.
Thank you
Hi @sdprelipceanu,
Thanks for sharing the detailed information.
There are some meaningful differences between the original PIX4Dcloud dataset you shared with us at the beginning of this thread, i.e., 1755179 and your more recent PIX4Dcloud dataset, i.e., 1770968.
To make sure we keep track of everything, you’ll receive a separate email with more information about your more recent dataset.
Good morning @sdprelipceanu.
I’m happy to report that PIX4Dcloud’s image processing pipeline has been updated to ensure that it detects your ground control point targets the next time you process a dataset that is similar to the original dataset that exhibited the unexpected behavior, i.e., PIX4Dcloud dataset 1755179.
With that in mind, the next time you create and process a PIX4Dcloud dataset, do not enable the PIX4Dmapper compatibility checkbox. By not enabling the checkbox, not only are you expected to receive your results in less time, but you’ll also be able to select the vertical coordinate reference system of your reconstructions.
Please let us know if you have any questions and thanks again for your contribution to the investigation.
This topic was automatically closed after 9 days. New replies are no longer allowed.