Closed aaarendt closed 3 years ago
Thanks @aaarendt! I had the same thought, regarding deleting the mountainhub module from this package so we only have one mountainhub Python api client (https://github.com/communitysnowobs/mountainhub-api). One additional thing that will be needed here to complete the removal is to remove 'MountainHub'
from https://github.com/communitysnowobs/validation/blob/master/validation/__init__.py#L8. I'll do this in a bit.
the Google Elevation API now costs to use. Have we explored using a free elevation API elsewhere?
I can't remember for sure (maybe you do?), but I think it's still free. I'm sure it's throttled to a usage volume limit. I did look at free elevation API services back when we were dealing with these issues late last year or early this year. I didn't find one obvious replacement with a global domain. But we can revisit it.
I also brought in Dave's metadata about missing data.
There is more to do here - the goal is to enable us to use SNODAS as one of several validation tools for a CSO data paper.
Agreed. Let's strive to move to this package (SNODAS.py
and util.py
) as much of the general SNODAS functionality found in the notebook as possible
This PR aims to revive the earlier code written by Jonah that acquires SNODAS data from the ftp site. Along the way I noted that the calls to the MountainHub script needed to be updated to Emilio's newer API version, and the the Google Elevation API now costs to use. Have we explored using a free elevation API elsewhere?
I also brought in Dave's metadata about missing data.
There is more to do here - the goal is to enable us to use SNODAS as one of several validation tools for a CSO data paper.