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
Use always_xy option in the pyproj Transformer #1036
Comments
Addressed in #998. |
About switching to the new pyproj CRS class -> I would like to do that fully at once (meaning: requiring pyproj > 2.1, so that the geopandas user has an consistent interface for And for fully requiring PROJ 6 / pyproj 2, I think we should wait a bit longer (last time I checked fiona / gdal was not yet compatible with the latest PROJ on conda-forge, that might be fixed in the meantime, but it's all still very recent) |
If you are not ready to have the CRS class returned, I could modify the PR to always return a dict. |
Hi there. I just ran into this problem. |
@jorisvandenbossche, I think this is a must for the 0.6 release. Would it be helpful for me to dissect #998 and focus it to address this without the CRS class? |
Related to pyproj4/pyproj#355 (comment), and another short term fix to ensure compatibility with recent pyproj versions (xref #1003).
We should use the
always_xy
option inTransformer.from_proj
(https://pyproj4.github.io/pyproj/stable/api/transformer.html#pyproj.transformer.Transformer.from_proj), if available (depending on the pyproj version), to ensure we always transform the coordinates in the expected order.The text was updated successfully, but these errors were encountered: