This error is expected for outputs having a significant size and/or a complex geometry. In this case, the tiling process failed, meaning that the generated 2D output could not be split into smaller web maps (tiles) for several zoom levels and, for this reason, the output cannot be displayed. The output has been generated and indeed it can be downloaded from the Files >Results page of the project, but the file is too big/complex to be displayed on the 2D view of Pix4Dcloud.
So far, these are the variables that seem to be impacting the tile generation speed:
The significant size of the file (large surface and/or high resolution, a large number of points).
The complex geographic transformation from the project coordinate system to WGS84 that is used on web maps.
Corridor projects.
The multiple-blocks project, with not homogeneous tiles.
a) Some proposed solutions if you want to keep the same resolution:
The file can be split into multiple parts with some third-party software (here a link that shows how to do that) and then uploaded again in different separate projects on Pix4Dcloud.
The file can be replaced with a smaller one.
A processing area can be defined in Pix4Dmapper before uploading the project to Pix4Dcloud for processing.
b) If you don’t need the full resolution for the visualization, reducing the size of the orthomosaic itself:
By reducing its resolution in Pix4Dmapper before uploading to Pix4Dcloud (if the project was uploaded for processing from Pix4Dmapper)
On the Menu bar in Pix4Dmapper, click Process > Processing Options…
Select the processing step 3. DSM, Orthomosaic and Index.
Select the tab DSM and Orthomosaic.
In the section Resolution , increase the resolution to multiples of the GSD or to a customized resolution [cm/pixel].
After processing on Pix4Dcloud
Alternatively, you can download the orthomosaic from the Pix4Dcloud and reduce its resolution in QGIS:
You can sub-sample the orthomosaic following these steps:
Right-click on the orthomosaic layer in the Layers panel. Then click Export > Save As…
Select the option Rendered image , choose a destination folder and define a lower horizontal and vertical resolution, which by default is the current layer resolution. You can select the option “Add saved file to map” to check the visual difference in QGIS itself. Then click OK.
Resizing the orthomosaic is not an option because I don’t want to lose quality.
The proces area is already been set by the project boundary, so it can’t be smaller
Split the orthomosaic into 3 or 4 parts for example can’t be done because this orthomosaic is part of a series of measurements so I can not make a new site because the compare function wouldn"t work anymore
So I hope that you have an 4th option ? Because the things that you pointed out doesn"t solve the problem…
Reducing the resolution by half (ie 4cm to 8cm) will reduce the file size by a factor of 4. So you don’t have to reduce it a lot to make a big difference in file size. If you can get the final ortho to be in the 5gb range, it should work.
And I don’t think there’s a 4th option, unfortunately.
The problem is at the data from the 31th of october. At 28 august, I import the same orthomosaic from a 3th party software. Then it worked, now it doesn’t…
I could notice that, when importing the orthomosaic file of the 28th August, QGIS didn’t ask me for any coordinate system transformation definition and that the counts on the bands look like this:
whereas when I import the file of the 31st October, QGIS does ask me which coordinate system transformation I want to apply and the counts on the bands look a bit different
Therefore I don’t think the files are identical in terms of coordinate system and bands.
As said in the past, we fully support the import of photogrammetric outputs that are generated by Pix4Dmapper only at the moment, but I hope this information might be helpful to you to solve your issue.
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.