

Individual engineers at these places do not have the power to make decisions about which map software to use, which are often six- or seven-figure contracts. More crucially, they are winning over executives of medium-to-large internet businesses with superior sales and marketing. Also the resolution is more or less the same, SRTM offers 25m horizontal resolution, that’s pretty high, IMO.

I haven’t personally compared them, but before picking SRTM for that embedded GIS project I’ve read about them, and concluded SRTM is more reliable. > including for example the USGS high res DEM where available Even though due to very slow target hardware (500MHz CPU, 256MB RAM, slow flash storage), I had to invent more optimized format for SRTM data (dense array of 32x32 tiles taking exactly 2kb/each, aligned by disk sector), and implement an offline converter. In the embedded software I’ve developed, I’ve layered SRTM-derived data on top of OSM tiles, worked quite well and wasn’t too hard to implement. mapping them together is very simple, too. The first/last row/columns of adjacent files overlap that’s why non-round numbers.īoth SRTM and tiles use Mercator projection, i.e. Each file contains 1201x1201 or 3601x3601 samples depending on resolution. Each file is an array of 16 bit integer values in meters, and it maps 1x1 degrees areas. The format is very simple to make sense of. how to take those files and turn them into a tiles that correspond with the same basemap image tiles.
