| |
ZL3AI > APRDIG 03.02.03 14:29l 264 Lines 9877 Bytes #999 (0) @ WW
BID : 785-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 25, 1/4
Path: DB0FHN<DB0ZWI<DB0HDF<DB0ERF<DB0FBB<DB0GOS<ON0AR<ON0AR<VK3TE<ZL2BAU<
ZL3VML
Sent: 030129/1002Z @:ZL3VML.#80.NZL.OC #:58385 [Chch-NZ] FBB7.00i $:785-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Saturday, January 25, 2003.
1. Re: Icon for I'net-only station?
2. RE: D700 As base digipeater
3. APRSWest.net
4. www.vicinity.com
5. RE: installed infrastructure, WAS: Symbols/Icons was something else
6. RE: Incident Command Post Symbol
7. Catch-22: Network Personality ID requires Spec Work
8. RE: Incident Command Post Symbol
9. RE: Incident Command Post Symbol
10. Re: Catch-22: Network Personality ID requires Spec Work
11. RE: Skywarn Symbol
12. New Garmin PDA
13. DIGI_NED floppy V1.1
14. Internet worm and slow internet overnight
15. Re: Icon for I'net-only station?
16. RE: Skywarn Symbol
17. RE: New Garmin PDA
18. RE: Incident Command Post Symbol
19. Re: Icon for I'net-only station?
20. Re: Icon for I'net-only station?
21. Re: Icon for I'net-only station?
22. Re: Icon for I'net-only station?
23. Re: Icon for I'net-only station?
24. Easy Symbol/Capability Suggestion
25. Re: Icon for I'net-only station?
26. Re: Icon for I'net-only station?
----------------------------------------------------------------------
Subject: Re: Icon for I'net-only station?
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Fri, 24 Jan 2003 23:13:28 -0600
X-Message-Number: 1
Well yea, yea, I could do that! 8)
>Okay! Pat, you are the man! Do it! Submit it to the list. I posted a
>good start for you...add to it and post it..ask Bob about the
>history...great source.
>Make a list we can all be proud of! This page:
>http://db.aprsworld.net/datamart/symbol-count.php will help you out too!
>;)
>
>Jim, WA6OFT
----------------------------------------------------------------------
Subject: RE: D700 As base digipeater
From: "Herb Gerhardt" <hgerhardt@charter.net>
Date: Fri, 24 Jan 2003 21:21:33 -0800
X-Message-Number: 2
Josh,
Yes, the D700 can be set as a digipeater, however, in the Pacific NW we
specifically have requested that base stations only respond to RELAY and are
NOT set as Digipeaters. If base stations are set as digis it will cause too
many useless packets to be generated and saturate the system. Yes, we do
have a number of home stations who insist on running "their station" as a
digi and there really is nothing that we can do about it, but we certainly
do not recommend it or encourage it.
Don't get me wrong, there are times you may need to set one as a digi, like
if you in a very remote area and do not have any mountain top digis
available. Also if you are working a SAR or Public Service Event, you may
need some temporary digis to make sure your local trackers are getting out
into the network for only as far as is necessary for your event. I do run
my D700 as a mobile digi during local SAR events.
Not sure I understand why you would want to replace the D700 tracker in your
mobile with a different tracker. The D700 is the ideal mobile tracker and
was designed for that purpose. That is where I keep and use mine.
Herb, KB7UVC
NW APRS Group, West Sound Coordinator
Our WEB Site: www.nwaprs.org
----------------------------------------------------------------------
Subject: APRSWest.net
From: "Dick Stanich" <dick@kb7zva.com>
Date: Fri, 24 Jan 2003 23:57:7
X-Message-Number: 3
This is just a heads-up to tell everyone that use APRSWEST.NET, as their
APRS IS server, a couple of new dedicated T1 lines will be finalized for
installation on Monday, Jan. 27.
It is likely that service will be interrupted at some point. There will be
some load testing starting soon in an attempt to tweak the system.
Dick, KB7ZVA
APRSWEST.NET
http://kb7zva.com
----------------------------------------------------------------------
Subject: www.vicinity.com
From: "Willnotreply GMX" <willnotreply@gmx.net>
Date: Fri, 24 Jan 2003 22:53:07 -0800
X-Message-Number: 4
Interesting, I went to www.vicinity.com and got this popup message:
Vicinity is now a subsidiary of Microsoft and part of the MapPoint
Business Unit. By combining the companies, customers will benefit
from accelerated development of location-enhanced technology and
services. Click here to continue to the Vicinity site, or click here to go
to the MapPoint site.
I suppose we can expect changes down the road with www.findu.com:(
----------------------------------------------------------------------
Subject: RE: installed infrastructure, WAS: Symbols/Icons was something else
From: "Bob D." <n2iph@comcast.net>
Date: Sat, 25 Jan 2003 07:26:49 -0500
X-Message-Number: 5
>>it is obvious that every improvement will take years to become widespread.
Or, we could take a page from Micro$oft's book and obsolete everyone
overnight, forcing an upgrade and synchronization for their own good :-(
Just kidding, but somehow we do need to get many of these DIGIs up to
date in a relatively short time as Henk says. Hey, we did it when we
QSY'd from 145.790, it can be done again. Yes, there may be those who
will balk at having to replace equipment that has been working just fine
for the last 5 years, but technology waits for no Ham. Is a 6 month or
one year time frame too long once we have agreed on what the minimum
DIGI capabilities/configuration should be?
BEFORE we jump into this though, we should hash out here what that new
system will be, as has been going on in these informative and thoughtful
discussions.
----------------------------------------------------------------------
Subject: RE: Incident Command Post Symbol
From: "Bob D." <n2iph@comcast.net>
Date: Sat, 25 Jan 2003 07:35:48 -0500
X-Message-Number: 6
>>I never heard if the Incident Command Post Symbol was ever adopted.
>What should it look like?
A box with ICP in it.
----------------------------------------------------------------------
Subject: Catch-22: Network Personality ID requires Spec Work
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Sat, 25 Jan 2003 08:27:16 -0500
X-Message-Number: 7
I may be stating the obvious, but *if* there is really the need to know
where the IGates, RGates, Digi's, WXStations etc are, and not require the
operator to follow an Icon standard, then there really needs to be an
enhancement to the APRS Spec.
This information is not presently embedded anywhere in a frame. Until it
is, it will not be possible to reach the goals that this group seems to
have or to mine for this info.
Top 9 Reasons (so as to avoid copyright infringement with a certain
latenight television show) as to why it really ought to be a priority to
add a Station Configuration Code to the spec:
9. It will give newbies greater insight into setting proper digi paths (read
the archives...this is a commonly recurring theme)
8. Originating stations can still express their own personality in using
display icons (this will always be an issue, anyway)
7. Multiple (Network) Personalities can be identified (and treated? <grin>)
6. Adding a Station Configuration Code can be done without breaking
anything that is presently in use (it can sit in the comment field)
5. It would provide authors with additional information against which they
can write useful enhancements to their client-side systems. This would
include things like: Display Digi's or Display IGates or Display Trackers
4. From an operator's standpoint, one would have enough information about
the infrastructure of the APRS system that you could make an informed
decision as to how to set your Unproto to get you to the network device
that you are most interested in getting to without "just flooding" the
network.
3. When it comes to S&R operation, embedding a band-of-origination
designation will help focus DFers
2. It will make your teeth whiter and will freshen your breath, too
1. It's easy to do, really it is. :o)
Maybe the question should have been asked, "Is this a need or not?". Maybe
this proposal is slaying an "Imaginary Dragon"?
Regards,
Ev, W2EV
----------------------------------------------------------------------
Subject: RE: Incident Command Post Symbol
From: "Spider" <spider@rivcom.net>
Date: Sat, 25 Jan 2003 06:42:19 -0700
X-Message-Number: 8
----- Original Message -----
From: "Bob D." <n2iph@comcast.net>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Saturday, January 25, 2003 5:35 AM
Subject: [aprssig] RE: Incident Command Post Symbol
>>>I never heard if the Incident Command Post Symbol was ever adopted.
>>What should it look like?
>
>A box with ICP in it.
The correct symbol is posted at www.wa6oft.com/icp.htm
Jim, WA6OFT
----------------------------------------------------------------------
Subject: RE: Incident Command Post Symbol
From: Robbie <mwrobertson@attbi.com>
Date: Sat, 25 Jan 2003 08:34:40 -0600
X-Message-Number: 9
Hi Jim,
Been there a couple times, and running Netscape 7.01, there is no black
border, "as shown".. Is there a border or not?
Robbie, wa9inf
----------------------------------------------------------------------
Subject: Re: Catch-22: Network Personality ID requires Spec Work
From: "Bud Talbot" <kb9wvg@arrl.net>
Date: Sat, 25 Jan 2003 10:3:23
X-Message-Number: 10
What was the organization of the group who authored our current spec? Could
a new or re-worked spec be authored in a similar manner or could it be done
as an online community collaborative? I see that there are a lot of people
on the sig with some good input.
Once any new version or addendum is complete, we also need to think about
popularizing it (ie- an "APRS for Newbies" version or something like that).
Version 1.0.1 (or whatever version we use now) isn't all that easy for the
average ham to read and use. By the way, I do use the chapter on
compression when teaching that subject to my high school engineering class!
Good stuff.
fwiw,
73
Bud
KB9WVG
http://home.houston.rr.com/kb9wvg
Elkins High School ARC: N5EHS
----------------------------------------------------------------------
Read previous mail | Read next mail
| |