Replies: 1 comment 3 replies
-
|
The logic for equality is handled upstream in PROJ. I think that you may have better luck asking the question there. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a case where I'm compare two CRS objects that should be considered equivalent but are not. Both are created from PROJ.4 dictionaries. One has
aandrfdefined:{'a': 6378137.0, 'lon_0': 0.0, 'h': 35786400.0, 'rf': 298.257223563, 'proj': 'geos', 'units': 'm', 'sweep': 'y'}And is coming from a data file from a satellite instrument.
The other CRS is coming from a YAML configuration file:
{'proj': 'geos', 'lon_0': 0, 'h': 35786400, 'x_0': 0, 'y_0': 0, 'ellps': 'WGS84', 'no_defs': None, }I've also tried adding
datum: 'WGS84'to the above but the resulting datums in the CRS object aren't considered equivalent:Since the a and rf are coming from a data file's attribute I can't really confidently change them to datum/ellps. Does anyone have ideas how I could specify these to be considered equal?
Beta Was this translation helpful? Give feedback.
All reactions