| |
ZL3AI > APRDIG 11.09.03 11:05l 288 Lines 9395 Bytes #999 (0) @ WW
BID : 1891-ZL3AI
Read: GUEST
Subj: TAPR Digest, Sep 08, 6/7
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0AR<VK6HGR<ZL2BAU<ZL3VML
Sent: 030910/1405Z @:ZL3VML.#80.NZL.OC #:8092 [Chch-NZ] FBB7.00i $:1891-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Homeport
From: Neil Johnson <njohnsn@njohnsn.com>
Date: Mon, 8 Sep 2003 19:27:37 -0500
X-Message-Number: 37
The HLR / VLR concept works for me.
Users could register their Tracker call sign and Home IGATE on a web server
"like" findu.
Then the server could monitor the APRS-IS Stream and then forward any packets
it sees with the Tracker call sign to the Home IGATE.
Although I could see a bunch of LIDS registering Dayton has their Home IGATE
to make sure all the Hamvention Attendees know where they are....
--
Neil Johnson
http://www.njohnsn.com
PGP key available on request.
----------------------------------------------------------------------
Subject: Re: Homeport
From: Randy Allen <ka0azs@earthlink.net>
Date: Mon, 08 Sep 2003 20:36:47 -0400
X-Message-Number: 38
I just pulled those numbers for my home station from FIND-U as an
example,
Still, EM79VQ is easier for me to remember than any lat long format
(case in point, I could type the grid from the top of my head, had to
look up lat long). Of course either would be much easier to remember
than UTMs! ;-)
73
--
Randy Allen, KAĜAZS
EC, Montgomery CO Ohio
OH Dist. 3 ARES Web Page:
http://www.qsl.net/ohd3ares/
----------------------------------------------------------------------
Subject: RE: Homeport
From: "Richard Amirault" <ramirault@erols.com>
Date: Mon, 8 Sep 2003 20:35:21 -0400
X-Message-Number: 39
----- Original Message -----
From: "Bob Bruninga" <bruninga@usna.edu>
Subject: [aprssig] RE: Homeport
(snip)
>Weighing all the above, I lean towards explicitly declaring the target....
>but no reason why we shouldn't have the LAT/LONG as an option. but lazy
>people might use it because they are too lazy to look up their local IGate
>and then we have in fact, created a NEW QRM source...
(snip)
How *would* you "look up their local IGate"? Is there more than one way?
Richard Amirault N1JDU Boston,
MA, USA
www.erols.com/ramirault "Go Fly A Kite"
----------------------------------------------------------------------
Subject: Re: Homeport
From: Steve Jones <s.jones@rogers.com>
Date: Mon, 08 Sep 2003 20:36:22 -0400
X-Message-Number: 40
on 9/8/03 8:08 PM, Randy Allen at ka0azs@earthlink.net wrote:
>Would it be significantly shorter in terms of packet length to define
>Homeport by Grid Square rather that Lat/Long, and also be more universal
>than Airport and FIPS codes?
Also keep in mind APRS is used worldwide. FIPS means nothing to anybody
outside the US.
Airport codes and CLLI's are used worldwide and could be good choices.
Whatever is decided, please make sure it's universal and not just US.
--
Steve <s.jones@rogers.com>
----------------------------------------------------------------------
Subject: Re: Homeport
From: "John Langtry, VE3NEC" <ve3nec@sympatico.ca>
Date: Mon, 08 Sep 2003 20:59:44 -0400
X-Message-Number: 41
Hi Bob & Gang,
I'll "second" Jim's, WA6OFT, idea of using the CLLI (common language); it's
been used in the telephone industry for more years that I have. (I'm now in
my 31st year at Bell Canada.)
Eight bytes locates any telephone exchange in N.A. - Bob, the last two
bytes can be tailored for our own use.
In my own case, as an example, BMTNON## is univerally known as an exchange
in Brampton, Ontario, Canada. The ## are just that, numerics; but there is
no reason that we can't use uppper and lower case alphabetics, for Amateur
use.
Just a thought ... I'll crawl back under my rock now.
vy 73 all de John VE3NEC
905-873-8715
----------------------------------------------------------------------
Subject: Re: Homeport
From: Randy Allen <ka0azs@earthlink.net>
Date: Mon, 08 Sep 2003 21:14:47 -0400
X-Message-Number: 42
Steve Jones wrote:
>Airport codes and CLLI's are used worldwide and could be good choices.
By universal, I meant that everyone has a grid square location, some
people may not have and I-gate near an airport for a Homeport (or may
have multiple airports as was pointed out for DFW area)
>Whatever is decided, please make sure it's universal and not just US.
RR
--
Randy Allen, KAĜAZS
EC, Montgomery CO Ohio
OH Dist. 3 ARES Web Page:
http://www.qsl.net/ohd3ares/
----------------------------------------------------------------------
Subject: Re: Homeport
From: "Spider" <spider@rivcom.net>
Date: Mon, 8 Sep 2003 18:28:38 -0700
X-Message-Number: 43
----- Original Message -----
From: "Randy Allen" <ka0azs@earthlink.net>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Cc: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Monday, September 08, 2003 5:36 PM
Subject: [aprssig] Re: Homeport
I just pulled those numbers for my home station from FIND-U as an
example,
Still, EM79VQ
Would that be the only designator you'd cover? I am guessing I'd be needing
a dozen or more of this type of designator to cover the area my igate covers
even without any hops. I would think the idea is to NOT pinpoint a station,
but rather the area of coverage an igate gives.
Jim
----------------------------------------------------------------------
Subject: Re: Homeport
From: Randy Allen <ka0azs@earthlink.net>
Date: Mon, 08 Sep 2003 21:40:57 -0400
X-Message-Number: 44
If you need to cover a wider area, just reduce the number of digits
used,
for example,
EM covers the area between 100 and 80 degrees West, and 30 and 40
degrees north.
EM79 covers Dayton, Cincinnati and Indianapolis (based on the map in my
copy or the ARRL Operating manual, 5th edition).
I'm hardly an expert on Maidenhead Squares, but it looks like it has
some possible utility in this situation.
Spider wrote:
>
>
>Still, EM79VQ
>
>Would that be the only designator you'd cover? I am guessing I'd be
>needing a dozen or more of this type of designator to cover the area my
>igate coverseven without any hops. I would think the idea is to NOT
>pinpoint a station, but rather the area of coverage an igate gives.
--
Randy Allen, KAĜAZS
EC, Montgomery CO Ohio
OH Dist. 3 ARES Web Page:
http://www.qsl.net/ohd3ares/
----------------------------------------------------------------------
Subject: TinyTrak3-TripmateUSB interface
From: "Charles Rocco Pistilli" <n3fkr@arrl.net>
Date: Mon, 8 Sep 2003 20:41:6
X-Message-Number: 45
I have been unable to interface the new Delorme Tripmate USB, using the
serial adapter cable, to the TinyTrak3. I was hoping this setup would be
plug-n-play. Surprise! Any advice would be appreciated. Thanks.
Rocky, N3FKR
----------------------------------------------------------------------
Subject: Dell Axim RandMcnally
From: Floyd Rodgers <kc5qbc@swbell.net>
Date: Mon, 08 Sep 2003 21:37:03 -0500
X-Message-Number: 46
Anyone done this hookup yet. I have the serial cable, but have no clue for
the required port settings other than 4800n81.
Floyd Rodgers KC5QBC
Multi ended candle burning artist in training
----------------------------------------------------------------------
Subject: Re: Homeport
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Mon, 8 Sep 2003 21:41:43 -0500
X-Message-Number: 47
Many good suggestions. There is no reason why an IGate couldn't
translate a grid square to a lat/lon so either format could be used.
Most client software already has this conversion built in.
Using airport codes, zip codes, and CLLI codes in paths all require that
the IGate operators and the end users both know the code(s) to use to
get to an area (my IGate covers far more than the CLLI for Melissa, TX
would indicate)(this is also one of the problems the Rose Net ran into).
Using path indicators could have a filter command added to javAPRSSrvr
by Roger, but, as pointed out before, it is not implemented at this time
and Roger does have a real job ;-)
Keep in mind, too, that what might be used here with APRS-IS could
easily be extended to a backboned network.
IMO, to get the most use (one of the key considerations Dale and I had
when we created and implemented the q-construct), the "routing"
method(s) must be easy to use by all, world-wide, must be compatible
with existing software and networks, and require few if any changes by
the majority of users. Such is the proposal for a generalized home port
message, a generalized non-home port message, and the
subscription-in-a-posit method. And all would only require the IGate
software to be modified to support them. None would substantially add
to QRM and if people started using them instead of RELAY,WIDE7-7, QRM
would be reduced substantially.
We held an APRS seminar/workshop last Saturday here in North Texas.
Over half of the attendees (120+) were not active on APRS. I can say
with great certainty that they left those individual seminars and
workshops with a greater understanding of APRS and how it works. I can
also say with great certainty that if we asked them to "learn" the local
network topology or learn CLLI codes, etc., they would leave APRS where
it was that morning - inactive. Instead, they walked away with a better
understanding of what it means to be a courteous operator on our shared
frequency and still get all the benefits that APRS offers.
As what was said many, many years ago by someone far smarter than me -
KISS.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
