<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1424066115624_15331" dir="ltr">+1 to K4HG Steve's idea<br></div><div id="yui_3_16_0_1_1424066115624_15332"><br><span></span></div><div id="yui_3_16_0_1_1424066115624_15334" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">1) The 4-digit bob's idea is based on grid square (that gives accuracy 1deg LAT 2deg LON) and does NOT cover all the world - if the interest area is not covered user must type 6-digits using APRStt style (2 digits per letter + 2 digits for the number 2*2+2) and AGAIN has accuracy of </span><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">1deg LAT 2deg LON). <br></span></div><div id="yui_3_16_0_1_1424066115624_17600" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">2) Mine 5-digit idea (that i sent to the list 2days ago) is based again on grid square (a</span><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">cc. </span><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">1d LAT 2d LON) BUT covers all the world.</span></div><div id="yui_3_16_0_1_1424066115624_22973" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">3) The 6-digit Steve's idea has accuracy of 1 degree for LAT / LON and covers all the world.</span></div><div id="yui_3_16_0_1_1424066115624_25384" dir="ltr"><br><span style="" class="" id="yui_3_16_0_1_1424066115624_15333"></span></div><div id="yui_3_16_0_1_1424066115624_25385" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">Why to produce so much complexity in order to save 2 digits and again have the chance that someone may need to type in the 6-digit APRStt style (so not standard format here)... instead of just use the 6-digit </span><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">K4HG format </span><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">that gives higher accuracy and doesnt need any conversion table??? <br></span></div><div id="yui_3_16_0_1_1424066115624_31637" dir="ltr"><br><span style="" class="" id="yui_3_16_0_1_1424066115624_15333"></span></div><div id="yui_3_16_0_1_1424066115624_31636" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">The user instead of getting his pos from gps, convert it to Grid Sq and look at a conversion table to find the 4 digit number......he just gets his pos from gps and converts it to a 6-digit number without calculations and coversion tables!!!</span></div><div id="yui_3_16_0_1_1424066115624_34417" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333"><br></span></div><div id="yui_3_16_0_1_1424066115624_36155" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">IMHO the 2 digits save... is more pain than gain!<br></span></div><div style="" class="" id="yui_3_16_0_1_1424066115624_17600" dir="ltr"><br><span style="" class="" id="yui_3_16_0_1_1424066115624_15333"></span></div><div id="yui_3_16_0_1_1424066115624_33718" style="" class="" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">73</span></div><div id="yui_3_16_0_1_1424066115624_36154" style="" class="" dir="ltr"><br><span style="" class="" id="yui_3_16_0_1_1424066115624_15333"></span></div><div id="yui_3_16_0_1_1424066115624_34418" style="" class="" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">sv8gxc</span></div><div id="yui_3_16_0_1_1424066115624_35288" style="" class="" dir="ltr"><br><span style="" class="" id="yui_3_16_0_1_1424066115624_15333"></span></div><div id="yui_3_16_0_1_1424066115624_35287" style="" class="" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1424066115624_15333">P.S. </span>BTW I know that it doesnt matter what I say ... since it has already been decided what will be used on QIKcom-2.</div><br> <div id="yui_3_16_0_1_1424066115624_15512" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_1_1424066115624_15511" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_1_1424066115624_15510" dir="ltr"> <hr id="yui_3_16_0_1_1424066115624_30251" size="1"> <font id="yui_3_16_0_1_1424066115624_15877" face="Arial" size="2"> <b><span style="font-weight:bold;">Απο:</span></b> Steve Dimse <steve@dimse.com><br> <b><span style="font-weight: bold;">Προς:</span></b> TAPR APRS Mailing List <aprssig@tapr.org> <br> <b><span style="font-weight: bold;">Στάλθηκε:</span></b> 3:11 π.μ. Δευτέρα, 16 Φεβρουαρίου 2015<br> <b><span style="font-weight: bold;">Θέμα:</span></b> Re: [aprssig] APRStt 4 digit grid squares...<br> </font> </div> <div id="yui_3_16_0_1_1424066115624_15690" class="y_msg_container"><br>If it were me, I'd say one digit for hemispheres (e.g. alphabetical 1-NE, 2-NW, 3-SE, 4-SW), 2 digits for lat and 3 for lon. Six digits instead of four, but it is unambiguous, easy to remember, easy to parse, and covers the entire world - in other words, completely un-Bob-like. This grid square way is like repeating every mistake in the APRS protocol at once, so of course Bob will use it.<br clear="none"><br clear="none">And even if Bob picked this idea, then he would realize that I only use 1 bit of the MSB for longitude, and 2 bits for hemisphere, so there are 5 bits that could be kludged, and it would get messy again...<br clear="none"><br clear="none">Steve K4HG<br clear="none"><br clear="none">On Feb 15, 2015, at 6:55 PM, Jeff Dugas (Mobile) <<a shape="rect" ymailto="mailto:N5TEV@CompuServe.com" href="mailto:N5TEV@CompuServe.com">N5TEV@CompuServe.com</a>> wrote:<br clear="none"><br clear="none">> Thanks Bob, got it.<br clear="none">> <br clear="none">> So, would I assume correctly that this system would preclude someone from operating APRS-TT Maritime Mobile from an area not covered by one of the designated areas?<br clear="none">> <br clear="none">> No quibble - just trying to ensure I understand how it all works.<br clear="none">> <br clear="none">> Jeff<br clear="none">> N5TEV<br clear="none">> <br clear="none">> -----Original Message-----<br clear="none">> <br clear="none">> Robert Bruninga <<a shape="rect" ymailto="mailto:bruninga@usna.edu" href="mailto:bruninga@usna.edu">bruninga@usna.edu</a>> wrote:<br clear="none">> <br clear="none">> Those get their first digit from the 3 orange squares off the East coast of the USA.<br clear="none">> <br clear="none">> On Sun, Feb 15, 2015 at 3:11 PM, Jeff Dugas (Mobile) <<a shape="rect" ymailto="mailto:N5TEV@compuserve.com" href="mailto:N5TEV@compuserve.com">N5TEV@compuserve.com</a>> wrote:<br clear="none">> Bob,<br clear="none">> <br clear="none">> On the map, how does it work for the 3-square red box (1-2-3) in the area over Indonesia?<br clear="none">> <br clear="none">> Jeff<br clear="none">> N5TEV<br clear="none">> <br clear="none">> -----Original Message-----<br clear="none">> <br clear="none">> Robert Bruninga <<a shape="rect" ymailto="mailto:bruninga@usna.edu" href="mailto:bruninga@usna.edu">bruninga@usna.edu</a>> wrote:<br clear="none">> <br clear="none">> Thanks everyone, for all the GRID ideas. But here is what we think we have decided to go with for the worldwide 4 digit DTMF Grid map we will use on QIKcom-2.<br clear="none">> <br clear="none">> <br clear="none">> <a shape="rect" href="http://aprs.org/qikcom-2.html" target="_blank">http://aprs.org/qikcom-2.html</a><br clear="none">> <br clear="none">> <br clear="none">> It uses a table from 00 to 99 to map to the first two ALPHA characters.<br clear="none">> <br clear="none">> <br clear="none">> Bob, WB4aPR<br clear="none">> <br clear="none">> <br clear="none">> From: <a shape="rect" ymailto="mailto:aprssig-bounces@tapr.org" href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a> [mailto:<a shape="rect" ymailto="mailto:aprssig-bounces@tapr.org" href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>] On Behalf Of George Vastianos<br clear="none">> Sent: Saturday, February 14, 2015 5:13 PM<br clear="none">> To: TAPR APRS Mailing List<br clear="none">> Subject: [aprssig] Σχετ: proposal for APRStt grid loc. Σχετ: 60 Grid Square............<br clear="none">> <br clear="none">> <br clear="none">> Oh SORRY!<br clear="none">> <br clear="none">> <br clear="none">> Thanks for the correction!<br clear="none">> <br clear="none">> <br clear="none">> I had in my mind that you have to look for the first letter on the black row below and then look for the second letter on the black column on left... so i wrote "Row 1st, Col 2nd" BUT THIS IS WRONG<br clear="none">> <br clear="none">> <br clear="none">> The correct is "Col 1st, Row 2nd" that means "Find the Column of 1st letter and then the Row of 2nd letter"<br clear="none">> <br clear="none">> <br clear="none">> e.g. KM = 502, NQ=536, UW=902<br clear="none">> <br clear="none">> <br clear="none">> THANKS AGAIN!<br clear="none">> <br clear="none">> <br clear="none">> <br clear="none">> Απο: Lynn W. Deffenbaugh (Mr) <<a shape="rect" ymailto="mailto:ldeffenb@homeside.to" href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a>><br clear="none">> Προς: TAPR APRS Mailing List <<a shape="rect" ymailto="mailto:aprssig@tapr.org" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>> <br clear="none">> Στάλθηκε: 11:57 μ.μ. Σάββατο, 14 Φεβρουαρίου 2015<br clear="none">> Θέμα: Re: [aprssig] proposal for APRStt grid loc. Σχετ: 60 Grid Square............<br clear="none">> <br clear="none">> <br clear="none">> Pardon my literalness, but if you say "Row 1st, Col 2nd", then for KM I'd go to row K up the right side and column M across the bottom and get 520 whereas your example says it's 502 which seems to be column K and row M?<br clear="none">> <br clear="none">> More than one example would make it more clear for those of us that need to see what you're talking about.<br clear="none">> <br clear="none">> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br clear="none">> <br clear="none">> On 2/14/2015 7:33 AM, George Vastianos wrote:<br clear="none">> <br clear="none">> <br clear="none">> Hello Bob<br clear="none">> <br clear="none">> IMO in APRStt the conversion between grid and numbers should be very easy in a way that no calculation algorithm will be needed by the user and only a small printed table will be enough. In this way with a small printed paper in the pocket and the low cost HT anyone could define his position in the APRS system (of course if he knows his position and if there is APRStt infrastructure in his area...)<br clear="none">> <br clear="none">> In the attached file (PNG picture) you can find my proposal for a simple conversion table<br clear="none">> <br clear="none">> the result is that you add a group of 3 number-digits for each 2 letters of the grid<br clear="none">> <br clear="none">> eg. KM = 502, KM17 = 50217, KM17uw = 50217902, KM17uw48 = 5021790248<br clear="none">> <br clear="none">> based on the fact that my proposal uses only the 0-9 digits and not the *,#,A-D this makes it compatible with the APRStt format.<br clear="none">> <br clear="none">> The conversion table was designed in a way that the conversion from the number to ascii will be very easy (even for 8-bit microcontrollers) and will not require usage of memory lookup tables.<br clear="none">> <br clear="none">> Below is a sample code (in basic style) that will convert the 3-digit number into the Grid Square letter characters (e.g. for i=502 then Chr(C1) becomes "K" and Chr(C2) becomes "M")<br clear="none">> <br clear="none">> ----------------------------<br clear="none">> <br clear="none">> 'example I=536 will print "NQ"<br clear="none">> <br clear="none">> Dim I, X, CO1, CO2, C1, C2 As Integer<br clear="none">> I = 536<br clear="none">> If (I >= 100 And I < 340) Then<br clear="none">> CO1 = 10: CO2 = 65<br clear="none">> ElseIf (I >= 400 And I < 640) Then<br clear="none">> CO1 = 40: CO2 = 75<br clear="none">> ElseIf (I >= 700 And I < 940) Then<br clear="none">> CO1 = 70: CO2 = 85<br clear="none">> End If<br clear="none">> X = Int(I / 10)<br clear="none">> C1 = 65 + X - CO1<br clear="none">> If C1 < 65 Or C1 > 88 Then End 'ERROR i is outside limits<br clear="none">> C2 = I - X * 10 + CO2<br clear="none">> If C2 < 65 Or C2 > 88 Then End 'ERROR i is outside limits<br clear="none">> MsgBox Chr(C1) & Chr(C2) <br clear="none">> <br clear="none">> --------------------------<br clear="none">> <br clear="none">> In the above sample code the C1 and C2 are integers that contain the ASCII value of the 2 characters..... This proposal is not only for the satellite app but for the APRStt in general.<br clear="none">> <br clear="none">> 73<br clear="none">> <br clear="none">> sv8gxc<br clear="none">> <br clear="none">> <br clear="none">> P.S. The limit of 40KB in aprssig list....really sucks! i tried 3 times to send the same email until it fits in limits. SORRY in case you received multiple times the same message (e.g. amsat-bb)<br clear="none">> <br clear="none">> <br clear="none">> <br clear="none">> <br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> aprssig mailing list<br clear="none">> <a shape="rect" ymailto="mailto:aprssig@tapr.org" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br clear="none">> <a shape="rect" href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><div class="qtdSeparateBR"><br><br></div><div class="yqt9319017407" id="yqtfd70697"><br clear="none">> <br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> aprssig mailing list<br clear="none">> <a shape="rect" ymailto="mailto:aprssig@tapr.org" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br clear="none">> <a shape="rect" href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br clear="none">> <br clear="none">> <br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> aprssig mailing list<br clear="none">> <a shape="rect" ymailto="mailto:aprssig@tapr.org" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br clear="none">> <a shape="rect" href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br clear="none">> <br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> aprssig mailing list<br clear="none">> <a shape="rect" ymailto="mailto:aprssig@tapr.org" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br clear="none">> <a shape="rect" href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br clear="none"><br clear="none">_______________________________________________<br clear="none">aprssig mailing list<br clear="none"><a shape="rect" ymailto="mailto:aprssig@tapr.org" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br clear="none"><a shape="rect" href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br clear="none"></div><br><br></div> </div> </div> </div></body></html>