Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an LCP download service #290

Closed
ksshannon opened this issue Apr 26, 2018 · 10 comments
Closed

Create an LCP download service #290

ksshannon opened this issue Apr 26, 2018 · 10 comments

Comments

@ksshannon
Copy link
Member

The EROS download service is painfully slow. With a little work, I think we can create our own, and host it. I don't think the traffic will be terrible, so a small server will do. We can fall back on the EROS service on failure. We'd have to get the data shipped to us and loaded some how. That might be the biggest head ache.

This can be done substantially easier if GDAL adds write/update/create support for the LCP driver, which I will investigate.

@nwagenbrenner
Copy link
Member

I think I have the data. I think I got it from Don a while back. I'll check and report back. What are you thinking for the server? We could use our weather.firelab.org server. Or yours. Or something else. Whatever's best.

@ksshannon
Copy link
Member Author

How big is the dataset? Is it easy to get it onto your server? I have upload limits on mine right now.

@nwagenbrenner
Copy link
Member

I'll have to double check what data I actually got from Don and the size, but it shouldn't be an issue to put it on our server. weather.firelab.org is an instance in an OpenStack setup Bryce is running. I'll check on this stuff tomorrow.

@nwagenbrenner
Copy link
Member

I have the CONUS data. I'll have to download AK and HI. Zipped up, the CONUS data is around 15 GB.

@fspataro-zz
Copy link

This could be set up on the WindNinjaMobile server ie. it could become the WindNinjaServer to support both Mobile and Desktop

@nwagenbrenner
Copy link
Member

Yeah, that's a good idea. I guess the only concern is that we don't know how long the AWS server will be around. But if it goes away we'll have to move WindNinja Mobile (probably to our OpenStack server) anyway, so we could migrate everything at that time. Makes sense to use the same data server for mobile and desktop WindNinja. @ksshannon @jforthofer?

@jforthofer
Copy link
Contributor

Makes a lot of sense to me. It will be on the AWS server anyway after the next changes.

@nwagenbrenner
Copy link
Member

Related issue firelab/windninja-mobile#113

@ksshannon
Copy link
Member Author

/cc @wmjolly

@ksshannon ksshannon removed their assignment Feb 20, 2019
@nwagenbrenner
Copy link
Member

We have a source now, see #459.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants