I see periodic objects show up with the icon of a gray circle with a red question mark. They are many miles from their actual location. Clicking on the icon gives me a box of either seemingly garbage characters or just a blank in the comments field. Many of these are fixed sites, so I know the location is not correct. Some are mobile, but when I talk to them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
The question mark icon is for stations with unknown positions. A station that sends a status message, telemetry, or positionless weather report first (as far as your station newly listening is concerned) means that YAAC doesn't know where to plot it or
what its symbol is. So YAAC guesses the station's location by assuming it's near its first digipeater (assuming the digipeater's position report has been heard). This feature is called "vicinity plotting".
Once YAAC hears an actual position report with an APRS symbol code from the station, it will change the icon and move it to the correct location on the map.?
While the station's actual position is not known, and either it wasn't digipeated and heard by an I-Gate whose position isn't known, or digipeated by a digipeater whose position isn't known, the position remains at latitude/longitude (0,0). The button
on the map toolbar with a big 0 on it will jump the map to that location.
Note that, if you don't like it, you can turn vicinity plotting off in the expert-mode configuration dialog.?
Hope this helps.
Andrew, KA2DDO
author of YAAC
toggle quoted message
Show quoted text
-------- Original message --------
From: Michael WA7SKG <wa7skg@...>
Date: 1/4/20 15:36 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Strange Position Reports
I see periodic objects show up with the icon of a gray circle with a red
question mark. They are many miles from their actual location. Clicking
on the icon gives me a box of either seemingly garbage characters or
just a blank in the comments field. Many of these are fixed sites, so I
know the location is not correct. Some are mobile, but when I talk to
them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
Still confused. The two items I see most are digipeaters. They show up on my map near (varying in about a five mile radius) a local digi, but one is actually 90 miles away and the other is 130 miles away with significant terrain between them and the local digi. They are persistent in that they move around a little bit, but are shown for days at a time in the same area. I do have "vicinity plotting" turned off, yet they still show up. They never show up in their actual locations.
I only have RF items on my map. Nothing from the Internet is displayed.
Just another of those APRS mysteries I guess.
Michael WA7SKG
Andrew P. wrote on 1/4/20 6:47 PM:
toggle quoted message
Show quoted text
The question mark icon is for stations with unknown positions. A station that sends a status message, telemetry, or positionless weather report first (as far as your station newly listening is concerned) means that YAAC doesn't know where to plot it or what its symbol is. So YAAC guesses the station's location by assuming it's near its first digipeater (assuming the digipeater's position report has been heard). This feature is called "vicinity plotting". Once YAAC hears an actual position report with an APRS symbol code from the station, it will change the icon and move it to the correct location on the map. While the station's actual position is not known, and either it wasn't digipeated and heard by an I-Gate whose position isn't known, or digipeated by a digipeater whose position isn't known, the position remains at latitude/longitude (0,0). The button on the map toolbar with a big 0 on it will jump the map to that location. Note that, if you don't like it, you can turn vicinity plotting off in the expert-mode configuration dialog. Hope this helps. Andrew, KA2DDO author of YAAC
-------- Original message -------- From: Michael WA7SKG <wa7skg@...> Date: 1/4/20 15:36 (GMT-05:00) To: [email protected] Subject: [yaac-users] Strange Position Reports I see periodic objects show up with the icon of a gray circle with a red question mark. They are many miles from their actual location. Clicking on the icon gives me a box of either seemingly garbage characters or just a blank in the comments field. Many of these are fixed sites, so I know the location is not correct. Some are mobile, but when I talk to them later, they were never in the area. What's up with that? Michael WA7SKG
|
Hmmm... vicinity plotting can also work in the opposite direction to guesstimate the position of "stealth" digipeaters (those that do not transmit position reports of their own, and only meet their legal station identification regulations by UITRACE-inserting their callsign into digipeat paths). When a regular station's position report is digipeated by a "stealth" digipeater, YAAC attempts to approximate the position of the digipeater as being in the centroid of all the stations it has been heard to digipeat. How do you know these digipeater positions are incorrect? How are you checking this? Please provide some callsigns of the participating stations so others can help you interpret what is going on. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Michael WA7SKG <wa7skg@...> Sent: Saturday, January 4, 2020 11:51 PM To: [email protected]Subject: Re: [yaac-users] Strange Position Reports Still confused. The two items I see most are digipeaters. They show up on my map near (varying in about a five mile radius) a local digi, but one is actually 90 miles away and the other is 130 miles away with significant terrain between them and the local digi. They are persistent in that they move around a little bit, but are shown for days at a time in the same area. I do have "vicinity plotting" turned off, yet they still show up. They never show up in their actual locations. I only have RF items on my map. Nothing from the Internet is displayed. Just another of those APRS mysteries I guess. Michael WA7SKG Andrew P. wrote on 1/4/20 6:47 PM: The question mark icon is for stations with unknown positions. A station that sends a status message, telemetry, or positionless weather report first (as far as your station newly listening is concerned) means that YAAC doesn't know where to plot it or what its symbol is. So YAAC guesses the station's location by assuming it's near its first digipeater (assuming the digipeater's position report has been heard). This feature is called "vicinity plotting".
Once YAAC hears an actual position report with an APRS symbol code from the station, it will change the icon and move it to the correct location on the map.
While the station's actual position is not known, and either it wasn't digipeated and heard by an I-Gate whose position isn't known, or digipeated by a digipeater whose position isn't known, the position remains at latitude/longitude (0,0). The button on the map toolbar with a big 0 on it will jump the map to that location.
Note that, if you don't like it, you can turn vicinity plotting off in the expert-mode configuration dialog.
Hope this helps.
Andrew, KA2DDO author of YAAC
-------- Original message -------- From: Michael WA7SKG <wa7skg@...> Date: 1/4/20 15:36 (GMT-05:00) To: [email protected] Subject: [yaac-users] Strange Position Reports
I see periodic objects show up with the icon of a gray circle with a red question mark. They are many miles from their actual location. Clicking on the icon gives me a box of either seemingly garbage characters or just a blank in the comments field. Many of these are fixed sites, so I know the location is not correct. Some are mobile, but when I talk to them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
My station = WA7SKG in Dallas, OR Digipeater = W7SRA about 20 miles SE of me, about 10 miles south of Salem, OR Digipeater = NICOLI about 90 miles NW of me near Westport,OR Digipeater = BAMBAM about 130 miles NE of me near Goldendale, WA (These digipeaters show up in their proper locations on aprs.fi)
The NICOLI and BAMBAM digipeaters routinely show up with gray icons with red question marks in a small area about 2-3 miles radius of W7SRA digipeater.
Michael WA7SKG
Andrew P. wrote on 1/5/20 6:30 PM:
toggle quoted message
Show quoted text
Hmmm... vicinity plotting can also work in the opposite direction to guesstimate the position of "stealth" digipeaters (those that do not transmit position reports of their own, and only meet their legal station identification regulations by UITRACE-inserting their callsign into digipeat paths). When a regular station's position report is digipeated by a "stealth" digipeater, YAAC attempts to approximate the position of the digipeater as being in the centroid of all the stations it has been heard to digipeat. How do you know these digipeater positions are incorrect? How are you checking this? Please provide some callsigns of the participating stations so others can help you interpret what is going on. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Michael WA7SKG <wa7skg@...> Sent: Saturday, January 4, 2020 11:51 PM To: [email protected] Subject: Re: [yaac-users] Strange Position Reports Still confused. The two items I see most are digipeaters. They show up on my map near (varying in about a five mile radius) a local digi, but one is actually 90 miles away and the other is 130 miles away with significant terrain between them and the local digi. They are persistent in that they move around a little bit, but are shown for days at a time in the same area. I do have "vicinity plotting" turned off, yet they still show up. They never show up in their actual locations. I only have RF items on my map. Nothing from the Internet is displayed. Just another of those APRS mysteries I guess. Michael WA7SKG Andrew P. wrote on 1/4/20 6:47 PM:
The question mark icon is for stations with unknown positions. A station that sends a status message, telemetry, or positionless weather report first (as far as your station newly listening is concerned) means that YAAC doesn't know where to plot it or what its symbol is. So YAAC guesses the station's location by assuming it's near its first digipeater (assuming the digipeater's position report has been heard). This feature is called "vicinity plotting".
Once YAAC hears an actual position report with an APRS symbol code from the station, it will change the icon and move it to the correct location on the map.
While the station's actual position is not known, and either it wasn't digipeated and heard by an I-Gate whose position isn't known, or digipeated by a digipeater whose position isn't known, the position remains at latitude/longitude (0,0). The button on the map toolbar with a big 0 on it will jump the map to that location.
Note that, if you don't like it, you can turn vicinity plotting off in the expert-mode configuration dialog.
Hope this helps.
Andrew, KA2DDO author of YAAC
-------- Original message -------- From: Michael WA7SKG <wa7skg@...> Date: 1/4/20 15:36 (GMT-05:00) To: [email protected] Subject: [yaac-users] Strange Position Reports
I see periodic objects show up with the icon of a gray circle with a red question mark. They are many miles from their actual location. Clicking on the icon gives me a box of either seemingly garbage characters or just a blank in the comments field. Many of these are fixed sites, so I know the location is not correct. Some are mobile, but when I talk to them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
There's a pretty good way to remove the mysteries of APRS...
Look at the packets being sent by a station and received by your station.
I can't see the packets being received by your station unless you show them to me, but I can look at what is being sent...
?
2020-01-06 18:32:15 MST:?>APTT4,WIDE1-1,WIDE2-2,qAR,:T#420,125,070,255,105,083,000010112020-01-06 18:37:18 MST:?>APTT4,WIDE1-1,WIDE2-2,qAR,:>KI7RUS-13?Cliffside?Launch?HP?WX
All BAMBAM is sending is status packets and telemetry...?
It's just a noise maker... there's an i-gate within simplex range that can gate the WX packets, and the 3 hop status messaging is just a waste of resources.
??
The position report that heard may have been heard years ago. stores information for a very long time. You can send your telemetry definitions once, and will keep them in memory for years.
Transient stations that come on every so often don't have that long term memory. BAMBAM is also very naughty, using a WIDE1-1 path, especially when it is located less than a mile from the JUNIPER digipeater. Why is it asking for assistance from a home fill-in digipeater to get heard by a main digipeater less than a mile away? Especially when there is evidence that ALAKES locates over 200 km away can hear BAMBAM direct?
NICOLI sends out positions reports via local only, and telemetry via a single hop.
??
2020-01-06 17:57:18 MST:?>APRS,WIDE2-1,qAR,:T#050,189,098,005,055,173,00000000 2020-01-06 18:06:24 MST:?>APRS,qAR,:!4605.21N/12327.31W#PHG2830W2,?ORn-N,?Fill-in?/?NA7Q?14.2V?76.2F??
YAAC is telling you that you heard the telemetry and/or status packets via the W7SRA digipeater, and with no location information, the best it can do is tell you that the W7SRA digipeater handled the packets.? NICOLI is operating in a much more network friendly manner than BAMBAM... it causes far less load on the system with conservative path settings. Most packets aren't going any further than onto the local airwaves.
??
Pretty tough to expect the computer to provide an accurate position for where the digipeaters are located with no position reports heard by your station.
There are no real mysteries in APRS, just answers that you have looked for yet.
toggle quoted message
Show quoted text
On Sun, Jan 5, 2020 at 9:06 PM Michael WA7SKG < wa7skg@...> wrote: My station = WA7SKG in Dallas, OR
Digipeater = W7SRA about 20 miles SE of me, about 10 miles south of
Salem, OR
Digipeater = NICOLI about 90 miles NW of me near Westport,OR
Digipeater = BAMBAM about 130 miles NE of me near Goldendale, WA
(These digipeaters show up in their proper locations on )
The NICOLI and BAMBAM digipeaters routinely show up with gray icons with
red question marks in a small area about 2-3 miles radius of W7SRA
digipeater.
Michael WA7SKG
Andrew P. wrote on 1/5/20 6:30 PM:
> Hmmm... vicinity plotting can also work in the opposite direction to guesstimate the position of "stealth" digipeaters (those that do not transmit position reports of their own, and only meet their legal station identification regulations by UITRACE-inserting their callsign into digipeat paths). When a regular station's position report is digipeated by a "stealth" digipeater, YAAC attempts to approximate the position of the digipeater as being in the centroid of all the stations it has been heard to digipeat.
>
> How do you know these digipeater positions are incorrect? How are you checking this?
>
> Please provide some callsigns of the participating stations so others can help you interpret what is going on.
>
> Andrew, KA2DDO
> author of YAAC
> ________________________________________
> From: [email protected] <[email protected]> on behalf of Michael WA7SKG <wa7skg@...>
> Sent: Saturday, January 4, 2020 11:51 PM
> To: [email protected]
> Subject: Re: [yaac-users] Strange Position Reports
>
> Still confused. The two items I see most are digipeaters. They show up
> on my map near (varying in about a five mile radius) a local digi, but
> one is actually 90 miles away and the other is 130 miles away with
> significant terrain between them and the local digi. They are persistent
> in that they move around a little bit, but are shown for days at a time
> in the same area. I do have "vicinity plotting" turned off, yet they
> still show up. They never show up in their actual locations.
>
> I only have RF items on my map. Nothing from the Internet is displayed.
>
> Just another of those APRS mysteries I guess.
>
> Michael WA7SKG
>
>
> Andrew P. wrote on 1/4/20 6:47 PM:
>> The question mark icon is for stations with unknown positions. A station
>> that sends a status message, telemetry, or positionless weather report
>> first (as far as your station newly listening is concerned) means that
>> YAAC doesn't know where to plot it or what its symbol is. So YAAC
>> guesses the station's location by assuming it's near its first
>> digipeater (assuming the digipeater's position report has been heard).
>> This feature is called "vicinity plotting".
>>
>> Once YAAC hears an actual position report with an APRS symbol code from
>> the station, it will change the icon and move it to the correct location
>> on the map.
>>
>> While the station's actual position is not known, and either it wasn't
>> digipeated and heard by an I-Gate whose position isn't known, or
>> digipeated by a digipeater whose position isn't known, the position
>> remains at latitude/longitude (0,0). The button on the map toolbar with
>> a big 0 on it will jump the map to that location.
>>
>> Note that, if you don't like it, you can turn vicinity plotting off in
>> the expert-mode configuration dialog.
>>
>> Hope this helps.
>>
>> Andrew, KA2DDO
>> author of YAAC
>>
>>>
>> -------- Original message --------
>> From: Michael WA7SKG <wa7skg@...>
>> Date: 1/4/20 15:36 (GMT-05:00)
>> To: [email protected]
>> Subject: [yaac-users] Strange Position Reports
>>
>> I see periodic objects show up with the icon of a gray circle with a red
>> question mark. They are many miles from their actual location. Clicking
>> on the icon gives me a box of either seemingly garbage characters or
>> just a blank in the comments field. Many of these are fixed sites, so I
>> know the location is not correct. Some are mobile, but when I talk to
>> them later, they were never in the area.
>>
>> What's up with that?
>>
>> Michael WA7SKG
|
On Mon, Jan 6, 2020 at 06:32 PM, James Ewen wrote:
There are no real mysteries in APRS, just answers that you have looked for yet.
?
So, the real problem is with the operators of BAMBAM and NICOLI, and YAAC is simply demonstrating the "Garbage In, Garbage Out" reality of computer technology. ? Which clears up my concerns about BAMBAM -- I routinely see it "co-located" on YAAC with my digipeater (WA2WA), which is about 130 miles away. ?I had wondered what the issue was. ?The operator (KI7RUS, from the status text) should add the lat/lon to his beacon and edit the WIDE1-1 setting. Thanks for that explanation. ? But I am puzzled about one matter concerning aprs.fi -- do you know if aprs.fi plots the position for BAMBAM using CWOP data? ?I ask because the FCC registered address for KI7RUS is in Vancouver, WA (no where near Goldendale). ?The CWOP database (http://wxqa.com/sss/search1.cgi?keyword=bambam) does have a lat/lon, which resolves to the same location shown on aprs.fi. 73, Jeff AL1Q?
|
I understand this thread is old. In fact I stumbled upon in because of the "BAMBAM" station that is operating under very poor ways..
I'm the owner of NICOLI (Nicolai Mountain) and various others APRS stations. But I see NICOLI was discussed by Jeff, so I'll address it.
So NICOLI operates in the most friendly of ways as a WIDE1 digi. It doesn't spew garbage beacons like BAMBAM or many of the other stations around. It beacons a position 1 time per 10 minutes, as is the legal requirement, AND does NOT use a path. I think that is very important. Because I have multiple igates within range, and is heard by many other igates, there is no reason to add a path.?
It also has 1, yes just 1 telemetry beacon that is sent 1 time, yes 1 time PER hour with a 1 hop path. This equals 7 beacons per hour, and only 1 hop in that duration. Pretty good compared to most that just clutter and congest the network beyond belief.
Another fun fact, NICOLI only uses 5 watts on a low gain antenna on top of the 30 foot tower.?
Why does it reach so far? Location location location. Nicolai Mountain has an incredible path through the Gorge and into the east side almost across the entire station of Washington and Oregon at times. Frequently my Trout Lake station is able to be heard on Nicolai under normal conditions. Everything about this digi is done with one thing in mind. Provide coverage to an area that isn't covered, reduce congestion, block as many digi beacons as possible that shouldn't be using a path. Unfortunately the unit has the maximum block slots filled up. So some junk gets through. Like BAMBAM....
I've been wanting to get a hold of KI7RUS because of BAMBAM. It's using a seriously bad path, and is able to be heard across the entire state of Washington and Oregon. I heard it coming across a digi in Idaho last week! It's outrageous. It's not even located at the location it beacons. It beacons too frequently for the weather and the telemetry. Which in his case is every 5 minutes. APRS.fi and APRSDirect only update at 10 minute intervals for weather and telemtry. So beaconing more often does nothing.
I hope to get a hold of that guy at some point, and I hope that he is understanding. All too often these guys are not.?
73 NA7Q
|
Hi,
I was up at steens mountain near Burns and a person was using Aprs on the repeater (non-aprs). ?I think they said the person was traveling around Idaho.
toggle quoted message
Show quoted text
On Jun 19, 2020, at 10:31 PM, Michael - NA7Q <mike.ph4@...> wrote:
? I understand this thread is old. In fact I stumbled upon in because of the "BAMBAM" station that is operating under very poor ways..
I'm the owner of NICOLI (Nicolai Mountain) and various others APRS stations. But I see NICOLI was discussed by Jeff, so I'll address it.
So NICOLI operates in the most friendly of ways as a WIDE1 digi. It doesn't spew garbage beacons like BAMBAM or many of the other stations around. It beacons a position 1 time per 10 minutes, as is the legal requirement, AND does NOT use a path. I think that is very important. Because I have multiple igates within range, and is heard by many other igates, there is no reason to add a path.?
It also has 1, yes just 1 telemetry beacon that is sent 1 time, yes 1 time PER hour with a 1 hop path. This equals 7 beacons per hour, and only 1 hop in that duration. Pretty good compared to most that just clutter and congest the network beyond belief.
Another fun fact, NICOLI only uses 5 watts on a low gain antenna on top of the 30 foot tower.?
Why does it reach so far? Location location location. Nicolai Mountain has an incredible path through the Gorge and into the east side almost across the entire station of Washington and Oregon at times. Frequently my Trout Lake station is able to be heard on Nicolai under normal conditions. Everything about this digi is done with one thing in mind. Provide coverage to an area that isn't covered, reduce congestion, block as many digi beacons as possible that shouldn't be using a path. Unfortunately the unit has the maximum block slots filled up. So some junk gets through. Like BAMBAM....
I've been wanting to get a hold of KI7RUS because of BAMBAM. It's using a seriously bad path, and is able to be heard across the entire state of Washington and Oregon. I heard it coming across a digi in Idaho last week! It's outrageous. It's not even located at the location it beacons. It beacons too frequently for the weather and the telemetry. Which in his case is every 5 minutes. APRS.fi and APRSDirect only update at 10 minute intervals for weather and telemtry. So beaconing more often does nothing.
I hope to get a hold of that guy at some point, and I hope that he is understanding. All too often these guys are not.?
73 NA7Q
|
If you're referring to my comment about hearing BAMBAM in Idaho, that is incorrect. Because BAMBAM uses a 3 path hop it has a HUGE potentional reach. The digi path is more like 4 hops because of an issue with older KPC units which do not properly mark the WIDE1 digipeat. So many of the next stations digipeat the WIDE1 again, and then properly mark it. It's pretty annoying.?
|
I hope I'm not hijacking this post, but I am seeing what I'd consider "strange position reports".  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
|