Bug/inferred metric

[ngottlieb]

addresses https://github.com/AmericanWhitewater/aw-components/issues/560

[tallowen]

I had done something similar on the serverside: https://github.com/AmericanWhitewater/aw-components/pull/602

Do you have a preference for whether we do it client or server side?

[ngottlieb]

@tallowen I think I like the front-end version better but I'm curious what you think about dealing with this problem I mentioned on the associated ticket:

neither the state table nor map table queries — getReachTableByIDs and stateView — support this because they ONLY respond with the correlation. Should I create a new task to deal with this? Any thoughts? As of now, we can see, for example, LW flows on beta box and the flow tab shows up properly...but it does not show a reading in the map view or state view.

[tallowen]

Sorry I'm getting so lost with all of the bugs at this point.

I think the little white would be addressed by this change: https://github.com/AmericanWhitewater/aw-components/commit/a7b89dbbc427c62f171e142ae0661c8e3b559560

Right now, the little white doesn't have a correlation because getCorrelationStatus doesn't respond when no flowbands are set. If it did, then there would be a metric field that you could look at which I think would fix many of these problems?

[ngottlieb]

these two comments are from the same task — PR + task. But you're misunderstanding what I'm saying. The issue here is not the Little White, nor the question of whether there is a correlation.

This fix allows us to show flows in the beta box even when a correlation isn't defined but a gauge is associated, which seems good. But we are still unable to see them in the NWI map table or the state index table, because those endpoints are completely different in what they return. It seems to me that if we see it in the beta box, we'd also want to see it in the index area stuff, so I'm wondering if you have any thoughts on how to deal with that.