Re: [Flightgear-devel] Terragear and 2 Arc Second elevation data

2011-10-15 Thread Christian Schmitt
Martin Spott wrote: We're not yet there. On a first test earlier today, 'genapts' ended in a segfault with the recent changes but I ran out of time, thus I have not yet verified if the source change in 'simgear' really was the culprit, Confirmed here. And I thought first it was the

Re: [Flightgear-devel] Terragear and 2 Arc Second elevation data

2011-10-15 Thread Christian Schmitt
Martin Spott wrote: We're not yet there. On a first test earlier today, 'genapts' ended in a segfault with the recent changes but I ran out of time, thus I have not yet verified if the source change in 'simgear' really was the culprit, Confirmed here. And I thought first it was the

Re: [Flightgear-devel] Terragear and 2 Arc Second elevation data

2011-10-07 Thread HB-GRAL
I am asking because I am currently working on Alaska elevation data for the relief. I had to clip 6 px overlap and I converted the .flt data to DEM format. HGT can not handle 1800x1800 px, but there is also a demchop in terragear, right? I like to share the data when it is useful for scenery

Re: [Flightgear-devel] Terragear and 2 Arc Second elevation data

2011-10-07 Thread HB-GRAL
When someone wants to run experiments with this data, you can find some test data in .dem format here: http://maptest.fgx.ch/public/2arc-alaska-dem/n70w140.zip Thanks a lot, Yves Am 07.10.11 12:07, schrieb HB-GRAL: I am asking because I am currently working on Alaska elevation data for the

[Flightgear-devel] Terragear and 2 Arc Second elevation data

2011-10-06 Thread HB-GRAL
Hi all Can terragear handle 2 arc second elevation data ? I read only about 1 arc and 3 arc data for the terragear toolchain. Cheers, Yves -- All the data continuously generated in your IT infrastructure contains a

Re: [Flightgear-devel] Terragear and 2 Arc Second elevation data

2011-10-06 Thread Curtis Olson
You might need to do some work with the tool that chops up the dem's into TerraGear tile sizes. There are different terrain formats so you might need to adapt the code to read a different format as well. This part sounds like it should be pretty straightforward if you have clear docs for the