Post
by Zaggy » 2007-03-03 16:23:28
Regarding SRTMv1 and SRTMv2 (v2 is the corrected Data, v1 is the RAW Data... v2 Was released maybe 12 months back or so, JUST after Bluey had finished his project, basically doing the same thing to the v1 Data... Bluey's Data, IMHO, is of better quality tho, fixing one or two of the things the v2 Data missed) and Berings Theater...
SRTM Data sits between 59S and 60N. Any Theater that will encompass Lat's outside that Range, will need to find a substitute for SRTM outside those ranges... BUT, its not overly difficult...
I'd start by resampling your SRTM source from 3ArcSec to 250m. Then acquiring 30ArcSec GLOBE or GTOPO30, which you'd interpolate to 250m. You would then create an overlap of say 30-60minutes of Lat, and interpolate the overlaps, so at the SRTM edge you'd be 100% biased to SRTM, and by the Interpolated GLOBE edge, the bias would have been gradually reversed to the GLOBE data...
As you can tell, i thought about this for the Berings Theater, but never put it into practice... Its something you'd probably like to see put into any SRTM app that Bluey creates; the ability to SPECIFY Source Elevation Array resolution, so you could use SRTM3, SRTM1 (just incase you got access to full res data somehow or wanted to do continental US) as well as User defined res, where we'd specify 250m, for the example above...
Just some thoughts... Would be relevant to Berings of course, as well as the Nordic guys...
Daniel "Zaggy" Bell
Old-School, Grumpy and Anti-Social
Also to be found lurking round FighterOps