Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Troubleshooting PIX4Dcloud Processing Errors

This article outlines common processing errors encountered in PIX4Dcloud and related applications (e.g., PIX4Dcatch, PIX4Dmatic, Engine Cloud API). It includes the root causes of each error and recommended solutions.

 

IN THIS ARTICLE:

Error 10002 – An unexpected error occurred
Error 10003 – Processing exceeded available resources
Error 10101 – Failed to create cameras
Error 10410 – Processing failed
   Error 10411 – Failed to densify sparse point cloud
Error 10501 – 3D textured mesh generation failed
Error 10601 – The input data is not valid
   Error 10611 – The selected output coordinate system is not isometric
   Error 10612 – The selected output coordinate system is not projected or arbitrary
   Error 10613 – An output CRS cannot be defined without a horizontal CRS component
  Error 10614 – A geoid model or geoid height cannot be specified without a CRS vertical component
   Error 10615 – A geoid height cannot be specified with a geoid model

 

Warning: If the problem is related to the display of the outputs and not the processing (the outputs are generated, but something in the display doesn't work, or no email is sent as error notification). For more information, Output is not displayed / feature is missing in the cloud.

Error 10002 – An unexpected error occurred

Description: This generic error often indicates issues related to dataset configuration or processing limitations.

Possible causes:

  • The processing took more than 48 hours to complete.

  • Oblique images were used with a nadir processing template that lacks a defined region of interest.

  • The selected processing options could not be handled efficiently with the available resources.

  • The output coordinate reference system (CRS) is incompatible with the input data.

  • Projects from the Japanese version of PIX4Dcatch are more likely to experience this issue. In these cases, the point cloud is often split into multiple disconnected blocks, while other outputs attempt to combine into a single file.

Recommended actions:

  • Use a processing template that matches the type of images (nadir or oblique).

  • Include a region of interest if oblique images are used.

  • Check and reduce processing complexity where possible.

  • Review and adjust the output CRS to ensure compatibility with input data.

  • If the project was uploaded from PIX4Dmapper or PIX4Dmatic to be processed in PIX4Dcloud,  then try choosing at least one of the following options:
    • Reducing the quality of outputs to be produced (e.g. decrease the density of the point cloud, define a smaller pixel size for the ortho...).
    • Reducing the number of images. Sometimes, there are flying modes in some drones that capture more images than necessary to cover the area, or sometimes, the images cover a larger area, and some of them can be skipped.
    • Ensuring the strictly necessary outputs are marked for their generation.
    • Defining a processing area.

Error 10003 – Processing exceeded available resources

Description: The project could not be processed due to insufficient system resources.

Recommended actions:

Error 10101 – Failed to create cameras

Root cause: Corrupted or incompatible image metadata.

Possible causes:

  • Image files have been edited.

  • Image format is unsupported.

Recommended actions:

  • Ensure images are unaltered and in a supported format before upload.

Error 10410 – Processing failed

    Error 10411 – Failed to densify sparse point cloud

     Root cause: Calibration quality issues.

     Recommended actions:

Information: It is also recommended to review the Quality Report that is usually available in the email that is sent after the process has finished.

To analyze the Quality report, see this article.


Error 10501 – 3D textured mesh generation failed

Root cause: A fragmented dense point cloud.

Recommended actions:

  • Ensure the dense point cloud consists of a single, cohesive block before mesh generation.

Error 10601 – The input data is not valid

Description: One or more input elements are invalid or improperly configured.

Recommended actions:

  • Verify the dataset and input parameters. Reupload if necessary.

Error 10611 – The selected output coordinate system is not isometric

Recommended actions:

  • Select a valid isometric coordinate system that maintains uniform scale in all directions.

Error 10612 – The selected output coordinate system is not projected or arbitrary

Recommended actions:

  • Choose a valid projected or arbitrary coordinate system.

Instructions by product:

Error 10613 – An output CRS cannot be defined without a horizontal CRS component

Recommended actions:

  • Use a CRS that includes a horizontal component.

Reference documentation:

Error 10614 – A geoid model or geoid height cannot be specified without a CRS vertical component

Recommended actions:

  • Either remove the geoid model or specify a vertical CRS component.

Reference documentation:

Error 10615 – A geoid height cannot be specified with a geoid model

Recommended actions:

  • Remove the geoid height or use a matching geoid model within the CRS definition.

Reference documentation:

Note: When working across platforms (PIX4Dcloud, PIX4Dcatch, PIX4Dmatic, Engine API), ensure consistent and valid CRS configurations to avoid processing failures.