# Misalignment at edges between merged subprojects **URL:** \ **Category:** PIX4Dmapper\ **Created:** [January 26, 2021, 4:59pm UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363 "2021-01-26T16:59:16Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jehammar](https://avatars.discourse-cdn.com/v4/letter/j/ce73a5/32.png) [@jehammar](https://community.pix4d.com/u/jehammar)\ **Post date:** [January 26, 2021, 4:59pm UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/1 "2021-01-26T16:59:16Z")
Dear Community, I have a bigger project of ca 22 000 images (1.9 TB) which I am trying to process into one orthomosaic and digital surface model (DSM). I split up the project into 12 subsets using Pix4D with ca 2000 images in each subset. Then my workflow was: 1. Do initial processing with all subsets 2. Merge projects: - Add Manual Tie Points (MTP) in Project A - Add the same MTP in Project B (name them the same) - Reoptimize in each project - Create new project with the option “Project Merged from Existing Projects” - Choose to treat objects with the same name as he same - Click finish - Reoptimize - Further Processes I tried to merge 5 of the subsets and run all steps and when I started to inspect the dense point cloud I realized there are some problems. Sometimes at the border between the subsets there is a misalignment and a gap in the pointcloud: Here we can see an area between to subsets: ![Offset_1.PNG](https://global.discourse-cdn.com/pix4d/original/2X/c/c41f72200829ff877642ade675902214b88bb838.jpeg) If we zoom in we can see that the images were taken under different light conditions: ![Offset_2.PNG](https://global.discourse-cdn.com/pix4d/original/2X/8/88b4178ec58de93e8e915f5b38b3231df065d0b4.jpeg) And here the misalignment becomes visible: ![Offset_3.PNG](https://global.discourse-cdn.com/pix4d/original/2X/0/0fee0e0c72adbee8d9d68a07b3527184d0238ae8.jpeg) Here is another example at the road: ![Offset_road.PNG](https://global.discourse-cdn.com/pix4d/original/2X/5/56f0c2e6ced96c78fe0b72dfcd041f6cb109caf4.jpeg) ![Offset_road.2PNG.PNG](https://global.discourse-cdn.com/pix4d/original/2X/0/027a58202248265c8e685f849f9a7bdf691ed002.jpeg) I guess this misalignment will cause artefacts in the DSM and since my goal is to to DSM analysis I would like the DSM to have as high accuracy as possible. Any ideas what can be the problem here and how can I solve it? Are the images taken in sun too different from the ones taken under cloudy conditions? Would it help to add more MTP in the errorous areas? Should I better perform all steps on each subset and then merge them in another program? Btw I cannot provide a quality report because Pix4D crashes every time I try. Thanks in advance 🙂 ---
**Author:** ![Christina](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/christina/32/303_2.png) [@Christina](https://community.pix4d.com/u/Christina)\ **Post date:** [January 27, 2021, 8:42am UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/2 "2021-01-27T08:42:40Z")
Hello! 22000 images! wow! Very challenging! Maybe you want to give it a try with our new product [Pix4Dmatic](https://www.pix4d.com/product/pix4dmatic-large-scale-photogrammetry-software) that is optimized for very large projects. It is possible that Pix4Dmatic processes it in one project. Regarding Pix4Dmapper, adding more **common** manual tie points (MTPs) especially in the areas with different light conditions will definitely help. Here you can see how MTPs helped with a different light conditions dataset: > **[Some Areas of the DSM have a lot of Noise](https://support.pix4d.com/hc/en-us/articles/202561119-Some-Areas-of-the-DSM-have-a-lot-of-Noise)** > > Error > Some areas of the DSM have a lot of noise. Instead of representing correctly the area, the DSM has rough distortions / noise. >   > Description > The Densified Point Cloud and consequently the DSM,... Also, merging 2 projects at a time is recommended (instead of merging 3 or more projects at a time) ---
**Author:** ![ole](https://avatars.discourse-cdn.com/v4/letter/o/fbc32d/32.png) [@ole](https://community.pix4d.com/u/ole)\ **Post date:** [January 27, 2021, 8:49am UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/3 "2021-01-27T08:49:17Z")
Guessing your errors come from reflections due to sunlight. I find that sundlight (especially a strong, but low sun) make a lot more noise in the pointcloud. ![bilde](https://global.discourse-cdn.com/pix4d/original/2X/9/9877ee68260bd52c699bab337f1214ac9841e387.png) However I, probably like you, don’t have the luxury to choose when to fly. Generally I find that the actual gound is at the same hight, so you just have to remove unwanted noise. This is ofcourse rather a pain for you with that amount of data. I wish there was a tool for selecting an area, thell the program that this is a mostly flat or uniform hight/incline area, and have it remove the worst noise. ---
**Author:** ![ole](https://avatars.discourse-cdn.com/v4/letter/o/fbc32d/32.png) [@ole](https://community.pix4d.com/u/ole)\ **Post date:** [January 27, 2021, 8:53am UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/4 "2021-01-27T08:53:44Z")
I don’t think Pix4Dmatic will slove the noise issue, as it does that same as Pix4Dmapper. The issue is in the limitations of the software as it needs similar lighting conditions. ---
**Author:** ![jehammar](https://avatars.discourse-cdn.com/v4/letter/j/ce73a5/32.png) [@jehammar](https://community.pix4d.com/u/jehammar)\ **Post date:** [January 27, 2021, 10:31am UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/5 "2021-01-27T10:31:56Z")
That would be a very useful tool! ---
**Author:** ![jehammar](https://avatars.discourse-cdn.com/v4/letter/j/ce73a5/32.png) [@jehammar](https://community.pix4d.com/u/jehammar)\ **Post date:** [January 27, 2021, 10:54am UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/6 "2021-01-27T10:54:30Z")
Hello Christina, I think I heard somewhere that Pix4Dmatic is not yet available for 16-bit-images? I tried to merge only two subsets with additional MTP at the road part. Here is a screenshot of the point cloud in Pix4D: ![sub5_10.PNG](https://global.discourse-cdn.com/pix4d/original/2X/2/271df0ded356e9960f54cfb004be9f8b4224ecf9.jpeg) in the attachment you find the quality report of two merged subsets with MTP added to the road part. In the preview there seem to be a lot of noise as described in the link you sent. And there is also a clear line artefact along the edge between the subsets: ![image](https://global.discourse-cdn.com/pix4d/original/2X/5/5cd1b43fc3a764bf90fdd86a0d877f60b2888890.jpeg) So adding MTP to noisy or errorous areas doesnt seem to help so much and would be very time consuming if I have to do it for all subsets. Any processing options I could change maybe? Best, [Merge\_5\_10\_report.pdf](https://community.pix4d.com/uploads/short-url/hLt7pikd8Ex0R3p5sxHGfe4NddV.pdf) (2.2 MB) ---
**Author:** ![Christina](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/christina/32/303_2.png) [@Christina](https://community.pix4d.com/u/Christina)\ **Post date:** [January 27, 2021, 5:00pm UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/7 "2021-01-27T17:00:28Z")
> I think I heard somewhere that Pix4Dmatic is not yet available for 16-bit-images? Here you can see the compatible cameras for Pix4Dmatic: > **[Supported cameras - PIX4Dmatic](https://support.pix4d.com/hc/en-us/articles/360037744571-Which-cameras-are-supported-in-Pix4Dmatic)** > > PIX4Dmatic can process images captured by practically any camera as long as the images contain the necessary EXIF/XMP (metadata) tags. > > > > Note: Multispectral and thermal cameras are not compatible ... Thanks for sharing more info! It helps us to better understand the case. I suggest you process with the 3D Maps template: > **[Processing Options Default Templates - PIX4Dmapper](https://support.pix4d.com/hc/en-us/articles/205319155-Processing-Options-Default-Templates)** > > Here is a description of the available processing templates: > > > > > Processing Options Template > > > Characteristics > > > Outputs generated > > > > Standard >   >   > > > 3D Maps > Generates a 3D map (point cloud, 3D text... That will process with _Full image scale_ and some other options that I believe are better for your project such as _Use MTPs_ ![options](https://global.discourse-cdn.com/pix4d/original/2X/1/13b78e98d9d87ec49614817749dd1cde28eae130.png) How accurate are your images’ coordinates? Do you use an RTK drone? ---
**Author:** ![Christina](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/christina/32/303_2.png) [@Christina](https://community.pix4d.com/u/Christina)\ **Post date:** [January 27, 2021, 5:04pm UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/8 "2021-01-27T17:04:26Z")
Also, I suggest you mark some of your MTPs on more images. Some are marked on only 2 images. I recommend min 5 images ---
**Author:** ![Andrew\_Milanes](https://avatars.discourse-cdn.com/v4/letter/a/a4c791/32.png) [@Andrew\_Milanes](https://community.pix4d.com/u/Andrew_Milanes)\ **Post date:** [January 28, 2021, 4:55am UTC](https://community.pix4d.com/t/misalignment-at-edges-between-merged-subprojects/16363/9 "2021-01-28T04:55:45Z")
Why don’t you change how you split the projects? Splitting by flight results in different radiometry on adjacent projects which is giving you the problems when merging. Try the opposite approach. Use half of the images from two adjacent flights in a single project. Try to split the projects within the same flight so the radiometry at the adjoining edges is the same. Pix4DMapper may be able to handle the large radiometric variability better within a single project as opposed to across projects.