StreamTeam Forum : American Whitewater Forums
Discussion area for StreamTeam and AW National River Database issues
How do I verify a reach?
Posted by: jkodadek (IP Logged)
Date: February 23, 2008 07:11PM
Even after I am a Streamkeeper, I can't seem to figure this part out. Thanks.
Jesse Kodadek,
Hamilton, MT
Edited 1 time(s). Last edit at 02/23/2008 07:36PM by jkodadek.
Jesse Kodadek,
Hamilton, MT
Edited 1 time(s). Last edit at 02/23/2008 07:36PM by jkodadek.
Re: How do I verify a reach?
Posted by: pmartzen (IP Logged)
Date: February 27, 2008 04:29PM
Hello Jesse,
The regional Stream Team Leaders do the verifying. There is a button on the river page to "Request Verification". You can also send a message to your regional ST with a link to the river and ask for verification and feedback.
Verification is just an excuse to have someone else confer with you and see that the river page is reasonably complete. There are no hard rules on when a reach is verified, but we like to see a decent description, some directions, flow information, descriptions of the major rapids and hopefully a few photos. River pages can always be added to and improved upon, but we want to see a solid foundation of information before we verify a reach.
Once we verify a reach, all that happens is that the name shows up in bold on the state river list. So it is really just encouragement to talk with a regional ST about the river page and get feedback. If you have a page that you are proud of, please post a link here, so that the rest of us can enjoy it and learn from your efforts.
Paul
The regional Stream Team Leaders do the verifying. There is a button on the river page to "Request Verification". You can also send a message to your regional ST with a link to the river and ask for verification and feedback.
Verification is just an excuse to have someone else confer with you and see that the river page is reasonably complete. There are no hard rules on when a reach is verified, but we like to see a decent description, some directions, flow information, descriptions of the major rapids and hopefully a few photos. River pages can always be added to and improved upon, but we want to see a solid foundation of information before we verify a reach.
Once we verify a reach, all that happens is that the name shows up in bold on the state river list. So it is really just encouragement to talk with a regional ST about the river page and get feedback. If you have a page that you are proud of, please post a link here, so that the rest of us can enjoy it and learn from your efforts.
Paul
Re: How do I verify a reach?
Posted by: rob (IP Logged)
Date: March 04, 2008 04:49PM
Well, as Paul said, "There are no hard rules on when a reach is verified..." That is unfortunately true. As a result, when a reach is marked as 'verified', it has very little meaning whatsoever.
Paul went on to say "...we like to see a decent description, some directions, flow information, descriptions of the major rapids and hopefully a few photos ..." and " we want to see a solid foundation of information before we verify a reach."
Frankly, as Midwest Regional STLeader, I do have a pretty well defined checklist that I follow before I will mark a reach as "verified".
(1) Put-in and Take-out Latitude+Longitude fields filled in (essential for "Maps" and "Directions" tabs to function)
(2) The "Directions" tab shows the normal (or at least a reasonable) shuttle route, or comments have been user-added to explain differences from what is shown. (The system default is based upon the entered Lat/lng for put-in and take-out, which sometimes have to be 'tweaked' to make the shuttle work out right!)
(3) HUC value filled in (essential for listing state "by drainage")
(4) Zip Code filled in (essential for "Weather" tab to function),
(5) length, gradient, and class values filled in,
(6) a fairly robust description which gives a good 'feel' for the nature of the reach.
Specific attention should be paid to significant drops, play features, and information on any known hazards.
If the run is fairly continuous, or if it contains only one or two significant rapids, I prefer NOT to see use of the "Edit Rapids" feature ("Rapids" tab), but rather just include all information in the general description.
If there are at least three or four distinct rapids, playable features, hazards, and so forth, the "River Info" description should be a general overview. It may contain specifics about access concerns, area amenities, and other peripheral matters, but should contain only a high-level overview of the run, since the details of the run will be provided in the "Rapids" tab.
(7) At least some kind of flow information.
If a USGS online gauge is available, at least a "Minimum Recommended Flow" should be specified. ("Maximum Recommended Flow" would be nice, but is less critical.)
If no online USGS gauge exists on the reach, and no nearby USGS gauge can provide any reasonable degree of correlation, then some other 'paddlers gauge' or other indicator of runnable levels should be given.
(8) If any photos of the reach have been uploaded, one of them should be selected as the "featured" photo.
All that said, I don't place much emphasis on "verification" because I believe the important part is to get the information out there. So much of the StreamTeam project/database/interface is in such a state of flux, undergoing regular and significant enhancements and changes. Reaches which may have been 'verified' years back may now be woefully lacking (within the currently defined structure of the website).
Rob Smage
AW member since 1992, volunteer since 2000, Midwest Regional StreamTeam Leader
Paul went on to say "...we like to see a decent description, some directions, flow information, descriptions of the major rapids and hopefully a few photos ..." and " we want to see a solid foundation of information before we verify a reach."
Frankly, as Midwest Regional STLeader, I do have a pretty well defined checklist that I follow before I will mark a reach as "verified".
(1) Put-in and Take-out Latitude+Longitude fields filled in (essential for "Maps" and "Directions" tabs to function)
(2) The "Directions" tab shows the normal (or at least a reasonable) shuttle route, or comments have been user-added to explain differences from what is shown. (The system default is based upon the entered Lat/lng for put-in and take-out, which sometimes have to be 'tweaked' to make the shuttle work out right!)
(3) HUC value filled in (essential for listing state "by drainage")
(4) Zip Code filled in (essential for "Weather" tab to function),
(5) length, gradient, and class values filled in,
(6) a fairly robust description which gives a good 'feel' for the nature of the reach.
Specific attention should be paid to significant drops, play features, and information on any known hazards.
If the run is fairly continuous, or if it contains only one or two significant rapids, I prefer NOT to see use of the "Edit Rapids" feature ("Rapids" tab), but rather just include all information in the general description.
If there are at least three or four distinct rapids, playable features, hazards, and so forth, the "River Info" description should be a general overview. It may contain specifics about access concerns, area amenities, and other peripheral matters, but should contain only a high-level overview of the run, since the details of the run will be provided in the "Rapids" tab.
(7) At least some kind of flow information.
If a USGS online gauge is available, at least a "Minimum Recommended Flow" should be specified. ("Maximum Recommended Flow" would be nice, but is less critical.)
If no online USGS gauge exists on the reach, and no nearby USGS gauge can provide any reasonable degree of correlation, then some other 'paddlers gauge' or other indicator of runnable levels should be given.
(8) If any photos of the reach have been uploaded, one of them should be selected as the "featured" photo.
All that said, I don't place much emphasis on "verification" because I believe the important part is to get the information out there. So much of the StreamTeam project/database/interface is in such a state of flux, undergoing regular and significant enhancements and changes. Reaches which may have been 'verified' years back may now be woefully lacking (within the currently defined structure of the website).
Rob Smage
AW member since 1992, volunteer since 2000, Midwest Regional StreamTeam Leader
Sorry, you do not have permission to post/reply in this forum.
RSS for this Forum