gerard robin wrote:
On mardi 20 janvier 2009, Martin Spott wrote:
gerard robin wrote:
On mardi 20 janvier 2009, Martin Spott wrote:
gerard robin wrote:
I wonder how you managed to draw a conclusion even before the error has
been identified properly,
i only have eye, a
On samedi 17 janvier 2009, Martin Spott wrote:
Brian Schack wrote:
There are several huge and very unnatural walls in the Himalayas, both
running NS and EW. I'll give the line of latitude or longitude that
the wall runs along, and the end coordinates of the walls:
The underlying SRTM
gerard robin wrote:
So older data were right.
I wonder how you managed to draw a conclusion even before the error has
been identified properly,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
On mardi 20 janvier 2009, gerard robin wrote:
On samedi 17 janvier 2009, Martin Spott wrote:
Brian Schack wrote:
There are several huge and very unnatural walls in the Himalayas, both
running NS and EW. I'll give the line of latitude or longitude that
the wall runs along, and the end
On mardi 20 janvier 2009, Martin Spott wrote:
gerard robin wrote:
So older data were right.
I wonder how you managed to draw a conclusion even before the error has
been identified properly,
Martin.
i only have eye, a computer, and archives
--
Gérard
Hi Brian,
Brian Schack wrote:
data (and by the way, much of this is guesswork on my part - if I'm
labouring under false assumptions, please let me know). Maneuvering
to an area in question, I checked 'srtm_elevation' and got ... nothing
at all. There is data there - checking 'v0_lake, for
gerard robin wrote:
On mardi 20 janvier 2009, Martin Spott wrote:
gerard robin wrote:
I wonder how you managed to draw a conclusion even before the error has
been identified properly,
i only have eye, a computer, and archives
So, did you create screenshots from the 1.0.1 Scenery as
Brian Schack wrote:
Given that we have this weirdness in the Himalayas, my first
inclination is to check the underlying data. Atlas and FlightGear
both showed the same problem, so this indicates that the problem is
not with Atlas or FlightGear, but with the data they use.
FlightGear and
On mardi 20 janvier 2009, Martin Spott wrote:
gerard robin wrote:
On mardi 20 janvier 2009, Martin Spott wrote:
gerard robin wrote:
I wonder how you managed to draw a conclusion even before the error has
been identified properly,
i only have eye, a computer, and archives
So,
Martin == Martin Spott writes:
Martin Brian Schack wrote:
There are several huge and very unnatural walls in the
Himalayas, both running NS and EW. I'll give the line of
latitude or longitude that the wall runs along, and the end
coordinates of the walls:
Martin
Brian Schack wrote:
There are several huge and very unnatural walls in the Himalayas, both
running NS and EW. I'll give the line of latitude or longitude that
the wall runs along, and the end coordinates of the walls:
Thanks for reporting!
Especially in these mountainous regions I feel a bit
Brian Schack wrote:
There are several huge and very unnatural walls in the Himalayas, both
running NS and EW. I'll give the line of latitude or longitude that
the wall runs along, and the end coordinates of the walls:
The underlying SRTM elevation data is known to have many voids in the
There are several huge and very unnatural walls in the Himalayas, both
running NS and EW. I'll give the line of latitude or longitude that
the wall runs along, and the end coordinates of the walls:
(1) e86.250 (NS), from n27.875 to n28.000
The above wall is capped on the north by an east-west
13 matches
Mail list logo
