Reaches and State listings

16 views
Skip to first unread message

Anthon Allred

unread,
Oct 4, 2025, 12:41:26 PMOct 4
to american-whitewate...@googlegroups.com
All,

Is there a way for the river editors to directly edit the State listing
for a particular reach?  Some time ago, the State listing for a reach
was settable by the river editors.  Apparently because this resulted in
a number of inconsistencies, this changed to an automatic State listing
which included the reach in two states if a reach crossed or paralleled
a State line.  But this automatic process fails when, for some reason,
the reach changes resulting in the State listing becoming incorrect. 
Once an error occurs, there seems to be no way for me to fix it.

I originally raised this issue in June, 2025, but got no response except
that someone (not me) did correct the Delaware Hancock, NY to Port
Jervis, NY reach that I had identified which was listed in New York, but
not in Pennsylvania to include the correct Pennsylvania listing.  So it
seems it can be done.  But how?

Errors I had identified as follows:

1. There is a New river reach - 8. Pearisburg,VA to Glen Lyn, VA
(Narrows) - located entirely in Virginia that appears in the West
Virginia listing.  (This apparently happened because a long reach was
split into two)

2. The Sideling Hill Creek reach (Maryland/Pennsylvania) shows the Creek
as running into West Virginia when no part of the creek is in West
Virginia (This occurred because the reach originally ran into the
Potomac triggering the West Virginia listing.  I changed the reach to
end before it got to the Potomac deliberately in order to avoid this
confusing result, but the West Virginia listing persists).

3. N. Br. Potomac:  6. Black Oak (Gary Yoder River Access) Nr. Rawlings,
MD to Upper Potomac Industrial Park reach properly shows in Maryland,
but in the West Virginia list there is a gap in the West Virginia
listing where it is not shown (this is inconsistent with how adjacent
reaches are shown).  (This occurred because the Pinto access was closed
and the reaches needed to be adjusted).

4. Stony River:  2. Route 50 (in West Virginia) to North Branch of
Potomac River originally ended before the N. Br. Potomac river
deliberately to avoid showing in Maryland, But since it showed in
Maryland anyway, I extended to reach to Kitzmiller, MD (since there's no
access at the confluence) and you have to run most of the Kitzmiller
section of the N. Br. Potomac anyway, this may not be such a bad result,
but it is odd to see it in the Maryland listings.

5. Section 3. of the Russell Fork (Lower Russell Fork - Breaks Park
River Access to below Elkhorn City is entirely in Kentucky, but it
appears in the Virginia Rivers list.  (I don't know how this occurred.)

6. Grassy Creek - Gateway Motel to Breaks Park River Access on the
Russell Fork (2.1 miles) continues into Kentucky, but it appears only in
the Virginia River list. (This occurred because there are two versions
of this reach, one that extends into Kentucky and one that ends at the
State Line).

How can these be fixed...

Tony Allred Jr.


Kevin Colburn

unread,
Oct 6, 2025, 10:35:25 AMOct 6
to American Whitewater StreamTeam Forum
Hi Tony, I hear ya loud and clear. Rather than code an edit interface we'll likely solve this with a new database query. I've been holding bugs like this one back as we've been prioritizing other projects, but I'll ask our programmers for you how we could tackle this and if this is something we could work into our work plan. Sorry that I haven't been more responsive on this issue, but I'll keep ya posted
Reply all
Reply to author
Forward
0 new messages