Limitations and good practice
QCALVIEW is designed to make visual/geographic relationships explicit. Its results are only as defensible as the input geometry, camera calibration and methodological assumptions.
Camera and image limitations#
Lens distortion#
PINHOLE is an ideal rectilinear model. Significant lens distortion should be corrected upstream.
Unknown crop/stitching#
A cropped or stitched image may not match nominal EXIF focal/FOV assumptions. Calibrate the image actually used.
Projection mismatch#
A wrong projection type can create systematic errors that orientation/offset controls cannot correctly solve.
Terrain limitations#
DEM is not automatically a surface model#
A DEM/MNT normally represents terrain, not every tree/building.
Do not assume photographed vegetation or buildings are part of terrain occlusion unless the elevation source explicitly includes them or they are represented separately.
Resolution matters#
A coarse DEM can miss narrow ridges/cuts and can shift horizon geometry. Choose terrain data appropriate to study scale.
Vertical datum/source consistency#
Observer/target elevations and DEM should be coherent. Unexpected vertical shifts may come from datum/source inconsistency rather than camera pitch.
Vector-screen limitations#
The required-screen-height calculation treats the screen as a controlled geometric vertical barrier at the supplied line/polygon location.
For vegetation, real screening also depends on:
- density;
- gaps;
- species/form;
- seasonal foliage;
- establishment time;
- maintenance;
- observer motion/parallax.
The calculated height is a geometric design indicator, not a guarantee of opacity.
Target representation limitations#
A simple vertical target height is an abstraction.
For complex objects:
- use meaningful geometry when supported;
- sample line/polygon targets adequately;
- interpret physical visible height in relation to the target type.
For a wind turbine, for example, “visible height” does not automatically encode rotor orientation or every blade position unless specifically represented by the target model.
Viewshed comparison#
A viewshed answers a broad territorial visibility question efficiently. QCALVIEW is valuable when the study asks more specific questions about how visibility occurs.
QGIS theme/state limitations#
A QGIS map theme controls layer visibility/style, while QCALVIEW can also store viewpoint-specific visual representation state.
When debugging a missing layer, separate:
- QGIS layer/theme visibility;
- QCALVIEW representation settings;
- saved viewpoint state;
Panorama seam#
EQUIRECTANGULAR/cylindrical views have wrap/seam behaviour that does not exist in ordinary rectilinear images. Geometry crossing ±180° may need duplication/splitting internally. Judge the final visual continuity, not raw intermediate coordinates.
Performance#
Expensive combinations include:
- many viewpoints × many targets;
- dense target sampling;
- fine terrain sampling;
- long analysis distances;
- heavy raster draping;
- large scenario Cartesian products.
Validate a small sample first.
Reproducibility checklist#
For a professional study, record:
- QCALVIEW version;
- QGIS version;
- project CRS;
- source/accuracy of viewpoint position;
- camera height convention;
- photograph/crop/projection;
- HFOV/VFOV;
- yaw/pitch/roll;
- DEM source/resolution/date;
- Earth-curvature setting;
- target height source;
- screen height source;
- sampling settings;
- distance/height search limits;
- scenario/theme name;
- classification thresholds used in published maps.
Current scope#
The public 40.21 documentation covers viewpoint calibration, photographic and schematic projection, terrain-aware rendering, vector/raster display, panoramas, monoplotting, QGIS themes and exports.
