I am working with a standalone app build with QGIS 2.8.1 on a CentOs7 machine. I got a new DTED data set which raises errors "somewhere" in the app. The app doesn't read the .dt? files directly, but as a VRT.
Even in debug mode this is all I get on the console:
Warning 1: Longitude count (195) of column 193 doesn't match expected value Process finished with exit code 139.
Just for info:
- About QGIS states: compiled with GDAL/OGR 1.11.1, running with GDAL/OGR 1.11.2; Python is running with gdal 1.11.2
- other DTED files work perfectly, readed directly or as VRT
- reading a single .dt? file works
- both, VRT and individual .dt? files work in QGIS application
- The columns may be different in each run, and there may be different counts of warnings
Unfortunately yesterday evening CentOs was proud to tell, that QGIS has successfully updated to the current version 2.8.3. But using this version, and after downgrading back to 2.8.1, there is no difference. I cannot state, if this error would have occur before updating, because I hadn't used the same DTED data before.
What is the reason for this GDAL error, which instructions will raise this exception, and why is the behaviour of the different components (VRT/direct reading, QGIS/QGIS components) so different?