Flying a phantom 4 rtk. After running step 1 with all stock settings I am getting the calibrated cameras landing in the raycloud. Screenshot is below. Sometimes, after re-running part 1 (and adjusting the geotags to 0.02m) the project fixes itself. It doesn’t seem to happen with any pattern, but happens about 50% of the time. It happens when the p4rtk is set up in GNSS mode with no post processing (so the geotags are accurate to 5m), and when it is set up with the DJI Mobile base station, and with VRS (so the tags are corrected to 0.02m).
Has anyone else seen this before? Any thoughts on how to stop this from happening when running part 1?
If I understand correctly, the reconstructed model (automatic tie points) are on the same height as the images. Is that correct?
This is not expected and we do not have other users reporting a similar issue at the moment. Could you check if there are some issues with the camera optimization in the quality report? Is the difference between the initial and computed camera parameters close to 0% or not?
Indeed, camera optimization is not optimal and this is why the cameras end up close to the generated points.
A quick solution would be to use the All Prior option. This will fix the camera parameters and will force them to stay close to the initial values.
To get more insights into the possible root causes and solutions, I would highly recommend checking the Processing Issue -> Step 1. -> Camera Optimization section in the Pix4Dmapper troubleshooter.
Best,
We - and our partners - use cookies to deliver our services. By using our website, you agree to the use of cookies as described in our
Cookie Policy
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.