<div dir="ltr"><div>AIRPort designators work if they somewhat match the city name, but some dont match at all, and wont be recognized by a m obile.<br><br></div>Yes, Gridsquares are a unique location, but when driving down the highway and FM18 would show up on the DISPLAY, I personally would have no clue where that is. (yes, I canpush a few buttons and see what grid my APRS radio position is currently in, but still, I am *diving* and cannot/should not do that. Also, it is hard to correlate across grid boundaries. <br>
<br>IE, how far and in what directin is FM19 if I am in EN37? Again, not human (hands-off) friendly. <br><br>Remember: Hands off-info display to the mobile operator is the #1 goal of APRS.<br><br>Bob, WB4APR<br><br><br>
<div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 20, 2014 at 8:01 AM, Jim Conrad <span dir="ltr"><<a href="mailto:jjc@oceanviewcom.com" target="_blank">jjc@oceanviewcom.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If you really want to building and enhance a network that can automate routing and be self healing why not use grid squares since that actually does convey a fairly accurate location. Not as nice as ANNAP from a human readable format but somewhere in between. My own naming nomenclature for several nodes on the east coast of some IP infrastructure I own is to use the FAA designator of the nearest airport.<br>
<br>
Jim - N4WFP<br>
<br>
At 03:15 PM 7/19/2014, you wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> Ah because of your situation the whole world has to jump to your wishes?<br>
<br>
No, not at all. I'm simply saying I see the value of using a digipeater's<br>
location name instead of a ham callsign. If it does not apply in anyone's<br>
situation, then don't do it.<br>
<br>
But where it makes sense, it seems to work very well.<br>
<br>
EXCEPT when people name them by their local reference, like GRNMTN for<br>
Green mountain when no one but the club members know where that is. Then<br>
such a change accomplishes nothing, since local club members know both the<br>
CALL and the MOUNTAIN. So there is no advantage.<br>
<br>
But a name like WASHDC meaning it is the Washington DC digi, then that<br>
serves a useful purpose.<br>
<br>
People need to think outside of their local box when thinking about how<br>
their local APRS digipeater serves travelers, and how it appears on their<br>
radio LISTS.<br>
<br>
And if the BEACON contains the other recommended features like local FREQ<br>
objects, and Club Net times and Club meeting dates, then they can actually<br>
reachout to passing traveling hams. The recommended format includes all<br>
that info in the single BEACON packet.<br>
<br>
Ill be recommending a change of our local digi from N3UJJ-6 to ANNAP<br>
(Annapolis) when I get a chance.<br>
<br>
Bob, Wb4APR<br>
.<br>
______________________________<u></u>_________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/<u></u>listinfo/aprssig</a><br>
</blockquote>
<br>
<:><:><:><:><:><:><:><:><:><:><u></u><:><:><:><:><br>
Jim Conrad - <a href="mailto:jjc@oceanviewcom.com" target="_blank">jjc@oceanviewcom.com</a><br>
<a href="tel:757-560-5970" value="+17575605970" target="_blank">757-560-5970</a> - <a href="tel:757-512-5710" value="+17575125710" target="_blank">757-512-5710</a> Fax<br>
Amateur Radio Callsign N4WFP<br>
CAGE 0UD60 - <a href="http://www.oceanviewcom.com" target="_blank">http://www.oceanviewcom.com</a> <br>
______________________________<u></u>_________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/<u></u>listinfo/aprssig</a><br>
</blockquote></div><br></div></div></div></div>