Opened 11 years ago
Last modified 11 years ago
#147 new
gmoc.py expects GeoLocation(longitude, latitude)
Reported by: | chaos@bbn.com | Owned by: | somebody |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Clients | Version: | |
Keywords: | v1.1.5 | Cc: | |
Dependencies: |
Description
The GeoLocation()
function in gmoc.py expects to be invoked as:
GeoLocation(longitude, latitude)
e.g.
GeoLocation(-71.147504, 42.389741)
Users may expect GeoLocation(latitude, longitude)
. Something should warn them that they are getting it wrong, since this could easily go unnoticed for a long time and lead to aggregates being mapped in radically incorrect places.
Note: See
TracTickets for help on using
tickets.
I would have assumed that lat/long was the convention if not specified. Since Kevin assumed it was long/lat, i'm going to suggest that there is no convention, and that the correct thing to do is to force the caller to name the args explicitly, e.g.