Fix CRS object being recreated when adding CRS coordinate #915
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.
While fixing other CRS issues with trollimage and pyresample, I noticed that the CRS coordinate being added by Satpy is always created from the
proj_str
attribute of the AreaDefinition. This is an inaccurate/lossy way of creating a CRS definition. This PR makes it so we just copy the CRS object from the AreaDefinition if it exists. When this functionality was originally added the AreaDefinition didn't have a 'crs' property so creating from the proj_str made a little more sense. Now that we have a 'crs' object in newer versions of pyresample we should use it.NOTE: I had uninstalled the pre-commit checks so I have not updated resample.py if it needs it.
flake8 satpy