Quote Originally Posted by lackofwords View Post
First of all, the problem is trying to clear up ambiguity caused by how people tend to read maps. Some people read maps as X,Y and others as Y,X. It causes ambiguity when trying to give directions. It was only cleared up a little bit when they made the position coordinates in game listed as X,Y standards oppose to what Eoreapedia used to read them as Y,X.

To refute what Murugan said

A map does not always list their locations as X,Y. Take for example road maps below published for AAA/CAA, and another one is tourist map. Noticed they are listing locations as Y,X.
(click for full image)

Even worst from the same publisher, hagstrom maps, list their locations always as LETTER, NUMBER. However, uses "red line" and "blue line" grids square systems, where the location of the letter and number could be X,Y or Y,X depending on the map. (publications of 1992 maps of Queens borough NY and Suffolk County NY)


Now, back to the issue of ambiguity, provided with the examples above. If these map publishers were to list their locations strictly as numbers, then it adds an ambiguity of what the numbers actually represents. However, since they labeled each axis as a distinct value, you can not possibly mistaken the axis regardless of how you provide the location.

Such as, saying the location is at A,5 and 5,A would mean the same thing since they are distinct values on the map.

However, saying 1,5 and 5,1 could mean either location when the axes are both labeled numerically.
Thanks. You said it better than I ever could. This is why the maps need to use Letter, Number.

Yoshi-P - Read it. Community Manager - Escalate it.