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
We use the locations endpoint of the NEON API to get all of our locality, habitat, soil taxonomy related information. We found out recently that plots and reaches, etc, can move around with time. So location data that we pull at the time of (re)harvest may not be accurate relative to the reality at the time of the sample's collection. There is an option to add location history to the API call that then gives data associated with that locationName and a start and end date. We need to investigate how to use both the locationName and the collectEndDate to pull in location related information during harvesting.
The text was updated successfully, but these errors were encountered:
We use the locations endpoint of the NEON API to get all of our locality, habitat, soil taxonomy related information. We found out recently that plots and reaches, etc, can move around with time. So location data that we pull at the time of (re)harvest may not be accurate relative to the reality at the time of the sample's collection. There is an option to add location history to the API call that then gives data associated with that locationName and a start and end date. We need to investigate how to use both the locationName and the collectEndDate to pull in location related information during harvesting.
The text was updated successfully, but these errors were encountered: