Frequently asked questions
What is QCALVIEW primarily for?#
Its primary purpose is to calibrate a photographic view against geographic data and use that calibrated camera to project QGIS layers correctly in perspective.
Is QCALVIEW a photomontage generator?#
It can support photomontage and visual-simulation workflows, but it is broader than that. Its core value is the geometric relationship between viewpoint, camera, terrain, image and GIS data.
Is QCALVIEW a QGIS 3D view?#
No. A QGIS 3D view creates a 3D scene. QCALVIEW starts from a specific observer/camera geometry and can use a real photograph as the visual reference. Raster/vector data are projected through that calibrated viewpoint.
Is QCALVIEW a viewshed/ZVI tool?#
Not primarily. QCALVIEW projects GIS information from a controlled observer/camera geometry. A conventional viewshed or ZVI remains the appropriate tool when a territorial visibility surface is required.
Which projection should I use?#
- ordinary rectilinear photo → PINHOLE;
- cylindrical panorama → CYLINDRICAL;
- spherical 360 × 180 panorama → EQUIRECTANGULAR.
If the fit is good in the centre but increasingly wrong toward the edges, verify the projection and HFOV before adding offsets.
Does PINHOLE include lens distortion?#
No. It is an ideal rectilinear/pinhole model. Correct significant lens distortion before calibration.
What is HFOV?#
Horizontal field of view: the angular width of the scene represented by the image.
Is focal length enough to know HFOV?#
Only if the effective sensor/image geometry and crop are known. A stitched or cropped image may have an effective HFOV different from the nominal lens metadata.
What is qcv_alt?#
It is the camera height/Z parameter used by QCALVIEW. In the normal terrain-based workflow it represents camera height above the terrain sampled at the viewpoint. Do not automatically interpret it as absolute altitude.
Why is my projected horizon vertically wrong?#
Check:
- DEM and vertical reference;
- camera height;
- pitch;
- viewpoint position;
- projection/FOV.
Vegetation/buildings visible in the photo but absent from the DEM can also make the photographic skyline differ locally.
Why does the centre fit but the edges do not?#
Common causes:
- wrong HFOV;
- wrong projection type;
- lens distortion;
- panorama stitching/crop assumptions.
Why should I avoid large image offsets?#
Offsets can hide a more fundamental calibration error. Solve viewpoint, projection, FOV and orientation first.
What does terrain occlusion include?#
Terrain from the selected DEM. It does not automatically include photographed vegetation or buildings.
Can vegetation/buildings be used as screens?#
Why use schematic view?#
Because many questions are geometric rather than photographic. Schematic view is useful for:
- synthetic viewpoints;
- grid analysis;
- pre-field work;
- meetings;
- camera states that no longer correspond to the source photograph.
Should I enable Earth curvature?#
For long-distance studies, usually yes if that matches the study method. For short distances its effect is small. The setting should be documented when relevant.
Why use GeoPackage instead of Shapefile?#
Why are some layers missing after switching a QGIS theme?#
Check:
- theme visibility;
- whether the layer belongs to the theme;
- QCALVIEW representation settings;
- whether the saved viewpoint visual state is being restored;
- whether a layer has been temporarily disabled/changed in QGIS.
If toggling a layer restores it, refresh the view and verify theme/layer state before assuming a geometry problem.
Where can I find every generated column name?#
See Attribute-field reference. It is intentionally placed directly after the glossary in the web manual because the output schemas are extensive.
