<div>Let's say that I use the B0 format to specify 10 discrete positions. Let's say 100 people show up to my event. Does the software dither the positions slightly, or does everyone at a particular location "stack up" on top of one another?</div>
<div> </div>
<div>Wes<br><br></div>
<div class="gmail_quote">On Mon, Jun 1, 2009 at 06:02, Bob Bruninga <span dir="ltr"><<a href="mailto:bruninga@usna.edu">bruninga@usna.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">>Bob, any thoughts on using USNG with APRSTT?<br><br></div>The beauty of APRStt is that it is a LOCAL system, SIMPLEX rnage only from the sender. Thus, each APRStt is set up to match the needs of its users (usually one club) and this is independent of how APRStt might be used somewhere else.<br>
<br>And APRStt can use any grid system, lat/long, SAR GRIDS, Mile marks, and even flea-market spaces at Dayton. And any one APRStt can support many of these at the same time if needed.<br><br>At our first system in Dayton, we defined the position format to be Bxy* Just one digit in X and one digit in Y. But the spec has always said there would be xxyy, xxxyyy, xxxxyyyy versions for greater precision, or greater coverage area.<br>
<br>So after dayton, we formalized this as follows. There are 10 possible Position formats that can be implemented in any instance. In most cases, only the one that is applicable at any parcicular APRStt will be used. But that does not prevent the engine from accepting more than one if needed. Here are their definitions:<br>
<br>B0x* One of 10 special positions<br>B1xy* 1 digit XY ( 10 mi in 60 mi area) (default)<br> (or 1 mi in 10 mi area)<br> (or.1 mi in 1 mi area)<br>B2xxyy* 2 digit XY ( 1 mi in 60 mi area) (default)<br>
(or .1 mi in 10 mi area)<br> (or 60 ft in 1 mi area)<br>B3xxxyyy* 3 digit XY ( .1 mi in 60 mi area) (default)<br> (or 60 ft in 10 mi area)<br>B4xxxxyyyy* 4 digit XY ( 60 ft in 60 mi area) (default)<br>
<br>B5zzzmm* at bearing zzz range mm miles<br>B6EEENNN* SAR UTM Grid - Easting and Northing<br>B7RRRMMM* Road RRR, Milemark MMM<br>B8......* Table interpolation<br>B9... * TBD<br><br>What we used at Dayton is now B1xy*. This added digit also is kind of a redundant check to make sure the proper number of digits has been received for a given posit.<br>
<br>Back to the original question, So what each XY grid represents and how much precision is independent of whether it is UTM or LAT/LONG or USNS. That is established at se-up time at that location.<br><br>Again, dont panic at all the options. Usually, only one format will be used in a given applcation depending on the area covered and the degree of precision desired. At Dayton, we only used B1xy*. At the 2010 Scout Jamboree, we will use B2xxyy* because the published map that will be in the hands of every scouter will have an XX YY grid already on it.<br>
<br><br>Hope that helps<br><br>Bob, Wb4APR<br>
<div>
<div></div>
<div class="h5"><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br><a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
</div></div></blockquote></div><br><br clear="all">
<div></div><br>-- <br>Wes<br>---<br>Where there's silence, there is no Hope.<br>