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
{{ message }}
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.
In looking at data from the National Estuarine Reserve System (NERRS) and comparing it to gridmet data for the same location, I have found that the temperature, precipitation, and wind direction match decently well. However the windspeed does not
here is a zoomed in version:
The nerrs data is only missing < 0.5% of the data (35/7305) so we will just linearly interpolate to fill missing days, but it's a little weird. One possible explanation is that the NERRS site is slightly inland from the estuary, while the gridMET resolution is 4km which includes part of the estuary. The average wind speed in that 4 km grid cell could just be higher if much of it were over open water.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In looking at data from the National Estuarine Reserve System (NERRS) and comparing it to gridmet data for the same location, I have found that the temperature, precipitation, and wind direction match decently well. However the windspeed does not
here is a zoomed in version:
The nerrs data is only missing < 0.5% of the data (35/7305) so we will just linearly interpolate to fill missing days, but it's a little weird. One possible explanation is that the NERRS site is slightly inland from the estuary, while the gridMET resolution is 4km which includes part of the estuary. The average wind speed in that 4 km grid cell could just be higher if much of it were over open water.
The text was updated successfully, but these errors were encountered: