Does anyone know if there’s a way to temporarily crop/trim a specific area of a very large orthomosaic (5Gb) and then export the cropped area as a smaller map?
I took a survey of a golf course and the whole file is 5Gb, but I’d like to be able to export, say, holes #1-3 from this map to it’s own full-resolution map so that the resulting file is much smaller. I don’t want to process only the images for the holes I want to make a smaller map from as to avoid more processing time since the full map is already generated.
I hope I’m explaining this well enough - thanks in advance.
Draw processing area around the holes 1-3 and process step 3 again. Backup your original orthomosaic because the step 3 will override the previous outputs
I agree with Jaakko: The processing area would be the solution.
Also, please note that Pix4D generates otrhomosaic tiles (smaller parts of the orthomosaic), that you can find here: …\project_name\3_dsm_ortho\2_mosaic\tiles if you have already processed your big project.
They are small files, easier to manage in 3rd party software.
If a processing area is set on the desktop solution and then upload it to cloud it will be further considered. There is no other way to trim the project at the moment then using a processing area.
No, unfortunately, it appears that rerunning processing is the only solution. I completely agree with you. There should ABSOLUTELY be a simple polygon tool to export map areas within a processed project. The orthomosaic tiles do absolutely no good unless you really want to bother attempting to manually stitch multiple tiles in a raster image processor… That seems completely ridiculous.
Wanted to bump this because I really wish 2 years later this feature would have been added. My work around is using Global Mapper to crop the .tif and export from there. One thing that sucks about this though is the export from Global Mapper won’t upload to the Pix4D cloud for easy sharing with coworkers or clients.
I work around water in all my projects in the coastal setting so I set my processing area out wide as to hopefully include as much water as possible in the ortho. The downside is all the rough edges around the perimeter of the ortho. It really helps presentation to crop that out.
I will use my most recent project for an example. Below is the orthmosaic preview created in step 1 that does not take into account the processing area.
Pay attention to the north side you will see where it cut off part of the land and water when compared to the mosaic processed with a wide processing area to make sure all of the beach and as much of the water is displayed as possible.
I understand the processing area limits or essentially crops to the area you want BUT in this instance and the way the software creates the tiles, it does not work for me. I want the software to give me as much coverage of the water as possible because it just makes for a better product in this setting.
SO I end up bringing the ortho into Global Mapper and crop it to remove the jagged edges of where the photos overlap. I myself don’t mind those edges, I think it looks cool BUT others, particularly clients, prefer a smooth, straight edge. Note the cropped photo in GM was actually from another processing where we added more coverage.
So again, it would be really great to be able to crop the ortho inside Pix4D. I don’t see it being very different from cropping/editing the point cloud and then exporting it again with edits.
And to address the issue of the export from GM creating an error on the Pix4D cloud, I believe it is because the embedded headers in the .tif differ between the two programs even though they are still the same parameters. Maybe you can shed some light on this as well.
Thank you for your honest feedback. Adding this feature is currently not on our roadmap. We understand how important this functionality is and rest assured that we will consider your suggestion for future improvements. In the meantime, you might want to export the ortho in the free software QGIS for additional streamlining and cropping.
Well the problem I am encountering is uploading that ortho export from Global Mapper to the Pix4D cloud. Once I have it cropped the way I want for final presentation, I would like to be able to upload it to the cloud for easy sharing with coworkers and clients. It uploads just fine but then it will always give me an error in the processing and thus never display.
I’m assuming its one of two things, Pix4D has something embedded in the .tif that it doesn’t recognize it coming directly from the Pix4D software then it won’t display it or its simply a matter of the difference between the embedded header information from Pix4D and Global Mapper. Maybe a combination of the two.
So I was hopeful that you could shed some light on this and perhaps the rules of uploading to the cloud.
Hi Andrew, We recommend not doing any edits before uploading to cloud. This is because some EXIF tags might be changed while you are editing. Can you upload the Pix4D ortho and the edited ortho in google drive and share the link with me?
Also, Andrew, the processing area is not taken into account in step 1 even if you add it before step 1. For removing the jagged edges, it will work the best if you add the processing area before step 3 and then process only step 3. Can you try that?
Hie @momtanu.chakraborty, I tried your suggestion to cleaning of edges in orthomosaic, I select a processing area and runs a processing step 3 for exporting a DSM and Orthomosaic. I check after completion of step, the DSM is taken effect according to changes making in a point group But the orthomosaic is not affected. Orthomosaic is generating completely, and not with respect to point groups(I moved some points from point cloud to disabled group).
I need same changes as the DSM in the orthomosaic too. Looking for your suggestions.
If there is a processing area after processing step 2. Point Cloud and Mesh :
Results of step 1. Initial processing and step 2. Point Cloud and Mesh will not be affected.
The display of the automatic tie points and the dense point cloud will be affected.
The dense point cloud exported through the list of layers will be affected. For more information about how to export the point cloud: How to export the point cloud.
The 3D textured mesh generated after step 2. Point Cloud and Mesh will be affected.
Results of step 3. DSM, Orthomosaic and Index will be affected.
Ankit, As Kapil mentioned, Processing area is taken into account for orthomosaic if added before step 2 or 3. If you edit point cloud, The DSM should not take into consideration the deleted points. Just edit the point cloud, save the project and regenerate step 3.
The orthomosaic, will be generated based on this new DSM but takes the color from the input images. The software does not know how to color the orthomosaic when information is deleted. For example:
Imagine you delete the roof of a house. The point cloud will have a hole. However, the orthomosaic will have the roof visible. Otherwise, we should have a hole in the orthomosaic.
The only thing that you could remove/delete from an orthomosaic is moving objects like cars. If there are images that do not “see” the car, you can select such an image as a planar projection and the car gets “disappeared”. For more information: how to use planar projections.
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.
