-
Notifications
You must be signed in to change notification settings - Fork 807
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
Create proj_degree_input/output for C-API #2027
Labels
Comments
kbevers
added a commit
to kbevers/PROJ
that referenced
this issue
Apr 11, 2020
Equivalent to proj_angular_input() and proj_angular_output() but checking for degree units instead. proj_create_crs_to_crs() rarely, if ever, returns pipelines that has radians as input or output so using proj_angular_*() is not a useful check for io units of pipelines. These two new functions should make life a bit easier for users that generally store there angular coordinates in radians. Closes OSGeo#2027
4 tasks
kbevers
added a commit
to kbevers/PROJ
that referenced
this issue
Apr 11, 2020
Equivalent to proj_angular_input() and proj_angular_output() but checking for degree units instead. proj_create_crs_to_crs() rarely, if ever, returns pipelines that has radians as input or output so using proj_angular_*() is not a useful check for io units of pipelines. These two new functions should make life a bit easier for users that generally store there angular coordinates in radians. Closes OSGeo#2027
kbevers
added a commit
to kbevers/PROJ
that referenced
this issue
Apr 11, 2020
Equivalent to proj_angular_input() and proj_angular_output() but checking for degree units instead. proj_create_crs_to_crs() rarely, if ever, returns pipelines that has radians as input or output so using proj_angular_*() is not a useful check for io units of pipelines. These two new functions should make life a bit easier for users that generally store there angular coordinates in radians. Closes OSGeo#2027
kbevers
added a commit
to kbevers/PROJ
that referenced
this issue
Apr 12, 2020
Equivalent to proj_angular_input() and proj_angular_output() but checking for degree units instead. proj_create_crs_to_crs() rarely, if ever, returns pipelines that has radians as input or output so using proj_angular_*() is not a useful check for io units of pipelines. These two new functions should make life a bit easier for users that generally store there angular coordinates in radians. Closes OSGeo#2027
kbevers
added a commit
to kbevers/PROJ
that referenced
this issue
Apr 12, 2020
Equivalent to proj_angular_input() and proj_angular_output() but checking for degree units instead. proj_create_crs_to_crs() rarely, if ever, returns pipelines that has radians as input or output so using proj_angular_*() is not a useful check for io units of pipelines. These two new functions should make life a bit easier for users that generally store there angular coordinates in radians. Closes OSGeo#2027
Thanks @kbevers! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there are:
Which is useful to know when the input needs to be converted from degrees to radians before performing a transform. However, some users of
pyproj
prefer to work in radians instead of degrees. So, to support them for thecs2cs
like behavior, I check the input/output CRS to see if they are geographic. Combining that withproj_angular_input/output
I am able to determine if the radians need to be converted to degrees or not. However, when attempting to support thecct
like behavior with pipelines, the solution is not as obvious. So, my thought is that adding functions that check if the input needs to be in degrees would resolve this need.Thoughts?
The text was updated successfully, but these errors were encountered: