What Happened to the USFS Listings?

Status
Not open for further replies.

jbaker6953

Member
Joined
Mar 2, 2008
Messages
59
I haven't looked at the RR database for California USFS frequencies in a while. When I went there today I was surprised to see a lot of frequencies that used to be in there were now missing. Is RR intentionally excluding some frequencies for a specific reason, or did they just get left out on accident?

I haven't had time to make an exhaustive review, but right off the top I see NIFC TAC 1, 2, an 3 are not listed. North and South air ops are also not listed (to be used in place of 170.000).

Some of the individual forests also used to have repeater information such as their associated peak names, but those are gone as well.
 

SCPD

QRT
Joined
Feb 24, 2001
Messages
0
Location
Virginia
I took a look after the latest update also and was surprised to see the repeater plan for each forest now missing. I took a great deal of time to gather and submit that information. Does anyone know why has been removed?

The listing for a UHF link common to Region 5 of 451.360 is erroneous.

Also, the latest BLM update for "Common Frequencies" does not appear correct.
 
Last edited:

kma371

QRT
Joined
Feb 20, 2001
Messages
6,204
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)

Exsmokey said:
I took a look after the latest update also and was surprised to see the repeater plan for each forest now missing. I took a great deal of time to gather and submit that information. Does anyone know why has been removed?

The listing for a UHF link common to Region 5 of 451.360 is erroneous.

Also, the latest BLM update for "Common Frequencies" does not appear correct.

The DB is supposed to reflect frequencies by the agency. For example, if Sacramento county fire has a Yolo county fire freq in their radio, it's not supposed to be listed because it's already listed in yolo county

A TON of stuff listed in the USFS part of the DB was like that. I know cause I updated most of it.

Also, we aren't supposed to list Thjngs like this:

Channel 1 154.800 repeater
Channel 2 154.800 simplex

I removed some of those as well.

Sorry you guys are upset but we as Admins are just following rules set forth by the DB guide.
 

LAflyer

Global DB Admin
Moderator
Joined
Mar 4, 2009
Messages
1,846
Location
SoCal
If you look at the page history, nothing has been deleted since November.(as far as the history goes).
 

kma371

QRT
Joined
Feb 20, 2001
Messages
6,204
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)

Also if something isn't there that belongs there, please resubmit it.
 

kma371

QRT
Joined
Feb 20, 2001
Messages
6,204
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)

LAflyer said:
If you look at the page history, nothing has been deleted since November.(as far as the history goes).

Yeah it's been that way a while. I guess with fire season coming up, some checks were made.
 

MtnBiker2005

Member
Premium Subscriber
Joined
Dec 19, 2002
Messages
3,565
Location
San Diego County, California

SCPD

QRT
Joined
Feb 24, 2001
Messages
0
Location
Virginia
Someone needs to make a submission for the erroneous listing of 451.360, which isn't a real frequency as far as I remember as the closest would be 451.3625 (narrowband) or 451.350 (wideband). This "non-frequency" is in a range not allocated to the federal government. Even if the second two digits have been transposed, 415.360 is still not a valid frequency. The lower of the pair of link frequencies is the downlink now, which is of the most interest to listeners as it transmits everything a repeater or remote base is hearing. The uplink is normally within range of the VHF channel being linked.

I went looking for a wiki page link on the Forest Service database for California and did not find the information I spent quite some time developing and submitting. It makes sense to put all the tone information for each National Forest on a wiki page and it was mixed between that and the database page, but now it doesn't exist in either location. With my time limited while being a caretaker for two elderly people for quite some time to come, I don't have much time to look at this webpage, let alone make submissions.

I think the tone data for individual repeaters is essential as it helps the listener understand where an incident may be located by being able to associate a repeater with its location.

I don't have time to look at the BLM stuff, but the newest two frequencies updated don't match with my memory of the latest internal information I've received.
 
Last edited:

lbfd09

Member
Premium Subscriber
Joined
Jan 13, 2005
Messages
488
Location
California
Exsmokey, I too spend more that a look up in another data base or hit on the scanner prior to submitting. I try my best to verify that I am hearing who I am submitting (with a few exceptions that I get from our radio loads - and a nod from the chief). Seeing some of my past submissions or those of others for my area having been deleted, makes me wonder, as I know some of those deletions are still in use. But I will re-verify and re-submit.

