-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add support for overlapping satellite CSV regions #46
Comments
When joining RGB or Landcoverage satellite data with iNaturalist observations and multiple regions are found return the region that has the closest centroid. Fixes #46
When joining RGB or Landcoverage satellite data with iNaturalist observations and multiple regions are found return the region that has the closest centroid. Fixes #46
In a meeting today a change was requested for this issue. Instead of finding the satellite region containing the observation find the satellite region with the closest centroid. Additional add two new columns to the resulting CSV:
|
We should also add a message on the fetch-observations screen explaining that the RGB/Landcover checkboxes are only meant for QUEST 2023.
|
When joining RGB or Landcoverage satellite data with iNaturalist observations found return the region that has the closest centroid. Include a columns for for `in` and `distance. `in` will be either 0 or 1. `distance` will be the distance from the lat/long point to the center of the closest satellite region. Fixes #46
Satellite CSV data can now be joined with iNaturalist observations (see #44). The satellite data may contain overlapping regions. This can result in multiple regions being matched for a single iNaturalist observation. When this occurs choose the region who's center is the closest to the observation lat/long.
The text was updated successfully, but these errors were encountered: