Why metadata is not a side topic in photogrammetry
Photogrammetry does not start with the point cloud. Software reads image size, camera model, focal length, sensor context, GPS positions, and sometimes XMP extensions before reconstruction. These values do not prove accuracy, but they provide important starting points for camera calibration, image alignment, and georeferencing.
Pix4D documents that its products read EXIF information and require or optionally use specific EXIF/XMP tags for project creation. OpenDroneMap uses GPS information embedded in images by default, but also supports a separate geolocation file when image GPS is missing or should be replaced by more accurate RTK or PPK data.
Practical view
Good metadata does not replace GCPs, checkpoints, or quality control. It reduces false starts and helps choose the right deliverable.
Which EXIF and XMP fields matter for 3D models
For architecture, roof, facade, and PV datasets, the most relevant fields are camera information, focal length, image size, capture date, GPS position, camera height, and optional accuracy values. XMP can add calibration values, camera model type, principal point, perspective focal length, position, orientation, or accuracy fields.
| Metadata Field | Value | Critical When | Practical Note |
|---|---|---|---|
| Camera model and image size | groups images by camera or sensor class | mixed cameras are processed as one group | Group datasets by camera, focal length, and resolution before reconstruction. |
| Focal length and sensor context | starting point for interior orientation | EXIF is missing or wrong | Agisoft notes that missing EXIF focal data can require manual focal length and pixel size input. |
| GPS position and height | initial pose and rough georeferencing | consumer GPS is treated as survey accuracy | Treat image GPS as approximate unless supported by RTK, PPK, GCPs, or checkpoints. |
| Yaw, pitch, roll | can support pose estimation and special workflows | angles are noisy or conventions are unclear | Use only when source and axis convention are known. |
| XMP calibration data | can provide better camera parameters and model type | metadata does not match the actual camera or lens | Validate against reprojection errors and visible geometry. |
What happens when metadata is missing, stripped, or wrong
Missing metadata does not automatically make a project impossible. It shifts effort and risk into processing. Without reliable focal length or sensor data, the camera must be calibrated more strongly from the images. Without GPS positions, software loses a rough spatial starting point.
Agisoft describes that Metashape may assume a default focal length when EXIF data is missing or insufficient, and that strongly wrong initial guesses can cause alignment failure. OpenDroneMap supports geolocation files with coordinate system, image name, X/Y/Z, and optional angle and accuracy fields.
| Risk Scenario | Why It Matters | Typical Symptom | Useful Countermeasure |
|---|---|---|---|
| Metadata stripped by export | Messaging, CMS tools, or editing often remove EXIF/XMP | Camera, GPS, and sequence context are missing | Provide original files from camera, drone, or memory card. |
| Wrong or changing focal length | Zoom, digital zoom, or edited images destabilize calibration | Alignment fails or edges deform locally | Separate images by camera and focal profile. |
| GPS read as proof of accuracy | Image GPS is often approximate | Model is roughly placed but not CAD-ready | Add GCPs, checkpoints, RTK/PPK files, or clear local references. |
How Voxelia checks supplied images before modeling
The metadata check answers whether an image package can become a dependable deliverable and which supporting data is useful. A viewer has different requirements than DXF/DWG, an orthophoto, BIM reference, or PV roof model.
- 01
Check originality
Review file type, resolution, compression, preserved EXIF/XMP, and filenames before reconstruction.
- 02
Build camera groups
Group images by camera, focal length, and resolution; flag problematic mixtures early.
- 03
Assess location and scale
Compare GPS, RTK/PPK files, GCPs, checkpoints, or local references with the target output.
- 04
State handoff risk
Before CAD, BIM, orthophoto, or PV export, define whether the output is georeferenced, locally scaled, or visual only.
Metadata leads to better CAD, BIM, orthophoto, and PV handoffs
The value of clean metadata appears in the next workflow. CAD needs clear units, location context, stable edges, and understandable export boundaries. BIM needs a decision between point cloud, mesh, or abstracted as-built geometry. Orthophotos need scale, coordinate context, and quality checks.
For PV planning, roof planes, obstructions, pitch, and shading geometry matter more than texture weight. Voxelia reviews, models, and hands off supplied image data with clear boundaries instead of selling a drone flight as the product.
Avoid false precision
EXIF GPS, a good-looking mesh, and high texture resolution are not proof of accuracy. Planning outputs need matching references and a clear handoff statement.
FAQ: EXIF, XMP, and photogrammetry datasets
Check image data before handoff
Turn supplied images into planning data
If you already have original images, EXIF/XMP data, measurements, or GCP files, we review which CAD, BIM, orthophoto, PV, or viewer handoff is technically realistic.