| |
ZL3AI > APRDIG 19.09.03 10:30l 140 Lines 5548 Bytes #999 (0) @ WW
BID : 1943-ZL3AI
Read: GUEST
Subj: TAPR Digest, Sep 16, 8/9
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PCC<OK0PAD<OK0PPL<DB0RES<ON0AR<WB0TAX<
7M3TJZ<EA5AKC<ZL2BAU<ZL3VML
Sent: 030918/1419Z @:ZL3VML.#80.NZL.OC #:8617 [Chch-NZ] FBB7.00i $:1943-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Abusive Digi id paths Was: Can someone contact this guy?
From: "hasan schiers" <schiers@netins.net>
Date: Tue, 16 Sep 2003 10:04:01 -0500
X-Message-Number: 51
It's a language problem, Earl. They aren't the "nodes" of old, it is simply
a network term for digipeater.
....hasan, N0AN
----------------------------------------------------------------------
Subject: Paths
From: Glenn Wiebe <gswiebe@mb.sympatico.ca>
Date: Tue, 16 Sep 2003 17:19:57 -0500
X-Message-Number: 52
What is the difference between WIDE & WIDE1-1.
73 de Glenn...VE4GN
----------------------------------------------------------------------
Subject: Re: Proper DIGI ID interleaving
From: "Scott Miller" <scott@opentrac.org>
Date: Tue, 16 Sep 2003 15:40:20 -0700
X-Message-Number: 53
Bob, can you put your recommendations in the spec errata? (Or would that be
the corrigendum?) Or maybe we need a separate file on best operating
practices...
----- Original Message -----
From: "Bob Bruninga" <bruninga@usna.edu>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Tuesday, September 16, 2003 3:11 PM
Subject: [aprssig] Proper DIGI ID interleaving
>Part of the problem might be that some digis are not correctly
>implementing the every-10-minute-Direct concept. If incorrectly done, it
>could be adding a LOT of duplication... Here is how I would do it:
----------------------------------------------------------------------
Subject: Re: Paths
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 16 Sep 2003 19:27:34 -0400 (EDT)
X-Message-Number: 54
On Tue, 16 Sep 2003, Glenn Wiebe wrote:
>What is the difference between WIDE & WIDE1-1.
WIDE is the universal digipeater alias. It is supposed to be supported by
all digipeaters everywhere. ANY TNC can be a WIDE digi by simply setting
its MYALIAS to WIDE. But since 1997, it has been improved in all modern
digis. In these digis, WIDE is one of the UIDIGI aliases, and these
trigger automatic callsign substitution. That is, the digi will
substitute its call in place of WIDE after it digipeats so that everyone
can see what digi was used. Once callsign substitution has been done,
then any given digi will not digipeat that packet again.
WIDE1-1 triggers a different algorithm in the digi. It triggers the
WIDEn-N algorithm. This algorithm digipeats the packet and decrements the
N counter. In this case, it only digipeats it once because afterwards
the packet is WIDE1-0 and it will not be further digipeated.
Notice the advantage of always starting a path with WIDE is that the
packet always then carries the callsign of the first digi that heard it.
THus, we can always tell where the packet entered the APRS system.
WIDEn-N was an advantage years ago when there were not many APRS stations
and everyone wanted to be seen all over their state and multi!
With a good printer and copy machine in the mobile comm vehicle you can
supply the teams with a proper map for their search area.
You end up handing out a lot of maps on big searches. Trying to print the
search area ahead of time never seems to work. They need to be printed at
the mobile CP for the specific search area.
Jim, WA6OFT
----------------------------------------------------------------------
Subject: Re: Proper DIGI ID interleaving
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 16 Sep 2003 19:58:53 -0400 (EDT)
X-Message-Number: 56
On Tue, 16 Sep 2003, Scott Miller wrote:
>Bob, can you put your recommendations in the spec errata?... Or maybe we
>need a separate file on best operating practices...
Its pretty much there. They are in the original DIGIS.TXT file that
google will find on my WEB page. Also, my ERRATA page points to most of
these problems in the ERRATA link FIXING 144.39. Here are the links:
DIGIS.TXT: http://www.ew.usna.edu/~bruninga/APRS-docs/digis.txt
ERRATA: http://www.ew.usna.edu/~bruninga/aprs/errata.html
FIXING 39: http://www.ew.usna.edu/~bruninga/aprs/fix14439.html
APRS DISENTIGRATION: http://www.ew.usna.edu/~bruninga/aprs/hacks.txt
de WB4APR@amsat.org, Bob
----------------------------------------------------------------------
Subject: Re: APRS software for SAR
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Tue, 16 Sep 2003 16:59:13 -0700 (PDT)
X-Message-Number: 57
On Tue, 16 Sep 2003, Spider wrote:
>It seems nobody ever has the exact map that would be considered right for
>the job. Having a complete USGS DGR Topos and photo map sets of your County
>on CD in 7.5 minute (where available) or 15 minute, would be a great thing!
>With a good printer and copy machine in the mobile comm vehicle you can
>supply the teams with a proper map for their search area.
>You end up handing out a lot of maps on big searches. Trying to print the
>search area ahead of time never seems to work. They need to be printed at
>the mobile CP for the specific search area.
We carry a set of printed maps plus have street and topo mapping
programs in the ICP. Usually we print a custom map to hand to each
team leader as they head out into the field. les to fit page" you no longer
have a truly scaled page. Stretched and compressed maps are the bane of
a cartographer's existence.
While it seems like a good idea, it's not always practical. If you can
retain X & Y scale and ratios, you're probably OK, but I'd not plan to
have a 1:250k map *BE* 1:250k when scaled to 11x17"
Gerry
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
