{"id":5365,"date":"2023-03-18T05:37:34","date_gmt":"2023-03-18T09:37:34","guid":{"rendered":"https:\/\/jeremyclark.ca\/wp\/?p=5365"},"modified":"2025-12-17T09:46:32","modified_gmt":"2025-12-17T14:46:32","slug":"splat-digital-elevation-data-with-qgis","status":"publish","type":"post","link":"https:\/\/jeremyclark.ca\/wp\/telecom\/splat-digital-elevation-data-with-qgis\/","title":{"rendered":"Splat! – Digital Elevation Data with QGIS"},"content":{"rendered":"\n

Introduction<\/h2>\n\n\n\n

Splat! (Ref.1<\/a>) is a very versatile propagation prediction program that I discussed in several previous posts. In my first post, I looked at installation on Windows and Linux, how to obtain the digital elevation data files, create QTH & LRP files, and run a simple point to point analysis (Ref.2<\/a>). In the second and third posts I examined Marine VHF communications calculations for AIS & VHF coverage (Ref.3<\/a>\/4<\/a>). In this post I will consider how we can use QGIS, an open source Geographic Information System, to analyze and convert various digital elevation data files so that they can be used with Splat! (Ref.5<\/a>). Splat requires SRTM 1arc_sec (30m) or 3arc_sec (90m) data files of type .hgt which can then be converted to .sdf splat data files.<\/p>\n\n\n\n

Canadian CDEM GeoTiff .tif vs. SRTM .hgt <\/h2>\n\n\n\n
\"\"
Fig.1 Canadian CDEM File Grid Near Toronto<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.2 GeoTIFF cdem_031D.tif Data PDF<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.3 GeoTIFF cdem_031D.tif on OpenStreetMap<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.4 SRTM N44W080.hgt on OpenStreetMap<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.5 gdalinfo cdem_031D.tif<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.6 gdal info N44W080.hgt<\/figcaption><\/figure>\n\n\n\n
Parameter<\/strong><\/td>GeoTIFF .tif File<\/strong>
cdem_dem_031D.tif<\/td>		SRTM .hgt File<\/strong>
N44W080.hgt<\/td><\/tr>
GEOGCRS
GeoCordSys<\/td>		NAD83(CSRS)<\/td>WGS84<\/td><\/tr>
Area<\/td>Lat: 44deg – 45degN
Long: 78deg – 80degW<\/td>		Lat: 44deg -45degN
Long: 79deg-80degW<\/td><\/tr>
Pixel<\/td>0.000208333333333deg
0.75arc_sec
+\/- 23.2m<\/td>		0.000277777777778deg
1arc_sec
+\/- 30.9m<\/td><\/tr>
File Size<\/td>9601,4801
92,227,633bytes<\/td>		3601,3601
25,934,402bytes<\/td><\/tr>
Band1<\/td>Block 9601×1
Int16
NoData=-32767
Min=114.0
Max=481.0
Mean=261.624
StnD=48.170<\/td>		Block 3601×1
Int16
NoData=-32768
Min=171.0
Max=410.0
Mean=243.75
StndD=38.544<\/td><\/tr><\/tbody><\/table>
Fig. 7 Main Differences GeoTIFF & HGT Files<\/figcaption><\/figure>\n\n\n\n

Let’s say we want to use Canadian CDEM files with Splat (Ref.6<\/a>). Figure 1 shows the CDEM grid around the Toronto area. Figure 2 shows the CDEM data pdf for file cdem_031D.tif. Figure 3 shows this file in grey scale overlayed on Open Street Map as viewed in QGIS. Figure 4 shows the SRTM file N44080.hgt overlayed on Open Street Map as viewed in QGIS. Note that 031D covers 2deg of Longitude whereas the N44W080 covers only 1deg. Figures 5 & 6 show the gdalinfo command output for each file. Figure 7 highlights the critical differences in each file, which basically are the reference model, sampling size, file size and boundaries.

In order to do the conversion, we need a two step process. First step is to use gdalwarp to change the reference projection, sampling size and boundaries. The second step is to use gdal_translate to convert from .tif to .hgt file type. GDAL “Geospatial Data Abstraction Layer” is a tool that is embedded in QGIS (Ref.7<\/a>).<\/p>\n\n\n\n

QGIS & GDALWARP<\/h2>\n\n\n\n
\"\"
Fig. 8 QGIS Workspace Showing cdem_031D.tif & Diagonal Profile<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.9 QGIS gdalwarp Menu<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.10 QGIS 031Dresamp<\/figcaption><\/figure>\n\n\n\n

In order to familiarize myself with QGIS, I found References 8<\/a> & 9<\/a> very helpful. The first step is to open cdem_031D.tif in QGIS and use gdalwarp to change the reference model, resample and crop. Figure 8 shows cdem_031D.tif with an arbitrary terrain profile line that we can use to check between the conversions. Figure 9 shows the gdalwarp menu with source cdem_031D.tif EPSG:4216 and target EPSG:4326. The output file resolution is resampled to 0.000277777777778deg and cropped to the boundaries of N44W080. The file is saved as 031Dresamp.tif. Based on Reference 10, I changed the resampling rule from “nearest neighbour” to “lanczos”. Figure 10 shows the resampled file.<\/p>\n\n\n\n

QGIS & GDAL_TRANSLATE<\/h2>\n\n\n\n
\"\"
Fig.11 QGIS gdal_translate Menu<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.12 Profile Comparisons<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.13 Profile Comparison Elevation Spreadsheet<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.14 Raster Subtraction N44W080.hgt – N44W080.hgt_converted<\/figcaption><\/figure>\n\n\n\n
\"\"
Fig.15 Diagonal Profile N44W080conv vs. Google Earth<\/figcaption><\/figure>\n\n\n\n

Now the last step is to take the resampled 031Dresamp.tif and convert this to an SRTM .hgt file. Figure 11 shows the gdal_translate Menu used to do this. You have to give the correct SRTM name in this case N44W080.hgt. Figure 12 shows the same profile as seen in the original .tif file, the resampled .tif, the real .hgt and the converted .hgt. Figure 13 is a spread sheet showing elevation values along the profile in meters vs distance in arc_deg along the profile line. Figure 14 shows the raster subtraction of the real .hgt file with the converted .hgt file.<\/p>\n\n\n\n

Conclusion<\/h2>\n\n\n\n

So how good is the conversion? You can see from the spreadsheet there are differences between cdem_031D.tif and N44W080.hgt to start off with. So after resampling, re-projection and cropping there are differences. The max difference over the path of 1.322arc_deg (147Km) between N44W080.ght and the N44W080conv.hgt is 12m, but only in several places, 9m of which is due to the original difference between cdem_031D.ti and N44W080.hgt. Typically the difference is about 2m. I am not a Geospatial expert, but this process seems to work. In the first step you do need to create a cropping mask so you have to know the exact SRTM coordinates. Finally Figure 15 shows the profile across the diagonal of the file compared to Google Earth showing a close match. <\/p>\n\n\n\n

\n