We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If geod(1) added cct(1)'s -c option, the user could avoid elaborate workarounds to get the input order ready for it,
geod(1)
cct(1)
-c
$ cat Makefile porS=120.866551 24.182822 tpc158=120.8710656 24.1873743 r= $(lastword $(1)) $(firstword $(1)) yukky: echo $(call r, $(tpc158)) $(call r, $(porS)) | geod +ellps=WGS84 -p -f %.6f -I better: #if we could use cct -c's option echo $(tpc158) $(porS) | geod -c 1,2 +ellps=WGS84 -p -f %.6f -I
This is even more pertinent, as geod(1) demands lat,lon order, the opposite from the default order of proj(1), cs2cs(1), and cct(1).
lat,lon
proj(1)
cs2cs(1)
The text was updated successfully, but these errors were encountered:
Just for clarification, cs2cs and cct does not have a default order. The reason is explained here: https://proj.org/en/9.4/faq.html#why-is-the-axis-ordering-in-proj-not-consistent
With that said, I think this would be a nice addition to geod.
Sorry, something went wrong.
No branches or pull requests
If
geod(1)
addedcct(1)
's-c
option, the user could avoid elaborateworkarounds to get the input order ready for it,
This is even more pertinent, as
geod(1)
demandslat,lon
order, theopposite from the default order of
proj(1)
,.cs2cs(1)
, andcct(1)
The text was updated successfully, but these errors were encountered: