Page 1 of 1

QGIS exports corrupted .bil

Posted: Tue Apr 03, 2018 5:02 pm
by GregHart1965
I am having a lot of trouble trying to get going with a new scenery. I have DL'ed the srtm data from earth explorer and managed to merge, warp and clip the data successfully. Aside from some missing data (how do we patch this???) everything looks fine in QGIS. When I open the .bil in RAW to TRN it is corrupted with just a set of jagged lines running across the image. I have gone through the process three times to try and eliminate any errors but always get the same result.

Some notes:
1.- It is not possible to enter the "-tr 30 30" more than once in the procedure. It works when warping the data to UTM but is NOT accepted when defining the clipping parameters.
2.- There is an error message when clipping saying that the selected area falls outside of area covered by the data, carrying on however. This area is sea so I cant see how this would make any difference. The clipped image looks OK.

Re: QGIS exports corrupted .bil

Posted: Tue Apr 03, 2018 5:03 pm
by GregHart1965
Are there any other sources for srtm 1 second data? Preferably data that has been patched already. I have tried using .hgt files but this does not produce a usable file.

Re: QGIS exports corrupted .bil

Posted: Tue Apr 03, 2018 5:30 pm
by Andy1248
Have you renamed the bil to raw before doing the raw to trn?

Re: QGIS exports corrupted .bil

Posted: Tue Apr 03, 2018 6:10 pm
by GregHart1965
Its not necessary as you can simply type in the name of the file and RAW to TRN will accept the file. I did try that however and it makes no difference at all

Re: QGIS exports corrupted .bil

Posted: Tue Apr 03, 2018 8:55 pm
by tomrob999
Hello Greg,

Please see my post "Problem in LandscapeEditor"
and let me know if we are having the same issue.

Regards

Tom

Re: QGIS exports corrupted .bil

Posted: Wed Apr 04, 2018 1:56 am
by GregHart1965
No. I see a damaged image after opening the file in RAWtoTRN.
EDIT: Just tried it again and this time RAW to TRN looked blank and in LE it looks like your issue. Same jaggy broken image.