[aprssig] Vicinity plotting
Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.toTue Nov 22 17:15:43 UTC 2011
- Previous message: [aprssig] Vicinity plotting
- Next message: [aprssig] Vicinity plotting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Having struggled with the same thing myself, I finally decided that any station from which I have not received a position report will be located at 0,0 until I get a position report. I examined many many paths before coming to the conclusion that there is NO good solution that will RELIABLY tell you where you should RANDOMLY position said station. And cluttering the map with ambiguity circles or any other indication that the station really is NOT where you're drawing it was worse than just keeping the station off the map until a position was received. I would also recommend against any sort of automatic query of a station from which you think you need additional information. Think of the traffic that would be generated when you successfully replace UI-View and 10,000 instances of your client (yes, it works via APRS-IS too, I assume) "decide" they need to know exactly where that event tracker actually IS and fire out the requests. Not a pretty picture in my mind's eye. If you haven't heard where a station is, then my opinion is that the station might as well be invisible, but at least I draw them at 0,0 off the coast of Africa. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 PS. All that said, I am considering some better approaches having watched the real-time plots of packet paths in APRSISCE/32. I may (or may not) implement some sort of user-option for "guessing" a position for a non-beaconing station... On 11/22/2011 11:30 AM, Andrew P. wrote: > Greetings, all. > > I've been trying to implement vicinity plotting of stations that don't send position reports, and I'm having a tough time of it. Many of them were originated over TCPIP, so they never had an initial digipeater to use for vicinity plotting. Others digipeated over a path without tracing, so their path only reports the WIDEn aliases. Yet others had an initial digipeater, but I never got a position report from the digi itself to use for vicinity plotting. > > So how should I handle these? Right now, they are being plotted off the coast of Africa at lat/lon 0,0. Should I be querying the invisible digis as to their position? That would at least help with some, but that would cause more spurious radio traffic. > > Thanks in advance. > > Andrew Pavlin KA2DDO > Sent from my Verizon Wireless BlackBerry > > > _______________________________________________ > aprssig mailing list > aprssig at tapr.org > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig >
- Previous message: [aprssig] Vicinity plotting
- Next message: [aprssig] Vicinity plotting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
