开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Fw: [yaac-users] Strange Position Reports


 

Meant to send this to the group...
________________________________________

How long have you been listening to these stations? YAAC implements a feature called "vicinity plotting", where, for stations that are transmitting, but haven't yet transmitted a _valid_ position report, Mic-E report, or status message with Maidenhead position, YAAC guesses where the station might be based on the location of the first digipeater or I-gate (if their position is already known) to forward the station's packets. If the original station is sending _invalid_ position reports, they don't count for accurate location, as YAAC can't decode them.

As to why aprs.fi can properly locate those stations, that could be for either of two reasons:

1. aprs.fi has more capability to decode more invalid formats than YAAC does (assuming the stations are sending invalid-format position reports).

2. aprs.fi has a long-term database of history, and may be using the recorded last decodable position for those callsign-SSID combinations.

Note that YAAC can also use vicinity plotting in reverse to guesstimate the location of non-position-beaconing ("stealth") digipeaters that only meet their beaconing requirements by embedding their callsigns in the digipeat path (TRACE mode).

-------- Original message --------
From: Jon Adams <n7uv.jon@...>
Date: 5/6/22 12:11 (GMT-05:00)
To: [email protected]
Subject: Re: [yaac-users] Strange Position Reports

I hope I'm not hijacking this post, but I am seeing what I'd consider "strange position reports".

[cid:[email protected]]
What I see here is that several station icons are grouped around (but strangely not on top of) a digipeater's (W7MOT-3) location atop the White Tank Mtns, west of town. There, I see my N7UV-5 icon, my ARSTRA icon, and the KE7NEA-1 icon.

This is a frequent issue, and I never resolved it myself, and perhaps that's why I wasn't using YAAC. In other s/w, like APRSIS32, and certainly in the aprs.fi server, the positions for these stations are shown correctly, so it seems to be an interpretation issue for YAAC, not a fundamental problem with the location packet.

Any ideas? I searched the listserv and this was the only msg that seemed to fit.

Cheers and 73 - Jon N7UV