Just a quick follow-up with some numbers for disk space usage for those
interested. I had a go at importing 10 metre contour lines for the whole
of Eurasia into PostGIS - latitudes of 0 - 46 degrees North required about
110 gig of disk space for the Postgres table and amounted to around 105
On Mon, Mar 17, 2008 at 11:05 PM, Jon Burgess
[EMAIL PROTECTED] wrote:
That is correct. When the --slim option was working the entire import
was IO bound and took several times longer than the RAM approach.
You could try ionice but I don't think that helps control swap IO.
I looked at the
On Tue, 18 Mar 2008, Martijn van Oosterhout wrote:
I looked at the code the other day and it seemed rather inefficient.
Fixing it will be a PITA though...
Would be very nice though, I'm think of looking into it when I have time...
I was pondering rewriting it from scratch with the aim to
Steve Hill wrote:
Contours layer presented by openpistemap is simply great. Does it
exist a server publishing only this layer?
There is still the relief layer available, using addresses like
http://srtm.in-ulm.de/layer/relief/z8/row89/8_134-89.jpg
The tutorial on how to use these is here:
Contours layer presented by openpistemap is simply great. Does it
exist a server publishing only this layer?
I'm working on Viking, a desktop GPS data editor capable of rendering
data on top of image downloaded on line. Having a contours layer would
be usefull to prepare hicking.
Thanks in
Contours layer presented by openpistemap is simply great. Does it
exist a server publishing only this layer?
I'm not sure how that would work - you really need the contours data set
to be the bottom layer, with the normal layers on top of that (is it
possible to ask OpenLayers to render the
On Mon, Mar 17, 2008 at 4:36 PM, Steve Hill [EMAIL PROTECTED] wrote:
Contours layer presented by openpistemap is simply great. Does it
exist a server publishing only this layer?
I'm not sure how that would work - you really need the contours data set
to be the bottom layer, with the
On Mon, 17 Mar 2008, Dave Stubbs wrote:
There's also the amount of time it would take to render the tiles. It
takes over 15 hours to render the contours used on the cycle map, and
all things considered that covers a very small % of the planet surface
at any kind of decent zoom level. It's a
On Mon, Mar 17, 2008 at 5:43 PM, Steve Hill [EMAIL PROTECTED] wrote:
On Mon, 17 Mar 2008, Dave Stubbs wrote:
There's also the amount of time it would take to render the tiles. It
takes over 15 hours to render the contours used on the cycle map, and
all things considered that covers a
Dave Stubbs wrote:
it's faster to just let it use swap,
I I/O load hits my server pretty hard. Trying to do anything else while
that's happening is quite painful. :-/
Doing it without the heavy I/O load is preferable, even if it takes a
couple of days - it can just trundle away in the
On Mon, Mar 17, 2008 at 8:00 PM, Steve Hill [EMAIL PROTECTED] wrote:
Dave Stubbs wrote:
it's faster to just let it use swap,
I I/O load hits my server pretty hard. Trying to do anything else while
that's happening is quite painful. :-/
Doing it without the heavy I/O load is
On Mon, 2008-03-17 at 20:28 +, Dave Stubbs wrote:
On Mon, Mar 17, 2008 at 8:00 PM, Steve Hill [EMAIL PROTECTED] wrote:
Dave Stubbs wrote:
it's faster to just let it use swap,
I I/O load hits my server pretty hard. Trying to do anything else while
that's happening is quite
12 matches
Mail list logo
