Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved handling of non-default central longitudes #281

Merged
merged 7 commits into from Jan 18, 2019
Merged

Conversation

@philippjfr
Copy link
Member

philippjfr commented Jan 17, 2019

Previously geoviews used some brittle logic to determine where to wrap longitudes. The correct thing to do instead is let the user declare the central_longitude as part of the crs. This PR ensures the central_longitude is handled correctly and updates docs and examples to make use of this feature.

@philippjfr philippjfr force-pushed the wrapping_fixes branch from 419299f to 0033ef0 Jan 17, 2019
@philippjfr philippjfr merged commit b054dab into master Jan 18, 2019
1 of 4 checks passed
1 of 4 checks passed
continuous-integration/appveyor/branch AppVeyor build failed
Details
continuous-integration/appveyor/pr AppVeyor build failed
Details
continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@philippjfr philippjfr deleted the wrapping_fixes branch Mar 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant
You can’t perform that action at this time.