Hi,
Quoting from
http://he.fi/aprsc/ :
"""
aprsc has been designed strictly for use within the APRS-IS core, hub and
Tier2 servers. It includes only the basic functionality required by those
servers.
It does not, and will not, have any additional functions such as igating,
digipeating, interfacing to radios, D-PRS or other gateway functions, or
object generation. The idea is to keep aprsc relatively simple and lean,
and leave the more specialized features for more specialized software.
"""
Data logging fits into the category of "not required by an APRS-IS core
server", so I won't be adding such a feature, to limit feature creep. If
such a feature would be implemented, it might invite APRS-IS server
operators to enable it, which might lead to performance issues and disk
space accidents when a lot of traffic is suddenly created, so I'd rather
keep logging mostly on different servers. I do a lot of logging and
archiving on
aprs.fi myself, using clients connecting to the aprsc server.
To get data of specific callsigns, you can tell aprsc to filter data by
callsign or prefix (b/ and p/ filters):
https://www.aprs-is.net/javAPRSFilter.aspx
- Hessu