[aprssig] SPOT engine on APRS.FI

[Andrew P.]

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.



_______________________________________________
aprssig mailing list
aprssig at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig


Sent from my Verizon Wireless BlackBerry