			<div   class='message  msg_warn'>
									
				You are currently not logged in or haven't verified your email in a while. Please login or complete the verifictation process to post.
				</div>
			<div style='clear:both'></div>
		<?xml version="1.0" encoding="iso-8859-1" ?>
<rss version="2.0">
  <channel>
    <title>StreamTeam Forum</title>
    <link>http://www.americanwhitewater.org//content/Forum/list/send/25/</link>
    <description><![CDATA[Discussion area for StreamTeam and AW National River Database issues]]></description>
    <language>EN</language>
    <pubDate>Thu, 05 Nov 2009 14:22:44 -0500</pubDate>
    <lastBuildDate>Thu, 05 Nov 2009 14:22:44 -0500</lastBuildDate>
    <category>StreamTeam Forum</category>
    <generator>Phorum 5.1.23</generator>
    <ttl>600</ttl>
    <item>
      <title>Re: Can anyone fix this guy's problem?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,17131,17186/#msg-17186</link>
      <author>pmartzen</author>
      <description><![CDATA[Matt figured out the problem and got him reinstated.    Mark was accidentally added to a list of defunct stream teamers who have not logged in for a long time.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,17131,17186/#msg-17186</guid>
      <pubDate>Thu, 05 Nov 2009 14:22:44 -0500</pubDate>
    </item>
    <item>
      <title>Re: Upload multiple photos using 1 report</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15447,17181/#msg-17181</link>
      <author>pmartzen</author>
      <description><![CDATA[I have added major edits to the original post, to clarify and make it more explicit.    

You can access your older reports and those of anybody else in several ways.  
Reports for a specific river are always listed at the bottom of the flow tab.   
Every photo will have a link to a report.   There will be small buttons under the thumbnail or on the photo's detail page.    Unfortunately, many people are still uploading multiple photos as individual reports rather than linking them in one report.
The most recent reports are also accessible via the AW menu.   Look under: River info/recent river reports.  
http://www.americanwhitewater.org/content/Report/list-recent/region/all/   
There is also a button to access recent reports on the top of the national river map page.   AW menu:  River info/national river database.

A nice benefit of uploading multiple photos in one report is that all of your photos from a trip will be organized in the order that you uploaded them rather than in reverse order.  So if you upload your photos in order from the beginning of your trip to the end of your trip, that is the way they will be displayed in that report.  Here are some examples.
http://www.americanwhitewater.org/content/Report/detail/id/537376/
http://www.americanwhitewater.org/content/Report/detail/id/477046/
http://www.americanwhitewater.org/content/Report/detail/id/568360/
http://www.americanwhitewater.org/content/Report/detail/id/552494/]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15447,17181/#msg-17181</guid>
      <pubDate>Thu, 05 Nov 2009 13:23:25 -0500</pubDate>
    </item>
    <item>
      <title>Re: Can anyone fix this guy's problem?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,17131,17158/#msg-17158</link>
      <author>pmartzen</author>
      <description><![CDATA[I have started to look into it as best I can.  I was able to reassign him to the Doe gorge section without problems and the email that he can't change to is the one presently listed in his profile.   So, despite the error messages, the email was changed to what he wants.  

 I have emailed him but have not heard back yet.    I want to hear back from him, document what happened in case it happens again to him or somebody else, and step through problem solving.   I cc'd Matt, but I think he is off and away right now.   

Some of these bugs can seem pretty random, but hopefully we can get some idea of what instigated it.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,17131,17158/#msg-17158</guid>
      <pubDate>Thu, 05 Nov 2009 03:13:46 -0500</pubDate>
    </item>
    <item>
      <title>Can anyone fix this guy's problem?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,17131,17131/#msg-17131</link>
      <author>skipmorris</author>
      <description><![CDATA[Received this via AW message.  Can anyone fix this guys problem?

/Skip
----------------------------------------------
Major Streamkeeper problems - please help
From: mtnsport
To: wildblue / skipmorris / Dag / dsteindorf / okeefe / pmartzen / rob / KenV / mwlcrx / KHCC-NY / stpcrkr
Date: 11/04/2009 02:00PM

I am searching for the Southeast Regional Streamkeeper or ANYONE who can help. I cannot tell who the SE regional streamkeeper is from the Regional SK directory.

I am having issues with the reaches I manage. Primarily, I cannot get to them to manage. I tried to post on this in the SK forum but was not allowed permission to post. I cannot locate my name in the directory of streamkeepers. Apparently I have been removed from all the reaches I've previously been managing, some for more than 5 years. What gives? I am a current AW member and have been for many, many years. Why was I removed from managing these reaches?

Until recently I was the streamkeeper in TN for the Doe River Gorge, Nolichucky Gorge, lower Nolichucky, and South Fork Holston. In North Carolina, I managed the Watauga Gorge and Nolichucky Gorge.

If this has been an error and these reaches have not already been reassigned to new stream keepers, I would like to again be their streamkeeper; otherwise I would like to know what the issue is.

p.s. please respond to THIS email --&gt; mtnsport70@verizon.net It is not listed as my email in my Email Settings and I cannot change it, everytime I try it leads to an error page. Do NOT respond to my old mtnsport70@chartertn.net address please.

Thank you,

Mark Stover]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,17131,17131/#msg-17131</guid>
      <pubDate>Wed, 04 Nov 2009 13:57:52 -0500</pubDate>
    </item>
    <item>
      <title>Re: Bugs: Reach length dissappearing --  Rapids alignment</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,16553,17055/#msg-17055</link>
      <author>pmartzen</author>
      <description><![CDATA[Other reach examples with misaligned rapid photos:
http://www.americanwhitewater.org/content/River/detail/id/1049/#tab-rapids
http://www.americanwhitewater.org/content/River/detail/id/3101/#tab-rapids
http://www.americanwhitewater.org/content/River/detail/id/3446/#tab-rapids
http://americanwhitewater.org/content/River_detail_id_114_#tab-rapids]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,16553,17055/#msg-17055</guid>
      <pubDate>Mon, 02 Nov 2009 11:55:39 -0500</pubDate>
    </item>
    <item>
      <title>Re: Bugs: Reach length dissappearing --  Rapids alignment</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,16553,17013/#msg-17013</link>
      <author>rob</author>
      <description><![CDATA[This one was written up as a trouble ticket: http://www.americanwhitewater.org/cgi-bin/trac.cgi/ticket/771

Two examples were listed in that ticket:
http://www.americanwhitewater.org/content/River/detail/id/2750/#tab-rapids

http://www.americanwhitewater.org/content/River/detail/id/2378/#tab-rapids]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,16553,17013/#msg-17013</guid>
      <pubDate>Sat, 31 Oct 2009 09:15:25 -0400</pubDate>
    </item>
    <item>
      <title>Re: Questions about gauge list</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15118,16983/#msg-16983</link>
      <author>rgroth</author>
      <description><![CDATA[I think this deals with efficiency. I am getting the real-time gauge info from a single page that only lists stage. To get flow I need to hit several gauges. I can come up with a parallel way to get flow on specified gauges, but probably can't get all cdec gauges that way.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15118,16983/#msg-16983</guid>
      <pubDate>Thu, 29 Oct 2009 18:00:06 -0400</pubDate>
    </item>
    <item>
      <title>Re: Adding USGS gage</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,16494,16982/#msg-16982</link>
      <author>rgroth</author>
      <description><![CDATA[They automatically get added now!

Ryan]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,16494,16982/#msg-16982</guid>
      <pubDate>Thu, 29 Oct 2009 17:56:35 -0400</pubDate>
    </item>
    <item>
      <title>Re: Bugs: Reach length dissappearing --  Rapids alignment</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,16553,16981/#msg-16981</link>
      <author>rgroth</author>
      <description><![CDATA[Fixed the first problem dealing with reach length. 

Can someone guide me to an example of the second?

Ryan]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,16553,16981/#msg-16981</guid>
      <pubDate>Thu, 29 Oct 2009 17:56:02 -0400</pubDate>
    </item>
    <item>
      <title>Re: Bugs: Reach length dissappearing --  Rapids alignment</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,16553,16595/#msg-16595</link>
      <author>rob</author>
      <description><![CDATA[A couple of comments about the 'work around' --

1) You need to make sure the description for the rapids is two lines (or more) when the rapids page is viewed in the regular browser. The pop-up WYSIWYG editor box (where you actually enter the description) will likely need to be at least three lines long in order for the resulting description to fill one line on the browser screen.

2) EACH and EVERY rapids down the list needs to have a description longer than one line (screen width), or the same problem will again arise.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,16553,16595/#msg-16595</guid>
      <pubDate>Thu, 15 Oct 2009 11:14:20 -0400</pubDate>
    </item>
    <item>
      <title>Bugs: Reach length dissappearing --  Rapids alignment</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,16553,16553/#msg-16553</link>
      <author>pmartzen</author>
      <description><![CDATA[There are two bugs that stream editors should deal with until they get fixed.  

1)  There was a short period when editing a reach caused the reach length to disappear.   Ryan fixed this problem, but many recently edited reaches are probably missing the length now.  Stream teamers need to check their pages and add the distance back in if that information is missing.

2)  On some reaches with rapids listed on the rapids tab and photos associated with rapids, the alignment has gotten very goofy.   Basically photos and descriptions are out of alignment with the names of the rapids.  

This bug appears when you have a photo for a rapid, but the rapid description is very short. The photo aligns to the right and the next few names of rapids slide up next to the photo on the left.

There is a simple work around. Start with the first photo that is shifted to the right and add enough rapids description, so that the description takes up more than one line on the final display.  The description editing box is very narrow, so the description will have to be 3 or 4 lines there. When the description extends all the way across the page, the photo will be aligned properly all the way back to the left, forcing the subsequent rapids names to display properly below.   Proceed to the next misaligned photo and write a longer description for that one also.   Do the same for all the misaligned photos.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,16553,16553/#msg-16553</guid>
      <pubDate>Tue, 13 Oct 2009 13:47:20 -0400</pubDate>
    </item>
    <item>
      <title>Re: Adding USGS gage</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,16494,16520/#msg-16520</link>
      <author>matt</author>
      <description><![CDATA[[url=http://www.americanwhitewater.org/content/Gauge2/search-limited/]It's there![/url]
It's also linked in the [url=http://www.americanwhitewater.org/content/Gauge2/view/state/GA/]Georgia list[/url].]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,16494,16520/#msg-16520</guid>
      <pubDate>Mon, 12 Oct 2009 19:52:25 -0400</pubDate>
    </item>
    <item>
      <title>Re: Questions about gauge list</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15118,16503/#msg-16503</link>
      <author>pmartzen</author>
      <description><![CDATA[Here is an example of a CDEC gauge that has stage and cfs, but AW only shows stage.
http://cdec.water.ca.gov/cgi-progs/stationInfo?station_id=MSN

Looks like all California CDEC based gauges only show stage even though the originating gauges show both flow and stage.

USGS based AW gauges seem to show both flow and stage.

edit:  I have started a bug ticket for CDEC gauges.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15118,16503/#msg-16503</guid>
      <pubDate>Mon, 12 Oct 2009 14:28:44 -0400</pubDate>
    </item>
    <item>
      <title>Adding USGS gage</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,16494,16494/#msg-16494</link>
      <author>ga_creeker</author>
      <description><![CDATA[How do you add a gage?  USGS has a new gage on the Chattooga for the Headwaters located at Burrells Ford.  This is the gage that will be used to regulate boating.

http://waterdata.usgs.gov/nwis/uv?02176930]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,16494,16494/#msg-16494</guid>
      <pubDate>Mon, 12 Oct 2009 12:46:30 -0400</pubDate>
    </item>
    <item>
      <title>Re: key to rapid ratings?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15989/#msg-15989</link>
      <author>KF8MO</author>
      <description><![CDATA[Agreed, some rapids actually get easier at higher water, etc.  When I refer to the Lower Yough not being Class III at 6 ft, I don't mean just because it's big and pushy (though it certainly is).  Some of the rapids in fact actually wash out almost completely; Double Hydraulic for example is much easier.  Others however become more complex and difficult, with definite must moves and significant consequences for missing them.  As per the Class IV definition, some become &quot;intense, powerful... with large unavoidable waves and holes&quot;, etc.  Water conditions definitely make self-rescue difficult, and if you swim you might be able to find your boat down at Connellsville... or not!

The point is that the river doesn't just become &quot;more&quot; of the same stuff at higher level, many of the rapids undergo significant qualitative changes that change their ratings (as well as change the lines).  It's not necessarily true of all rivers, it really depends on the structure of what forms the rapids as to whether they flush out or get more complicated.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15989/#msg-15989</guid>
      <pubDate>Thu, 24 Sep 2009 22:37:51 -0400</pubDate>
    </item>
    <item>
      <title>Re: key to rapid ratings?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15949/#msg-15949</link>
      <author>rob</author>
      <description><![CDATA[Well, that does enter into one of my other 'pet peeves'. Just because a river is running 'big', does not mean the rating (inherent difficulty level) goes up. And in cases where it does go up, [i]generally[/i] I can see it bumping up just a half step or one full rating. It is highly unlikely that a stream would go from class II (at 'normal' 'usual' flows) to class IV or V (at any high boatable flow).

If you look at the ratings descriptions (http://www.americanwhitewater.org/content/Wiki/do-op/id/safety:start#class_i_rapids) and actually read them CAREFULLY and thoroughly, and really critically assess things, I hope you would agree with this assertion. In fact, particularly for the lower rated rivers/rapids (up to class III-) it is almost as likely that high water may actually diminish the inherent difficulty, as the river/rapids may just 'wash out', or alternate lines open up. Again, critical reading even for just a class III suggests (with my emphasis added in bold) &quot;[i]moderate, irregular waves [b]which may be difficult to avoid[/b][/i]&quot; and &quot;[i][b]Complex maneuvers[/b] in fast current and good boat control in [b]tight passages[/b] or around ledges are often required[/i]&quot;. So, just because perhaps a BIG hole develops somewhere (at high water), doesn't necessarily mean the rapids is necessarily a class III or IV. If you can easily see it, and a reasonably experienced/skilled boater can easily get around it, the river/rapids may still only merit a class II. Without a doubt, the river will be more 'pushy', and it may put somewhat (or even significantly) higher demand on the skill and confidence you need to successfully negotiate it. Those not experienced in high-water runs may be way out of their comfort zone. However, the inherent difficulty of the river/rapids is likely to bump up only slightly (again, a half- to a full-step).

Parallel to this idea, I think too many people have the idea that anything rated class II means 'beginner whitewater', and that virtually any beginner/novice boater should be absolutely fine on it. As if ALL you need to know is the class rating. (Unfortunately, that idea is reinforced in the cited AW page on ratings, by the fact that the headings state &quot;Class II Rapids: Novice&quot;, &quot;Class III: Intermediate&quot;, &quot;Class IV: Advanced&quot;, etc.) In fact, all experienced boaters know that a whole combination of factors all enter into the equation of how 'beginner appropriate' (or, for that matter, how appropriate for some particular intermediate or more experienced paddler) some rapids or stretch of river is. Rating (class) is but one measure, one consideration. Whether the rapids are short (pool/drop) or long (continuous) is another important consideration. Whether the river and rapids are wide, open, and unobstructed, or complex, boulder bed, ledge-drops, constricted, narrow, steep-walled dells/gorge, etc, is another important consideration. Whether any bigger drops or blind drops exist, and whether one can easily get out to scout them, is obviously quite important. And, yes, flow (and the boater's specific experience and comfort level with higher flow) is an important consideration.

So, a more appropriate idea would be Class II, low -to-moderate flow, pool-drop, fairly open, 'boat-scoutable' rivers and rapids are 'beginner whitewater'. Class II, high flow, continuous, perhaps only minimal shoreline eddies, and difficult (or impossible) banks to get out to scout or portage, is NOT beginner whitewater! (And, all that [i]could[/i] fit into the class II description.) In fact, I could cite a good number of rivers or rapids (in the upper Midwest, where I do almost all my boating) which I would say rate class II (at fairly 'normal', moderate flows) but which are NOT what I would call 'beginner whitewater', either due to being fairly continuous, or being small, intimate creeks having few eddies, or being in steep-walled banks (with virtually no chance for recovery of a swimmer and their gear). Beginners could do them, but only if accompanied by experienced boaters.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15949/#msg-15949</guid>
      <pubDate>Wed, 23 Sep 2009 09:54:46 -0400</pubDate>
    </item>
    <item>
      <title>Re: key to rapid ratings?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15931/#msg-15931</link>
      <author>matt</author>
      <description><![CDATA[Thanks for the explanation, Rob. I've listed this as an FAQ Question in [url=http://www.americanwhitewater.org/content/Wiki/do-op/id/rivers:sk:instructions]StreamTeam 101[/url].]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15931/#msg-15931</guid>
      <pubDate>Tue, 22 Sep 2009 05:52:31 -0400</pubDate>
    </item>
    <item>
      <title>Re: key to rapid ratings?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15923/#msg-15923</link>
      <author>KF8MO</author>
      <description><![CDATA[I like the idea of rating by flow.  I paddle the Lower Yough a lot, and it's generally said to be Class III.  It is, at normal summer rafting levels (1.7-2.2 feet).  At 6.6 feet, it's most definitely not Class III, either in skills required or in consequences!]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15923/#msg-15923</guid>
      <pubDate>Mon, 21 Sep 2009 20:23:46 -0400</pubDate>
    </item>
    <item>
      <title>Re: key to rapid ratings?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15863/#msg-15863</link>
      <author>rob</author>
      <description><![CDATA[It 'should' mean the former, I.E., &quot;mostly Class III and IV, but has one Class V drop on it,&quot; However, to be completely honest, since the river pages are the result of contributions by volunteer StreamTeam members, there is unfortunately no guarantee that this interpretation stands in all cases. There may be some sections on the database for which the StreamTeam member lists a rating which intends to cover the range of difficulty at the range of flows the river may be boated. This is unfortunate, especially now, since (on the whole river, not on each particular rapids listed, if they have been detailed for the run) we do now have the provision for the ratings to be tied to flow (on the rivers which have online gauges available). Thus, for example, you may see a river listed as class II-III when the flow is in the lower end of it's boatable range (let's say maybe 200-500 cfs), listed as class III when the flow is in the middle of recommended boatable range (maybe 500-1000 cfs), and listed as class III-IV or IV when flows are in the high end of recommended range. We should all get away from this notion that we can categorically state that such-and-such a river IS class II or class III or whatever, without at the same time specifying AT WHAT FLOW. After all, when you look at the &quot;Standard Rated Rapids&quot; list (http://www.americanwhitewater.org/content/Wiki/safety:class1benchmarkrapids), you will see not only the river and rapids name, but a specified flow/level. The same concept should apply to classifying or characterizing the whole river.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15863/#msg-15863</guid>
      <pubDate>Mon, 21 Sep 2009 08:11:45 -0400</pubDate>
    </item>
    <item>
      <title>key to rapid ratings?</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15854/#msg-15854</link>
      <author>KF8MO</author>
      <description><![CDATA[I'm sure this is covered somewhere on the AW site but I'm not having any luck finding it.  What is the meaning of a rating of, for example, Class III-IV(V)?  Does that mean the stretch is mostly Class III and IV, but has one Class V drop on it, or that it's Class V at higher water levels, or what?  Thanks for any enlightenment.  -Lee]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15854,15854/#msg-15854</guid>
      <pubDate>Sun, 20 Sep 2009 17:11:29 -0400</pubDate>
    </item>
    <item>
      <title>Re: Upload multiple photos using 1 report</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15447,15498/#msg-15498</link>
      <author>matt</author>
      <description><![CDATA[I've added your instructions to [url=http://www.americanwhitewater.org/content/Wiki/do-op/id/rivers:sk:photo_video_101]Photo/Video 101[/url]. Thanks!]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15447,15498/#msg-15498</guid>
      <pubDate>Mon, 31 Aug 2009 18:28:32 -0400</pubDate>
    </item>
    <item>
      <title>Re: Upload multiple photos using 1 report</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15447,15491/#msg-15491</link>
      <author>rob</author>
      <description><![CDATA[It is important to note this means one report per RIVER trip.
If your day (or your weekend or your week . . .) included different rivers,
or even if it included different sections of the same river,
a different report should be created for each,
so the photos will be attached to the correct section.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15447,15491/#msg-15491</guid>
      <pubDate>Mon, 31 Aug 2009 13:35:27 -0400</pubDate>
    </item>
    <item>
      <title>Upload multiple photos using 1 report</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15447,15447/#msg-15447</link>
      <author>pmartzen</author>
      <description><![CDATA[When you take a number of photos on a single river reach, please upload them to the AW website via a single report for that river section.  When you create a new report for a river trip, you enter the state, river reach, and date information and also some description of the trip.  It is very nice and adds a lot if you enter descriptive information for photos and reports.   The reach information is important as that will link the report to the correct river.  Reports and photos will not automatically link to a river if you do not enter the reach info.  

You can create a new report from several locations on the AW website.  

1) The photo page:  Menu: Library/Photo Video   http://americanwhitewater.org/content/Photo/view/     Near the upper left corner of this page are 3 buttons one of which is &quot;Upload Multiple Photos&quot;.  Clicking this takes you to the report editor.  

2)  Your personal photo page:  Menu: My Account/ Manage Photos    Click on the &quot;Upload Multiple Photos&quot; button.

3) From any river page go to the Flow Info tab and look at the bottom of that page.  Click on the  button for &quot;New Report&quot;.

At the Report editor, fill in the appropriate information about the river and trip.  
1)  Give the report a simple title
2)  Write a brief description of the trip or paste in a full length trip report.  
3)  Location -  I think this refers to nearest city or town.
4, 5, 6)  Country, State, River/Section:  Each of these boxes have drop down/up menus to allow the correct selection.   Click on the gadget at the right end of the entry box and wait for the menu to respond.  Or, start typing the name and wait for the menu to respond with more limited options.  
7) Date, time and time zone.    Enter the date or use the calendar button to change the date.   Use the drop down menu to change the time to some approximate time of the trip.    The time zone never stays where I put it, so I don't know what to say about that.   Maybe the time zone has some effect, maybe it doesn't.  
8) River level:   Check mark what ever option seems appropriate to you.
9)  Gauge level:  If you check &quot;Yes&quot; additional options appear that allow you to list the gauge (confusing but possible) and to state what you think the gauge reading was.
10)  Add Photo:   This button appears if you are editing a report and if you are creating a new report from the &quot;Upload Multiple Photos&quot; button.  It does not appear on the report editor accessed from the &quot;New Report&quot; button on the river reach flow tab.
11)  Save 

Presently (2009) there are two versions of the report editor.   I think that the one accessed from the photo/video page is a bit nicer as it has a bigger box for entering a trip description and it actually has a button on the bottom of the page that says, &quot;Add Photo&quot;.   

If you start a &quot;New Report&quot; from the flow tab of a reach, the river reach info is automatically entered, but the &quot;Add Photo&quot; button is missing.   Save the report, see it in the reach report list, click on it to open the report, then click on &quot;edit report&quot;   At that point the &quot;Add Photo&quot; button will show up at the bottom of the page.

Click on the &quot;Add Photo&quot; button to open a pop up window / sub window where you can browse for the photo file and add info specific to that photo.  
1) Caption - A short title for each photo
2) Author - You, but should be automatically entered.
3) Subject - Generally the name/names of people in the picture.
4)  Description -  Please write something about the photo to explain it.  It is a small box, but you can write multiple lines.  
5)  Rapid name -  if there is one and you know it.  

Click on the &quot;Update Photo/Video&quot; button and wait for the upload to finish.  After the upload is finished a thumbnail will appear on the right side of the report editor.  You can again click on the &quot;Add Photo&quot; button.   You can add all the photos from a  trip on a single river section to the same report, since much of the information will be the same for all of the photos.

You can come back and re-edit a report to add further information and more photos at any time.  Reports for a reach are found at the bottom of the flow tab for each reach.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15447,15447/#msg-15447</guid>
      <pubDate>Sun, 30 Aug 2009 16:14:04 -0400</pubDate>
    </item>
    <item>
      <title>Re: Questions about gauge list</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15331/#msg-15331</link>
      <author>pmartzen</author>
      <description><![CDATA[Yes, I meant stage and flow/cfs.   I forget which gauges where USGS has both Stage and cfs but AW has only a gauge with stage.   I have seen a few instances.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15331/#msg-15331</guid>
      <pubDate>Tue, 25 Aug 2009 02:38:48 -0400</pubDate>
    </item>
    <item>
      <title>Re: Questions about gauge list</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15323/#msg-15323</link>
      <author>matt</author>
      <description><![CDATA[I think Paul meant that there are several gauges where our AW list only shows a stage gauge, but USGS has both stage and [i]flow[/i]. Paul, can you clarify?]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15323/#msg-15323</guid>
      <pubDate>Mon, 24 Aug 2009 18:12:17 -0400</pubDate>
    </item>
    <item>
      <title>Re: Questions about gauge list</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15302/#msg-15302</link>
      <author>rgroth</author>
      <description><![CDATA[Stage should be feet, most of the time...?

Ryan]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15302/#msg-15302</guid>
      <pubDate>Mon, 24 Aug 2009 14:51:48 -0400</pubDate>
    </item>
    <item>
      <title>Re: Questions about gauge list</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15295/#msg-15295</link>
      <author>pmartzen</author>
      <description><![CDATA[With USGS and some other gauges, there can be several measurements taken at a single location.  So a single gauge can have info for both stage and cfs, historical flows, temperature, water quality, etc.   

I find it a bit confusing when the AW gauges have different numbers for the same gauge when it has both stage and cfs.   I have noticed several gauges where our AW list only shows a stage gauge, but USGS has both stage and feet.  (Oops, I meant Stage and cfs.)]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15295/#msg-15295</guid>
      <pubDate>Mon, 24 Aug 2009 04:02:08 -0400</pubDate>
    </item>
    <item>
      <title>Re: Questions about gauge list</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15193/#msg-15193</link>
      <author>rob</author>
      <description><![CDATA[I completely understand the legitimate reasons for the use of rainfall amounts (from 6hr, 12hr, 24hr). It is only the [b]annual rainfall[/b] amount which seemed almost completely irrelevant to report. And, again, aside from that, the more important matter was to stimulate discussion or thought about other ways to organize or selectively display the list.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15193/#msg-15193</guid>
      <pubDate>Tue, 18 Aug 2009 07:06:24 -0400</pubDate>
    </item>
    <item>
      <title>Re: URGENT: &quot;MAP IT&quot; is broken on &quot;Rapids&quot; tab.</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,12921,15155/#msg-15155</link>
      <author>rgroth</author>
      <description><![CDATA[I have a fix. There was a version up on PHP upstream on our update servers and I needed to use most of the weekend to head off problems with it, as well as provide a couple tweaks including this one. I expect a release early this week.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,12921,15155/#msg-15155</guid>
      <pubDate>Sun, 16 Aug 2009 21:44:31 -0400</pubDate>
    </item>
    <item>
      <title>Re: Questions about gauge list</title>
      <link>http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15154/#msg-15154</link>
      <author>rgroth</author>
      <description><![CDATA[I'd be open to ways to organize the data. The option for rain allows us to gauge microcreeks. It was requested by Alex Zendel, and didn't cost us any more money.]]></description>
      <category>StreamTeam Forum</category>
      <guid isPermaLink="true">http://www.americanwhitewater.org//content/Forum/read/send/25,15118,15154/#msg-15154</guid>
      <pubDate>Sun, 16 Aug 2009 21:40:51 -0400</pubDate>
    </item>
  </channel>
</rss>
