[
https://issues.apache.org/jira/browse/CLIMATE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056977#comment-16056977
]
ASF GitHub Bot commented on CLIMATE-918:
----------------------------------------
GitHub user huikyole opened a pull request:
https://github.com/apache/climate/pull/446
CLIMATE-918 - Revise LAT_NAMES and LON_NAMES
- LAT_NAMES and LON_NAMES in ocw.data_source.local have been revised to
prevent loading wrong variables for longitudes and latitudes when using OCW
loaders
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huikyole/climate CLIMATE-918
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/climate/pull/446.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 #446
----
commit 8b2f8160185afb1b70dd57a18aed95a790b1a4fa
Author: huikyole <huiky...@argo.jpl.nasa.gov>
Date: 2017-06-21T04:33:37Z
CLIMATE-918 - Revise LAT_NAMES and LON_NAMES
- LAT_NAMES and LON_NAMES in ocw.data_source.local have been revised to
prevent loading wrong variables for longitudes and latitudes when using OCW
loaders
----
> Revise LAT_NAMES and LON_NAMES in ocw.data_source.local
> -------------------------------------------------------
>
> Key: CLIMATE-918
> URL: https://issues.apache.org/jira/browse/CLIMATE-918
> Project: Apache Open Climate Workbench
> Issue Type: Improvement
> Reporter: Huikyo Lee
> Assignee: Huikyo Lee
> Priority: Critical
>
> Currently, there are too many LAT_NAMES and LON_NAMES. As a result, the file
> loaders can retrieve wrong variables from the netCDF files that have multiple
> variables with spatial information. This ticket will address the issue by
> providing limited options for LAT_NAMES and LON_NAMES. Users can always
> specify names for latitude and longitude variables in a configuration file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
