[aprssig] DXCluster to APRS-RF

[Robert Bruninga]

Avoiding problems like this is why APRS was designed to
support the display of position ambiguity.  A DX spot with 
position inferred by callsign lookup, should be transmitted 
with 60 mile ambiguity so that it does not show up in a 
confusing location on any maps that may be zoomed in
below the 1024 mile range scale.

That way, they show up when you are looking at the world
map, but do not imply any more precision than that...
And do not show up when the map is zoomed in below the
zoom level where the SYMBOL is smaller than the ambiguity.

de Wb4APR, Bob

>>> steve at dimse.com 05/18/06 10:55 AM >>>

If this is the software I am thinking of, I am not a big fan. One  
piece of software out there reformats DX spots, generates a lat/lon  
based on the call, and sends it as an APRS position . The problem is  
that it results in clusters of position in the wrong spot, especially  
bad if you happen to live near the arbitrary position chosen (e.g.  
there is one position for all N4/W4/K4 calls, the near.cgi for these  
areas becomes worthless). I also field emails from angry hams who do  
not want their position on APRS.

I have no problem with the retransmission of the dx spot itself, only  
with reformatting the report with an artifical lat/lon. If this is  
not the software that does that, nevermind!

Steve K4HG

_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org 
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig