I just didn't feel like trying to separate out the boundaries. For instance, in Northern Panhandle of WV there are 2-3 sites that are part of 1F6 (Ohio) even though they are in West Virginia -- and that's because their intent is to serve Ohio, not WV. I'm not sure if the same kind of thing exists for border separations down south -- meaning I'm not sure if there will be some sites in some states that look like they should be part of one operating company but which may be intended to server another system ID across the border.
That tiny little blob of SWEPCO in the Texas Panhandle doesn't make a whole lot of sense. . .I will attempt to separate them out further though, thanks. I was going by the Outage Maps. It might be that the maps you provided will allow me to decide upon boundaries without going crosseyed.
Edit: Ok, you are talking about the SWEPCO Territory map. I'm betting it makes sense to them.That tiny little blob of SWEPCO in the Texas Panhandle doesn't make a whole lot of sense. . .
It's real.That tiny little blob of SWEPCO in the Texas Panhandle doesn't make a whole lot of sense. . .
I don't doubt it, it just seems odd, a tiny chunk of 5 counties that far away from the rest of the SWEPCO territory.It's real.
Oy vei. I was hopingNice map though. There you go, Mike, that should be helpful updating your Google map.
Looks like I might need to look for another potential FRN. I notice that on my map I don't have any sites listed south of Bienville and DeSoto counties in Louisiana, but the SWEPCO map shows service territory in five or six counties below there. Doggonit -- more investigative work needed.It's real.
Your best bet is to add the AEP P25 sites to your scanner and make sure you enable ID SEARCH (Uniden) or add a Group Wildcard (GRE / Whistler). You likely already know that. At any rate, that'll be the only way to hear the traffic if you don't know / have the talkgroups for your area specifically programmed in. I can say that up in Eastern Ohio, they have switched. In most places in East Ohio, there isn't even an EDACS control channel online anymore. When they first fire up a P25 site, from what I hear the radio techs say they enable "Hybrid" mode. Not sure what that is all about, but I'm sure it has something to do with supporting P25 / EDACS at the site at the same time. But if you aren't hearing any EDACS control channels, they may have turned down the EDACS sites down there after the P25 sites were online like they did here.I'm assuming AEP in Ohio (at least SE Ohio) has switched to the new P25 system. I've heard Athens County Fire request AEP on several occassions but heard nothing. I've been monitoring EDACS on the Trimble site for 2 months and have heard nothing. Silence. Now to find those new P25 talk groups.
@BigLebowski Could you / would you periodically check this site for the existence of new site neighbors (and their associated CC freqs)? I have seen quite a number of FCC updates from Appalachian Power microwave licenses in VA, which is suggestive that they are moving ahead pretty quickly on getting some sites online in VA.Have a 1F7 CC on 854.8625 (ACC's 856.3125 & 856.4125), RFSS 66, Site 66 receivable north of Greensboro, NC tonight. Not showing any neighbors and the only license in VA I see on this frequency is in Salem.
Mike,@BigLebowski Could you / would you periodically check this site for the existence of new site neighbors (and their associated CC freqs)? I have seen quite a number of FCC updates from Appalachian Power microwave licenses in VA, which is suggestive that they are moving ahead pretty quickly on getting some sites online in VA.
@HikerGuy Thank you. The more people keeping an eye out, the better.Mike,
I'm within line of sight of this particular site (Poor Mountain) and am not seeing any neighbors listed yet. I plan to monitor it on a religious basis for any activity.