Closed joewheaton closed 6 years ago
The issue is withe PQ 2005 and occurs at the edges. An interesting aside is that this raster has stats set really messes with QGis and causes it to crash.
but I digress: we were talking about edge effects:
The issue is that the PQ 2005 raster's nodata
value is set incorrectly:
-3.40282e+38 (nodata value for the raster)
-3.40282347e+38 (value in each Nodata cell
The workaround for the workshop is to setnull on the PQ_2005
before you use it so the NDV gets set properly. After that you shouldn't have this issue.
That being said we absolutely should fail more gracefully than this.
I like the idea of failing more gracefully. I will aspire to such heights in all my future failures.
The Problem
When deriving an FIS error surface, I have a problem with an exception being thrown when it tries to add this to the map. I've seen two behaviors:
I can't tell if this is a problem with the calculation of statistics, or the actual NoData values saved in the raster.
See here: https://youtu.be/TnnQ7ugmEO4?t=13m6s (I just noticed that it sounds like I'm talking with a lisp... I'm using a Bose set of headphones and not my normal headset... I wonder if the Bluetooth and frequency of audio is just doing something off... anyhow kind of funny, but also choppy.)
Reproduction steps
2005DEM
, and derive Associated Surfaces ofSlope Degrees
from DEM andPointDensity
fromSurveyFile
, and loadPQ2005
for 3D Point Quality.GPSZErrorPDSLPdegPQ.fis
in FIS folder.Exception message