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

Enable nearest neighbor interpolation in ExtData #786

Closed
rmontuoro opened this issue Apr 5, 2021 · 3 comments · Fixed by #788
Closed

Enable nearest neighbor interpolation in ExtData #786

rmontuoro opened this issue Apr 5, 2021 · 3 comments · Fixed by #788
Assignees
Labels
🎁 New Feature This is a new feature

Comments

@rmontuoro
Copy link
Contributor

A configuration option enabling nearest-neighbor interpolation is missing for ExtData.

This interpolation method is required when reading surface properties used, for instance, by dust schemes such as the NOAA/ARL FENGSHA scheme currently being implemented in GOCART.

@rmontuoro rmontuoro added the 🎁 New Feature This is a new feature label Apr 5, 2021
@rmontuoro rmontuoro self-assigned this Apr 5, 2021
@tclune
Copy link
Collaborator

tclune commented Apr 5, 2021

@bena-nasa Please let us know how involved this extension will be.

rmontuoro added a commit that referenced this issue Apr 5, 2021
via regridding keyword 'E'. See issue #786.
@rmontuoro rmontuoro linked a pull request Apr 5, 2021 that will close this issue
7 tasks
@rmontuoro
Copy link
Contributor Author

PR #788 enables this feature. I've used the E keyword to request nearest-neighbor interpolation in the ExtData resource file, but please feel free to implement a different keyword if needed.

bena-nasa added a commit that referenced this issue Apr 8, 2021
…neighbor-interpolation

Enable nearest-neighbor interpolation for ExtData
@rmontuoro
Copy link
Contributor Author

Closing after merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎁 New Feature This is a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants