<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 2/27/2012 4:13 PM, Bob Bruninga wrote:
<blockquote cite="mid:015301ccf594$a9f396a0$fddac3e0$@edu"
type="cite">
<pre wrap="">Can you or Hessu think of a way to aggregate all this data into one 2000
mile long string of data? Or do we just collect callsign reports and then
wait till we have enough data and then manually connect them?</pre>
</blockquote>
<br>
I've been playing around with OpenStreetMap data recently and they
seem to have the Appalachian Trail in as a way of connected nodes.
It'd be really neat if there was an easy way to detect an APRS
position report close to this line to get an automated way of
collecting points, but I'm not that good with geo-relations in
PostGreSQL (yet). So for now, the only thing I would know is to
manually collect and connect reports as submitted by the hikers
using callsign and date/time range.<br>
<br>
<blockquote cite="mid:015301ccf594$a9f396a0$fddac3e0$@edu"
type="cite">
<pre wrap="">Even if we came up with a clever SYMBOL or other flag to indicate the AT,
the chances are that some will forget it and do it wrong, so we will end up
having to manually connect the data anyway.</pre>
</blockquote>
<br>
Yeah, that's probably not even worth asking them to do, IMHO. We'll
get more people telling us when they were there than we would people
getting the symbol right.<br>
<br>
<blockquote cite="mid:015301ccf594$a9f396a0$fddac3e0$@edu"
type="cite">
<pre wrap="">So unless you have a clever idea, Im just going to ask everyone to REPORT
their DATES and TIMES and CALLSIGN when they were actually on the trail and
we can aggregate it later?</pre>
</blockquote>
<br>
That's a good start. If we have that information, we can always do
it the hard way. If we miss capturing that data, we might miss our
last chance to get what you're after.<br>
<br>
<br>
<blockquote cite="mid:015301ccf594$a9f396a0$fddac3e0$@edu"
type="cite">
<pre wrap="">How long is data retention in your data base of Hessu's before we have to be
sure to capture the data?</pre>
</blockquote>
<br>
My DB is limited to 5 days (sufficient for my purposes), but I store
all raw packets forever (for now), so I could go back and resurrect
paths if necessary. But I believe Hessu keeps posits in his DB for
a LOT longer than my 5 days and has some good queriability to boot.<br>
<br>
<blockquote cite="mid:015301ccf594$a9f396a0$fddac3e0$@edu"
type="cite">
<pre wrap="">We will ask all hikers to use a 2 minute rate while hiking unless they are
running Proportional Pathing, then a 1 minute rate is the same thing.</pre>
</blockquote>
<br>
Did AL0I-7 do one of your "destination" posits earlier today? If
not, then he's backtracking for some reason today. Hopefullly the
following screen cap will come through. His first posit was to the
SW, then he jumped to the NE and is now working his way back. Last
posit was 1.75 hours ago.<br>
<br>
<img src="cid:part1.06090607.02070102@homeside.to" alt=""><br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
</body>
</html>