[ 
https://issues.apache.org/jira/browse/CLIMATE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960936#comment-13960936
 ] 

ASF GitHub Bot commented on CLIMATE-393:
----------------------------------------

GitHub user MJJoyce opened a pull request:

    https://github.com/apache/climate/pull/10

    CLIMATE-393 - Add dataset_processor.safe_subset

    - Add safe_subset for gracefully handling subsetting when not all of the
      bounding parameters are fully contained in the target dataset. If any
      of the bounding values fall outside of the dataset's bounds they are
      defaulted to the dataset's maximum/minimum.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/MJJoyce/climate CLIMATE-393

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/climate/pull/10.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #10
    
----
commit 58eb9e786cc9452bdacb6118ef6ba89281c1e48c
Author: Michael Joyce <jo...@apache.org>
Date:   2014-04-05T02:54:40Z

    CLIMATE-393 - Add dataset_processor.safe_subset
    
    - Add safe_subset for gracefully handling subsetting when not all of the
      bounding parameters are fully contained in the target dataset. If any
      of the bounding values fall outside of the dataset's bounds they are
      defaulted to the dataset's maximum/minimum.

----


> Add less strict subsetting functionality
> ----------------------------------------
>
>                 Key: CLIMATE-393
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-393
>             Project: Apache Open Climate Workbench
>          Issue Type: New Feature
>          Components: regridding/data processing
>    Affects Versions: 0.3-incubating
>            Reporter: Michael Joyce
>            Assignee: Michael Joyce
>             Fix For: 0.4
>
>
> The current subsetting functionality requires that the subregion be entirely 
> in the bounds of the dataset being subset. This can cause a number of 
> problems, especially when dealing with data where the information falls on 
> fractional lat/lon grid values. It would be nice to have a subset function 
> that wouldn't error out if one or more of it's values are outside of the 
> dataset's bounds. Instead, it should return the overlap of the subset bounds 
> and the dataset's bounds.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to