Order Tray | Contact Us | Home | SIG Lists

[aprssig] BALDY APRS Station

Randy Love rlove31 at gmail.com
Mon May 21 12:44:34 UTC 2012

The issue in this case isn't that it's tactical-ly called. It's that the
creator of the newest digi didn't check uniqueness of his tactical call.

Bad digi operator!

Tacticals need to be manually checked on the aprsis for uniqueness when
being tactically named - same as a repeater object would be.

It's a lot easier when analyzing a local network where you can only see the
raw packets ( such as the raw packet history in aprs.fi or other archiving
sites or live packet display on a D700/D710 head ) when the call insertions
are, for example LANSNG, HOLLY, SFLDV, and SFLDU instead of W8FSM-3,
W8FSM-4 W8FSM-12, and W8FSM-13.

Tactical naming of digis is more for human recognition of network layout
when a visual display isn't available. And there are times when we don't
have a nice, pretty map based client available.


On Thu, May 17, 2012 at 2:05 AM, Lynn W. Deffenbaugh (Mr) <
ldeffenb at homeside.to> wrote:

> Greetings "owner"s of the BALDY APRS station,
> (Well, I would have copied both of you, but VE7WRT doesn't have an e-mail
> address at QRZ.com)
> What's wrong with Tactical-ly named APRS stations?  It gets really
> confusing when two different parts of the world use the same one. Consider
> what you'll see at:
> http://aprs.fi/?c=raw&call=**BALDY <http://aprs.fi/?c=raw&call=BALDY>
> Lynn (D)- KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> PS.  No, I'm not trying to start a flame war about Tactical station IDs.
>  I'm just trying to help the collisions get sorted out as I notice them.
>  If anyone can forward this to VE7WRT, I'd appreciate it.
> I only noticed this when a communications path line shot 1/4 the way
> across my map.
> ______________________________**_________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/**mailman/listinfo/aprssig<https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20120521/2f5f649f/attachment.htm>

More information about the aprssig mailing list