The two new location procedures are getlocations and getlocationinfo.

the procedure getlocation returns the geographical point type supported by  
PostGRESQL and will mostly be used for internet mapping.

The getlocationinfo procedure is more intended for use with software that  
can directly or ODBC into the database and can use specific fields to plot  
points.  The return record type is locationresult with four fields:


SELECT * from getlocations('19-Oct-2004 10:00:00', '19-Oct-2004 14:00:00',  
null, null, true, 77);

SELECT * from getlocationinfo('19-Oct-2004 10:00:00', '19-Oct-2004  
14:00:00', null, null, true, 77);

SELECT * from getlocationinfo('19-Oct-2004 10:00:00', '19-Oct-2004  
14:00:00', null, null, true);

Input:

   StartTime(Timstamp)  : Time of day to start bearing calculation
   EndTime(Timstamp)    : Time of day to end bearing calculation
   NoiseLimit(Integer)  : Minimum acceptible noise level (e.g. -13000)
   BearingTime(Integer) : Time limit in seconds to use a a grouping value
                          (used since a burst may not give enough data)
   AllLocations(Boolean): Return all (true) or only converged (false)  
locations
   AnAnimal(Integer)    : Animal ID value (optional for getlocationinfo  
function)


For AllLocations, if this is set to "true" the you will get all estimated  
locations, probably very bad locations.  If you set AllLocations to  
"false" then only those locations that converged with the MLE estimator  
will be returned.  My tests shows that AllLocations as "false" means  
sometimes you get no returned locations.