| |
ZL3AI > APRDIG 14.05.04 22:07l 246 Lines 10380 Bytes #999 (0) @ WW
BID : 3241-ZL3AI
Read: GUEST
Subj: TAPR Digest, Apr 26, 2/3
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<DK0WUE<HA3PG<7M3TJZ<ZL2BAU<ZL2BAU<
ZL3VML
Sent: 040514/1923Z @:ZL3VML.#80.NZL.OC #:24021 [Chch-NZ] FBB7.00i $:3241-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Compromise proposal
From: "Jordi Costa" <bvjordi@bitsnvolts.com>
Date: Mon, 26 Apr 2004 15:44:19 +0200
X-Message-Number: 5
Gerry,
Now I have the SporTrak configured as dual coordinate display (Primary &
Secondary). I have it displaying both UTM in local datum (EUR50), for hiking
activities, and Lat/Lon in WGS84 as in NMEA output and sent by tracker.
I have been always transmitting WGS84 mainly because:
- Most hams in my area use them (GPSs default).
- We used Mapblast/Vicinity for street level tracking.
Sometimes, when I desire precission positioning out of cities I used OziAprs
in order to do Datum & Projection transform to topo local maps (UTM). Do not
forget that projection could be as important as datum and some programs, as
UIView; does not manage them.
Jordi
----------------------------------------------------------------------
Subject: Re: APRS+SA Programming
From: "Tim Cunningham" <tim_cunningham@mindspring.com>
Date: Mon, 26 Apr 2004 09:58:08 -0500
X-Message-Number: 6
John,
The maps are controlled by the map options files. First, you have to
identify what map you are viewing on your screen and create a MOP file for
that specific view if you want to control the magnitude of the view. The
problem is easy to solve, but first you have to be a little more specific
about what map display you are viewing.
I posted the following comments on this SIG on 01-AUG-2001 concerning the
Map Options or MOP files and this should get you started in solving your
problem:
There is a way to display Power-Height-Gain circles, but this is not the
same as the weather circles. They are completely different animals. Many
parameters can be changed to show how the map is displayed including the
zoom level, track lines for a moving station, and the detail level of the
map. Many of the MAP settings that you would select in SA can be
controlled from the MOP files.
What are MOP files and why did I mention it. There were several other
posts that contained questions about how the SA settings got changed or why
my map looks different. So I will try to briefly explain this very nice
feature quickly. I learned all about the MOP files when setting up APRS+SA
for the Rocket City Marathon in Huntsville and we have several maps and
zoom levels configured so that we would get a birds eye view of the whole
track, portions of the track, and zoom to appropriate levels automatically.
All we had to do is sit back and watch the show.
I am not going to go into full detail, but you can play with it yourself.
Click on Commands -> Map Options
This will give you a window with four tabs:
1. Symbols & Text
Allows you to control Symbol, Text, and Track Lines size and color
2. Center & Mag
Allows you to control the ZOOM level control of the map
3. Map Features
Allows you to control map features displayed on SA
4. Circles
Allows you to control the thickness of the line on a circle.
You can also specify a fill color if desired.
This has nothing to do with NWS circles (red or yellow)
5. APRS
Allows you to control APRS functions on how some things are displayed.
You can select including range circles, track lines, track lines
included in the zoom display, and a few others here.
These settings determine what options are used for specific maps. I believe
the default file will be MapOptions.mop so be careful how and what you save.
What do I mean by specific maps. If you display your SA map on the screen
and look in the top left corner of the window on the title bar, you will
see something like MapOption, Map9, Map5, etc followed by some other text
and the SA file extension like .sa8 Mine shows .sa8 because I am using
Street Atlas version 8 and I have APRS+ writing SA8 files on the updates.
The MOP files are located in the DATA directory under the APRS+ main
software directory on your hard drive.
When I look for MOP files in this directory I see the following:
Map5.mop
Map6.mop
Map7.mop
Map8.mop
Map9.mop
Digipeaters.mop
TrackMap.mop
MapOptions.mop
You will not have all these files. Do not worry, because you are going to
create them if you want.
If you go to the "Maps" tab in APRS+ and look at all the maps you can
display, then you can realize how many MOP files you could have to control
how each of these maps will look to suit your own desires. Try clicking on
All Stations which uses Map9 as a default. now look at the top left corner
of the SA window and see what the title bar shows before the "+" sign in
the text. Mine shows Map9+B.sa8. Do not worry about all of this except
the Map9 at this point. If you create a Map9.mop file, you will find that
you can control how it is displayed. The same is true for the Digipeaters
button on that screen. Yes, if you have a Digipeaters.mop file you can
control how it looks. In mine I have the range circles activated so I can
see where all the digpeaters are located and also see there range circles
to see where we need new digipeaters or where a digipeater may be off the
air.
Does all of this sound good. I hope I can explain it so you can get to the
meaning of it.
How do I create a MOP file?
Click on Commands -> Map Options
Change all the settings you would like to have and then save the file as the
proper mop name. For instance, if I want to create a Map9.mop, I will click
on Commands -> Map Options. Then, I will make my changes and click on
File -> Save As, and then the name of the map I want to affect. It is that
simple. A word of caution. You should turn off all automatic map updating
functions when doing this. If a map gets updated in the process of you
making changed, you will quickly find that your settings are most likely
being changed by some unknown force. This includes turning off auto map
update under the Track tab in APRS+. Also make sure the enable box is
not checked under the Maps tab. This will help make things go smoother
in making a MOP file and saving it before the auto functions in the software
does its thing before you do.
If you do not know what map is created on the Map tab for each button, then
click on the button and look at the title of the SA window. You will find
the name of the map preceding the "+" symbol in that text. All you need to do
is create a MOP file with that name, save it, and the next time you click on
that button the screen will look just like you set it.
It takes a little while to get use to what all those MOP settings can do for
you so you will need to do a little experimenting.
I hope I have shed a little light on this very useful feature. I apologize
for any typos of crazy wording, but my time was running light tonight.
73's,
Tim - N8DEU
Huntsville, Alabama
----- Original Message -----
From: "John Troutman" <w4dcr@ctc.net>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Saturday, April 24, 2004 8:17 AM
Subject: [aprssig] APRS+SA Programming
>Sir: About 24 hours ago I asked some assistance in programming the APRS+SA
>program. The problem always goes back to the World map each time it
>refreshes and I have to zoom in on my position each time the map changes.
>From Map 1A to Map 2A etc. Since I have had no answer to the problem I will
>seek the answer else where and I will unsubscribe to the website. Tnx. John
>W4DCR
----------------------------------------------------------------------
Subject: Re: Objects and D7 are easy.
From: "Curt, WE7U" <archer@eskimo.com>
Date: Mon, 26 Apr 2004 09:13:33 -0700 (PDT)
X-Message-Number: 7
On Fri, 23 Apr 2004, Brian Riley (maillist) wrote:
>OK, I see this. But isn't this more accurately a 'pseudo-object?' When an
>OBJECT is created on an APRS client program, doesn't it go out formatted in
>some way that indicates its an OBJECT and who really is the source of the
>object?
If you go by how things are labeled in the spec, what Bob described is
really another station posit, but it has the effect of looking/acting just
like a real "Object" as defined in the spec.
The major differences are that other people wouldn't be able to manipulate
the object like they can objects/items, and that you wouldn't necessarily
know who sent the packet out.
This report will time out on people's screens after some short time period.
30 mins for UI-View. Variable based on user settings for Xastir.
Still, a very useful thing to do when stuck in traffic, as Bob said.
--
Curt, WE7U archer at eskimo dot com
Arlington, WA, USA http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: Timeslotting
From: "Scott Miller" <scott@opentrac.org>
Date: Mon, 26 Apr 2004 09:57:23 -0700
X-Message-Number: 8
Timeslotting support is one of those things that's been on my to-do list for
the OpenTracker for some time, and I'm finally getting a chance to start
working on it. I know that the TT3 at least supports timeslotting - not
sure what other devices might do it as well. I want my implementation to be
as compatible as possible with what's out there already, but this means
being in agreement with other devices as to exactly what time it is.
Now, on the surface this doesn't seem like a big problem, since the GPS
receiver provides a very accurate time reference. Trouble is, fractional
seconds are not indicated in the NMEA sentences, and I can't find any
documentation to indicate if the time is valid at the start of the sentence,
the end of the sentence, the start of the paragraph, or some other point.
If it's referenced to the sentence, it shouldn't be a big deal since it only
takes maybe 1/6 second to send it. But if it's referenced to the start of
the paragraph, it might be a second or two.
I've used GPS receivers for precision timing before, but they're specialized
units with 1PPS and IRIG outputs. And really, being 'right' isn't as
important in this case as just being in agreement with other trackers. So
if anyone knows exactly how the timeslotting time is derived in existing
implementations, please let me know.
Thanks...
Scott
N1VG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
