Tuesday, September 8, 2009

GUEST COLUMN: Cleveland Digital TV

OMW NOTE: We are basically no longer updating the Ohio Digital TV blog, which was designed to "carry the heavy load" during the period around the digital TV transition on June 12.

From now on, we will continue to post digital TV-related items on the regular Ohio Media Watch blog, like the item below...which we've copied over here for convenience.

----------------


Long-time OMW reader Trip Ericson (RabbitEars) gives us his take on the local digital TV situation, including potential channel availability should one of the Cleveland market stations wish to make a channel move...particularly the alleged CBS affiliate currently stuck on RF digital channel 10...

-----------------

Hello, all!

I'm Trip Ericson, the lunatic behind the website RabbitEars.Info, and I've penned this special guest feature on Ohio Media Watch to try to address some of the questions about WOIO and where they could move assuming they wanted to jump ship from channel 10.

This entire article will be written with the assumption that channel 31 is reserved for WJW, even though in reality, it's not. If WOIO was to take channel 31, then this article would apply to WJW just as well. Channel 31 is an open channel by all standards, and would solve the problem for one, but not both, of the VHF broadcasters in the market.

The big problem with all of this is that the FCC's interference rules are rather vicious. In the analog world, there were hard distance limits. If you were x miles away, your station fit. If you were x-1 miles away, your station did not fit. Very simple to understand and very logical.

In digital, the FCC requires a Longley-Rice interference study. The FCC rule is that your allotment cannot create more than 0.5% new interference to any one station. That is to say, you can cause 0.49% interference to station A, and 0.49% interference to station B, and still be within the rules.

The software to run these studies is made available on the FCC website but only runs on a specific computer system. Any other software to perform these studies costs many thousands of dollars, putting it out of the reach of many. I have a friend with access to some software to run these analyses, and had hoped to have him run some studies on WOIO for me, but as press time approaches, he has not been online since I decided to write this article.

Cleveland being where it is, so close to the Canadians, also makes this complicated. To start with, let's look at the Cleveland-area vacant allotments according to Canada:

Cleveland:
03 1024' 9 kW ND
05 1027' 9 kW ND
25 994' 67 kW ND
31 (Ignored)

Akron:
N/A

Canton:
39 958' 200 kW ND

Shaker Heights:
19 1151' 151 kW ND

Lorain:
43 1105' 170 kW ND

A few of these can be tossed out right away. 3 and 5, obviously, would be worse than 10 is now, and thus are removed from the list. 43 is useless due to proximity to WGGN-42, which would almost certainly be way, WAY above 0.5% interference. A signal on 25 would be crippled by KDKA in Pittsburgh and thus unable to adequately cover the area. So this leaves us with channels 19 and 39.

Now, these are just channels that the Canadians have already negotiated with the United States; there's nothing preventing more channels from being negotiated. Let's pull in some other channels to run through that might look good at first glance:

14, 18, 21, 27, 44, 51

Most of these can be tossed out right away:

14 and 18: These two look very clean, until you read through FCC regulations and learn they are reserved for "land mobile." That is, they're used for two-way communication in Pittsburgh among public safety and other licensees. There's a hard spacing rule of 155 miles that Cleveland simply does not meet.

21 and 44: Adjacent channel issues to WFMJ and WNEO aside, which would probably toss these two out right away, spacing to WMYD and WWJ in Detroit probably would do it too. I would not expect either of these allotments to work out.

19 and 51: These frequencies, though promising, have adjacent channel problems. 19 would likely fail with regard to WFMJ-20, and 51 would certainly fail with respect to WEAO-50. Thus, these channels are not under consideration.

At this point, we now see that what started out as a pretty interesting list of channels under consideration, is now narrowed down to two possibilities: Channels 27 or 39. Let's analyze them.

Channel 27: On the adjacent channels, we find WVIZ-26 and WUAB-28, both of which are co-located and thus would not cause any issues. This leaves us with co-channel concerns. WBGU on 27 is probably far enough away that a minor directional null would safely protect it, though this should be checked with an interference study. The big problem is CKCO-DT-3 in Sarnia, which is allotted 994' 810 kW. Even with a WKYC-style directional pattern, I'm not sure that the Canadians would be willing to accept a channel 27 in Cleveland.

Channel 39: This one is more promising than channel 27. The adjacent channels are more than 100 miles away, which means that interference to them should be minimal. There's a Class A at 92 miles that could be an issue, but an interference study would be needed to determine how much of a problem it would be. WADL is both directional away from Cleveland, and on a short tower, and I suspect would not be a problem. Plus, channel 39 already existed as an allotment for WDLI, so the chances of it working are good. My question would be just how much power they could run on 39. It's possible that it wouldn't be enough to satisfy them.

Now, I was staring at it for a while, and I came up with another possibility that might actually be superior to either channel 27 or 39, but I'm not sure how much of a problem it will cause.

Channel 33 caught my eye because it was clean except for a single Canadian station at 76 miles. CICO-TV-59 (analog 59/digital 33) is only allotted 492' 4 kW ND (that's not a typo) on channel 33. I don't know a lot about Canadian allotments, but unless I missed something, it looks like the currently unbuilt CICO-TV-59 digital signal could be moved from channel 33 to channel 20. This would actually reduce interference that it would receive from adjacent channels.

Relocating CICO-TV-59 would then open up channel 33 for use in Cleveland. The only concern would be to CICO-TV-32 in Windsor, allotted 703' 350 kW ND. A slight directional pattern might protect it if it's even an issue. I wonder what the Canadians would say to this proposal, given that the vacant but agreed upon channel 31 allotment is also adjacent to it. Perhaps WOIO could trade the current channel 19 analog antenna to CICO-TV-59 to use on channel 20 digital, assuming it's usable for that.

It seems perfectly logical. I suppose that's why it would never happen.

Ultimately, after all that study and analysis, the most certain answer I can give is "I don't know."

Without the ability to run an interference study, channel 39 looks the best, but that's no guarantee that it works in a satisfactory manner. I would suspect that if WOIO wanted to get off of channel 10 bad enough and they were not in the Canadian border zone, they could make it work regardless, but the Canadians are an unknown.

Finally, I'd like to direct readers to a project I've been working on. I have been teaching myself PHP through coding a project for RabbitEars. I put it in public beta last week and it's currently called the "DX Tool." I plan to change that name, as it's misleading in that it's not just for DXers.

I would like to ask readers of Ohio Media Watch who use over the air to consider trying out the DX Tool. By doing this, the DX Tool allows for the inversion of the reception reports to form a coverage map based on real world reports.

Sign up and submit reception reports for your local stations and maybe we can fill in this map with data showing just how bad reception is for WOIO, plus reception issues for WJW or maybe other stations as well can be shown on their own respective maps.

Thank you to Ohio Media Watch for giving me the opportunity to write this essay. Continue the great work!

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.