[aprssig] APRS-IS Database :: Query for static dataset

Nagi Punyamurthula n0agi at n0agi.com
Mon Jul 20 18:18:16 EDT 2015

Thank you Pete for this info. I will do some browsing of servers ports and do whip up some code for pulling some data and testing


-----Original Message-----
From: aprssig [mailto:aprssig-bounces at tapr.org] On Behalf Of Pete Loveall AE5PL Lists via aprssig
Sent: Monday, July 20, 2015 4:01 PM
To: TAPR APRS Mailing List <aprssig at tapr.org>
Subject: Re: [aprssig] APRS-IS Database :: Query for static dataset

One more thing on the history queue: a number of years ago, javAPRSSrvr was modified to only queue position reports (any type of position report including Status packets with grid square and Item in Message packets).  This was done to reduce the number of packets being flooded to the client by eliminating packets which have no historical value to a display client (the original purpose, as Steve stated, for history ports).  The history port was never meant to be a database dump nor something to connect to on a regular basis with a single client due to the large volume of packets being sent (not everyone has fiber run to their servers or clients).  In javAPRSSrvr, it was intended to display stations that have appeared over the past 30 minutes (and any track that might have occurred over that same time period) especially after the introduction of javAPRSFilter which allowed further reduction of the number of packets being sent to the client.


Pete Loveall AE5PL
pete at ae5pl dot net
aprssig mailing list
aprssig at tapr.org

More information about the aprssig mailing list