Issues with coordinates given as longitude latitude height
The bold words hint at things that are often done wrong.
Longitude (first), Latitude (second) must be
given in decimal degrees, not degrees minutes seconds.
For our station Onsala
Onsala 11.9264 57.3958 7.3000
You may notice that the pair 11.9264 57.3958 is as acceptable
as if it appeared in reverse order. It's not uncommon that our
clients have committed that mistake. It's obvious when a
latitude value is read and found out ot range because the user
had misplaced a longitude of, say, -123.4567 degrees.
So we have built in a safeguard. If the
values in both columns 1 and 2 are inside a sector from -90 to
+90 degrees in all station records, the system bothers the
user by presenting a map of their stations, prompting whether
they are in the intended locations. The code machinery behind
this is quite complex (we hope it's stable). User responses may
feel awkward and at odds with intuition so that work with the
request may get stuck. But also repeatedly been confronted with
maps of correctly positioned locations might become overly
tiresome.
As an opt-out we present a tick box on the
form page where you can make a solemn vow to never swap
longitudes and latitudes. The vow is associated with your
E-mail address, so it's moved along with your forthcoming
log-ins. You can even rescind it.
As to the consequences of ambiguous degree pairs further down the chain
of submission,
consult this link.
A short reminder. With coordinates in general, XYZ in meters as well as geographic degrees, you need to reserve a blank
gully at column 25 separating the part for the station's
name from the coordinates part. And lines starting with //
are not regarded as station specifications; they are treated as
comments. We use this markup to provide some help text, like the
ruler