-
Notifications
You must be signed in to change notification settings - Fork 4
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
Remove Basin Lat Long in favor of on the fly calculation #97
Comments
@scotthavens how do you feel about this being abstracted and added to spatialnc? |
Where else does this get used? I don't see this being used many other places at a the moment. I can see #100 being moved to spatialnc since katana and others would use it. |
The function I wrote to calculate the center is what I was thinking might go into spatialnc. You are right I don't think it gets used anywhere but I thought if might be useful for general analysis stuff. Thats a good call on #100, I will try to add that to spatialnc. |
The basin lat/lon is only used in the solar angle calucation that was improved on it PR #141. Down the road, we can calculate the sun angle for every point on the basin which would allow us to remove this. |
* Updated utm py package, Removed basin lat/lon for autocalc, assigned all lat log references to the topo class, retrieving zone number from the topo.nc, added a northern hemisphere config option to avoid rewriting topos files since they dont have the zone number. Removed a couple deprecated recipes relating to topo * Updating the tests, added in a center finding for the basin mask only * Added in a loadtopo test * Removed all the gridded zone numbers and zone letter references to the config file. Updated the config file and autocalculated the basin_lat long. Fixed #100 and #97 * Removed all the class attributes in loadGrid so they directly refer to the topo class, added a test to insure these attributes stay. * DRYing out load grid while I am here * Updated gold config files
We would like to remove the basin lat and long from the config file in exchange for calculating it on the fly from the topo.nc
The text was updated successfully, but these errors were encountered: