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

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

GitHub user MJJoyce opened a pull request:

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

    CLIMATE-392 - Shift lat/lon grid during Dataset creation

    - When creating a Dataset object with a lon grid that ranges from 0-360
      the values are now shifted to fall within [-180, 180).

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

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

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

    https://github.com/apache/climate/pull/9.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 #9
    
----
commit b75633b191840daef0780cb417fb8dd1a46525f2
Author: Michael Joyce <[email protected]>
Date:   2014-04-05T00:34:25Z

    CLIMATE-392 - Shift lat/lon grid during Dataset creation
    
    - When creating a Dataset object with a lon grid that ranges from 0-360
      the values are now shifted to fall within [-180, 180).

----


> OCW Dataset should shift lon values that range from 0-360
> ---------------------------------------------------------
>
>                 Key: CLIMATE-392
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-392
>             Project: Apache Open Climate Workbench
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 0.3-incubating
>            Reporter: Michael Joyce
>            Assignee: Michael Joyce
>             Fix For: 0.4
>
>
> At the moment we don't force datasets to fall onto a default grid nor do we 
> document this anywhere. This can result in some annoying problems when 
> datasets aren't on the same grid. As a default, we will shift a 0-360 grid to 
> fall from -180 to 179.



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

Reply via email to