Chattahoochee at atlanta on the aw page is only reading in feet.

[www.americanwhitewater.org]

[waterdata.usgs.gov]

USGS is still showing cfs. Anyway to have our code recognize the cfs reading?

Hmmm. I am working on gauge code for the next version of the site. I'll take a look at it.

Brad,

When someone edits a river page, the Flow - Stage setting has a tendancy to default to Stage. I can't tell why it does this sometimes and not others. It accepts the Flow setting when I deliberately reset it to Flow.

So this could have been the problem on the Chattahoochee at atlanta page. It is correctly reading Flow now, so somebody fixed it.

##



Edited 1 time(s). Last edit at 03/11/2008 02:11AM by BradR.

well, it was back for a bit, and now it has dropped out again........and folks are calling me asking why.

I don't know why this is happening. The USGS site for this gage is reporting properly; we have the correct parameters for the Hooch Gage in our database (and the gage does read the Flow and Stage correctly from the USGS site); and the Metro Hooch reach does indeed have "Flow" selected as the parameter. I'm stumped; I'll try one more thing...

Hey, that worked! I reset the gage by editing the reach, selecting "Stage" as the parameter, then edited the reach yet again, this time correctly selecting "Flow" as the parameter. Now it's reading the Flow, reporting 826 cfs (as of 8 AM this morning) and color-coding it in pink (salmon?), as it's just a few spoonfuls below the 850-cfs min. That's a workaround, equivalent to the Microsoft model of turning the 'puter off and turning it back on again...butt at least it worked, this time.

I return to what I said at the beginning: I have no idea why, without human intervention, the database decided to stop using the Flow reading and color-coding the reach.

broken again.....

it's back.
I've seen it down, and I noticed that the graph didn't show and the flow was blank. The logic involved is that if we get a blank flow (from a broken gauge) then we don't show the graph. We get updates about once every four hours on that gauge and we throw away the results of last flow if we get a new stage update. I suspect that USGS isn't or doesn't report a flow every once and a while (ice, flood, etc..) and then decides to do an update later. The result would be what you have seen. The new system uses the last value found in 48 hours or nothing to keep dead gauges from sticking around for 10 years. You (as an SK) can setup multiple gauges as well to specify flow or no flow. For this reach I would recommend using the equivalent high and low stages for now since stage keeps coming in without a problem.

rgroth Wrote:
-------------------------------------------------------
...You (as an SK) can setup multiple gauges as well to specify flow or no flow. For this reach I would recommend using the equivalent high and low stages for now since stage keeps coming in without a problem.

How do we set up multiple gauges? Are you saying that there's a tool which allows us to link a reach to a variety of gauges at the same time?

rgroth Wrote:
-------------------------------------------------------
. For this reach I would recommend using
> the equivalent high and low stages for now since
> stage keeps coming in without a problem.


Does this mean every time that USGS burps on its data we should automatically change how the gauge reads from stage to flow, or flow to stage? Flow is the best indicator of what the stream is actually doing, unless there is a historical precedent with the gauge. And even on runs where the stage is has been used forever, say the New River gorge, folks tend to prefer using flow over stage when possible. The Georgia USGS page appears to have undergone some changes that are causing us problems. If that is the case will someone have to modifiy every gauge that changes back from flow to stage?