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
Something changed between pyproj 2.6.1.post1 and pyproj 3.0.0.post1 that is leading to small variations in projected coordinates, which is then propagated on to point snapping distance, cost matrices, etc. For now, pinning to 2.6.1.post1 is reasonable (#66). A longer term solution is either updating the tests to reflect the altered projection results or figuring out if this is an actual bug. The code chunk below demonstrates the output difference between pyproj 2.6.1.post1 (top) and pyproj 3.0.0.post1 (bottom) with an example through geopandas and a MWE with only pyproj.
I think that this is a result of changes in how proj handles transformation grids. The new result should have the higher precision compared to the other one, so I would fix the tests. There was one issue of this kind in geopandas some time ago.
Something changed between
pyproj 2.6.1.post1
andpyproj 3.0.0.post1
that is leading to small variations in projected coordinates, which is then propagated on to point snapping distance, cost matrices, etc. For now, pinning to2.6.1.post1
is reasonable (#66). A longer term solution is either updating the tests to reflect the altered projection results or figuring out if this is an actual bug. The code chunk below demonstrates the output difference betweenpyproj 2.6.1.post1
(top) andpyproj 3.0.0.post1
(bottom) with an example throughgeopandas
and a MWE with onlypyproj
.@knaaptime @slumnitz @martinfleis Have any of you noticed this in your work?
The text was updated successfully, but these errors were encountered: