| commit | eaec006a1a0540d23a4d17bb6c3be38d0ff2b03a | |
| author | Gergely Imreh <imrehg@gmail.com> | |
| Thu, 25 Sep 2008 17:36:50 +0000 (25 18:36 +0100) | ||
| committer | Gergely Imreh <imrehg@gmail.com> | |
| Thu, 25 Sep 2008 17:36:50 +0000 (25 18:36 +0100) | ||
| tree | 7c83706bb156fc202f8117364e2179c189614f13 | treesnapshot (tar.gz zip) |
| parent | e15b1240ed4553a35ac1fb8827f0a7694ab7669a | commitdiff |
Change: location with Lat,Lon order in gsmpos database
For quick checking locations, it is good to handle it
in a standard way: with Lon,Lat format one can check
any location in the gsmpos database with one copy/paste
e.g. at GoogleMaps, and no need to switch them around.
Plotting coordinates are in Lon,Lat order (opposite than
map lookups), but that's easy to handle in the software.
Every other exposed database/output/log/code should have
Lat,Lon order! (might affect Cell Locator as well...)
For quick checking locations, it is good to handle it
in a standard way: with Lon,Lat format one can check
any location in the gsmpos database with one copy/paste
e.g. at GoogleMaps, and no need to switch them around.
Plotting coordinates are in Lon,Lat order (opposite than
map lookups), but that's easy to handle in the software.
Every other exposed database/output/log/code should have
Lat,Lon order! (might affect Cell Locator as well...)
| gsmpos/gsmpos.py | diffblobblamehistory |