search

rmeitl / Local-Report-Issue-Tracking

0 stars 0 forks source link

Planned Credit Issue #7

Closed rmeitl closed 8 years ago

rmeitl commented 8 years ago

The logic is similar to the Bay TMDL, and we still need to be dispersing the credit across all watersheds, not just the ones that appear in this report. I think we had that logic down for the bay report, it just probably needs to be tweaked here.

Next time you have an available minute, you can call and we can chat about it.

Basically if there are 50 acres of trees planned for Frederick County for 2018 in the project_credit table, and no watershed is assigned. Your script still needs to subtract any existing treatment in the luchange_bmp table joined to tmdl_activity. And then the remaining should be dispersed evenly between watersheds. So there are X amount of watersheds in Frederick county, so the value should be divided by X. And then that is the resulting number that gets placed in the planned column for these individual county-watershed tabs in the local report.

rmeitl commented 8 years ago

It looks like this is functioning for strategies when there is no similar project ids in the tables joined to tmdl_activity. Closing this one for now.