[OSM-dev] Import NASA SRTM3 data into Postgres (SOC update)
Sjors Provoost
sjors at sprovoost.nl
Mon Jun 2 02:51:51 BST 2008
On Sun, Jun 1, 2008 at 3:24 AM, Andy Allan <gravitystorm at gmail.com> wrote:
> On Sat, May 31, 2008 at 12:13 PM, Andy Allan <gravitystorm at gmail.com> wrote:
>> Hi Sjors,
>>
>> What does your (quite extensive) script do that the scripts on the
>> wiki don't? Both appear to convert SRTM DEMs into polylines in
>> postgis.
>>
>> http://wiki.openstreetmap.org/index.php/Contours#Importing_the_SRTM3_data
>>
>> I'm concerned that you've spent a long time potentially reinventing
>> the wheel, but I'm interested to see what advantages your methods
>> have.
> My apologies, I've read the scripts a bit more carefully now, and can
> see what you're doing.
>
> Cheers,
> Andy
Hi Andy,
I understand the confusion, so let me just clarify it in general.
The main difference between that approach and what I am doing, is that
I am not using contours: I use the original grid of data points. I am
thinking about calculating local contours on the fly, or use some form
of interpolating the data points. That way I should be able to safe
storage space and it may also be easier to combine it with altitude
data from other sources at some point in the future.
Also, my script adds the (not very spectacular) service of downloading
and verifying the zip files.
I already discovered that my approach eats way to much hard disk
space, so I am changing a few things:
* In stead of storing the coordinates as two double precision floats
(2 * 8 bytes), I will create a bigint index (1 * 8 bytes). Also I
changed the altitude from double (8 bytes) to smallint (2 bytes),
since the SRTM data was already to rounded to the nearest meter.
* In stead of the whole continent I will stick to a smaller part of
Australia for my laptop. I'll see how far I push my home computer
later.
Kind regards,
Sjors
More information about the dev
mailing list