Re: [FRC] FRC-Info Digest, Vol 1, Issue 64
I threw up a site at http://tools.byronservers.com/sites/, which queries the same mysql database dump from the recent Reddit posting (the latter of which isn't my handywork, I'm just a fan of mysql thanks). It's not displaying the contact info, coordination status or lat/long coordinates of sites, but does have breakdowns by band type, output freq, callsign, district/city/county names. I've found it more useful than the assortment of stale PDF files from the actual (or is it former now?) FRC site. I wish it was reporting off live data, oh well.
I'm sure they will get right on it... after the billion accounts hacked from Yahoo etc... anyway does anyone have the repeater listings? I needed to look something up and they are all gone
On Wed, Oct 5, 2016 at 8:15 AM, kg4ugk <kg4ugk@kg4ugk.com> wrote:
According to FRCs website.. their data was in fact breached.. and they have contacted the authorities.
Sent from my Samsung Galaxy smartphone.
-------- Original message -------- From: Bryan Fields <Bryan@bryanfields.net> Date: 10/4/16 12:05 PM (GMT-05:00) To: Florida Repeater Council Discussion <frc-info@lists.keekles.org> Subject: Re: [FRC] Melbourne Hamfest Postponed...
On 10/4/16 11:48 AM, Jon Pearl - W4ABC wrote:
**
*Due to HURRICANE MATTHEW the MELBOURNE HAMFEST and ARRL FLORIDA STATE CONVENTION has been Postponed *until October 21th and 22nd.
So, this does beg the question, will the FRC postpone their meeting? Per the bylaws they require 30 days notice to have a meeting.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ FRC-Info mailing list FRC-Info@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info
_______________________________________________ FRC-Info mailing list FRC-Info@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info
Hi Byron, Fantastic work! I've got Mysql loaded in my shack computer to manage my logbook and you're right... a relational database beats the heck out of hunting and picking through a static .pdf file, any day. There are a lot of old entries in this file that could be culled but as you say, if this database was the product of real-time information, it would speed up the search process for amateurs hunting pairs. 73, Jon Pearl - W4ABC www.w4abc.com On 10/7/2016 7:11 PM, Byron Felts wrote:
I threw up a site at http://tools.byronservers.com/sites/, which queries the same mysql database dump from the recent Reddit posting (the latter of which isn't my handywork, I'm just a fan of mysql thanks).
It's not displaying the contact info, coordination status or lat/long coordinates of sites, but does have breakdowns by band type, output freq, callsign, district/city/county names. I've found it more useful than the assortment of stale PDF files from the actual (or is it former now?) FRC site. I wish it was reporting off live data, oh well.
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On 10/7/16 11:30 PM, Jon Pearl - W4ABC wrote:
I've got Mysql loaded in my shack computer to manage my logbook and you're right... a relational database beats the heck out of hunting and picking through a static .pdf file, any day. There are a lot of old entries in this file that could be culled but as you say, if this database was the product of real-time information, it would speed up the search process for amateurs hunting pairs.
I did just this with FCC data looking for commercial pairs. This selects frequencies at base stations between 464 and 465 from a central point, and orders them by furthest to nearest. A query such as this could be run via a web interface after clicking "here" on a map and ranking all frequencies in use in furthest to near from that point. ie, you click on a point and it tells you the frequencies in use there sorted by distance.
SELECT f.frequency_assigned,f.call_sign, f.location_number,f.unique_system_identifier, l.dec_lat, l.dec_long, (ROUND( 3956 * acos( cos( radians(lat) ) * cos( radians(l.dec_lat) ) * cos( radians(l.dec_long) - radians(lon)) + sin(radians(lon)) * sin( radians(l.dec_lat))) )) AS distance FROM `FREQUENCY` f right join LOCATION l on l.location_number = f.location_number and l.unique_system_identifier = f.`unique_system_identifier` WHERE f.frequency_assigned >=464 and f.frequency_assigned <=465 and l.dec_lat is not null AND f.frequency_assigned NOT in (SELECT distinct f.frequency_assigned FROM `FREQUENCY` f right join LOCATION l on l.location_number = f.location_number and l.unique_system_identifier = f.`unique_system_identifier` WHERE f.frequency_assigned >=464 and f.frequency_assigned <=465 and l.dec_lat is not null AND ROUND( 3956 * acos( cos( radians(lat) ) * cos( radians(l.dec_lat) ) * cos( radians(l.dec_long) - radians(lon)) + sin(radians(lat)) * sin( radians(l.dec_lat))) ) < 15 ORDER BY `f`.`frequency_assigned` ASC) ORDER BY `f`.`frequency_assigned`, `distance` DESC
-- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
participants (3)
-
Bryan Fields -
Byron Felts -
Jon Pearl - W4ABC