<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16674" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=141441513-02072008><FONT face=Arial
color=#0000ff size=2>That site seems unable to handle anything in Europe.
It mangles the locator/location, and shows no maps.
:-(</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=141441513-02072008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=141441513-02072008><FONT face=Arial
color=#0000ff size=2>73.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=141441513-02072008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=141441513-02072008><FONT face=Arial
color=#0000ff size=2>Dave G0WBX.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=141441513-02072008></SPAN> </DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Gregory A. Carter
[mailto:gcarter@openaprs.net] <BR><B>Sent:</B> 01 July 2008
23:34<BR><B>To:</B> aprssig@lists.tapr.org<BR><B>Subject:</B> [aprssig] APRS
Search Engine --- Request for Comment<BR></FONT><BR></DIV>
<DIV></DIV>Hello all,<BR><BR>I've been toying around with the idea of creating
an APRS search engine that acts much the same way as web search engines only
for ARPS data/packets. I recently created a new site that uses the same
backend as OpenAPRS (which on another note should be far more stable and
reliable than it used to be) that allows you to basically search through the
APRS data using a pretty simple search interface to find position reports,
weather and telemetry. I plan to implement more search features for
messaging in the near future. The site is at <A
href="http://www.oaprs.net/">http://www.oaprs.net/</A> and the results point
back to the "Info" interface on OpenAPRS's main site when a station is
clicked, though much of the data is included right in the search results for
quick lookups. The engine will also search by FCC ULS and display both
ULS information specifically or in addition to position/telemetry/weather
reports. Most everything is sortable by callsign, speed or age at the
moment.<BR><BR>There are some options like measurement units, geocoordinates
display preferences (not quite implimented yet) and default timezone that can
be set and searching can be narrowed by using several options inline with your
query (you can find what I call "quibbles" or search options under the help
link next to the search input box). I am also pondering the idea of
adding search capabilities for Satellite data and pass prediction in some sort
of searchable format. The basic idea I had for this search engine was to
be able to "find" stations, whether they be stations you know the callsign
for, stations you may know a partial callsign for or perhaps stations you just
would like to find by the type of data they are offering to the APRS
network. I am also considering focusing on adding features that help to
debug APRS packets quickly and easily for users who are learning to get their
APRS stations dialed in and who feel a bit overwhelmed at the idea of hitting
findu and trying to figure out the scripts.<BR><BR>As I am not quite sure of
the direction I want to take this, I wanted to get some input from the experts
on how useful this interface would be and what suggestions for additions,
subtractions or other design modifications/features would make this a powerful
tool that would benefit the APRS community. I'd love to hear any
comments or constructive criticism that everyone may have to offer either on
or off list, fire away!<BR><BR>Greg<BR><BR>NV6G (previously
N7NXS)<BR>OpenAPRS.Net<BR></BLOCKQUOTE></BODY></HTML>