On Mon, Nov 6, 2017 at 12:10 PM, Stephan Marx <[email protected]> wrote:
> if you want to enter UTM Coordinates from a Paper Map for example into
> Osmand+ it returns an error code as it requires the 32N Zone instead of 32T
> like in the example below:
>
> Correct: 32 T 692591 5154426 = 46.51584°N 11.51069°E
>
> Osmand turns 46.51584°N 11.51069°E into: 32 N 692591 5154426
>
> Is that an already filed bug, or do I get something wrong here?

The system used in Osmand simply indicates whether the numbering
is north or south of the Equator, so (32N) and (32S) are the only zones
it uses.

The lettered latitude bands actually aren't all that useful, since the
false northing is sufficient to identify the band. Most of the software
I've used uses the simple 'North' and 'South' convention rather than
the latitude grid letters, and Osmand is no exception.

The only zone in which this presents an ambiguity
is zone S (which is in the norther hemisphere), and alas, I don't
know of a good approach other than to make it clear what system
is in use.

See http://earth-info.nga.mil/GandG/coordsys/grids/utm_basics_2005.doc
(page 7) to see that even government agencies concede that there
is no standard here. That's why the US military uses MGRS in
preference to straight-up UTM coordinates. In place of

32 T 692591 5154426

it would write

32TPS9259154426

which has the advantage of being read unambiguously - it's
unquestionably in the Italian Alps, rather than North Africa.
A Bolzano bambino can find his way home.

It's ugly, and I don't know a good solution.

-- 
You received this message because you are subscribed to the Google Groups 
"Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to