Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with split_catchment for a station #355

Open
cheginit opened this issue Dec 5, 2022 · 5 comments
Open

Issue with split_catchment for a station #355

cheginit opened this issue Dec 5, 2022 · 5 comments

Comments

@cheginit
Copy link

cheginit commented Dec 5, 2022

I found an issue with NLDI's basin endpoint for station ID of 08074500. Here's what it looks like w/o splitCatchment:

image

The small bit in the right corner of the left subplot is where the station is located.

Here's the request URL: https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-08074500/basin?simplified=true&splitCatchment=false

@cheginit
Copy link
Author

cheginit commented Dec 5, 2022

For reference, I got the basin from gagesii_basins layer of WaterData's GeoServer:
image

@dblodgett-usgs
Copy link
Member

Thanks for this @cheginit -- I've shared this with @Anders-Hopkins to see if he can look into the little dangler polygon.

The gagesii polygon is derived from a different source -- so going to be different in many cases.

@cheginit
Copy link
Author

I found another station (USGS-03238140) where NLDI with split set to true returns a very large geometry that has an area of, 188221 sqkm while the original drainage area of the basin is 11 sqkm!

@dblodgett-usgs
Copy link
Member

@Anders-Hopkins can you look into this?

@Anders-Hopkins
Copy link

Just got back from some vacation. I'm catching up on work, but I'll look at this as soon as I can. Just shooting from the hip on this one, my guess is that the query point is snapping to the next major river (which looks like the Ohio in this case) and delineating the basin from there. Not sure why this is happening but I'll get to the bottom of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants