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
ENH: Added support for int-like strings and numpy dtypes #1049
ENH: Added support for int-like strings and numpy dtypes #1049
Conversation
…ents of numpy array
…ents of numpy array
…ents of numpy array
…ents of numpy array
Thoughts about instead adding a method called
>>> from pyproj import CRS
>>> import numpy
>>> CRS.from_epsg(numpy.array(4326))
<Geographic 2D CRS: EPSG:4326>
Name: WGS 84
Axis Info [ellipsoidal]:
- Lat[north]: Geodetic latitude (degree)
- Lon[east]: Geodetic longitude (degree)
Area of Use:
- name: World.
- bounds: (-180.0, -90.0, 180.0, 90.0)
Datum: World Geodetic System 1984 ensemble
- Ellipsoid: WGS 84
- Prime Meridian: Greenwich
>>> CRS.from_epsg("4326")
<Geographic 2D CRS: EPSG:4326>
Name: WGS 84
Axis Info [ellipsoidal]:
- Lat[north]: Geodetic latitude (degree)
- Lon[east]: Geodetic longitude (degree)
Area of Use:
- name: World.
- bounds: (-180.0, -90.0, 180.0, 90.0)
Datum: World Geodetic System 1984 ensemble
- Ellipsoid: WGS 84
- Prime Meridian: Greenwich |
@snowman2 Indeed a |
D
I like the current implementation, it looks good 👍. I think this would be sufficient: def _is_epsg_code(auth_code: Any) -> bool: |
…adme contributers
@iboates would you like to squash your commits or would you mind if I did it on merge? |
@snowman2 You can do it on merge it's fine |
Realized that there was an |
Codecov Report
@@ Coverage Diff @@
## main #1049 +/- ##
==========================================
+ Coverage 96.27% 96.29% +0.01%
==========================================
Files 20 20
Lines 1771 1779 +8
==========================================
+ Hits 1705 1713 +8
Misses 66 66
Continue to review full report at Codecov.
|
Thanks @iboates 👍 |
history.rst
for all changes andapi/*.rst
for new APII don't think
api/*
needs updating but maybe I am wrong.