8 Commits

Author SHA1 Message Date
Martin Dobias
9009971c88 Improve handling of vertical ranges
So far we used a fixed vertical range for 3D bounding boxes with range [0, 500]
This of course would not work well if Z values are outside of this range
(e.g. tiles may not show at all or get pruned prematurely)

The approach now is to start with an estimate of the vertical range based
on few features from the source vector layer and then once our tile is completely
loaded, update the 3D bounding box to better represent the actual 3D extent.
2020-01-12 16:22:20 +01:00
Nyall Dawson
e47d55f6e3 Grammar 2019-10-02 21:37:52 +10:00
Nyall Dawson
741c051321 Spelling 2019-10-02 21:37:52 +10:00
Nyall Dawson
9b07075fae Add a switch to QgsTessellator to avoid z handling and fallback to a
purely 2d tesselation

Optimises tessellation when only a 2d tessellation is required by
skipping unnecessary/unwanted calculations
2019-10-02 21:37:52 +10:00
Nyall Dawson
a9228f576d Spelling and build warning 2019-10-02 21:37:52 +10:00
Nyall Dawson
8ee1c20bb2 [tesselator] Allow internal scaling of coordinates by input coordinate
bounds to avoid numerical instability with close coordinates (e.g. calculating
tesselation of geometries in geographic CRS)
2019-10-02 21:37:52 +10:00
Peter Petrik
69fa26183f fix travis errors 2018-05-30 12:26:36 +02:00
Peter Petrik
7af2e68e23 misc optimization for geometries and fixes 2018-05-30 10:06:23 +02:00