<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Browse around my APRS Infrastructure usage graphs at:<br>
<br>
<a class="moz-txt-link-freetext" href="http://tinyurl.com/APRSAct24">http://tinyurl.com/APRSAct24</a><br>
<br>
<a class="moz-txt-link-freetext" href="http://tinyurl.com/APRSAct00">http://tinyurl.com/APRSAct00</a><br>
<br>
And the Balloon coverage graphs at <a class="moz-txt-link-freetext" href="http://tinyurl.com/APRS-Balloons">http://tinyurl.com/APRS-Balloons</a><br>
<br>
Is that kind of what you have in mind?<br>
<br>
Lynn (D) - KJ4ERJ - APRS Infrastructure Visualization<br>
<br>
<br>
On 2/18/2011 2:41 PM, Jim Alles wrote:
<blockquote
cite="mid:AANLkTik8GomgXEX_gy9ZGZJtQCxpJtP9a5bx0FZ8o_K0@mail.gmail.com"
type="cite">Hello All,<br>
<br>
I want to run an idea for an application past everyone.<br>
<br>
I live in central Pennsylvania, with a relatively high density of
digipeaters on mountaintop sites. 2 hops can easily cover the
state and more. I am working on a map display of which stations
hear a first transmission, which digis transmit the first hop (and
their PHG circles), which stations hear that, etc.<br>
<br>
My proof of concept was with URL shortcuts that initiated <a
moz-do-not-send="true" href="http://aprs.fi">aprs.fi</a>
queries, based on 1000 raw packets. Several shortcomings
encountered were: slow and cumbersome, can only request 20 call
signs at a time, and the data is already filtered.<br>
<br>
I do understand that we can't analyze the RF network from what we
see on the Internet. But if paths are reported even once, it does
show that the RF signal is capable of being present.<br>
<br>
So I am considering what it would take to take a feed from <a
moz-do-not-send="true" href="http://aprs.is">aprs.is</a>
servers, collect real time data, parse the packets, construct the
profile and present the data graphically. Doing it once is a
chore. Doing more than once is a job for a computer program. I
don't even know what programming language to use (other than
guessing PERL).<br>
<br>
I believe that if people had a tool that they could plug their
Callsign into, and see the propagation blossom live on a map, it
might be easier for them to ask: "why does my packet need to be
out that far away?", and maybe cut back on the hops a little.<br>
<br>
Any feedback or suggestions would be appreciated.<br>
<br>
73<br>
<br>
Jim Alles<br>
<br>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>