<div>Amen to this... it's a bad idea to convert data from one format to another in transit. </div>
<div> </div>
<div>At one time (10 years ago) , I had the bright idea to catch a packet at the first hop and if I knew it was the first hop, convert NMEA sentences from a 'dumb' kpc3 tracker to mic-e format. The idea was to save bandwidth by reducing the lenght of the original packet 80bytes to 32 bytes. The problem was that there was no way to know that my digi was the only digi to hear the packet on the first hop, and we ended up with two different packets circulating the network with the same information at the same time.</div>
<div> </div>
<div>Another example was in WinAPRS they did the conversion to mic-e on the fly but due to different levels of precision in the NMEA and MIC-e format(or a math error??), my car appeared to have double positions very close to one another. </div>
<div> </div>
<div>It's much better (ie correct) to force the clients to decode the data they want to see rather than convert it for them.</div>
<div><br clear="all">Wes<br>---<br>It may be necessary temporarily to accept a lesser evil, but one must never label a necessary evil as good.<br><br><br></div>
<div class="gmail_quote">On Thu, Jan 15, 2009 at 4:39 PM, Heikki Hannikainen <span dir="ltr"><<a href="mailto:hessu@hes.iki.fi">hessu@hes.iki.fi</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="Ih2E3d">On Thu, 15 Jan 2009, Earl Needham wrote:<br><br></div>
<div class="Ih2E3d">> I wonder if there's a way to show these ships on UI-View...<br><br></div>No, I don't think there is any proper way to do it. You can't expand<br>UI-View to show AIS as such. Without converting AIS to APRS, which in turn<br>
isn't really possible to do well, since APRS packets don't have the fields<br>required to transmit all the interesting extra information present in AIS<br>packets.<br><br>So, I think it's a bad idea to try to convert AIS (or ADS-B) data to APRS<br>
format, and if someone still decides to do it, it should never be fed into<br>the APRS or APRS-IS networks.<br><br> - Hessu<br>
<div>
<div></div>
<div class="Wj3C7c"><br><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>