Merge to updated repo #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In working with the GOES16 data, the coordinate identification in parse_cf fails because there are two coordinates with "projection_x_coordinate" as their standard name. But, only one of them is actually a dimension coordinate, and we would want that one to be selected. This commit implements and tests for this.
xarray Coordinate Identification Cleanup
This commit changes the protected method _make_cartopy_globe in CFProjection into a property, and exposes that property in our xarray DataArray accessor as well.
Expose cartopy globe in CFProjection and xarray accessor
permit usage of temperature in Kelvin for heat_index calc
Adds the sphinx-gallery configuration to the template so we can link to the Github edit page for the gallery .py files. The template also identifies the index.html files and directs them to the README.txt files.
"Improve this page" links for examples and tutorials
fix apparent_temperature when only windchill is calculated
In the course of working on xarray examples in metpy, the current implementation of lat_lon_grid_deltas only allowing 1D or 2D input was a hinderance. This commit makes a simple change to allow >2D arrays, so long as the trailing dimensions are y, x.
The deprecation warnings for lat_lon_grid_spacing were not being tested/handled, and some of the comments for lat_lon_grid_deltas still referenced lat_lon_grid_spacing instead. This commit fixes those.
This commit removes the deprecated kinematics functions slated for removal in 0.9, as well as stopping the warning for using the default dim_order, as outlined in #690.
Based on issues with some kinematics calculations generalizing to data that has extra leading dimensions (such as time or vertical as commonly encountered when working with xarray examples), this commit modifies the default derivative axes in kinematics calculations to be based on trailing axes (-2 and -1) rather than leading (0 and 1), to follow our convention (and CF option) of (..., Y, X) dimension ordering. Numerous tests are added to make sure that the affected calculations work with extra dimensions (tested on 4-D data). Additionally, the gradient function previously only supported the full gradient of an array according to its description, but a useful case is just obtaining the horizontal gradient along all levels or times. Handling of the "axes" kwarg and was added to the _process_gradient_args function to resolve this, so that "axes" becomes a kwarg of gradient and laplacian. It must be less than or equal to in length compared to the coordinates/deltas.
In conf.py, adds xarray to intersphinx mapping so that we can easily link from our documentation to xarray's.
We're just checking a size here, so be less aggressive and warn rather than error out. It's completely possible to be off a little in size and still parse through the file fine.
With latest RDA Build 18.0, the size of the status message has increased with some spare bytes. Just include the spares in the size check for now.
This commit modifies the module template to allow it to be overridden by a custom module page, implements a make checker for that override, and implements this to better organize the docs for metpy.calc. Also updates the Travis and AppVeyor doc builds to use the overridecheck option.
Cleanup kinematics calculations and permit leading dimensions
Update nexrad
WIP: Reorganization of calc docs (with module template override option)
Remove removed functions from doc page override
This commit adds a `cross_section` function to `interpolate`. It allows interpolation to a cross-sectional slice through gridded data along a geodesic path between two lat/lon points. Associated changes are also made to some xarray functionality. Additionally, this adds a number of calculations to the calc subpackage in support of cross section functionality: - unit vectors - tangential and normal components - absolute momentum (pseudoangular momentum)
While I was working through examples, I noticed that the parse_cf function, when applied to the full dataset of the NARR example, would fail...the x and y coordinates would double in size, and many NaN's appeared. This was because the lon and lat variables lacked a grid_mapping attribute, and so, their x and y coordinates did not get scaled from km to m like the other variables that did. Thus, they did not line up when xarray tried to combine them back together in a non-unit-aware fashion. This commit fixes this by changing when _fixup_coords is called, so that all x/y coordinates get scaled accordingly.
Fix Scipy 1.3 not-C-contiguous error
migrate mpl.cbook.iterable to numpy.iterable
arrays to be from high to low pressure.
Completes the fix to #1003.
this update converts '%' units to 'percent' units within the MetPy xarray accessor. Fixes #1038.
Units: convert '%' to 'percent' for within the xarray MetPy accessor
Documentation update for pressure in profile calculations
Updated deprecated function in matplotlib 3.1
Prevent an EL below a LCL
first pass at better docs for declarative
xarray Coordinate Identification Refactor
that linear distance or degrees can be the units of the input coordinates (and resultantly, the resolution of the grid). Fixes #1060.
Interpolate_to_grid doc update
Remove components due for removal in 0.11
Xarray: Add warning if lat/lon is assumed for projection
Fix docstring for vertical velocity functions to render equations
identified within a sounding. This fixes #992 and begins to address
Provide identification of multiple LFCs and ELs
|
Looks good |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.