Having the radio loads of other agencies, particularly that of a national forest or park is of benefit of a responder who might going to there; as it helps us to be able to monitor some of the traffic en-route and to grasp what is happening. It can also make it easier when a dispatcher says something like, "They are on our channel 7," when dispatch may not know the actually NFIC name of the channel.

Now placing this in the wiki is all great, BUT - this can be edited, deleted, or just plain messed with; after someone spends a fair to great amount of time gathering, assembling, and posting this info. If there was a level in the submissions that could lock certain info to that of the poster or above only, Then we can share some of this "extra" or excessive (to the novice listener) data without cluttering up the data base. I think the CHP section is a great example of this.
 

kma371

QRT
Joined
Feb 20, 2001
Messages
6,204
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)

More detailed information, such as repeater sites or channel loads belongs in the wiki. Plain and simple.

Other wise we will have stuff duplicated all over the place. Its become more neat and organized than it was in the beginning.
 

lbfd09

Member
Premium Subscriber
Joined
Jan 13, 2005
Messages
488
Location
California
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)

More detailed information, such as repeater sites or channel loads belongs in the wiki. Plain and simple.

Other wise we will have stuff duplicated all over the place. Its become more neat and organized than it was in the beginning.

Yes, I understand and agree. Now - is there a way that when one places a radio load of a particular agency such as Yosemite Park, that it will be there and not messed up by another wiki user?

While we are on this subject does a flag on the county's page designate that there are entries in the wiki?
 

jbaker6953

Member
Joined
Mar 2, 2008
Messages
59
Its become more neat and organized than it was in the beginning.

It is true that removing listings makes things more neat and organized, but what isn't immediately apparent to me is whether it's more useful. To make an analogy, my garage would be a lot more neat and organized if I threw everything out, but I would have a hard time getting anything done.

The real world doesn't operate with perfect divisions of frequencies between agencies. The Forest Service radios are loaded with local and federal frequencies and one incident will see people using those frequencies. It is not uncommon to be on a single incident in the Angeles National Forest such as a traffic collision and having rescue personnel talking on NIFC TAC2, while the incident commander is relaying information to dispatch on Forest Net, and emergency crews and others are talking on California state frequencies. Now that things are "neat" somebody without an intimate knowledge of the interrelationship between these agencies will have no idea what to listen for on an incident. I was thinking that the point of the RR database was to help people who didn't have this knowledge already. If it's just going to be a duplicate of the FCC and NTIA frequency assignments, what purpose is that serving?


It makes more sense to me to have an agency's radio programming available so a listener can approximate the agency's loadout and hear what the agency's personnel hear.
Sorry you guys are upset but we as Admins are just following rules set forth by the DB guide.

I suppose the question then becomes, what are the procedures for modifying the DB guide?
 
Last edited:

benca

Member
Premium Subscriber
Joined
Jan 29, 2005
Messages
125
Location
Orangevale, ca
US Forest SVC

I agree how does RR maintain the below statement of a complete frequency database when so many frequencies have been removed... how is this complete? It has been reduced to just a few suggested frequencies not a complete frequency database.

RadioReference.com is the world's largest radio communications data provider, featuring a complete frequency database

DB Admin really need review the previously removed frequencies...and add the deleted frequencies back...I'm sure there is a back up file that can be restored from.

The point of having all the information common to the forest was to indicate all of the potential frequencies that are available in that forest....not have to guess at what may or may not be used in a particular area...

Example in the INYO during the summer lightning storms many more frequencies are used beyond the north and south net...where did those frequencies go...
INYO LAW, Service1, Service2, Service3, extenders, how were those frequencies deemed not necessary to be included...
 

SCPD

QRT
Joined
Feb 24, 2001
Messages
0
Location
Virginia
Police Call only showed the frequencies licensed to a particular entity and thus didn't show that the Torrance FD had the Long Beach FD F1 in their radios as channel 9 (just a hypothetical). This makes things difficult if Torrance puts out a message for apparatus to respond to Long Beach on channel 9 for assignment. That was a shortcoming of Police Call Volumes 1-9, however the southern Calif detailed edition made up for that in just the area it covered by showing each agencies complete channel plan. Recently published books such as the Scannerstuff Southern California Frequency Directory list each channel in LAPD's radios including those of cooperating agencies. It would seem to me that the paper directories would have to be purchased for information like that because RR decided to not show these "duplicate listings."

