[aprssig] [APRS] DIGIPEATER Callsigns (by location) & common sense

[Charles Doughtie]

https://www.youtube.com/embed/JHixeIr_6BM?rel=0&autoplay=1&iv_load_policy=3


 

Hands off-info display
 
de Charlie, N5EXY, Grid EM10fl, 
South Suburban Greater Hutto




>________________________________
> From: Robert Bruninga <bruninga at usna.edu>
>To: TAPR APRS Mailing List <aprssig at tapr.org> 
>Sent: Sunday, July 20, 2014 6:52 PM
>Subject: Re: [aprssig] [APRS] DIGIPEATER Callsigns (by location) & common	sense
> 
>
>
>AIRPort designators work if they somewhat match the city name, but some dont match at all, and wont be recognized by a m obile.
>
>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.  
>
>IE, how far and in what directin is FM19 if I am in EN37?  Again, not human (hands-off) friendly.  
>
>Remember:  Hands off-info display to the mobile operator is the #1 goal of APRS.
>
>Bob, WB4APR
>
>
>
>
>
>
>On Sun, Jul 20, 2014 at 8:01 AM, Jim Conrad <jjc at oceanviewcom.com> wrote:
>
>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.
>>
>>Jim - N4WFP
>>
>>At 03:15 PM 7/19/2014, you wrote:
>>
>>> Ah because of your situation the whole world has to jump to your wishes?
>>>
>>>No, not at all.  I'm simply saying I see the value of using a digipeater's
>>>location name instead of a ham callsign.  If it does not apply in anyone's
>>>situation, then don't do it.
>>>
>>>But where it makes sense, it seems to work very well.
>>>
>>>EXCEPT when people name them by their local reference, like GRNMTN for
>>>Green mountain when no one but the club members know where that is.  Then
>>>such a change accomplishes nothing, since local club members know both the
>>>CALL and the MOUNTAIN.  So there is no advantage.
>>>
>>>But a name like WASHDC meaning it is the Washington DC digi, then that
>>>serves a useful purpose.
>>>
>>>People need to think outside of their local box when thinking about how
>>>their local APRS digipeater serves travelers, and how it appears on their
>>>radio LISTS.
>>>
>>>And if the BEACON contains the other recommended features like local FREQ
>>>objects, and Club Net times and Club meeting dates, then they can actually
>>>reachout to passing traveling hams.  The recommended format includes all
>>>that info in the single BEACON packet.
>>>
>>>Ill be recommending a change of our local digi from N3UJJ-6 to ANNAP
>>>(Annapolis) when I get a chance.
>>>
>>>Bob, Wb4APR
>>>.
>>>_______________________________________________
>>>aprssig mailing list
>>>aprssig at tapr.org
>>>http://www.tapr.org/mailman/listinfo/aprssig
>>>
>><:><:><:><:><:><:><:><:><:><:><:><:><:><:>
>>        Jim Conrad - jjc at oceanviewcom.com
>>          757-560-5970 - 757-512-5710 Fax
>>           Amateur Radio Callsign N4WFP
>> CAGE 0UD60 - http://www.oceanviewcom.com 
>>_______________________________________________
>>aprssig mailing list
>>aprssig at tapr.org
>>http://www.tapr.org/mailman/listinfo/aprssig
>>
>
>_______________________________________________
>aprssig mailing list
>aprssig at tapr.org
>http://www.tapr.org/mailman/listinfo/aprssig
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20140720/91fff4d9/attachment.html>