[Xastir] Using time field data in Xastir objects plus trail colour

[Gerry Creager N5JXS]

There's been a lot of anguish about this on the APRS sig and the strong 
opinions of some of the scions of this aspect of the hobby that, well, 
thanks to the 'tactical' nature of APRS, timestamping them when received 
is good enough.

Harrumph...

I'd really like to see a timestamp associated with 'em.  I think it'd be 
beneficial.  It's another datapoint that I happen to believe will 
benefit a number of groups.

gerry

Tom Tessier wrote:
> Hello,
> 
> I see there are some comments in the source code regarding the use of the
> time field in APRS packets, so someone must have thought about this before!
> Right now the age of positions in Xastir are based on when Xastir received
> them. This also applies to replaying saved trails - the age is shown from
> the time of replay, not the time the trail was originally recorded. This is
> great, and works very well. Now, the people I'm working with are looking at
> using Xastir in SAR situations. One thing that came up in discussion was
> that we may want to replay a past search trail as a comparison to a current
> one but want to make sure the replayed trail isn't confused with one that is
> fresh.
> 
> If a received packet actually has the time embedded, it would be beneficial
> if the time in the packet be used throughout Xastir - or at least an option
> to do so - including playbacks. Is anyone looking at this kind of change?
> May I humbly volunteer to assist in this effort if this isn't already in the
> works?
> 
> 73's,
> 
> -Tom
> 
> de VE4TRT
> 
> 
> _______________________________________________
> Xastir mailing list
> Xastir at xastir.org
> https://lists.xastir.org/mailman/listinfo/xastir

-- 
Gerry Creager -- gerry.creager at tamu.edu
Texas Mesonet -- AATLT, Texas A&M University	
Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.847.8578
Page: 979.228.0173
Office: 903A Eller Bldg, TAMU, College Station, TX 77843