Now the RR database listing for the L.A. County Fire Department shows how their VHF tactical radios are programmed. It includes duplicates of the Angeles National Forest frequencies depending on the channels in the radio. In a multi-agency response you may hear a tactical channel assignment given out over a dispatch or command frequency for all arriving resources to use channel 113, which is channel 1 or simplex Forest Net for the Angeles NF. The present policy for the database would have us wondering what the tac assignment is and force us to try to listen to everything, instead of locking out channels to narrow our focus on one incident that is particularly interesting or extremely important, such as living in the Angeles NF urban interface.

This is why I submitted the entire channel plan for each Forest, Park and BLM District. I've been dispatched to incidents with instructions to use "channel 14 168.775 SQF channel 3, Fire Net Simplex." I may hear traffic while enroute that everyone is to switch to channel 14 6. As a listener I may not have heard the initial instructions regarding frequency use because my scanner was locked on another frequency at the time, or I might be arriving in the vicinity (as a scanner listener) after the announcement was made and hear some of the Inyo folks saying "the tactical is on 14." If I know the Inyo's channel plan then I can look up 14 and keep it in the program to scan and lock out other frequencies.

I would think we are trying to build a database that is at least as good as the paper directories, especially if the publishers of the directories go out of business.

This is my observation of the situation. It is likely it won't make any difference in the long run.

Another observation is that the Wiki site is difficult to use. From the initial layout it is difficult for me to look up the NIFC frequencies because it seems hidden when it is lumped into "common frequencies" along with business itinerants. Another suggestion is that common federal frequencies or any others that are used nationwide should have a nationwide page for the federal government. That way a listing of NIFC frequencies won't be different depending on the state you are in or how recent someone in a particular state submitted the NIFC frequency information or if that person has picked up on some changes made to the NIFC channel plan. When I noticed this I wrote the Wiki section on the NIFC channel plan (which I haven't updated as I should) but if I have trouble finding it after many months of not navigating to it, how does someone who is not familiar find it?

This is probably an exercise in futility as some of these policies seem to be oriented top down instead of bottom up, or some reasonable compromise of the two. Then again it might be due to server space and such. There may be some other reasons too, one should not interpret this policy as something handed down from above us to purposely cause inconvenience for no reason, although I would be curious of that reason.

Now that I've taken a break to write this, it is back to finishing up taxes for the two elderly folks I care for. When I return to this forum is something I can't predict . . . . .
 
Last edited:

kma371

QRT
Joined
Feb 20, 2001
Messages
6,204
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)

Nothing was removed. Its just not in the same place you found it before. Its located in the indivudual agency page who the frequency is licensed to.

You guys ever heard the term, "dont shoot the messenger?"

If you guys feel that strongly, i suggest you contact eric who is in charge of the DB. I just follow the guide.
 

kma371

QRT
Joined
Feb 20, 2001
Messages
6,204
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)

lbfd09 said:
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)

More detailed information, such as repeater sites or channel loads belongs in the wiki. Plain and simple.

Other wise we will have stuff duplicated all over the place. Its become more neat and organized than it was in the beginning.

Yes, I understand and agree. Now - is there a way that when one places a radio load of a particular agency such as Yosemite Park, that it will be there and not messed up by another wiki user?

While we are on this subject does a flag on the county's page designate that there are entries in the wiki?

Thats a great question for the wiki admin. I dont know the answer.
 

LAflyer

Global DB Admin
Moderator
Joined
Mar 4, 2009
Messages
1,846
Location
SoCal
Now the RR database listing for the L.A. County Fire Department shows how their VHF tactical radios are programmed. It includes duplicates of the Angeles National Forest frequencies depending on the channels in the radio. . . . . .

The LACoFD listings will be "cleaned up" very shortly as its on my to-do list.

Again, the idea behind the DB is not to duplicate agency radio programming channel line ups, and end up listing the same frequency over and over across multiple agencies, but to list frequencies only belong to each agency.

While I can see how this can be frustrating for some, it can likewise be frustrating and take up precious scanner memory space for others downloading the same frequencies multiple times needlessly when they access the DB.
Additionally I would like to draw attention to problems that can be encountered when frequencies are updated by their primary agency, and you might now have old and incorrect orphan listing left in the DB under various other agencies that had the original frequencies listed also. Not a model for data accuracy.
 
Status
Not open for further replies.
Top