[
https://issues.apache.org/jira/browse/CLIMATE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736241#comment-14736241
]
ASF GitHub Bot commented on CLIMATE-667:
----------------------------------------
GitHub user huikyole opened a pull request:
https://github.com/apache/climate/pull/229
CLIMATE-667 - OCW spatial_boundaries bug
- ocw.dataset.spatial_boundaries uses np.min and np.max instead of min and
max
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huikyole/climate CLIMATE-667
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/climate/pull/229.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 #229
----
commit a0d705794f4bb2ba682a306b0e618d5feab78ef8
Author: huikyole <[email protected]>
Date: 2015-09-09T06:03:30Z
CLIMATE-667 - OCW spatial_boundaries bug
- ocw.dataset.spatial_boundaries uses np.min and np.max instead of min and
max
----
> OCW spatial_boundaries bug
> --------------------------
>
> Key: CLIMATE-667
> URL: https://issues.apache.org/jira/browse/CLIMATE-667
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Components: general
> Reporter: Huikyo Lee
> Assignee: Huikyo Lee
>
> Currently, dataset.spatial_boundaries does not properly find maximum and
> minimum values of self.lats and self.lons if self.lats and self.lons are two
> dimensional. This can be easily solved by using numpy.min and numpy.max
> functions instead of min and max.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
