You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test for equality takes about ~10ms on pyproj==3.0.1 and ~10µs on pyproj==2.6.0. I measured in jupyter notebook using timeit cell magic:
%%timeWGS==CRS4326
I noticed that when function that was applied to thousands of geometries became much slower after pyproj upgrade. And the main reason was increased time for crs comparison.
Is this expected behavior in pyproj==3.0.1? If yes, what is better way to test crs for equality? Maybe something like this:
Code Sample, a copy-pastable example if possible
Problem description
Test for equality takes about ~10ms on pyproj==3.0.1 and ~10µs on pyproj==2.6.0. I measured in jupyter notebook using timeit cell magic:
I noticed that when function that was applied to thousands of geometries became much slower after pyproj upgrade. And the main reason was increased time for crs comparison.
Is this expected behavior in pyproj==3.0.1? If yes, what is better way to test crs for equality? Maybe something like this:
?
Environment Information
for pyproj==3.0.1:
for pyproj==2.6.0:
Installation method
The text was updated successfully, but these errors were encountered: