I was not able to put the AW gage ID in the feild when I tried to update a river reach in NY:
[www.americanwhitewater.org]
I wanted to put this in AW data base: [waterdata.usgs.gov]
There seems to be instructions for put a gage that has an AW ID into the field when updating a river reach but there dose not seem to be instructions when the gage needed is not in the AW reach.
The gage at Phencia seems to be no longer in service. The link above for USGS # 01362370 was somewhere along rte 214. I believe this is a new gage. In any case, it on line, the other that was on AW (USGS 01362380) is not avaiable. A friend (thanks Cameron), showed me this a while back.

James,

We should have every USGS gauge in our database. Most likely, the one you're looking for is there somewhere, but when our bot fetched it from the USGS server, it didn't fetch the name. I'll look into it and get back to you when the gauge is clearly visible, where it belongs among the NY gauges.

I am also having problems finding a USGS gauge in the AW database, the gauge I am looking at is USGS 08158400 Little Walnut Ck at IH 35, Austin, TX, any ideas?

Thanks,
Chris

Got'em.

They are, respectively, #10772, Stony Clove Creek blw Ox Clove at Chichester and #10771, Little Walnut Ck at IH 35, Austin, TX.

Please let me know of any other "missing" USGS gauges.

Thanks Matt. I put the gage # in but it didn't take yet. Same is true with the Upper Roundout. Is this a 'bug'?
BTW, how did you find it. If I know what you did then perhaps I can do the same without bugging anyone.

Thanks a lot Matt! Jay you may need to click the publish button once you have created a new stretch...

James,

A gauge input, like the reach and photo ID inputs, should react with a drop down menu showing the name of the gauge, after you type in the ID. You have to click on that drop down option to get the input to actually take effect. If the drop down menu does not show, just wait, or type it in again, or ???

Yes, it is a bug that causes problems for others as well. I suspect we will come up with a better system pretty soon.

jaydeeriver Wrote:
-------------------------------------------------------
> Thanks Matt...
> BTW, how did you find it. If I know what you did then perhaps I can do the same without bugging anyone.

Thanks for the offer, but I'm afraid that I have to do it.
I found it by querying the database, using a text-based SQL (Structured Query Language) utility, for the USGS number of the gauge you were looking for. I'm one of the few who have the permissions required to dig that deeply.

I am working on the Gauge Requirements for the site now. One of the new features is the ability to query by gauge id of the upstream provider (USGS gauge #, for example). Hopefully that will help with some of these problems.