Federal Freqs. Database - Page 3

milf · #41 (**permalink**) 09-21-2009, 12:21 AM

I can look into the states I admin for and see if anything needs cleaned up.... If I can find anything that is not say county/parish specific that I can move to the Fed sections on State level I will... The Federal/Military TRS's I am leaving on the County/Local and State level areas where they are. Conventional freqs that I can reset up I will start on that, may take a lil time as I am reverifying/cleaning up those states deata wise to get things as accurate and usable as possible.

mike_s104 · #42 (**permalink**) 09-21-2009, 05:12 AM

Great!!!! Thanks. I'm sure others will find this helpful as well.

JESSERABBIT · #43 (**permalink**) 09-21-2009, 06:41 PM

milf, thank you. Your efforts are much appreciated.

al95 · #44 (**permalink**) 09-21-2009, 07:32 PM

Thank you for taking the time to work on it. Thanks

wa8pyr · #45 (**permalink**) 09-22-2009, 09:04 AM

Quote:

Originally Posted by milf

I can look into the states I admin for and see if anything needs cleaned up.... If I can find anything that is not say county/parish specific that I can move to the Fed sections on State level I will... The Federal/Military TRS's I am leaving on the County/Local and State level areas where they are. Conventional freqs that I can reset up I will start on that, may take a lil time as I am reverifying/cleaning up those states deata wise to get things as accurate and usable as possible.

Time permitting, I'll take a look at Ohio again and if there is anything listed at the county level that should be statewide I'll migrate it to the existing Ohio Federal page. However, anything county-based (such as a frequency used at a specific Federal courthouse, for example) will remain in or go back to that county; I don't see any point to adding a location-specific frequency to a statewide page merely because it's a Federal frequency. In my mind, it's no different than a local law enforcement frequency in that respect.

I don't expect to see much because Mark Meece (our Federal guru) has already done a pretty good job of cleaning up the Ohio Federal listings.

mike_s104 · #46 (**permalink**) 10-24-2009, 05:08 PM

Just wondering if anything has been done?

I found another example of things that need to be changed. Look at this link:
Civil Air Patrol Scanner Frequencies and Radio Frequency Reference

Now look at this one:
Civil Air Patrol Scanner Frequencies and Radio Frequency Reference

Anyone see anything odd? The MD link is more complete for VA than the VA link is.

mike_s104 · #47 (**permalink**) 10-26-2009, 12:20 PM

What I thought... NOTHING

zerg901 · #48 (**permalink**) 10-26-2009, 01:12 PM

There is another thread at radioref where editors were talking about moving some statewide info and / or regional info to the Wiki. Sorry I dont have the URL of the thread - I think it is ongong and current however. Maybe you can jump on that thread from the Federal aspect. Peter Sz

mike_s104 · #49 (**permalink**) 10-26-2009, 07:02 PM

Quote:

Originally Posted by zerg901

There is another thread at radioref where editors were talking about moving some statewide info and / or regional info to the Wiki. Sorry I dont have the URL of the thread - I think it is ongong and current however. Maybe you can jump on that thread from the Federal aspect. Peter Sz

Good idea, but that's not going to help anyone that wants to program their scanner from the RRDB that they paid to have access for.

mike_s104 · #50 (**permalink**) 10-29-2009, 09:50 PM

Wirelessly posted (XV6975 Opera/9.50 (Windows NT 5.1; U; en))

just checking to see if anyone was going to do anything about this. if nothing is going to be done, just say so.

AlabamaRS · #51 (**permalink**) 10-29-2009, 10:03 PM

I am checking in on this also

Jay911 · #52 (**permalink**) 10-29-2009, 10:39 PM

Quote:

Originally Posted by mike_s104

It also won't help if someone needs to download the info from the DB using software to access it.

This is a point that needs to be remembered each time we decide to move frequencies or talkgroups to the wiki.

ericcarlson · #53 (**permalink**) 11-01-2009, 06:19 PM

I agree that a "nationwide" feature in the db to facilitate downloading nationwide frequencies, including nationwide federal frequencies, would be a good idea. This would be a new feature which would have to be implemented by Lindsay. He prioritizes and implements new features so ultimately this is his call.

With respect to the organization of federal frequencies, here is a breakdown of how we currently handle this:
1. Truly nationwide frequencies are to be listed in the wiki.
2. Multi-county and truly statewide frequencies should be on state-level pages.
3. Local frequencies should be on the appropriate county page (or county agency page). Please keep in mind that while there are some truly nationwide allocations, a lot of federal frequencies are local (furthermore, analog/digital mode, tones and exact local usage may vary).

