Is there a technical reason why Android tools (DDMS, and emulator "geo fix") expect longitude before latitude?

This isn't really a problem, I am able to use the Android tools correctly, but they always trip me up when I come back to them because they expect input with longitude first, then latitude (geo fix, and DDMS).

That's backward from the way I have always used them, and from the way every other tool/API I've used has represented them, and even from the way the Android APIs use them (GeoPoi开发者_开发技巧nt, for example, expects latitude first, then longitude).

I am curious if there is a technical reason for this that I don't understand, or if it's easier in some context or something (some reason for it, or is it just random)?

I think that PROJ.4 is one of the most widely spread libraries for coordinate transformations. Similar to Android it is also using Longitude before Latitude.

I had a problem with that when I started to use it: How to transform coordinate from WGS84 to a coordinate in a projection with PROJ.4?

So all the coordinate libraries that I have used in programming have used Longitude before Latitude, but I don't think there is any standards on this and no technical reason since it's just two values and one of them has to be first.