I've tried to add photos to reach descriptions, or to change the signature photo for a reach, without success. I enter the search terms in the field, and the interface returns a "the value you entered is not valid" error massage.
So when I blank out the field, the system gives me a choice from among the photos associated with the reach. That's cool. I choose a photo and click on "Update Edit Copy."
Butt two things happen:
1) When I click on Preview, the new photo doesn't show up; and
b) When I go back to the Description tab, the photo field shows some unrelated photo, similar to the problem that Paul described above. (In my case, I'm editing the Bottom Moose, and the field has some photo from the Chili Bar reach of the SF American--yet another case of Californians poking their nose into everyone else's business.)

Looks as though the whole Photos interface needs some serious attention.

StreamTeamer Steve Ettinger, who's populated the MD-WV-PA area with dozens of runnable flow recommendations, noted that some streams were listed as "L9," though they weren't anywhere near runnable. One example: Gunpowder Falls, running 9 cfs.

This is apparently because the lowest of the "Too Low" range defaults to some low negative number, so the algebra thinks that 9 is very close to the minimum (40 cfs).

I fixed this with the Anacostia, Northwest Branch reach, by setting the "Too Low" range to 0-50. Now, at 8 cfs, it's reading "L1." (And it's a pale yellow, rather than the "neon yellow" that one BT'er criticized.*) So that's good.

However, doing this for thousands of reaches would take quite a bit of time. I recommend that, for every reach that reads in flow (cfs), the "Too Low" range default to (0 to min), where min is the (already set) runnable minimum.

If this can't easily be put into the website with the code, perhaps I can do a global change once I've received the tutorial on the inner workings of the new design.



* The BT'er said something like "What's with the Neon Yellow? Did you get that color for free, or something?" LOL. Though I gotta point out that neon doesn't fluoresce in the yellow range of the spectrum, I still thought it was a pretty funny dis.

...post it tomorrow hopefully.

As far as the lows, I think I am going to turn them all a solid yellow and keep the runnable ranges the way they are for a while.

That would be great . . . as long as it's a solid 'light yellow', not the 'bright yellow'.

Rob Smage
AW member since 1992, volunteer since 2000, Midwest Regional StreamTeam Editor

Not sure if it is part of same photo problem/fix, but . . .

I came across a photo (#3391) which has been assigned to reach#3187.
Problem is, that reach appears to be a dead, skeletal reach.
The correct reach is #4255.
Interestingly, the photo has been pulled in to that reach as the 'featured photo',
but does not appear on the "Photos" tab because (as mentioned) it is on the old, mistaken, skeletal remnant reach.

The photo should be reassigned to the correct reach, but I see no way to do that now.
Once that is done, the defunct, skeletal reach (#3187) can be deleted.

Rob Smage
AW member since 1992, volunteer since 2000, Midwest Regional StreamTeam Editor

I probably need a merge reach function to help with that. To edit a photo into your reach, click on the photo detail, then view associated report, then reassign the report to the new reach.

Unfortunately, that's not working exactly right, either.

I followed those steps for a Chattooga Gauge Photo, and when I selected from various Georgia streams, and saved the result, the software ended up assigning it to some Alaskan reach! The latest attempt assigned it to the Nadina River. D'oh!

Yeah, it seems that the drop down is broken. I am looking at a fix for it now.

Fixed the drop down for photos.