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 on page /hex-3000-m.html #6

Open
louiseschreyers opened this issue May 19, 2023 · 1 comment
Open

Issue on page /hex-3000-m.html #6

louiseschreyers opened this issue May 19, 2023 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@louiseschreyers
Copy link
Collaborator

The analysis with the new land-use dataset is very interesting. I see you present the results only for the lake locations, but I could see in the resources document that the land-use was also extracted for the river survey locations. Any reason to not aggregate rivers and lakes results, as it was done with the old land-use dataset?

@hammerdirt-analyst hammerdirt-analyst self-assigned this May 20, 2023
@hammerdirt-analyst hammerdirt-analyst added the question Further information is requested label May 20, 2023
@hammerdirt-analyst
Copy link
Owner

Hi there are at least three reasons:

  1. Homogenization of sampling conditions: Experience in the field has demonstrated a big difference in the sampling conditions between lakes and rivers. Therefore, lakes or rivers are taken as just another independent variable to account for.
  2. The recommender (machine learning model) is initially being developed for lake locations. IT will be interesting to see how the output from the ML model compares to the Rho values for lake locations.
  3. River samples are reported separately in the federal report. As the report evolves it just makes sense to do the same with any anlysis.

That being said it really depends on how you want to exress the effects of river sampling on survey results:

  1. As a coefficient in an equation
  2. As an independent model

For now it is simpler to make the models separately.

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

No branches or pull requests

2 participants