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

OPF import fails for projects with GCPs created in version 2.9 or older

 

IN THIS ARTICLE

Overview
Symptoms
Cause
Affected versions
Workaround
Notes

Overview

Starting with PIX4Dmatic 2.10, importing an OPF project may fail if it was created in PIX4Dmatic 2.9 or older and contains Ground Control Points (GCPs) whose coordinate reference system (CRS) definition is ambiguous. This primarily affects projects located in the United States, where multiple geoid models exist for the same authority code.

Symptoms

When importing an OPF project into PIX4Dmatic 2.10 or later, the import fails with an error indicating that the GCP CRS is incompatible with the project CRS.

Cause

In PIX4Dmatic 2.9 and earlier, the GCP CRS was exported in the format Auth:Code+Code ->  EPSG:32614+5773. When only one geoid model was available for that definition, PIX4Dmatic could resolve it unambiguously. However, when multiple geoid models are available — as is common for US-based coordinate systems — the definition becomes ambiguous.

PIX4Dmatic 2.10 introduces a stricter compatibility check between the GCP CRS and the project CRS during OPF import. Projects with ambiguous GCP CRS definitions fail this check.

Affected versions 

Condition Details
OPF project created in PIX4Dmatic 2.9 or older
Import attempted in PIX4Dmatic 2.10 or later
Affects Projects with GCPs located in regions with multiple geoid models (e.g., United States)

Workaround

To fix an affected OPF project, replace the GCP CRS definition with the complete WKT2 string from the scene reference frame:

  1. Locate the OPF project folder.
  2. Open the file scene_reference_frame.json and copy the full CRS definition (a complete WKT2 string that includes the geoid model).
  3. Open the file input_control_points.json.
  4. For each GCP entry, replace the existing CRS definition with the WKT2 string copied from scene_reference_frame.json.
  5. Save the file and re-import the OPF project into PIX4Dmatic 2.10.

Notes

  • This issue does not affect projects that do not contain GCPs.
  • Projects created in PIX4Dmatic 2.10 or later are exported with complete, unambiguous CRS definitions and are not affected.
  • If you are unsure whether your project is affected, try the import — the error will appear at import time and does not modify or corrupt the original OPF files.