longitude

Edit: And furthermore, wouldn't the spread be somewhat random with respect to the longitude of the ascending nodes?

This is especially true when you consider that it's doing Manhattan distance on raw latitude and longitude.

Your little timesheet app can simply log that at time t worker W clocked in/out at latitude and longitude x y.

While in the GIS world apparently this is the standard, outside the GIS world everybody talks in terms of latitude,longitude (y,x).

Holding people accountable for crossing the.08 limit is like holding them accountable for trespassing once they walk past a particular longitude.

It is possible to determine your longitude, but it is awfully tricky if you don't own a sextant or GPS unit.

Breaking it down by longitude would be very helpful too, and not much reason to not make that breakdown in addition to the lattitude one, which means 5mb data chunks.

Along the way, we could mostly straighten out our measurements for dates/times, angles including longitude/latitude, etc.

But on a globe, two lines of longitude that are both at 90 degrees to the equatorial line will nevertheless converge at the pole.

Then again, there's probably some more edge cases even with latitude/longitude coordinates.

Place a circle at the south pole, and slide it along that line of longitude until your sliding circle touches any other already-placed circle.

Knowing the destination and my latitude and longitude, at least I'd know I was close, without having to reference this service.

There is nothing that says "the standard is longitude,latitude".

A Point is not a Size, but an array of numbers could be interpreted as either, or as a Latitude/Longitude pair, or as anything else.