[aprssig] SPOT engine on APRS.FI

Andre aprs at pe1rdw.demon.nl
Mon Feb 20 09:37:58 CST 2012

Not unimportant let the POI server monitor the IS for takeovers and 
kills so people can asume ownership of objects that might need 
correcting etc.

73 Andre PE1RDW
ps should be a requirement for all servers injecting objects into the IS.

Op 20-2-2012 16:26, Andrew P. schreef:
> How long should such objects be refreshed on the APRS-IS network before they are allowed to expire and time out? If forever, you would eventually fill the map with ancient objects and bring down the SPOT/POI server from the sheer volume of data it would have to maintain; if not refreshed periodically, users might miss the object altogether if they weren't listening when it was first sent out.
> Need to define a default lifespan and an option to override the default (but no option for immortality).
> Alternatively, this could just be inferred by the clients that are tracking the sending node, such that no Object messages have to be sent at all; the clients (including aprs.fi) just snapshot the last known position of the sender when they receive the POI message.
> Just my $.02.
> Andrew Pavlin, KA2DDO
> ------Original Message------
> From: Stephen H. Smith
> To: aprssig at tapr.org
> Sent: Feb 20, 2012 10:17 AM
> Subject: Re: [aprssig] SPOT engine on APRS.FI
> On 2/20/2012 10:11 AM, Bob Bruninga wrote:
>> I wonder if we should implement a SPOT engine that looks for messages to SPOT and then turns them into objects at the senders location.
> SPOT -- Bad choice of word.   I thought you were referring to the SPOT
> emergency locator satellite sevice.  Then when you started taking about people
> on the Appalachian Trail, I through even more you were referinging to  the
> satellite service.
> Perhaps POI   (Point Of Interest as in map databases and Garmin GPS car
> navigators) would be a better term.   Also it saves one character in APRS
> message lines.

More information about the aprssig mailing list