QCALVIEW40.21
User documentation · QCALVIEW 40.21

Attribute fields

QCALVIEW

Attribute-field reference

This page lists the persistent and interactive attribute fields documented for the public 40.21 release.

The tables distinguish:

  • persistent viewpoint fields — stored on the QCALVIEW viewpoint layer;
  • scenario fields — used to drive repeatable variants;
  • internal/cache fields — normally not edited manually;
  • legacy/import aliases — recognized for compatibility but not the preferred output names.

Field names are shown exactly as used in the data. They are intentionally not translated.

Persistent QCALVIEW viewpoint fields#

These are the canonical camera/viewpoint fields managed by QCALVIEW.

Field Meaning Typical values / units
qcv_id User-facing viewpoint identifier text
qcv_img Source image path file path/text
qcv_mode View source/mode AUTO, PHOTO, SCHEMA
qcv_proj Camera projection PINHOLE, CYLINDRICAL, EQUIRECTANGULAR
qcv_360 Full-360 flag 0/1
qcv_yaw Horizontal camera orientation degrees
qcv_pitch Vertical camera orientation degrees
qcv_roll Rotation about view axis degrees
qcv_hfov Horizontal field of view degrees
qcv_vfov Vertical field of view degrees
qcv_ahf Automatic-HFOV flag/state integer flag
qcv_alt Camera height/Z used by QCALVIEW; with terrain normally observer height above local terrain metres
qcv_ofh Horizontal image offset pixels or percentage according to qcv_ofmd
qcv_ofv Vertical image offset pixels or percentage according to qcv_ofmd
qcv_ofmd Offset mode 0 = pixels, 1 = percentage
qcv_mdst Maximum projection/analysis distance associated with viewpoint metres; 0 may mean no explicit limit depending on context
qcv_iw Image/view width pixels
qcv_ih Image/view height pixels
qcv_foc Focal length mm
qcv_sens Sensor width mm
qcv_stat Optional status field text
qcv_note User note text
qcv_upd Last-update timestamp/text text/date representation

Stable internal viewpoint identity#

Field Meaning
qcv_uid Stable internal QCALVIEW viewpoint identity used to track a feature more reliably than FID. Normally hidden and not manually edited.

Legacy/import aliases for viewpoint fields#

QCALVIEW can recognize several historical/alternate column names when reading layers. New work should use the canonical names above.

Canonical field Recognized aliases
qcv_mode qcv_source, qcv_src
qcv_alt qcv_cam_h
qcv_ofh qcv_off_h
qcv_ofv qcv_off_v
qcv_ofmd qcv_off_mode, qcv_ofmod
qcv_mdst qcv_maxdist, qcv_maxdst
qcv_iw qcv_img_w
qcv_ih qcv_img_h
qcv_foc qcv_focal
qcv_sens qcv_sensorw, qcv_sensw
qcv_stat qcv_status
qcv_upd qcv_updated, qcv_updatd

Internal FOV/cache fields#

These fields are used internally to store auxiliary QCALVIEW geometry. Do not edit them manually unless you are debugging the plugin.

Field Purpose
qcv_fov_full Cached full FOV geometry/state
qcv_fov_symbol Cached FOV symbol geometry/state
qcv_fov_ring Cached ring geometry/state
qcv_fov_axis Cached view-axis geometry/state
qcv_fov_equi Cached equirectangular FOV geometry/state

Related live/internal variants may appear with suffixes such as _live. These are implementation details rather than persistent user fields.

Monoplotting point-layer fields#

When monoplotting creates point outputs, fields include:

Field Meaning
mp_id Monoplotting record identifier
src_mode Source/click mode
src_pdv Source viewpoint identifier/reference
src_name Source name
dist_m Distance to monoplot point
dist_h_m Horizontal distance
az_deg Azimuth
z Result elevation used by output
z_raw Raw sampled elevation/value
z_view Elevation/view-adjusted value
z_mode Elevation mode
curv_on Earth-curvature flag
proj Projection
hfov HFOV at creation time
vfov VFOV at creation time
yaw Yaw at creation time
pitch Pitch at creation time
roll Roll at creation time
created Creation timestamp
label User/display label
is_ctrl Whether point is marked/used as a control point

Monoplotting ray-layer fields#

Field Meaning
mp_id Monoplot record ID
src_pdv Source viewpoint
dist_m Ray/result distance
az_deg Ray azimuth

Interactive occlusion/screen diagnostic fields#

The interactive schematic/occlusion tool may create or expose diagnostic records with fields such as:

Field Meaning
hedge_fid Screen/hedge feature FID
target_fid Target feature FID
target_h Target height
h_geom Height derived from geometric line-of-sight relation
h_nominal Nominal/current screen height
crown_ratio Schematic vegetation crown ratio where applicable
z_ground Ground elevation at intersection
z_los Line-of-sight elevation at intersection
dist_cam Distance from camera
part Geometry part index/reference
segment Segment index/reference
first_hit First-intersection flag
controls_h Whether this hit controls the required height
h_source Source of screen height

Fields you may see in project-state/style logic but should not treat as data outputs#

QCALVIEW also stores visual/style information in project state, for example layer visibility, opacity, labels, 2.5D settings, schematic symbol parameters and QGIS theme/style names. These are not ordinary analytical attribute columns and are therefore not listed as result fields here.

How to use this reference#

When a map or table is unclear:

  1. identify which algorithm created the layer;
  2. find that algorithm section above;
  3. verify units and aggregation logic;
  4. if using a synthesis field, check the associated controlling-target field;
  5. treat NULL separately from zero;
  6. keep the detailed relationship table when auditability matters.

Interactive screening result field#

Field Meaning
qcv_h_req Required screening height written by the interactive screening tool. The user can choose another output field name in the dialog.

QCALVIEW names that are not ordinary attribute columns#

  • qcv_layer_crs — QGIS layer expression variable describing the layer CRS;
  • qcv_work_crs — QGIS layer expression variable describing the QCALVIEW working CRS;
  • qcv_wkt — temporary/expression geometry variable used by FOV geometry logic;
  • qcv_theme — accepted scenario/theme alias, not the canonical generated scenario column (theme);
  • qcv_fov_*_live — live expression variables paired with internal FOV caches.

This distinction is useful when searching the source code: not every qcv_* token is an attribute-table header.

User-selected source fields that have no fixed QCALVIEW header#

Some QCALVIEW controls let you choose an existing field from the source layer instead of creating a canonical column. In particular, the Order field used for previous/next viewpoint navigation can be any suitable source field. There is no required qcv_order column. If no explicit order field is selected, QCALVIEW can fall back to identifiers/FID according to the current logic.