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

Capacity for NEW EXCHEQUER-LK MCCLURE seems incorrect #516

Open
michellehoda opened this issue May 20, 2018 · 2 comments
Open

Capacity for NEW EXCHEQUER-LK MCCLURE seems incorrect #516

michellehoda opened this issue May 20, 2018 · 2 comments

Comments

@michellehoda
Copy link

Hiya! Thanks for making this available—we've been using this viz and associated datasets for research on how young people learn w/ data-driven media.

I suspect there is an error in the listed capacity for the EXC reservoir as it appears in the ca_reservoirs.json and ca_reservoirs.csv files. Right now it says 209 Ac-ft, but the actual storage values in the corresponding EXC.csv are all much greater than that.

@jordansread
Copy link

Hi @michellehoda - we are limited in capacity to correct this issue right now, but thank you for bringing it to our attention.

It does look like the actual capacity of the reservoir is greater than what we are reporting: http://cdec.water.ca.gov/dynamicapp/profile?s=EXC&type=dam

As noted in the reservoir readme, these data were extracted from a variety of sources. The capacity data came from one of two pdfs (depending on state or fed) and the links to those pdfs no longer land on the documents. We built these files in 2014 and it seems this is one place (there may be others) where the initial information we had was corrected in later data sources.

if for your purposes it is only a matter of updating the estimate of capacity to the value currently reported, you should be all set. But if your work requires us to update the data visualization with the new values, it may take us some time to free up the bandwidth to do the update.

@jordansread
Copy link

@michellehoda I think this is now resolved. Can you take a look?

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

No branches or pull requests

2 participants