You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For any navigation, we should be able to filter on stream order. This is mostly useful for the flowline response, but would be useful in general.
There is a nhdplus.plusflowlinevaa_np21 that has a streamorder column that is an integer. We should be able to return only comids with stream order according to a filter.
The implementation of this could be through two URL query parameters. something like: minimum_streamorder and maximum_streamorder. If only minimum is specified then maximum is assumed to be unbounded, or the max in the dataset and vice versa.
This can be closed once you can add ?minimum_streamorder=2&maximum_streamorder=3 to a navigate request that would otherwise return all data for that navigation from some data source.
The text was updated successfully, but these errors were encountered:
For any navigation, we should be able to filter on stream order. This is mostly useful for the flowline response, but would be useful in general.
There is a
nhdplus.plusflowlinevaa_np21
that has astreamorder
column that is an integer. We should be able to return only comids with stream order according to a filter.The implementation of this could be through two URL query parameters. something like:
minimum_streamorder
andmaximum_streamorder
. If only minimum is specified then maximum is assumed to be unbounded, or the max in the dataset and vice versa.This can be closed once you can add
?minimum_streamorder=2&maximum_streamorder=3
to a navigate request that would otherwise return all data for that navigation from some data source.The text was updated successfully, but these errors were encountered: