Hello ,
I am reaching out to you as I recently began learning and utilizing Pix4Dmatic software for my mapping and surveying projects. While navigating through the software, I encountered a challenge that I am hoping you could help me with, along with a couple of related queries.
My primary issue revolves around merging multiple projects in Pix4Dmatic. Specifically, I have been attempting to merge new projects, where tentative points have been set, into a final project. However, despite ensuring that all projects are set to the same coordinate system before merging, the final output suggests that the projects are not aligned within the same project area or coordinate system. Additionally, my version of Pix4Dmatic appears to lack a specific window or feature that facilitates the merging of new projects, further complicating the process.
Furthermore, I am eager to learn more about Ground Control Points (GCPs) and tie points within the Pix4Dmatic environment. While I understand their significance in achieving accurate georeferencing and alignment, I would appreciate further clarification on how to effectively utilize them within my projects.
Thank you
Can you tell us which version of the software you have been using? You can see the version in the bottom left corner of the welcome view. I’d recommend to download version 1.58.1 here: Download Pix4D software
Also, could you show some screenshots of the error messages you get? or of the resulting project you have? This will help us understand the context of your project better.
You do have overlap between the projects you’ve merged, right?
Thank you very much for your prompt response .
The version of the software is 1.47.1 , I will try to update into the mentioned version.
Yes I do have overlap between the projects after merged. ( i attached screenshots ).
It looks like your subprojects are not located at the same spot (i.e. either by having the same GCPs in both projects, by having two RTK/PPK projects,…). In such cases, you need to create min 3 MTPs in each project at the same spot. These will be used for the “register” step in the merge procedure, so that they end up in the same spot. More details in the article I linked above.
Thank you very much , it worked . but I faced other issues , after merging the (mesh) the images is not appear or the visibility is not clear like as individual projects ( No Orthomosaic after merging) . any advices to avoid and improve this ?
this image after clabration and before add the GCPs and MTP
here after merging , no overpaling but , but images is not appear or the visibility is not clear like as individual projects ( No Orthomosaic after merging)
@ebaa289 the merging currently only merges the Automatic Tie Points (ATPs), which is the result you get after the “Calibrate” step, this explains why there is no ortho, no mesh, no dense, after you merged. You need to process these in the merged project, so that it takes the merged calibration outputs as input.
If you reoptimize, only the ATPs get reoptimized, all other already processed outputs are “Outdated”, this explains why there are orange circles next to the other outputs in the content panel.
In summary, you need to process the densification, mesh, dsm, ortho once the project was merged, or reoptimized. This is meant so that you can ensure the quality of the calibration first, which will lead to more accurate results in the rest of the process.
Thank you very much for your continued support. I managed to do it but again an issue has been experienced.
The problem I faced is the final result has 2 surfaces instead of 1. and aslo the quailty of mesh is not good.
Do you have any dvice to solve this proplem
Thank you in advance.
If there are two surfaces on the ground, it means that the calibration did not work as expected yet. This can be improved either by having the same GCPs in the projects you plan to merge, or by adding MTPs on places that are visible in both sets of images that you merge.
There are two approaches:
You can add MTPs in the merged project, reoptimize. This can work if the problem is not too big.
If that method didn’t work for some reason, I would export the marks you have made in the merged project (with the “…” at the top of the tie points table => Export marks (with absolute path! so that if you have twice the camera with the same name it knows which one it is)), then import these marks in the initial projects, reoptimize them, merge again, check if it’s ok, if not, reoptimize the merged project once more.
Thank you very much for your valuable support. It was really helpful.
I tried to create new trial projects from scratch using more MTP to avoid overlapping and ensure accuracy. I managed to calibrate and merge the projects, which is much better than the projects I shared earlier. However, I have a small inquiry: if I want to calculate the project’s area, is there any automatic tool to do that, or should I use the polygon selection from the toolbox?
Also, there is still overlapping in some small areas. If I want to check the distance within the overlapping areas, how should I do that?
The polygon tool would be the right thing to do here:
and then you can see the details of the measurement in the properties panel on the right:
Note: based on your screenshot it seems that you’re on a relatively old version of PIX4Dmatic. I would encourage you to update to the newest preview build (and next week we will release a new stable version). That way you have all the new developments. You can click on the “stable release available” notification at the top right of your screen or download here: Download Pix4D software
As for this, when you say “overlap”, do you mean “double surfaces” ? If that is the case, it means the calibration was not yet successful in these areas and you should try to fix them as described above. If you mean something else with overlap, please provide more context. Thanks!
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.