Jon Stockill writes:
Wow, looks likt there's some real detail in there. What's the global
coverage like for this data? The current UK DEM data is rather coarse,
resulting in very flat terrain - I'm guessing there'll be huge
improvements if the UK SRTM data has been released?
I expect
David Megginson writes:
The new scenery code is still rough, and some tiles fail to build at
all, but I am extremely impressed with Curt's recent work on TerraGear
combined with the better Canadian elevation data available through the
SRTM.
David,
Thanks for the kind words. Yes there is a
David Megginson writes:
The new scenery code is still rough, and some tiles fail to build at
all, but I am extremely impressed with Curt's recent work on TerraGear
combined with the better Canadian elevation data available through the
SRTM.
Yup Open Source 'collaboration' yields wonders
Jim Wilson writes:
This looks great! Is the bay area ready for the base package yet?
There are a couple open issues.
1. I'm using the 1km raster land use/land cover data set rather than
vmap0 land use.
2. I have yet built in roads, railroads, or streams.
3. There are some tile boundary
Curtis L. Olson writes:
I'm also pretty happy with the quality of the SRTM data. If/when 3 or
1 arcsec terrain data is released for the entire word, I'll need a 1
gazillion terrabyte HD to do all the processing and a 256 node super
computer cluster also wouldn't hurt. :-)
In the
I'm also pretty happy with the quality of the SRTM data. If/when 3 or
1 arcsec terrain data is released for the entire word, I'll need a 1
gazillion terrabyte HD to do all the processing and a 256 node super
computer cluster also wouldn't hurt. :-)
flightgear.distributed.net. :)
g.
David Megginson writes:
In the meantime, there is 3 arcsec SRTM data for Canada and Mexico, so
we can join the club.
Really? Where can I fetch it?
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED]
Curtis L. Olson writes:
In the meantime, there is 3 arcsec SRTM data for Canada and Mexico, so
we can join the club.
Really? Where can I fetch it?
The same place as the U.S. data:
ftp://edcsgs9.cr.usgs.gov/pub/data/srtm/North_America/3arcsec/
The 1 arcsec data covers only the
Gene Buckle [EMAIL PROTECTED] wrote:
flightgear.distributed.net. :)
If someone provides a portable distribution mechanism for distributed
scenery generation, then I think I can provide some horsepower for this,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends
Curtis L. Olson [EMAIL PROTECTED] wrote:
I'm also pretty happy with the quality of the SRTM data. If/when 3 or
1 arcsec terrain data is released for the entire word, I'll need a 1
gazillion terrabyte HD to do all the processing and a 256 node super
computer cluster also wouldn't hurt. :-)
Martin Spott writes:
Gene Buckle [EMAIL PROTECTED] wrote:
flightgear.distributed.net. :)
If someone provides a portable distribution mechanism for distributed
scenery generation, then I think I can provide some horsepower for this,
The big problem is that scenery building is much more
Curtis L. Olson [EMAIL PROTECTED] wrote:
For scenery building I'd love to have at least an 8-16 node cluster
with really high bandwidth/ low latency net between them, a terrabyte
of scsi disk space, [...]
A terabyte of disk space is quite affordable these days. When the necessity
becomes
Curtis L. Olson [EMAIL PROTECTED] said:
The big problem is that scenery building is much more slanted towards
data shuffling (i.e. reading and writing files is typically the
largest component of the task.) There is a computational component
but it is generally small in comparison. When you
Locally I have about 220Gb of HD space dedicated towards storing the
original raw data. The intermediate preprocessed form of the data.
The shared edge data. And the final scenery.
Oh. I didn't expect it to be that much...
If we get SRTM data for the whole world, that will have to jump up
Major A writes:
Locally I have about 220Gb of HD space dedicated towards storing the
original raw data. The intermediate preprocessed form of the data.
The shared edge data. And the final scenery.
Oh. I didn't expect it to be that much...
I'm not maxed out yet, and occaisonally I keep
* [EMAIL PROTECTED] (Curt Olson) [2003.03.20 14:40]:
Martin Spott writes:
Gene Buckle [EMAIL PROTECTED] wrote:
flightgear.distributed.net. :)
If someone provides a portable distribution mechanism for distributed
scenery generation, then I think I can provide some horsepower for this,
David Megginson writes:
Curtis L. Olson writes:
In the meantime, there is 3 arcsec SRTM data for Canada and Mexico, so
we can join the club.
Really? Where can I fetch it?
The same place as the U.S. data:
ftp://edcsgs9.cr.usgs.gov/pub/data/srtm/North_America/3arcsec/
Just an idea: how about using the HP TestDrive farm? They have some
nice computers there such as a quad 1GHz Alpha. It would be
necessary to ask for their permission first, but this being an
open-source project, I wouldn't think this would be a problem. We
can then give credit on the
On Thu, 20 Mar 2003 15:34:24 -0600,
Curtis L. Olson [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Major A writes:
Locally I have about 220Gb of HD space dedicated towards storing
the original raw data. The intermediate preprocessed form of the
data. The shared edge data. And
On Thu, 20 Mar 2003 16:05:26 -0600,
Cameron Moore [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
PPS - I forget the company, but there's a back-cover ad in the most
recent Linux Journals where you can enter to receive a $50K research
grant by applying in this company's contest. Long
Major A writes:
I've just checked, the central file space is 160GB, which is about 50%
full right now. It's shared via NFS, unfortunately, so it's not that
good really. They still have impressive computing power, I've just
checked that they have a 4x800MHz Itanium and a 4x1GHz Alpha. The
Curtis L. Olson writes:
But, to answer your question CPU speed does definitely help.
Generally I'm never memory bound on a 256 machine except for the one
time task of splitting up the world land mass data set into
tiles... it would have been nice to have 1Gb RAM for that.
Note that
Gene Buckle writes:
After a bit of experimentation, I see little benefit in the 1arcsec
data for our needs. We can't even come any where close to rendering
the full 3arcsec data. We are talking about preserving the top 1%
most important data points from the 3 arcsec data. For the
From: Major A [EMAIL PROTECTED]
Sorry for the lame question, but how far are the sample points apart
from
each other in feet with the 3 arc second data? How far is it for the 1?
24 arc hours = 44000km (roughly the perimeter of the earth)
1 arc hour = 1833km
1 arc minute = 30.55km
1 arc
1 arcsec = approximately 30 meters = approximately 100 feet.
3 arcsec = approximately 90 meters = approximately 300 feet.
The points are on the lat/lon grid lines so the horizontal spacing
becomes smaller as you get further away from the equator.
Ahhh, damn, I should have thought a little
Hmmm, are you sure ?
from my understanding :
360 degres = 44000km
1 degre = 122.22km
1 minute = 2.037km
1 second = 0.033km
That's what I just realized. I think it's bedtime.
Andras
===
Major Andras
e-mail:
Hello Curt,
Curtis L. Olson [EMAIL PROTECTED] wrote:
But, to answer your question CPU speed does definitely help.
Generally I'm never memory bound on a 256 machine except for the one
time task of splitting up the world land mass data set into
tiles... it would have been nice to have 1Gb RAM
On Thu, 20 Mar 2003, Curtis L. Olson wrote:
Here are some more pictures taken in and around the Bay area:
http://www.flightgear.org/Gallery/Source/terrain1.jpg
http://www.flightgear.org/Gallery/Source/terrain2.jpg
http://www.flightgear.org/Gallery/Source/terrain3.jpg
On Thu, 20 Mar 2003, Gene Buckle wrote:
I'm also pretty happy with the quality of the SRTM data. If/when 3 or
1 arcsec terrain data is released for the entire word, I'll need a 1
gazillion terrabyte HD to do all the processing and a 256 node super
computer cluster also wouldn't hurt. :-)
Frederic Bouvier writes:
from my understanding :
360 degres = 44000km
1 degre = 122.22km
1 minute = 2.037km
1 second = 0.033km
Let's keep it simple. 1 minute of latitude is one nautical mile --
that's its definition.
All the best,
David
--
David Megginson, [EMAIL PROTECTED],
On Thu, 20 Mar 2003 21:36:13 -0500,
David Megginson [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Frederic Bouvier writes:
from my understanding :
360 degres = 44000km
1 degre = 122.22km
1 minute = 2.037km
1 second = 0.033km
Let's keep it simple. 1 minute of
Sorry for the lame question, but how far are the sample points apart from
each other in feet with the 3 arc second data? How far is it for the 1?
1 arcsec = approximately 30 meters = approximately 100 feet.
3 arcsec = approximately 90 meters = approximately 300 feet.
The points are on
Gene Buckle writes:
Sorry for the lame question, but how far are the sample
points apart from
each other in feet with the 3 arc second data? How far is it
for the 1?
1 arcsec = approximately 30 meters = approximately 100 feet.
3 arcsec = approximately 90 meters = approximately 300
From: Arnt Karlsen [EMAIL PROTECTED]
On Thu, 20 Mar 2003 21:36:13 -0500,
David Megginson [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Frederic Bouvier writes:
from my understanding :
360 degres = 44000km
1 degre = 122.22km
1 minute = 2.037km
1 second =
34 matches
Mail list logo
