strongh/climateactionr

climateactionr's Issues

Climate::PRISM normals

http://www.prism.oregonstate.edu/normals/

Colorado River salinity data

Land use mix

http://geodacenter.asu.edu/%5Btermalias-raw%5D/land-use-mix

Historic river flow

Land use::vegetation maps

hardiness zones

Bad news: the official USDA data is not free (?!?!).

Good news: it's easy to calculate ourselves. The hardiness zone is simply determined by the average minimum temperature. Also the USDA just uses the PRISM data, which is free, so if we also use PRISM we should get the same result.

bounding box?

Probably makes sense to have a standard bounding box for the region of interest. Roughly this could be the southwestern US. Something like

• lat: from 31 to 42
• long: from -124 to -104

River basin boundary mismatch

River basin boundaries should be used with caution. The Full, Upper, and Lower boundaries don't align in all parts of the basin. This is unlikely to be a projection issue, but the metadata are not clear as to how the basin boundaries are determined.

Potential solutions:

• Find better shapefiles
• Use only more reputable Full basin file, ignore Upper and Lower files

check milestones

Please check the wording on the milestones to make sure they're clear and concrete enough

can we move all the data scripts into a sub directory?

it's getting a bit crowded at the root.

dataset: CA population projections

crops with hardiness zone

reservoir capacities

Might not be the same thing, but here are historical records
Lower basin:
http://www.usbr.gov/lc/region/g4000/hourly/hav-elv.html
http://www.usbr.gov/lc/region/g4000/hourly/moh-elv.html
http://www.usbr.gov/lc/region/g4000/hourly/mead-elv.html

Upper basin:
http://www.usbr.gov/rsvrWater/faces/rvrOSMP.xhtml

water quality

http://waterdata.usgs.gov/nwis/qw