Lars Ahlzen wrote:
Either way, I guess the thing for me to do would be to clean things up
just enough to be readable and then put the code and instructions up on
the wiki. Then we can all play with it. :)
If you want to try it out, I put the scripts and other files up at
Apollinaris Schoell wrote:
This sounds like an interesting experiment worth running on Amazon's
EC2 cloud. Their x-large machines run at $1/hour, but sure would
chomp on this data quickly!
I would be willing to try (and pay for) it if Lars went through a
did an updated
On Fri, Sep 4, 2009 at 12:44 PM, Lars Ahlzen l...@ahlzen.com wrote:
There's also the size of the data sets. The entire hi-res NHD and NED
would probably be many, many TB. Unpacking, preparing and indexing that
data requires plenty of additional disk space as well. One would
probably have to
This sounds like an interesting experiment worth running on Amazon's EC2
cloud. Their x-large machines run at $1/hour, but sure would chomp on this
data quickly!
I would be willing to try (and pay for) it if Lars went through a did an
updated setup doc.
We could start our own distributed
Hi All!
It's been a while since the last TopOSM update, but I haven't been
resting. After Massachusetts, I decided to pick a state with somewhat
more interesting topography: Colorado.
http://toposm.com/co/
There are still a few rough edges and things that are missing (like the
map legend), so
TopOSM-CO has a few important differences from TopOSM-MA:
What, MASSGIS doesn't cover Aspen?
* Color-by-elevation in base layer.
interesting
* Contour lines and hillshading generated from NED [1].
does that mean you're interpolating lines from a grid?
* Hydrography (lakes, rivers,
6 matches
Mail list logo
