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

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

GitHub user MJJoyce opened a pull request:

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

    CLIMATE-371 - Allow user to pass variable names to local.py

    

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

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

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

    https://github.com/apache/climate/pull/132.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 #132
    
----
commit e3e59787667e8a360c5e43d93111625e6b8ffafc
Author: Michael Joyce <[email protected]>
Date:   2014-11-07T22:20:02Z

    CLIMATE-371 - Allow user to pass variable names to local.py

----


> local.load_file should accept lat/lon/time variable names
> ---------------------------------------------------------
>
>                 Key: CLIMATE-371
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-371
>             Project: Apache Open Climate Workbench
>          Issue Type: Improvement
>          Components: data sources
>    Affects Versions: 0.3-incubating
>            Reporter: Michael Joyce
>            Assignee: Michael Joyce
>             Fix For: 0.5
>
>
> Currently the local data_source tries to guess lat/lon/time variable names 
> and doesn't allow the user to specify any of them. Dataset loading could be 
> greatly simplified in situations where the user knows the name of the 
> variables they want to use. Allowing explicit names to be provided also helps 
> to reduce the likelihood of complicated datasets loading improperly due to 
> possible name clashes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to