change google cloud api into GEE api about hydrate

[KMarkert]

Hi @kongdd 👋 ,

Theoretically the backend data access from EE can be changed over to using the Python API as opposed to using the REST API. But, by doing this though there will be limitations on user requests which can take a very long time to get the data for large areas or just fail. This is particularly the case for meteorological forcing data. So, using the cloud REST API was more of a performance choice.

If the Python API were to be used, the data model and how data is accessed/formatted will need to be updated. There can be another backend data model added so users can pick whichever API access is most convenient for them.

It will take a good amount of time to make these changes which I, unfortunately, do not have at this moment...I will be happy to guide and work with you to make these updates if you would like to work on them. Please let me know if that is the case!

[kongdd]

Thanks for your warminy help. I have produced those forcings successfully. But running into another problem.
Could you give an example about how to use the routing function in VIC, https://github.com/KMarkert/hydrate/blob/master/hydrate/models/vic.py#L14?

Cheers,
Dongdong