Invalid height when an ascii DEM file is opened

[yeodh]

Hello,

I would like to report a case that looks weird to me. This could be a bug or my mistake (I am a rookie user)

When I opened an ascii DEM file in CC (as a raster), I got a window message "This raster has pixels with invalid heights. Shall we remove them?." If say No, the height of that part (considered invalid by CC) was changed to -1.877606. When I checked the file by an editor, all numbers looked good. I could avoid this problem when I translated the height by -100 (in z) in opening it. However, there occurred another problem: invalid height somewhere else in the file (which was originally the lowest height (zero)). The height was expected to -100 because of the translation, but the value was changed to -1.877606. This implies they were considered as invalid height as this trial.

I think the problem might be caused by the height of the box set by CC which is smaller than real height of the file. I was wondering if I could increase the height dimension of the box set by CC.

I used version 2.12 alpha.

Thank you.

PS: I could not attach a screen-capture because the board attachment quota has been reached.

[daniel]

See https://github.com/CloudCompare/CloudCo ... ssues/1402