-
Notifications
You must be signed in to change notification settings - Fork 211
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
Handling of compound CRS #265
Labels
Comments
I think adding a |
This is also what the GDAL "is projected" function does, it special cases for CompoundCRS: |
snowman2
added a commit
to snowman2/pyproj
that referenced
this issue
Apr 12, 2019
snowman2
added a commit
to snowman2/pyproj
that referenced
this issue
Apr 12, 2019
snowman2
added a commit
to snowman2/pyproj
that referenced
this issue
Apr 12, 2019
snowman2
added a commit
to snowman2/pyproj
that referenced
this issue
Apr 12, 2019
snowman2
added a commit
to snowman2/pyproj
that referenced
this issue
Apr 12, 2019
snowman2
added a commit
to snowman2/pyproj
that referenced
this issue
Apr 13, 2019
snowman2
added a commit
that referenced
this issue
Apr 23, 2019
…s; update CRS repr) (#263) * updated CRS repr for clarity; added BaseCRS for datum/ellipsoid/prime_meridian * add check to ensure input to CRS is a CRS (issue #267) * added support for compound CRS (issue #265) * updated repr to use EPSG code with 100% confidence for input & removed EPSG in repr * added docstrings for cython classes; cleaned up unused attributes in crs cython classes; added examples for CRS usage * fixed setting the coordinate operation name * change boolean like objects from int to bool * check if bound crs is geographic (issue #274) * added support for from_auth to CRS,Ellipsoid,PrimeMeridian,CoordinateOperation,Datum classes
I am going to close this as the solution is merged into master. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One of the type of CRSses is a "compound CRS", which is a combination of one CRS for the horizontal coordinates and a vertical CRS for the z coordinate.
An example is EPSG:5972 (http://epsg.io/5972, taken from https://github.com/OSGeo/proj.4/blob/master/data/sql/compound_crs.sql):
So this does not fully fit in the current CRS class:
proj_crs_get_sub_crs
) Or is that too much detail for end users, and is it fine enough with having the current API?is_projected
return True if the horizontal CRS is projected?(some similar questions can be raised for the Bound CRS)
The text was updated successfully, but these errors were encountered: