[PROJ] Supported geographical coordinate formats

[Andreas B]

Right, so longitude is expected to be in the first input column and
latitude in the second. If you get this wrong proj wont warn you. Got
it, thanks.

PS! Is +proj=latlong the same as +proj=longlat?

Andreas

On Thu, Jul 2, 2020 at 5:57 PM Charles Karney <charles at karney.com> wrote:
>
> Because PROJ uses the order of the coordinates to distinguish latitude
> and longitude.  E.g.,
>
>    echo 4N 10W | cs2cs +proj=latlong
>
> =>
>
>    4dE     10dS 0.000
>
>
> On 7/2/20 9:43 AM, Andreas B wrote:
> > Thanks for answering Charles.
> >
> > I'm not sure if I understand. Why would 10W be interpreted as lat = -10?
> >
> >
> > Andreas
> >
> > On Thu, Jul 2, 2020 at 3:33 PM Charles Karney <charles at karney.com> wrote:
> >>
> >> One major usability issue with PROJ is that the hemisphere designators
> >> NESW *only* specify the sign of the coordinate.  Thus it's easy for
> >> 10W to be interpreted as lat = -10.  Fixing this would required some
> >> replumbing of PROJ since the two horizontal components would need to
> >> be decoded together.
> >>
> >> On 7/2/20 9:17 AM, Andreas B wrote:
> >>> Hi,
> >>>
> >>> Is there any formal description or definition of what kind of
> >>> geographical coordinate format the proj command line tools support
> >>> (input and output)?
> >>>
> >>> Several styles are presented in the docs, e.g.
> >>> (https://proj.org/apps/cs2cs.html#using-proj-strings)
> >>>
> >>> 45d15'33.1" 111.5W
> >>> 45d15.551666667N -111d30
> >>> +45.25919444444 111d30'000w
> >>>
> >>> Any preferred format?
> >>>
> >>> Thanks,
> >>> Andreas
>
> --
> Charles Karney <charles at karney.com>
> Princeton, NJ