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

Pyproj geodesic trace #2069

Merged
merged 2 commits into from
Aug 23, 2022
Merged

Conversation

greglucas
Copy link
Contributor

This is @QuLogic's work in the first commit, and removes the last remaining remnants of PROJ required for installation. I removed all the mentions of the library and requirements in the second commit.

This will likely be slower (only with geodesic calculations), similar to the previous move to pyproj in v0.20, but I think it will greatly simplify the installation, making up for the loss in speed and moving us one step closer to building wheels...

QuLogic and others added 2 commits August 20, 2022 19:00
The Geod class doesn't support `geod_line` from the geodesic routines,
but we can simulate that by individual forward/inverse calls.
Copy link
Contributor

@dopplershift dopplershift left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy to see this go in regardless of performance just to eliminate our PROJ install problems.

Any idea how good our test coverage is for our use of the geodesic stuff? Or more directly, how likely is this to break stuff?

@greglucas
Copy link
Contributor Author

Halfway descent: https://github.com/SciTools/cartopy/blob/main/lib/cartopy/tests/test_geodesic.py

I am also in-favor of this :) and when I was playing around with wheel building, I believe geos was much easier to build than proj, so we could probably even give the wheels a shot before removing the geos dependency as well.

@dopplershift
Copy link
Contributor

Wheels are a great idea idea in theory, but we still have the problem of needing to make sure that at all times CartoPy is built against the same version of GEOS as Shapely. #1174

The next step is to eliminate compiling against GEOS and just rely on Shapely.

@dopplershift dopplershift merged commit 357bd6b into SciTools:main Aug 23, 2022
@greglucas greglucas deleted the pyproj-geodesic-trace branch August 25, 2022 01:43
@QuLogic QuLogic added this to the 0.21 milestone Aug 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants