| |
ZL3AI > APRDIG 09.02.04 13:36l 264 Lines 9169 Bytes #999 (0) @ WW
BID : 2799-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 06, 1/9
Path: DB0FHN<DB0THA<DB0ERF<DB0FBB<DB0GOS<DB0EEO<DB0RES<ON0AR<ZL2BAU<ZL2BAU<
ZL3VML
Sent: 040209/1054Z @:ZL3VML.#80.NZL.OC #:18731 [Chch-NZ] FBB7.00i $:2799-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Friday, February 06, 2004.
1. MapPoint, etc and Xastir or UI-View
2. Re: some maps numbers
3. converting other formats to shapefiles
4. Re: IGate WEB page.
5. Re: converting other formats to shapefiles
6. IGate filtering by POSIT
7. Re: IGate WEB page.
8. HF APRS
9. Re: maps
10. RE: HF APRS
11. Re: HF APRS
12. Re: converting other formats to shapefiles
13. RE: HF APRS
14. Mapping plans
15. Re: MapPoint, etc and Xastir or UI-View
16. Re: MapPoint, etc and Xastir or UI-View
17. Re: MapPoint, etc and Xastir or UI-View
18. Findu and the find-us query
19. Re: MapPoint, etc and Xastir or UI-View
20. Re: Findu and the find-us query
21. Re: MapPoint, etc and Xastir
22. Re: HF APRS
23. Re: Findu and the find-us query
24. Re: MapPoint, etc and Xastir or UI-View
25. Re: Findu and the find-us query
26. Re: Findu and the find-us query
27. Re: Findu and the find-us query
28. Re: Findu and the find-us query
29. Re: IGate WEB page.
30. Re: Mapping plans
31. Re: IGate WEB page.
32. Re: Mapping plans
33. Re: IGate WEB page.
34. Re: HF APRS
35. Re: Mapping plans
36. Re: Mapping plans
37. Re: Mapping plans
38. Re: HF APRS
39. Re: HF APRS
40. Re: HF APRS
41. Re: HF APRS
42. Re: Mapping plans
43. Re: Mapping plans
44. Re: Mapping plans
45. Re: HF APRS
46. Re: Mapping plans
47. Re: Mapping plans
48. No more RELAY,WIDE defaults for fixed stns
49. Re: Wi-Sys All-in-One APRS system (except radio)
50. Re: No more RELAY,WIDE defaults for fixed stns
51. Re: Mapping plans
52. Re: Mapping plans
53. Re: Mapping plans
54. Fw: Mapping plans
55. Re: Fw: Mapping plans
56. Re: No more RELAY,WIDE defaults for fixed stns
57. Re: IGate WEB page.
58. Re: IGate WEB Page
----------------------------------------------------------------------
Subject: MapPoint, etc and Xastir or UI-View
From: "Darryl Smith" <Darryl@radio-active.net.au>
Date: Fri, 6 Feb 2004 16:22:37 +1100
X-Message-Number: 1
OziAPRS now allows you to send data directly to MapPoint... It also allows
decoding RINO data and many other features...
More information is available on
http://www.radio-active.net.au/web/gpsaprs/oziaprs.html, although I don't
think I have added much data about MapPoint yet..
Darryl
---------
Darryl Smith, VK2TDS POBox 169 Ingleburn NSW 2565 Australia
Mobile Number 0412 929 634 [+61 4 12 929 634 International]
www.radio-active.net.au - www.radio-active.net.au\web\tracking
----------------------------------------------------------------------
Subject: Re: some maps numbers
From: "Dick Stanich" <dick@kb7zva.com>
Date: Fri, 6 Feb 2004 0:58:29
X-Message-Number: 2
Jim,
I finally found time to go over to aprsworld.net, and I'm impressed with
what you have done. Excellent work. You certainly will have my support.
Dick, kb7zva
APRSWest
----------------------------------------------------------------------
Subject: converting other formats to shapefiles
From: James Jefferson <jj@aprsworld.net>
Date: Fri, 6 Feb 2004 01:58:06 -0600
X-Message-Number: 3
Hey list,
David Norris wrote me this a bit ago:
>Can dosaprs, winaprs, pocketaprs, etc maps be converted to shapefiles?
>Feature-wise, I mean. Maybe those data could be converted to shapefiles
>and incorporated into the APRSWorld mapserver for countries where data
>is sparse. (Assuming you haven't already done this.)
Anybody up for this? I wrote a aprsDOS to shapefile converter a few years ago,
but it got lost in a disk crash.
By using shapelib (or there is a shapefile writing library for Java, Gregg :-)
do these converters isn't hard. Perhaps the input files could be parsed using
some of the code from xastir. I see nice files in the source tree called
map_dos.c and map_pdb.c that might work with some adapting.
I'm still not convinced that all of aprsDOS maps are high enough quality to
use, but perhaps there is something. A map that was hand digitized might look
okay on its own, but once it gets registered to a bunch of other layers might
not look so great.
-Jim
(last message for the night)
----------------------------------------------------------------------
Subject: Re: IGate WEB page.
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Fri, 06 Feb 2004 08:29:52 -0500
X-Message-Number: 4
>>>"Dick Stanich" <dick@kb7zva.com> 2/5/04 7:28:57 PM >>>
Tell us Bob/Steve, what should be considered local for an Igate?
REPLY:
My answer would be the ALOHA CIRCLE. And since we MUST get every
single APRS operator to understand the concept, I think it might be
useful for FINDU to have an "ALOHA" page that with one click tells each
and every APRS user what his own PERSONAL local network is.
Yes, we have that now, in a secondary way, by going to the NEAREST
stations. But I'd rather have a page named ALOHA CIRCLE that is more
focued that Google can find..:
1) It has a paragraph explaining the ALOHA Circle
2) It prints the words: "Your LOCAL APRS range should be less than X
3) It filters the CW stations out of the equation
4) It reminds the station: "To set your APRS PATH do the following:"
a) Look through this list and see the number of digipeaters.
b) If you can hit them all direct, then your path should be VIA
WIDE
c) If it takes 2 hops to hit them all, then your path is VIA
WIDE,WIDE
5) If your path is any longer than this, you are only adding useless
QRM to your surrounding neighbors...
de WB4APR, Bob
----------------------------------------------------------------------
Subject: Re: converting other formats to shapefiles
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Fri, 06 Feb 2004 08:41:41 -0500
X-Message-Number: 5
>>>James Jefferson <jj@aprsworld.net> 2/6/04 2:58:06 AM >>>
I'm still not convinced that all of aprsDOS maps are high enough
quality to use, but perhaps there is something. A map that was hand
digitized might look okay on its own, but...
REPLY: About the only hand rendered APRSdos maps are the WORLD and USA
maps and a few early ones back 12 years ago that have all been replaced.
All the rest were derived from USGS DLG data.
But admittedly, that USGS data was still crude for use below about the
8 mile Range Scale.
----------------------------------------------------------------------
Subject: IGate filtering by POSIT
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Fri, 06 Feb 2004 09:43:15 -0500
X-Message-Number: 6
>>>"AE5PL Lists" <HamLists@ametx.com> 2/5/04 11:17:20 AM >>>
Depends on the IGate software.
Just to clarify from previous threads, an IGate shouldn't add ALL
stations heard on RF to its "local" list; just the stations whose
packets meet the IGate's "local" criteria. This last part is
implemented as distance in some software (requiring a posit)....
REPLY:
Ah, distance is a wrong criteria. Using distance denies any messages to
someone who may be sending out a bad posit or none at all. This violates
the fundamental principles of APRS. That is, that NO apriori information
is required to communicate. Please, lets identify that software and get it
fixed.
A perfect example is a traveler with only a D7 HT. His HT has his last
known posit. More often than not, it is the wrong position . Thus those
IGates which demand position-only information are failing this traveler at
a time when he is traveling and when he NEEDS messaging MOST.
AE5PL says:
If a limit is not put in place, then there is a lot of needless cluttering
of local RF due to IGates attempting to gate for stations well out of range
of the IGate's path setting.
REPLY:
Agreed. But we must do it some other way than dependence on a -valid-
position report. Now that everyone should understand the ALOHA circle we
need to make the IGate software smart enough to recognize neighboring
IGates and set their "local" hop counter appropriately. Not easy, but I
cant think of any other way...?
In latest versions of APRSdos, it automatically recognizes all IGates and
draws their PHG circle on the map at all times. Thus it is very easy to
see the IGates and their coverages all the time... And sure enough, the
two that serve our area are simplex to each other yet 2 ore more hops from
most everyone else... go figure...
----------------------------------------------------------------------
Subject: Re: IGate WEB page.
From: Steve Dimse <k4hg@tapr.org>
Date: Fri, 6 Feb 2004 10:14:48 -0500
X-Message-Number: 7
On 2/5/04 at 7:28 PM Dick Stanich <dick@kb7zva.com> sent:
>Tell us Bob/Steve, what should be considered local for an Igate?
The important thing is it should be based on who is in digipeater range of
the IGate, which can vary wildly in terms of distance. It must therefore be
based on digipeater hops.
The original spec was two hops, one of the original programs allowed a
choice of one or two. So assuming it is two:
K4HG-8>APRS:WIDE,WIDE*,WIDE:asasdasdasdassd
is in range, while
K4HG-8>APRS:WIDE,WIDE,WIDE*:asasdasdasdassd
Is not in range.
It should be the same as the number of hops on the output side of the
IGate, so if the number is two the UNPROTO of the IGATE should be WIDE,WIDE
(or WIDE2-2).
Steve K4HG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
