Re: File format question

--===============1971206187==
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

Hi,

>the difference between the GRS80 and WGS84 ellipsiods are pretty minor [...]

Thanks Hamish for clearing this out. I opted to not bothering with the
conversion and concidering the data WGS84.

Anyway, I have some progress, and I have tested with small subsets of
the data to generate a USGS DEM file using mostly gdal and some python
scripts I hacked up. I'm in the process of extracting the whole of
e130n30 right now.
So here is another question:
The terragear tutorial:
http://www.terragear.org/docs/scenery-tutorial/fg-scenery-tutorial.html
and the docs seem to indicate that the format terragear supports are the
following:
30-arcsec SRTM
30-arcsec world wide data: GLOBE project
30-arcsec world wide data: GTOPO30 data
SRTM (1 and 3-arcsec nearly world wide coverage)
3-arcsec ASCII DEM files

My target output (thus the target input for terragear) is the 3-arcsec
ASCII DEM format.
My data comes in 2seconds increments, so I'm guessing I'm supposed to
convert the data to 3-arcsecs.
I think gdalwarp can do this for me with something like:
gdalwarp -tr 0.0008 0.0008 2sec.tif 3sec.tif

The question is can I import my data without interpolating to 3secs? Or
would I have to do the above to get terragear to work properly?


Cheers, and my apologies for the newbie-ish, not totally TerraGear devl
postings....
Vik



--===============1971206187==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Terragear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/terragear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
--===============1971206187==--