Permit writers need to be able to view combined annual and monthly data per facility. Currently data is presented in a list format by well or annually, but a way to make a table to show/evaluate monthly use per well and combined well monthly withdrawal for each month with the annual totaled amount is needed. An excel spreadsheet accessible from the reporting page would be fine. Allows one to access use history and compliance anytime and is very needed for pre-application meetings, etc.

Comments

cetisdale created an issue. See original summary.

c_thomas’s picture

c_thomas’s picture

Thanks for the feedback, Erinn. I had set something like this up but it looks like it was overwritten or not working now. We'll take a look. I will be sure to add excel exports wherever they are useful.

Robert - I used the sql views you created for the compliance reports in order to display annual and monthly totals for Facilities. However, it looks like those views aren't working anymore (I swear they were two weeks or so ago when I made them). A few examples of this are (same thing is happening on d.dh as d.beta):

1. On the permit level, Annual Water Use totals are showing up fine. But Monthly totals are not displaying and I'm not seeing a difference between that and the Annual Use view. It seems like the same thing that was happening with the compliance views last week. See: beta/?q=gwp-permit-dash-compliance/66166. The corresponding view to that side panel is: beta/?q=admin/structure/views/view/ows_permit_monthly_use_report/edit.

2. I also set these up to be displayed on the Facility compliance/reporting panel, referencing the permit level. However, both the Annual and Monthly total views are not working here either. The view in question is here: beta/?q=admin/structure/views/view/ows_facility_annual_use_report/edit/page and an example of where the Monthly totals is used is here: beta/?q=gwp-facility-dash-info/66974
I haven't been able to identify an issue with the Views themselves, as I tried a few things to recreate the same data tables.

Could both of these just be a result of the sql views acting up? Let me know what you think.

robertwb’s picture

Curt - check that the "status" variable in any conditions has been changed to the new "fstatus". Also, I noted that in the Permit view the new date range has rolled over and the first report shows blank unless you click for last quarter. If thsts acty what's happening I may just have to clean up that query a bit.

Erinn - when these get updated they will show the paged table view as well as having an s download of the full set of records.

c_thomas’s picture

I changed the status variable to the fstatus and most seems to be working normally. However, for some reason the Facility Monthly Use view is not working properly on d.dh even though it works fine on d.beta. d.dh is not pulling the data, it just has a bunch of empty first months. Check these out:
beta/?q=gwp-facility-dash-info/66974 - Working on d.beta
dh/?q=gwp-facility-dash-info/66974 - Not working on d.dh
dh/?q=admin/structure/views/view/ows_facility_annual_use_report/edit/page_1 - View in question on d.dh

One thing I did notice, the "fstatus" variable is different on d.beta and d.dh. On d.beta, it is still set as a numeric field so "1" is used in the filter to be active. On d.dh, it is set for the text field so "active" is used in the filter. I had to change this on import to make it work. This is probably just something that needs copied over to d.beta, when that happens I can change the views accordingly.

robertwb’s picture

Curt - I think I got this sorted - at least the one facility view. The numeric argument filter for year employs the enahncement that I coded to allow us to specify "ON" or "WHERE" for the filter criteria. For some reason, it seems that the one on d.dh was using "ON" even though the setting was "WHERE" - but all you have to do is save the argument handler and it works. I need to spruce up my patch on this so that we don't run into this any longer.

Try now: http://deq2.bse.vt.edu/d.dh/?q=gwp-facility-dash-info/66974

As for the 'active' versus '1' on d.beta, that is one of the reasons that we need to do a full cloning this week, they have gotten out of synch enough that it is impeding testing. More later.

c_thomas’s picture

Thanks for taking a look, that fixed it. I may rearrange what goes where since it slows down the Overview page a bit. It is working now though.

Handling the rest of my migration list this afternoon, so we should be close to cloning tomorrow on my end.

c_thomas’s picture

Status: Active » Needs review
robertwb’s picture

Cool - after the migration we can take a look at this and see if there are some good ways to speed it up.

jkleiner’s picture

Priority: Normal » Minor
Status: Needs review » Closed (fixed)