-
Notifications
You must be signed in to change notification settings - Fork 16
Closed
Labels
type: enhancementNew enhancement requestNew enhancement request
Description
Feature Request Criteria
- Feature is not implemented by
xarray - Feature is not implemented by another actively developed xarray-based package
- Feature is not limited to specific use cases (e.g., data quality issues)
- Feature is generally reusable
- Feature is relatively simple and lightweight to implement and use
Is your feature request related to a problem?
The PCMDI group is interested in providing feedback and feature suggestions based on their most used features in CDAT.
Describe the solution you'd like
- Create a survey to gather a list of features that are most used by CDAT and PCMDI group members
- Aggregate the responses by count
- Check if the features can already be accomplished in
xarraywith relative ease - Check if some of the features are already implemented or can be extended in xCDAT
- Check if the features can already be accomplished in
- Create a poll for the top 10 responses and send out to the CDAT/PCMDI community
- Add a note for the features that can accomplished in
xarrayor are already implemented inxCDAT
- Add a note for the features that can accomplished in
- Discuss the results with the xCDAT team
- Follow the feature request criteria to narrow down list
- How valuable is the feature request for the broader community?
- Send out follow up email of the results
Describe alternatives you've considered
No response
Additional context
Things to consider:
- Potential for feature bloat and scope-creep!
- The target audience for xCDAT should include new or existing xarray users in addition to CDAT users. We don't want to pigeonhole this package to the needs of a single community, which is why we want to serve the broader climate community as a whole.
Metadata
Metadata
Assignees
Labels
type: enhancementNew enhancement requestNew enhancement request