<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Import NASA SRTM3 data into Postgres</title>
	<atom:link href="http://sprovoost.nl/2008/05/31/import-nasa-srtm3-data-into-postgres/feed/" rel="self" type="application/rss+xml" />
	<link>http://sprovoost.nl/2008/05/31/import-nasa-srtm3-data-into-postgres/</link>
	<description>All about me</description>
	<lastBuildDate>Sat, 04 Feb 2012 18:53:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Sjors</title>
		<link>http://sprovoost.nl/2008/05/31/import-nasa-srtm3-data-into-postgres/comment-page-1/#comment-881</link>
		<dc:creator>Sjors</dc:creator>
		<pubDate>Mon, 02 Jun 2008 01:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://sprovoost.nl/?p=74#comment-881</guid>
		<description>@Stefan : thanks for the link.
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&#039;ll see how far I push my home computer
later.</description>
		<content:encoded><![CDATA[<p>@Stefan : thanks for the link. </p>
<p>The main difference between that approach and what I am doing, is that<br />
I am not using contours: I use the original grid of data points. I am<br />
thinking about calculating local contours on the fly, or use some form<br />
of interpolating the data points. That way I should be able to safe<br />
storage space and it may also be easier to combine it with altitude<br />
data from other sources at some point in the future.</p>
<p>Also, my script adds the (not very spectacular) service of downloading<br />
and verifying the zip files.</p>
<p>I already discovered that my approach eats way to much hard disk<br />
space, so I am changing a few things:</p>
<p>* In stead of storing the coordinates as two double precision floats<br />
(2 * 8 bytes), I will create a bigint index (1 * 8 bytes). Also I<br />
changed the altitude from double (8 bytes) to smallint (2 bytes),<br />
since the SRTM data was already to rounded to the nearest meter.</p>
<p>* In stead of the whole continent I will stick to a smaller part of<br />
Australia for my laptop. I&#8217;ll see how far I push my home computer<br />
later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan</title>
		<link>http://sprovoost.nl/2008/05/31/import-nasa-srtm3-data-into-postgres/comment-page-1/#comment-871</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Sun, 01 Jun 2008 12:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://sprovoost.nl/?p=74#comment-871</guid>
		<description>Just making a reference to OpenStreetMap&#039;s Wiki: http://wiki.openstreetmap.org/index.php/Contours#Importing_the_SRTM3_data.</description>
		<content:encoded><![CDATA[<p>Just making a reference to OpenStreetMap&#8217;s Wiki: <a href="http://wiki.openstreetmap.org/index.php/Contours#Importing_the_SRTM3_data" rel="nofollow">http://wiki.openstreetmap.org/index.php/Contours#Importing_the_SRTM3_data</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

