Project offline? about open-elevation HOT 22 CLOSED

Hey,
I put some work in this project and got a working version

https://github.com/Developer66/open-elevation

I also added a java downloader for downloading and using the TanDEM 90m resoulution from https://geoservice.dlr.de/web/dataguide/tdm90/

Maybe someone will use this version. I would be happy about a star if I could help.

Developer66

from open-elevation.

I've been working on an API to address some of the outstanding issues with open-elevation, such as: interpolation, .hgt support, and offering 30m datasets and bathymetry in a public API.

Code: ajnisbet/opentopodata
Docs & public API: www.opentopodata.org

Hope this is helpful!

from open-elevation.

I've uploaded the 250m dataset to gdrive, just copy it to data server folder, it will work. Actually there are more (and better) data sources online, e.g. the Japanese dataset (30m): https://www.eorc.jaxa.jp/ALOS/en/aw3d30/index.htm

from open-elevation.

But the data source in download-srtm-data.sh is still not available.

http://gisweb.ciat.cgiar.org/TRMM/SRTM_Resampled_250m/SRTM_NE_250m_TIF.rar
... and so on gives error 404

Do you also have an alternate source for the elevation data?

from open-elevation.

Here you go (#22): https://drive.google.com/drive/folders/1EdpJe9O2vXsKdop_yRr_ZbnPKHakO57j?usp=sharing

Well, the Japanese dataset works well with openelevation server, just needs a "bit" more space ;)

from open-elevation.

Sorry if I wasn't verbose enough, but you just need to modify the create-dataset.sh to not run download-srtm-data.sh and make sure to untar them yourselves. Then run create-dataset.sh

The Japanese ALOS dataset seems cool.

from open-elevation.

Maybe is a memory issue. Try to split the TIF files into smaller tiles using /code/create-tiles.sh script.

docker run -t -i -v $(pwd)/data:/code/data openelevation/open-elevation /code/create-tiles.sh /code/data/SRTM_NE_250m.tif 10 10

from open-elevation.

I guess so :( unfortunately I cannot find any other solution getting free elevation data.

from open-elevation.

I was able to get the docker image today. I needed to download from mirror @sTorro set up to create the dataset. I was also able to run it without docker on my own system. The GDAL requirement was a little tricky but the stackexchange link helped.
#22 (comment)
https://gis.stackexchange.com/questions/28966/python-gdal-package-missing-header-file-when-installing-via-pip

from open-elevation.

@sTorro do you have the link to your gdrive? :) that would be very nice.

The japanese dataset does not seem like it is in the needed format :/

from open-elevation.

Thanks a lot :)

from open-elevation.

Keep in mind the Japanese dataset uncompressed are about 1 TB if I remember well, but the quality is better by far.

from open-elevation.

I am getting the following error when using the TIF files from the Google Drive link:

ERROR 1: TIFFReadEncodedStrip:Read error at scanline 4294967295; got 1364 bytes, expected 201620
ERROR 1: TIFFReadEncodedStrip() failed.
ERROR 1: data/SRTM_NE_250m.tif, band 1: IReadBlock failed at X offset 0, Y offset 0
ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0
'NoneType' object is not subscriptable
'NoneType' object is not subscriptable
'NoneType' object is not subscriptable

I basically downloaded the data from Google Drive, uncompressed it with rar and link it to the "data" folder.

Any ideas?

from open-elevation.

Since my issue is very related (IMHO) with this, I'll continue posting here.

I have tried running the docker machine, by doing the following:

• First, downloaded the gdrive files and unzipped them
• Later, I split the 3 tif files, using the following (and it worked):

./create-tiles.sh code/data/SRTM_NE_250m.tif 10 10
./create-tiles.sh code/data/SRTM_SE_250m.tif 10 10
./create-tiles.sh code/data/SRTM_W_250m.tif 10 20

• And finally, I run docker run -t -i -v $(pwd)/data:/code/data -p 8080:8080 openelevation/open-elevation

To check everything's working, I checked a real location by visiting this URL: http://localhost:8080/api/v1/lookup?locations=48.6089816,-1.5139133

And the result was:
{"results": [{"latitude": 48.6089816, "longitude": -1.5139133, "error": "No such coordinate (48.6089816, -1.5139133)"}]}

It seems that somehow the elevation data is not being read. Could anyone help me here please?

from open-elevation.

@carlos-mg89 I'm not sure, maybe make sure all the files are in the right place? That data is pointed to the right place. I modified data so it works in docker or my real system.

You can run:
docker run -t -i -v $(pwd)/data:/code/data -p 8080:8080 openelevation/open-elevation bash
To get a bash prompt to see what the docker image sees.

When I run your url I get:
{"results": [{"latitude": 48.6089816, "elevation": 7, "longitude": -1.5139133}]}

from open-elevation.

sorry to ask somewhat random qs here but i am not sure where else to ask. given that the 250m data is unavailable, will the 30m data work? that does seem to be available (and i could just donwload the areas i am interested in)? sorry if this is a dumb question - i am new to this.

eg https://www.researchgate.net/post/How_can_I_download_SRTM_data_of_30_m_resolution

edit/update - it turned out to be easier to just implement the whole thing myself. if anyone else wants it, code available at https://github.com/andrewcooke/choochoo/blob/master/ch2/sortem/__init__.py (or nearby directory if that gets refactored)

from open-elevation.

@bluthen I have the elevation data with all the tif files on /code/data (on my Linux computer, the host) and I run the above docker run I posted on open-elevation/docker folder. There, I can see a data folder, but it only contains a summary.json after I run either the docker run I posted or the one you posted.

I think I'm messing things up with the directories. I have tried now movind the data directory, to the open-elevation directory, but the docker/data contains the same summary.json and if I run the docker run, the API call returns the same answer 😩

from open-elevation.

@bluthen I definitely messed it up with the folders. Now I have created a data folder within the clonned open-elevation project. From there (previously, I executed the docker command, from the open-elevation/docker folder), I run docker run -t -i -v $(pwd)/data:/code/data -p 8080:8080 openelevation/open-elevation and voilà! It works like a charm!!!

Thank you so much!

from open-elevation.

See #29 (comment) :)

from open-elevation.

Hi.

For the better part of the last 2 years, the API has been completely overloaded (sadly, very little comes in the way of donations, and so I can't really pay for a more beefed up machine).

As of two days ago, though, I have done some tweaks to the backend and the API should be handling the workload much better. Give it a try again!

I will also be pushing a series of updates to the repository and dockerhub, to modernize the project and make it work again.

I will close this issue because I believe that the public API is now working, but feel free to reopen it if it is not. If you have other issues, please open a separate issue for that.

from open-elevation.

The problem is inside download-srtm-data sh.
It extract the downloaded file into the
data/SRTM_NE_250m_TIF/, data/SRTM_SE_250m_TIF/ and data/SRTM_W_250m_TIF folder in windows machine.

Also docker server take upto 20GB of ram for SE map. It runs extremely slow.

from open-elevation.

Hi @iisri-vu Please open a separate issue for the problem you're having. I'm not sure I understood the issue you are having.

This original issue had to do with the fact the public API at https://open-elevation.com/ was overloaded. That problem has since been fixed.

Regarding the 20GB, it should not be slow, because the files are split into chunks. Perhaps you're having another issue.

I will be waiting for another issue from you.

from open-elevation.