Skip to content
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.

AzimuthalEquidistant did not handle spherical Earth #953

Merged
merged 5 commits into from
Nov 18, 2017
Merged

AzimuthalEquidistant did not handle spherical Earth #953

merged 5 commits into from
Nov 18, 2017

Conversation

rschmunk
Copy link
Contributor

Almost identical to the previous problem with handling the cylindrical equal area (#614), the azimuthal equidistant was experiencing an NPE if the grid mapping variable attributes described a spherical Earth. Solution, create a spherical Earth object if the call to makeCoordinateTransform did not construct an object.

Also set handling the spherical case of both these projections to watch for a specified Earth radius, and to pass that along when creating the Earth object. The previous update to handling the CEA did not do so.

rschmunk and others added 5 commits November 14, 2017 18:44
Creation of spherical Earth object did not check whether an Earth radius had been found in attributes, so object would be created with hard-coded default.
The call to readStandardParams would create a null Earth object if the attributes specified a spherical Earth. This would lead to subsequent NPE when creating a EquidistantAzimuthalProjection here.
@lesserwhirls lesserwhirls merged commit d5c15b2 into Unidata:master Nov 18, 2017
@lesserwhirls
Copy link
Collaborator

Thank you @msdsoftware! We plan to get a 4.6.11 release the week after Thanksgiving, and this fix will be in there.

@rschmunk
Copy link
Contributor Author

@lesserwhirls, Good to know. I'm planning a Panoply +0.0.1 release before the end of the month and will try to wait for 4.6.11.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants