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

Think about switching from "within" to "intersect" in get_spatial_data() #64

Open
ericnost opened this issue Jan 25, 2024 · 0 comments
Open
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@ericnost
Copy link
Member

Currently, we look up spatial data that is within a more well-known geography (e.g. get watersheds that are completely contained by a state). Unfortunately, this means some watersheds will never be selected because they cross state borders.

I think using "within" is safer from a "too much data" perspective, but it is very limiting.

@ericnost ericnost added the enhancement New feature or request label Jan 25, 2024
@ericnost ericnost self-assigned this Jan 25, 2024
@ericnost ericnost added this to the v0.2.0 milestone Jan 25, 2024
@ericnost ericnost moved this to Todo in ECHO_modules Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

1 participant