<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-signature">Yes, anyone can put whatever they want in
the comment section of THEIR OWN packets. IGates and digipeaters
MUST NOT modify the packet except as provided in the path section
for their particular operations. The source, destination, and
payload of packets must not be modified as the packet traverses
the RF and APRS-IS networks.<br>
</div>
<div class="moz-signature"><br>
</div>
<div class="moz-signature">Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
<br>
<br>
<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 8/17/2023 5:52 PM, Bob Poortinga
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEEMhL5EqUhXX6kLup-N+aCYr5+NKGiWBfH8FSBouhfyEuGouQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div dir="auto">Nothing prevents you from using the free text
comment section of an APRS position report, object, or status
packet for your own needs. Create a software parsable format
that is distinct (e.g. starting the comment with "&&")
and stuff your meta data there.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Bob W9IZ </div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Aug 17, 2023, 4:14
AM Borja Marcos <<a href="mailto:ea2ekh@gmail.com"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">ea2ekh@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I am new to the list, I hope this is the right place to
discuss this issue. This is not a complete proposal, of
course,<br>
just a “weather balloon” ;)<br>
<br>
As many members will be aware, there is an effort underway
to use LoRa modulation on 433 MHz for<br>
APRS. There are several open source projects which, as a
plus, are based on dirt cheap and easy to obtain<br>
hardware,<br>
<br>
<a href="https://github.com/richonguzman/LoRa_APRS_Tracker"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/richonguzman/LoRa_APRS_Tracker</a><br>
<a href="https://github.com/dl9sau/TTGO-T-Beam-LoRa-APRS"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/dl9sau/TTGO-T-Beam-LoRa-APRS</a><br>
<a href="https://github.com/lora-aprs/LoRa_APRS_iGate"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/lora-aprs/LoRa_APRS_iGate</a><br>
<br>
There is also one commercial product available, picoAPRS
LoRa. It is more pricey, but, well, all of us know<br>
that developing and supporting an actual product is hard.<br>
<br>
<a href="http://www.db1nto.de/index_en.php" rel="noreferrer
noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://www.db1nto.de/index_en.php</a><br>
<br>
All of it is a bit ad-hoc now with no agreed standards (as
far as I know). While some of the developers have<br>
agree informally to use APL?? device IDs for LoRa based
equipment, not every developer is following that<br>
rule, <br>
<br>
As far as I know there are also other modems/phys used with
APRS. For example VARA on HF.<br>
<br>
I think it would be great to add some metadata to the
databses used by the APRS mapping applications including,<br>
as a minimum, a modem/phy identification (and frequency,
which could be useful for HF) so that they can be<br>
more useful to study/check certain kinds of APRS activity. <br>
<br>
Right now, for example, there are dashboards relying just on
APL??? device IDs. <br>
<br>
<a
href="http://lora.ham-radio-op.net/?center=43.3508,-3.0499&zoom=12"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">http://lora.ham-radio-op.net/?center=43.3508,-3.0499&zoom=12</a><br>
<br>
Another interesting possibility offered by a more flexible
database model could be adding some metadata specific<br>
to certain modems. As an example, LoRa chips can provide
RSSI and SNR data which could prove valuable for <br>
propagation/coverage studies.<br>
<br>
What do you think?<br>
<br>
<br>
73,<br>
<br>
<br>
Borja Marcos / EA2EKH<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@lists.tapr.org" rel="noreferrer
noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">aprssig@lists.tapr.org</a><br>
<a
href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a>
<a class="moz-txt-link-freetext" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>