This object is in archive!
hgt source
Answered
Peter's response in
http://help.locusmap.eu/responses/where_to_download_srtm_data_for_my_country
doesn't actually answer the question where the Locus app itself downloads elevation maps from. Usgs or viewfinderpanorama?
If the former, pity, the problems are obvious even to me (looking at n47e011 in 3dem). If the latter - why then are the one degree tiles downloaded separately when the site offers them as zips containing 24 maps each?
Also: Can Locus use the 1" maps (the 25M per 1 degree tile ones) correctly?
P.S.: I have Pro, though I wouldn't dream of providing G* with identifiable data for a play store account or publishing said account's dead mailbox, so you won't find me in your customer DB.
The same question
The source of HGT data is combination of Viewfinderpanoramas and standards SRTM data.
Our system for downloading of *.hgt files are created like: one request - one hgt file. Anyway you can download mentioned *.zip file manually and unpack it into folder /Locus/data/srtm/
Locus can handle 1'' data file. So you can download them to the same folder Locus/data/srtm/
We're planning to create some packages of hgt files so users will be able to download elevation data for some specific region
The source of HGT data is combination of Viewfinderpanoramas and standards SRTM data.
Our system for downloading of *.hgt files are created like: one request - one hgt file. Anyway you can download mentioned *.zip file manually and unpack it into folder /Locus/data/srtm/
Locus can handle 1'' data file. So you can download them to the same folder Locus/data/srtm/
We're planning to create some packages of hgt files so users will be able to download elevation data for some specific region
about 1" files:
try it!
I don't know if they are "correctly" - but it works...
about 1" files:
try it!
I don't know if they are "correctly" - but it works...
Thanks for the extra quick reply!
So, I'd interpret this as follows:
- The Locus App, when offering to download e.g. N47E011.hgt, will not connect to either http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N47E011.hgt.zip nor http://www.viewfinderpanoramas.org/dem3/L32.zip, but to a server of your own where you keep the hgt files you deem best? So when my motivation is to have an idea which quality I'll be getting automatically, I'd have to think "Trust a Locus editor" not "all usgs srtm 2.1" or "always what de Ferranti thinks best for his 3"-DEM world coverage"? Either way is OK, I'm just saying users might want to know.
- For 1 arc-second files, yes, you didn't fall into the trap to hardcode a division by 1200 :) I only asked because that is something quite hard to actually verify by testing Locus output.
- Packages are a good idea. Europe up to E029 including islands excluding greenland including 1" Alps would be 760M 7-zipped.
Keep up the good work.
Thanks for the extra quick reply!
So, I'd interpret this as follows:
- The Locus App, when offering to download e.g. N47E011.hgt, will not connect to either http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N47E011.hgt.zip nor http://www.viewfinderpanoramas.org/dem3/L32.zip, but to a server of your own where you keep the hgt files you deem best? So when my motivation is to have an idea which quality I'll be getting automatically, I'd have to think "Trust a Locus editor" not "all usgs srtm 2.1" or "always what de Ferranti thinks best for his 3"-DEM world coverage"? Either way is OK, I'm just saying users might want to know.
- For 1 arc-second files, yes, you didn't fall into the trap to hardcode a division by 1200 :) I only asked because that is something quite hard to actually verify by testing Locus output.
- Packages are a good idea. Europe up to E029 including islands excluding greenland including 1" Alps would be 760M 7-zipped.
Keep up the good work.
Replies have been locked on this page!