All of the formats work perfectly. It is the human interface that is the weak link. Have people read a GPS, call 911 on a cell phone, have the 911 operator relay to an officer. Listen to the back and forth discussion.

TEST -
Transmitting what you see on the screen using voice -
Interpreting voice and typing the location -
Sending emails of the location -
Receiving emails of the location –
Pasting into a mapping program -


All 12 of these work as inputed.

N 43.96633 W 116.18937
N43.96633 W116.18937
43.96633N 116.18937W
43.96633 -116.18937
43.96633, -116.18937
43.96633-116.18937


N43 57.980 W116 11.362
N 43 57.980 W 116 11.362
N 43° 57.980’ W° 116 11.362’
N 43° 57' 58" W 116° 11' 21"
N 43° 57' 58" W 116° 11' 21"
43° 57' 58"N 116° 11' 21”W

Not sure what your point is?

Any format can get garbled by the "human interface". That's why you always have them read back. There is nothing particularly magic in that regard about decimal degree format. And that's why I suggested also sending (when possible) your position relative to some geographic landmark. That allows for an easy way to cross check by the recieving party.

By the way, you forgot a decimal point in your second example (the one I bolded).

Great idea.

Where do you get the data for Tacan locations?

Blake

One good place is airnav.com which as an example you could select Corvallis Municipal Airport and then go down the page to:

I take the information there and then try to use that info on GoogleEarth to locate the tacan or VOR precisely. There are other web resources (FAA?) that also have precise location data once you have the name of the NAVAID. Use multiple sources, they should match. If you can visually see the NAVAID, even better.