Stream updates

Gage x Gauge:
Genearal Metadata "Gage" should replace "Gauge" (this goes for all streams)

General metadata instances count -- throughout all files, here is an example of Hydro metadata only.

Filename : Number of "gauge" instances

File Name Update Status
=========================
adams.xml:10 Done
aiken.xml:10 Done
anderson.xml:10Done
barteast.xml:11Done
bartflume.xml:11Done
bartwest.xml:11Done
bohner.xml:7Done
canada.xml:10Done
clark.xml:11Done
commonwealth.xml:10Done
crescent.xml:10Done
delta.xml:11Done
garwood.xml:10 Done
green.xml:10Done
harnishf11.xml:10Done
harnishf7.xml:10Done
house.xml:10Done
huey.xml:10Done
lawson.xml:10Done
lostseal.xml:10Done
lowermiers.xml:11Done
lyons.xml:10Done
onyx_lwright.xml:11
onyx_vanda.xml:11
priscu.xml:10
santafe.xml:13
victorialkout.xml:11
victoria.xml:11
vonguerard.xml:10
= = = = = = = = = = = = =
for example, in "adams.xml":

Line number: actual sentence with gauge : XML tag/group
132: longitudes for each stream gauge can be found in the this web site. Adams Stream : geocov
160: The 'discrete_stream_gauge' table was created by Harry House in early 1994. It : maintenance
168: a geographic information system, Denise created a field for "strmgageid" (stream gauge id), : maintenance
172: to location, and contains records from the start date of monitoring for a given stream gauge. : maintenance
218: and conductivity in a network of stream gauges. Stage is monitored with pressure : methods
230: simultaneously noting the readings from the gauge probes. : methods
280: Code representing discrete stream gauge measurements dataset : attributeDef
286: Code representing discrete stream gauge measurements dataset : attribute/nominal/definition
299: Code representing stream gauge : attribute/attributeDefinition
305: Code representing stream gauge : attribute/nominal/definition

=== = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Other tasks/updates

Aiken Creek Hydrology
Gage removed 17 Jan 2013 at 12:52, new gage installed upstream on 21 Dec 2011, awaiting enough field visits to populate rating curve to finalize data.
*New site, needs multiple seasons of record to develop stage-discharge relationship.

Bohner Stream Hydrology
Cannot get to site metadata. Gage control was constructed on 27 Jan 2011 at -77.696302°, 162.558285° and the data record began on 02 Feb 2011.
*New site, needs multiple seasons of record to develop stage-discharge relationship.

Bohner metadata was not properly entered in the database. Fixed

Harnish Creek Hydrology
2000-2001 No flow for season Done
1997-2000 No flow for season marks adjusted to show on web Done
general metadata and measurement metadata updated

House Stream Hydrology
Gage was removed 30 Jan 2012 due to lake level rise Done
general metadata and measurement metadata updated

Huey Creek Hydrology
Gage removed 19 Jan 2011 due to debris flow, new gage upstream has not yet provided useable data
2011-2012 Data Not Collected
2012-2013 *New site, needs multiple seasons of record to develop stage-discharge relationship.
2013-2014 *New site, needs multiple seasons of record to develop stage-discharge relationship.
Done - well, need Page footnote!
general metadata and measurement metadata updated

Priscu Stream Hydrology
Gage removed 18 Jan 2011 due to lake level rise and sedimentation of control, no new site constructed.
Done
general metadata and measurement metadata updated

Santa Fe Stream Hydrology
2000-2001 Gage control was destroyed in flood, site was abandoned. Done
general metadata and measurement metadata updated

Von Guerard Stream Hydrology
Gage removed 20 Dec 2012 due to lake level rise, new gage upstream has been in use since 2012-2013 season Done
general metadata and measurement metadata updated

----------------------------------------------------
details on tasks
from email exchange:

Chris, What about having "new site" and "relocated site" to distinguish between Aiken and Bohner for example. the other text would be the same.

We can emphasize that in the metadata like you all propose. I think we can add a message also more visible somewhere else in the website, a footnote in the page. While I think if someone *really* needs the data, she'll make an effort to read the metadata, where she'd learn how to access it, but perhaps adding a 'footnote' sign like a * to the short message

New Site*
Relocated Site*

will enable us to be explicit right on the page, while preserving the fragile table layout that requires us to be brief.

and extra page footnote would urge the reader to email us for access to prelim. metadata, and also, to read the metadata for detailed cautionary warnings about that preliminary data. With all those cautionary notes, do you think we may have cover everyone needs?

==============================================================

Status: 

Priority: 

Normal