Please understand that are two major use cases for federal frequencies:
1. Confirmed, specific local usage.
2. "Big lists," usually organized by agency, used for reference and identifying new frequencies/usages.

For now, those "big lists" go in the wiki. I realize this is a barrier to automatic programming of scanners but for now we don't have a way to make this data available through the database interface in a consistent, easy to maintain and easy to use manner. Any of you who have been hanging around this site for a while know that it is under continuous development and Lindsay continues to roll out new features on an ongoing basis -- hope is not lost!

MPSCS · #54 (**permalink**) 11-01-2009, 06:54 PM

Quote:

Originally Posted by milf

Issues with that- 1 Federal information is classified, MCW

Milf, are you certain about this? I know they're not listed in the FCC database, or openly published like public safety frequencies are, but have you confirmed that they are in fact "Classified"?

I ask because I was discussing this at breakfast this morning. I was asking if I were to be parked near the St. Clair River, in Michigan, monitoring the Feds, Homeland Security, Border Patrol, US Customs, etc, and was approached by the local police, could I be in for some problems?

With all the post 911 paranoia, we've all heard the stories of being hassled for taking pictures of buildings and bridges in large cities, etc. So it stands to reason there may be some LEO's that would have issues with a situation like I described above. If they're not classified, I think it would be a happy ending. But if they are classified, couldn't we all be in jepordy for simply possessing a list, let alone having them programmed in our scanners?

I don't want to derail the thread, but I thought it's a good time to clear the air on this, considering what's being discussed.

Thanks

loumaag · #55 (**permalink**) 11-02-2009, 08:50 AM

Quote:

Originally Posted by MPSCS

... have you confirmed that they are in fact "Classified"?

They are not classified. Official published lists of federal frequencies may very well be marked FOUO ("For Official Use Only") which is not a "classification". Some usages of frequencies may very well be classified, but that is not the concern of someone who discovers those frequencies by listening. Monitor to your heart's content.

MPSCS · #56 (**permalink**) 11-02-2009, 10:15 AM

Thank you for the clarification.

ecps92 · #57 (**permalink**) 11-02-2009, 05:39 PM

And many in the RR DB are the old Wideband channels, not the current info

Quote:

Originally Posted by mike_s104

Just wondering if anything has been done?

I found another example of things that need to be changed. Look at this link:
Civil Air Patrol Scanner Frequencies and Radio Frequency Reference

Now look at this one:
Civil Air Patrol Scanner Frequencies and Radio Frequency Reference

Anyone see anything odd? The MD link is more complete for VA than the VA link is.

ecps92 · #58 (**permalink**) 11-02-2009, 05:42 PM

Problem is folks not Posting what they hear

Shame tho, especially the FEDS

FOUO just puts a scare in those Non Educated folks.
Like someone telling me they are from "Homeland Security" and I reply
"yea, so what Agency"

Quote:

Originally Posted by loumaag

They are not classified. Official published lists of federal frequencies may very well be marked FOUO ("For Official Use Only") which is not a "classification". Some usages of frequencies may very well be classified, but that is not the concern of someone who discovers those frequencies by listening. Monitor to your heart's content.

mike_s104 · #59 (**permalink**) 11-14-2009, 11:04 AM

just checking to see how things are progressing on this? plus I didn't want the post to fall to the bottom and forgotten about like last time.

MaxTracker · #60 (**permalink**) 11-15-2009, 02:37 AM

I don't know if this has been covered, but Grove created the Federal Frequency Database and published it on CD Rom some moon's ago. When printed and this puppy was two column per page and included DEA, FBI ect was 180 pages long.

Now it listed info sorta like: 407.0125 CH 406 USPS, DEA, FBI Nationwide, VA, yadda so on and so fourth.

I don't think Grove has published this in a few years, but I'm not sure. Its almost one of those cases of; If this info was published here on this website to the degree Grove published it. Would it be worth the time and trouble to The owner and inner circle of RadioReference.com LLC with the possible legal repercussion that will surely follow? And would you want to come in and discuss these on the forums in this New Secure post 911 world knowing darn good and well that Some Federal agency was watching your thread and IP?

That might be extreme, I know. but which would be the greater liability, the stuff we scan and post as we do now or an entire database with user, NAC code and area's used published for anyone to see?

I sometimes think when it comes to Federal scanning. We're better off to keep our own private lists and our mouths shut. Maybe sharing only in PM or submitting non-classified info such as Veterans Affairs Maintenance frequencies. But then again, Most of the GOOD fed frequencies run encryption far more advanced then scanners on the drawing boards of the future.