This object is in archive!

# Problem putting UTM coordinates into Locus Map

Answered

Hi,

I wanted to put in some UTM coordinates in the following shape:

32T xxxxx yyyyy

The corresponding UTM field in Locus Map only allows me to type in X and Y Coordinates and the zone and hemisphere.

32T already determines the Zone pretty well. But there is no way to give account to the zone letter "T" in the programm.

So if I then type in the coordinates (and 32N), they mislead me to an unrealistic point.

Another idea I´ve had was to put them into MGRS/UTMref, but therefore I´m missing the square letters following right after "32T".

Does anybody understand my problem and know how to fix it?

Thanks ;)

Hello

You can use:

1. EPSG 25832 (without using 32, just let it away)

2. EPSG 4647 (With leading 32 in first coordinate row)

3. EPSG 32632 (WGS84 Referenze, without leading 32)

The "T" can be let away, if written in Numbers.

Hello

You can use:

1. EPSG 25832 (without using 32, just let it away)

2. EPSG 4647 (With leading 32 in first coordinate row)

3. EPSG 32632 (WGS84 Referenze, without leading 32)

The "T" can be let away, if written in Numbers.

Hi guys,

seems that Markus is more skilled with coordinate systems than anyone in our team, nice thanks!

Anyway, why you need to specify also the latitude "T" letter? Isn't zone number 32 + X and Y coordinates enough to correctly specify a certain location on Earth?

Menion

Hi guys,

seems that Markus is more skilled with coordinate systems than anyone in our team, nice thanks!

Anyway, why you need to specify also the latitude "T" letter? Isn't zone number 32 + X and Y coordinates enough to correctly specify a certain location on Earth?

Menion

Thanks guys for your replies.

But is there no way without changing the projection to put in UTM coordinates?

If I put in my UTM coordinates and put the Zone numer to 32 (and ignore the letter "T"), the whole coordinates change subsequently to completely different ones (and also the zone changes).

Thanks guys for your replies.

But is there no way without changing the projection to put in UTM coordinates?

If I put in my UTM coordinates and put the Zone numer to 32 (and ignore the letter "T"), the whole coordinates change subsequently to completely different ones (and also the zone changes).

I still do not perfectly understand, why "T" should be necessary here, excuse me.

May you Niklas please write here full UTM and final lat/lon coordinates you try to convert? Thank you!

I still do not perfectly understand, why "T" should be necessary here, excuse me.

May you Niklas please write here full UTM and final lat/lon coordinates you try to convert? Thank you!

Hello Niklas

your screensot display a invalid Y value in count of digits as well as in meters

X value have to be 6 digits

Y value have to be 7digits e.g. 5553986.00 > for example your values without the leading 1.

Y values range for germany are ~ 5250000-6070000

so you get a valid point

Wolfgang

Hello Niklas

your screensot display a invalid Y value in count of digits as well as in meters

X value have to be 6 digits

Y value have to be 7digits e.g. 5553986.00 > for example your values without the leading 1.

Y values range for germany are ~ 5250000-6070000

so you get a valid point

Wolfgang

The "T" Stands for a Sector. So his coordinates are without the leading Numbers. = shorter. But there is till now, no EPSG code for this kind of input format,or at least i dont find one.

On Paper cards should all necessary be printed.

Maybe we can create a new input methide to calculate the leading numbers ?

The "T" Stands for a Sector. So his coordinates are without the leading Numbers. = shorter. But there is till now, no EPSG code for this kind of input format,or at least i dont find one.

On Paper cards should all necessary be printed.

Maybe we can create a new input methide to calculate the leading numbers ?

Hi guys, thanks for the answers and help here.

I still miss an answer from Niklas. Anyway, I understand it correctly, perfect. Character value only defines a sector that may anyway simply be defined by Y leading value. I do not consider this as a necessary change in the app as the most common format I ever saw is simply digital-based, so without sector values.

Please, let us Niklas know if you were able to solve this and if not, please provide specific values you try to convert, thanks.

Menion

Hi guys, thanks for the answers and help here.

I still miss an answer from Niklas. Anyway, I understand it correctly, perfect. Character value only defines a sector that may anyway simply be defined by Y leading value. I do not consider this as a necessary change in the app as the most common format I ever saw is simply digital-based, so without sector values.

Please, let us Niklas know if you were able to solve this and if not, please provide specific values you try to convert, thanks.

Menion

Hi guys,

thats again for this overwhelming support!

The coordinates I´m trying to convert are

32T 13303 16994

This is at least, what I got to solve a geocaching-like riddle.

Since I knew that the point must be in my close area, my solution was to put it into UTMref/MGRS, take the zone number as well as the following three letters from my current position and then put the 2x5 digits right after it.

When I did this, I got the right point.

But this doesn´t feel like a good and clear solution, as I would struggle, when I get coordinates that are out of my current square.

Hi guys,

thats again for this overwhelming support!

The coordinates I´m trying to convert are

32T 13303 16994

This is at least, what I got to solve a geocaching-like riddle.

Since I knew that the point must be in my close area, my solution was to put it into UTMref/MGRS, take the zone number as well as the following three letters from my current position and then put the 2x5 digits right after it.

When I did this, I got the right point.

But this doesn´t feel like a good and clear solution, as I would struggle, when I get coordinates that are out of my current square.

Hello

Hm.. if i think about this more, i also found out that it would be helpful in some cases if Locus can calculate it.

Because while communication with Walkie-Talkies, there also is used the short form of coordinates.

On the other Hand, we mostly use normal Latitude/Longitude coordinates. Also airplanes and rescue Helicopters often use normal WGS84 degree coordinates.

I think, this short form, is still a not so often used coordinate format.

To calculate it... at first look the additional sectors seem to be in a degree net... and dont exactly hit the metric net.

Hello

Hm.. if i think about this more, i also found out that it would be helpful in some cases if Locus can calculate it.

Because while communication with Walkie-Talkies, there also is used the short form of coordinates.

On the other Hand, we mostly use normal Latitude/Longitude coordinates. Also airplanes and rescue Helicopters often use normal WGS84 degree coordinates.

I think, this short form, is still a not so often used coordinate format.

To calculate it... at first look the additional sectors seem to be in a degree net... and dont exactly hit the metric net.

Replies have been locked on this page!