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
Morning! Thanks for this, so, assuming those gages are on the same aggregated flowpath then this is what I would expect to see. The "proper" way to work with both the flowpath-attributes and network layers (given their many-many propoerties) is to only work with distinctly unique rows (subset to the columns you are interested in) . So in this case, for t-route I would define the columns you need, only extract those, run distinct() (or the python equivalent on the resulting data.frame, and proceed.
Yup! Thanks Mike for the insight. Subsetting the flowpath columns cleared up the issue without needing to drop duplicates as the gage column was no longer needed.
I'm good to have this issue closed considering my case is working, and it looks like the above duplicated gage
is an expected output of v2.2
Problem
conus_nextgen.gpkg
by ID there are duplicate IDs in theflowpath-attributes
layerwb-2436960
Steps to reproduce
Here are the outputs, where each column is one of the duplicate rows. The only difference of any of the attributes is the
gage
Temporary Solution:
The text was updated successfully, but these errors were encountered: