How a 2D result source's XY coordinates relate to the model's CRS. More...

#include <mesh2dh5reader.h>

Collaboration diagram for openswmmvis::io::CoordinateReference:

Public Attributes
QString	crs
	model CRS, verbatim; empty if undeclared

double	metresPerModelUnit = 1.0
	stored = model x this

QString	storedUnits
	unit of the stored coords, e.g. "m"

bool	declared = false
	true when read from a `/crs` variable

Detailed Description

How a 2D result source's XY coordinates relate to the model's CRS.

The engine's 2D solver runs in SI, so every x/y it writes is in metres — even when the model (and its .2dm mesh, and its [OPTIONS] CRS) is authored in feet. Consumers must divide by metresPerModelUnit before reprojecting out of crs, or the results land ~0.3048x toward the CRS origin while the .2dm-backed mesh layer renders correctly (issue #155).

Engine 6.0+ states this explicitly in the file's /crs variable. Older files (and the live in-process source) declare nothing — declared is then false and the caller falls back to the layer CRS's own linear unit.

Member Data Documentation

◆ crs

QString openswmmvis::io::CoordinateReference::crs

model CRS, verbatim; empty if undeclared

◆ declared

bool openswmmvis::io::CoordinateReference::declared = false

true when read from a /crs variable

◆ metresPerModelUnit

double openswmmvis::io::CoordinateReference::metresPerModelUnit = 1.0

stored = model x this

◆ storedUnits

QString openswmmvis::io::CoordinateReference::storedUnits

unit of the stored coords, e.g. "m"

The documentation for this struct was generated from the following file: