Here is a file that has all the TV transmitter records from the FCC database converted into a Google Earth file. It will let you visualize where all the TV transmitters are located relative to your location within the 3D world of Google Earth.

I'll try to maintain updates here and post additional tools & info for OTA seekers as things develop.



Content details:

FCC data was extracted on 6/20/2007
14,799 records were found
Icons were placed in separate Analog and Digital subfolders
Extracted record types include
- TV / DT
- Repeaters / Boosters
- Translators
- Special Temporary Authorities (STAs)
- Low Power TV / DT
Each icon is set to the elevation specified in the FCC database for 3D viewing



Change log:
20-Jun-2007
· Updated to latest snapshot of FCC database
· Fixes for KDEV and WKBW [thanks milehighmike]

24-May-2007
· Updated to latest snapshot of FCC database
· Fix for KMGH
· Added network affiliation to transmitter details

6-May-2007
· Updated to latest snapshot of FCC database
· Fixes for KCAH, KSPX, KYW, WWOR, and WNET

28-Apr-2007
· Updated to latest snapshot of FCC database
· Fixes for WGHP, KMMW-LP, K45HC, KCNC, KRMA, KUSA, and KTVD [thanks Calaveras and longrider]

16-Apr-2007
· Updated to latest snapshot of FCC database
· Fix for WWRD-LP and W66AQ [thanks Nitewatchman]

14-Apr-2007
· Updated to latest snapshot of FCC database
· Fix for W42CK [thanks Trip in VA]
· Changed callsign determination algorithm that fixed a lot of transmitters that were previously overlooked. This added 1,520 transmitters to the total collection.

10-Apr-2007
· Updated to latest snapshot of FCC database.
· Fixes for WJJA-TV and WYIN-TV [thanks sebenste]

1-Apr-2007
· Fixed software bug that caused several transmitters to be omitted. If you downloaded this file prior to today, I recommend that you download it again.

30-Mar-2007
· Updated to latest FCC database snapshot
· Now, clicking on a transmitter icon brings up a balloon with vital stats and a link to the FCC query



Requirements:

Google Earth 4.0 or later (free download from here (http://earth.google.com/download-earth.html))
A very good 3D graphics card
Lots of RAM
A fast internet connection



As an example, here is a view of the transmitter icons on Mt. Wilson looking down toward Los Angeles:
http://i221.photobucket.com/albums/dd262/andy_s_lee/tvfool/Mt_Wilson.jpg


Comments:

The FCC database is known to contain various errors including simple typos, outdated entries, future entries (license grants that haven't been built yet), erroneous technical details, a few missing entries, and some superfluous entries. Since this is essentially a capture of the FCC database, most of the same errors will show up here.


Despite the limitations of the source data, I believe this data set to be better than 95% accurate. If you know of any specific errors that should be corrected, please let me know so that future releases will contain the fix.


Setting the terrain exaggeration to 3 (max) in the Google Earth options makes it a lot easier to see the more subtle terrain variations. Just note that this also exaggerates the transmitter heights, so the exaggeration should be set back to 1 if you want the transmitter heights to have the correct relative altitude appearance.


There are a LOT of icons to display in this file. Trying to display all the transmitters on screen at one time can really slow down some computers and graphics cards. It might help to turn off the transmitter display first, zoom into an area of interest, and then turn the transmitter display back on. In this file, the transmitter display is initially turned off. The icons can be turned on via the check box next to the desired sub-folder.



Best regards,
Andy



P.S. AVS Forum does not allow attachments larger than 500KB and the latest Transmitter Icons file is now 507KB, so you'll need to go to www.tvfool.com (http://www.tvfool.com/index.php?option=com_content&task=view&id=16&Itemid=46) to download the latest file. Sorry for any inconvenience. I'm sure the file will come back down in size around the February 2009 shutdown of analog transmitters.

These are transmitter placemarks and coverage maps that have been created for viewing in Google Earth. Individual packages per metro will be made available here. The purpose of these files is to help you visualize the TV "environment" within the 3D virtual world of Google Earth and perhaps help you understand some of the factors that affect your ability to receive OTA broadcasts.

The result should be something like this:
http://i221.photobucket.com/albums/dd262/andy_s_lee/tvfool/WGN_Screen_Shot.jpg
With the full 3D capabilities of Google Earth, you can "fly around" and explore the transmitters and coverage maps interactively.



Requirements:

Google Earth 4.0 or later (free download from here (http://earth.google.com/download-earth.html))
A very good 3D graphics card
Lots of RAM
Fast internet connection
BitTorrent client for downloading the files

Note: To avoid burdening the forum servers and for better download speeds, I am distributing these files via BitTorrent. If you need help with downloading torrents, try reading this FAQ (http://www.utorrent.com/beginners-guide.php). Some popular free BitTorrent clients include
uTorrent (http://www.utorrent.com/) (Windows)
Azureus (http://azureus.sourceforge.net/) (Java, any platform)
BitTorrent/Mainline (http://www.bittorrent.com/) (Python, any platform)




If you are looking for a specific coverage map, you can try search through the master callsign list at tvfool.com (http://www.tvfool.com/index.php?option=com_content&task=view&id=31).

Metropolitan Statistical Areas (MSAs):

1. New York, NY - last updated 4-Jun-2007, 126 transmitters (59.7 MB download torrent (http://www.tvfool.com/kmz/torrent/New_York_NY.kmz.torrent))
2. Los Angeles, CA - last updated 4-Jun-2007, 169 transmitters (64.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Los_Angeles_CA.kmz.torrent))
3. Chicago, IL - last updated 4-Jun-2007, 88 transmitters (61.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Chicago_IL.kmz.torrent))
4. Washington D.C. - Baltimore, MD - last updated 4-Jun-2007, 91 transmitters (68.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Washington_Baltimore_MD.kmz.torrent))
5. San Francisco, CA - last updated 4-Jun-2007, 104 transmitters (83.3 MB download torrent (http://www.tvfool.com/kmz/torrent/San_Francisco_CA.kmz.torrent))
6. Philadelphia, PA - last updated 4-Jun-2007, 97 transmitters (55.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Philadelphia_PA.kmz.torrent))
7. Boston, MA - last updated 4-Jun-2007, 84 transmitters (64.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Boston_MA.kmz.torrent))
8. Detroit, MI - last updated 4-Jun-2007, 100 transmitters (83.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Detroit_MI.kmz.torrent))
9. Dallas - Ft. Worth, TX - last updated 4-Jun-2007, 57 transmitters (53.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Dallas_TX.kmz.torrent))
10. Houston, TX - last updated 4-Jun-2007, 63 transmitters (46.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Houston_TX.kmz.torrent))
11. Atlanta, GA - last updated 4-Jun-2007, 63 transmitters (41.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Atlanta_GA.kmz.torrent))
12. Miami - Ft. Lauderdale, FL - last updated 4-Jun-2007, 75 transmitters (28.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Miami_FL.kmz.torrent))
13. Seattle, WA - last updated 4-Jun-2007, 60 transmitters (41.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Seattle_WA.kmz.torrent))
14. Phoenix, AZ - last updated 4-Jun-2007, 59 transmitters (32.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Phoenix_AZ.kmz.torrent))
15. Minneapolis - St. Paul, MN - last updated 4-Jun-2007, 43 transmitters (50.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Minneapolis_MN.kmz.torrent))
16. Cleveland, OH - last updated 4-Jun-2007, 72 transmitters (49.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Cleveland_OH.kmz.torrent))
17. San Diego, CA - last updated 4-Jun-2007, 73 transmitters (22.4 MB download torrent (http://www.tvfool.com/kmz/torrent/San_Diego_CA.kmz.torrent))
18. St. Louis, MO - last updated 4-Jun-2007, 40 transmitters (37.8 MB download torrent (http://www.tvfool.com/kmz/torrent/St_Louis_MO.kmz.torrent))
19. Denver, CO - last updated 4-Jun-2007, 150 transmitters (69.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Denver_CO.kmz.torrent))
20. Tampa, FL - last updated 4-Jun-2007, 67 transmitters (30.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Tampa_FL.kmz.torrent))
21. Pittsburgh, PA - last updated 4-Jun-2007, 82 transmitters (52.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Pittsburgh_PA.kmz.torrent))
22. Portland, OR - last updated 4-Jun-2007, 100 transmitters (51.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Portland_OR.kmz.torrent))
23. Cincinnati, OH - last updated 4-Jun-2007, 54 transmitters (47.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Cincinnati_OH.kmz.torrent))
24. Sacramento, CA - last updated 4-Jun-2007, 69 transmitters (43.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Sacramento_CA.kmz.torrent))
25. Kansas City, MO - last updated 4-Jun-2007, 42 transmitters (43.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Kansas_City_MO.kmz.torrent))
26. Milwaukee, WI - last updated 4-Jun-2007, 74 transmitters (57.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Milwaukee_WI.kmz.torrent))
27. Orlando, FL - last updated 4-Jun-2007, 104 transmitters (57.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Orlando_FL.kmz.torrent))
28. Indianapolis, IN - last updated 4-Jun-2007, 52 transmitters (42.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Indianapolis_IN.kmz.torrent))
29. San Antonio, TX - last updated 4-Jun-2007, 83 transmitters (51.5 MB download torrent (http://www.tvfool.com/kmz/torrent/San_Antonio_TX.kmz.torrent))
30. Norfolk, VA - last updated 4-Jun-2007, 66 transmitters (42.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Norfolk_VA.kmz.torrent))
31. Las Vegas, NV - last updated 16-Jun-2007, 128 transmitters (35.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Las_Vegas_NV.kmz.torrent))
32. Columbus, OH - last updated 16-Jun-2007, 65 transmitters (47.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Columbus_OH.kmz.torrent))
33. Charlotte, NC - last updated 16-Jun-2007, 54 transmitters (45.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Charlotte_NC.kmz.torrent))
34. New Orleans, LA - last updated 16-Jun-2007, 63 transmitters (38.6 MB download torrent (http://www.tvfool.com/kmz/torrent/New_Orleans_LA.kmz.torrent))
35. Salt Lake City, UT - last updated 16-Jun-2007, 280 transmitters (57.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Salt_Lake_City_UT.kmz.torrent))
36. Greensboro, NC - last updated 16-Jun-2007, 67 transmitters (54.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Greensboro_NC.kmz.torrent))
37. Austin, TX - last updated 16-Jun-2007, 92 transmitters (59.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Austin_TX.kmz.torrent))
38. Nashville, TN - last updated 16-Jun-2007, 62 transmitters (43.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Nashville_TN.kmz.torrent))
39. Providence, RI - last updated 16-Jun-2007, 97 transmitters (72.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Providence_RI.kmz.torrent))
40. Raleigh, NC - last updated 16-Jun-2007, 76 transmitters (65.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Raleigh_NC.kmz.torrent))
41. Hartford, CT - last updated 16-Jun-2007, 90 transmitters (62.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Hartford_CT.kmz.torrent))
42. Buffalo, NY - last updated 16-Jun-2007, 91 transmitters (58.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Buffalo_NY.kmz.torrent))
43. Memphis, TN - last updated 16-Jun-2007, 61 transmitters (44.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Memphis_TN.kmz.torrent))
44. West Palm Beach, FL - last updated 16-Jun-2007, 79 transmitters (31.8 MB download torrent (http://www.tvfool.com/kmz/torrent/West_Palm_Beach_FL.kmz.torrent))
45. Jacksonville, FL - last updated 16-Jun-2007, 60 transmitters (32.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Jacksonville_FL.kmz.torrent))
46. Rochester, NY - last updated 16-Jun-2007, 103 transmitters (63.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Rochester_NY.kmz.torrent))
47. Grand Rapids, MI - last updated 16-Jun-2007, 70 transmitters (45.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Grand_Rapids_MI.kmz.torrent))
48. Oklahoma City, OK - last updated 16-Jun-2007, 64 transmitters (43.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Oklahoma_City_OK.kmz.torrent))
49. Louisville, KY - last updated 16-Jun-2007, 47 transmitters (37.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Louisville_KY.kmz.torrent))
50. Richmond, VA - last updated 16-Jun-2007, 73 transmitters (55.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Richmond_VA.kmz.torrent))
51. Greenville, SC - last updated 16-Jun-2007, 138 transmitters (62.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Greenville_SC.kmz.torrent))
52. Dayton, OH - last updated 16-Jun-2007, 89 transmitters (69.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Dayton_OH.kmz.torrent))
53. Fresno, CA - last updated 16-Jun-2007, 71 transmitters (36.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Fresno_CA.kmz.torrent))
54. Birmingham, AL - last updated 16-Jun-2007, 72 transmitters (47.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Birmingham_AL.kmz.torrent))
55. Honolulu, HI - last updated 16-Jun-2007, 33 transmitters ( 7.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Honolulu_HI.kmz.torrent))
56. Albany, NY - last updated 16-Jun-2007, 85 transmitters (46.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Albany_NY.kmz.torrent))
57. Tucson, AZ - last updated 16-Jun-2007, 37 transmitters (24.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Tucson_AZ.kmz.torrent))
58. Tulsa, OK - last updated 16-Jun-2007, 54 transmitters (37.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Tulsa_OK.kmz.torrent))
59. Syracuse, NY - last updated 16-Jun-2007, 112 transmitters (73.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Syracuse_NY.kmz.torrent))
60. Omaha, NE - last updated 16-Jun-2007, 71 transmitters (51.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Omaha_NE.kmz.torrent))
61. Albuquerque, NM - last updated 16-Jun-2007, 55 transmitters (46.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Albuquerque_NM.kmz.torrent))
62. Knoxville, TN - last updated 16-Jun-2007, 123 transmitters (47.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Knoxville_TN.kmz.torrent))
63. El Paso, TX - last updated 16-Jun-2007, 37 transmitters (22.5 MB download torrent (http://www.tvfool.com/kmz/torrent/El_Paso_TX.kmz.torrent))
64. Bakersfield, CA - last updated 16-Jun-2007, 106 transmitters (29.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Bakersfield_CA.kmz.torrent))
65. Allentown, PA - last updated 16-Jun-2007, 153 transmitters (82.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Allentown_PA.kmz.torrent))
66. Harrisburg, PA - last updated 16-Jun-2007, 96 transmitters (52.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Harrisburg_PA.kmz.torrent))
67. Scranton, PA - last updated 16-Jun-2007, 137 transmitters (52.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Scranton_PA.kmz.torrent))
68. Toledo, OH - last updated 16-Jun-2007, 86 transmitters (64.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Toledo_OH.kmz.torrent))
69. Baton Rouge, LA - last updated 16-Jun-2007, 92 transmitters (52.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Baton_Rouge_LA.kmz.torrent))
70. Youngstown, OH - last updated 16-Jun-2007, 107 transmitters (73.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Youngstown_OH.kmz.torrent))
71. Springfield, MA - last updated 16-Jun-2007, 120 transmitters (89.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Springfield_MA.kmz.torrent))
72. Sarasota, FL - last updated 16-Jun-2007, 85 transmitters (40.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Sarasota_FL.kmz.torrent))
73. Little Rock, AR - last updated 16-Jun-2007, 41 transmitters (38.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Little_Rock_AR.kmz.torrent))
74. McAllen, TX - last updated 16-Jun-2007, 38 transmitters (16.3 MB download torrent (http://www.tvfool.com/kmz/torrent/McAllen_TX.kmz.torrent))
75. Stockton, CA - last updated 16-Jun-2007, 101 transmitters (79.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Stockton_CA.kmz.torrent))
76. Charleston, SC - last updated 16-Jun-2007, 42 transmitters (22.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Charleston_SC.kmz.torrent))
77. Wichita, KS - last updated 16-Jun-2007, 27 transmitters (21.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Wichita_KS.kmz.torrent))
78. Mobile, AL - last updated 16-Jun-2007, 50 transmitters (29.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Mobile_AL.kmz.torrent))
79. Columbia, SC - last updated 16-Jun-2007, 47 transmitters (39.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Columbia_SC.kmz.torrent))
80. Colorado Springs, CO - last updated 16-Jun-2007, 109 transmitters (56.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Colorado_Springs_CO.kmz.torrent))
81. Fort Wayne, IN - last updated 16-Jun-2007, 67 transmitters (46.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Fort_Wayne_IN.kmz.torrent))
82. Daytona Beach, FL - last updated 16-Jun-2007, 67 transmitters (36.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Daytona_Beach_FL.kmz.torrent))
83. Lakeland, FL - last updated 16-Jun-2007, 117 transmitters (59.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Lakeland_FL.kmz.torrent))
84. Johnson City, TN - last updated 16-Jun-2007, 126 transmitters (47.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Johnson_City_TN.kmz.torrent))
85. Lexington, KY - last updated 16-Jun-2007, 42 transmitters (28.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Lexington_KY.kmz.torrent))
86. Augusta, GA - last updated 16-Jun-2007, 46 transmitters (36.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Augusta_GA.kmz.torrent))
87. Melbourne, FL - last updated 16-Jun-2007, 69 transmitters (34.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Melbourne_FL.kmz.torrent))
88. Lancaster, PA - last updated 2-May-2007, 105 transmitters (73.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Lancaster_PA.kmz.torrent))
89. Chattanooga, TN - last updated 2-May-2007, 58 transmitters (34.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Chattanooga_TN.kmz.torrent))
90. Des Moines, IA - last updated 2-May-2007, 44 transmitters (35.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Des_Moines_IA.kmz.torrent))
91. Kalamazoo, MI - last updated 2-May-2007, 93 transmitters (68.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Kalamazoo_MI.kmz.torrent))
92. Lansing, MI - last updated 2-May-2007, 114 transmitters (91.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Lansing_MI.kmz.torrent))
93. Modesto, CA - last updated 2-May-2007, 88 transmitters (59.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Modesto_CA.kmz.torrent))
94. Fort Myers, FL - last updated 2-May-2007, 41 transmitters (16.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Fort_Myers_FL.kmz.torrent))
95. Jackson, MS - last updated 2-May-2007, 46 transmitters (35.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Jackson_MS.kmz.torrent))
96. Boise City, ID - last updated 2-May-2007, 60 transmitters (36.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Boise_City_ID.kmz.torrent))
97. Madison, WI - last updated 2-May-2007, 80 transmitters (62.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Madison_WI.kmz.torrent))
98. Spokane, WA - last updated 7-May-2007, 70 transmitters (45.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Spokane_WA.kmz.torrent))
99. Pensacola, FL - last updated 7-May-2007, 55 transmitters (27.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Pensacola_FL.kmz.torrent))
100. Canton, OH - last updated 7-May-2007, 103 transmitters (70.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Canton_OH.kmz.torrent))
101. Saginaw, MI - last updated 7-May-2007, 64 transmitters (34.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Saginaw_MI.kmz.torrent))
102. Salinas, CA - last updated 7-May-2007, 49 transmitters (27.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Salinas_CA.kmz.torrent))
103. Santa Barbara, CA - last updated 7-May-2007, 71 transmitters (24.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Santa_Barbara_CA.kmz.torrent))
104. Shreveport, LA - last updated 7-May-2007, 62 transmitters (34.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Shreveport_LA.kmz.torrent))
105. Lafayette, LA - last updated 7-May-2007, 83 transmitters (41.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Lafayette_LA.kmz.torrent))
106. Beaumont, TX - last updated 7-May-2007, 57 transmitters (25.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Beaumont_TX.kmz.torrent))
107. York, PA - last updated 7-May-2007, 98 transmitters (74.5 MB download torrent (http://www.tvfool.com/kmz/torrent/York_PA.kmz.torrent))
108. Corpus Christi, TX - last updated 7-May-2007, 65 transmitters (23.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Corpus_Christi_TX.kmz.torrent))
109. Reading, PA - last updated 7-May-2007, 131 transmitters (78.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Reading_PA.kmz.torrent))
110. Rockford, IL - last updated 7-May-2007, 63 transmitters (40.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Rockford_IL.kmz.torrent))
111. Provo, UT - last updated 7-May-2007, 403 transmitters (66.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Provo_UT.kmz.torrent))
112. Visalia, CA - last updated 7-May-2007, 93 transmitters (45.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Visalia_CA.kmz.torrent))
113. Biloxi, MS - last updated 7-May-2007, 64 transmitters (39.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Biloxi_MS.kmz.torrent))
114. Davenport, IA - last updated 7-May-2007, 63 transmitters (48.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Davenport_IA.kmz.torrent))
115. Appleton, WI - last updated 7-May-2007, 39 transmitters (29.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Appleton_WI.kmz.torrent))
116. Peoria, IL - last updated 7-May-2007, 63 transmitters (56.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Peoria_IL.kmz.torrent))
117. Huntsville, AL - last updated 7-May-2007, 52 transmitters (28.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Huntsville_AL.kmz.torrent))
118. Hickory, NC - last updated 7-May-2007, 113 transmitters (65.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Hickory_NC.kmz.torrent))
119. Reno, NV - last updated 7-May-2007, 101 transmitters (29.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Reno_NV.kmz.torrent))
120. Brownsville, TX - last updated 7-May-2007, 35 transmitters (15.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Brownsville_TX.kmz.torrent))
121. Montgomery, AL - last updated 7-May-2007, 73 transmitters (50.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Montgomery_AL.kmz.torrent))
122. Springfield, MO - last updated 7-May-2007, 69 transmitters (42.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Springfield_MO.kmz.torrent))
123. Eugene, OR - last updated 7-May-2007, 134 transmitters (40.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Eugene_OR.kmz.torrent))
124. Macon, GA - last updated 7-May-2007, 43 transmitters (34.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Macon_GA.kmz.torrent))
125. Fort Pierce, FL - last updated 7-May-2007, 46 transmitters (17.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Fort_Pierce_FL.kmz.torrent))
126. Huntington, WV - last updated 7-May-2007, 45 transmitters (25.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Huntington_WV.kmz.torrent))
127. Killeen, TX - last updated 7-May-2007, 62 transmitters (43.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Killeen_TX.kmz.torrent))
128. Fayetteville, AR - last updated 7-May-2007, 89 transmitters (44.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Fayetteville_AR.kmz.torrent))
129. Fayetteville, NC - last updated 7-May-2007, 84 transmitters (76.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Fayetteville_NC.kmz.torrent))
130. Utica, NY - last updated 7-May-2007, 97 transmitters (64.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Utica_NY.kmz.torrent))
131. Evansville, IN - last updated 11-May-2007, 40 transmitters (30.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Evansville_IN.kmz.torrent))
132. New London, CT - last updated 11-May-2007, 102 transmitters (78.3 MB download torrent (http://www.tvfool.com/kmz/torrent/New_London_CT.kmz.torrent))
133. Savannah, GA - last updated 11-May-2007, 36 transmitters (20.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Savannah_GA.kmz.torrent))
134. Tallahassee, FL - last updated 11-May-2007, 64 transmitters (37.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Tallahassee_FL.kmz.torrent))
135. Erie, PA - last updated 11-May-2007, 52 transmitters (25.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Erie_PA.kmz.torrent))
136. Columbus, GA - last updated 11-May-2007, 46 transmitters (29.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Columbus_GA.kmz.torrent))
137. South Bend, IN - last updated 11-May-2007, 104 transmitters (83.8 MB download torrent (http://www.tvfool.com/kmz/torrent/South_Bend_IN.kmz.torrent))
138. Anchorage, AK* - last updated 11-May-2007, 84 transmitters (28.6 MB download torrent*)
139. Ocala, FL - last updated 11-May-2007, 86 transmitters (43.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Ocala_FL.kmz.torrent))
140. Binghamton, NY - last updated 11-May-2007, 121 transmitters (62.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Binghamton_NY.kmz.torrent))
141. Charleston, WV - last updated 11-May-2007, 49 transmitters (26.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Charleston_WV.kmz.torrent))
142. Fort Collins, CO - last updated 11-May-2007, 122 transmitters (55.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Fort_Collins_CO.kmz.torrent))
143. Naples, FL - last updated 11-May-2007, 32 transmitters (13.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Naples_FL.kmz.torrent))
144. Lincoln, NE - last updated 11-May-2007, 72 transmitters (51.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Lincoln_NE.kmz.torrent))
145. San Luis Obispo, CA - last updated 11-May-2007, 51 transmitters (21.2 MB download torrent (http://www.tvfool.com/kmz/torrent/San_Luis_Obispo_CA.kmz.torrent))
146. Duluth, MN - last updated 11-May-2007, 47 transmitters (36.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Duluth_MN.kmz.torrent))
147. Portland, ME - last updated 11-May-2007, 39 transmitters (26.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Portland_ME.kmz.torrent))
148. Lubbock, TX - last updated 11-May-2007, 78 transmitters (28.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Lubbock_TX.kmz.torrent))
149. Odessa, TX - last updated 11-May-2007, 59 transmitters (25.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Odessa_TX.kmz.torrent))
150. Roanoke, VA - last updated 11-May-2007, 66 transmitters (48.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Roanoke_VA.kmz.torrent))
151. Wilmington, NC - last updated 11-May-2007, 47 transmitters (30.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Wilmington_NC.kmz.torrent))
152. Johnstown, PA - last updated 11-May-2007, 94 transmitters (54.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Johnstown_PA.kmz.torrent))
153. Green Bay, WI - last updated 11-May-2007, 30 transmitters (28.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Green_Bay_WI.kmz.torrent))
154. Asheville, NC - last updated 11-May-2007, 155 transmitters (67.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Asheville_NC.kmz.torrent))
155. Yakima, WA - last updated 11-May-2007, 139 transmitters (53.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Yakima_WA.kmz.torrent))
156. Gainesville, FL - last updated 11-May-2007, 71 transmitters (33.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Gainesville_FL.kmz.torrent))
157. Amarillo, TX - last updated 11-May-2007, 92 transmitters (36.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Amarillo_TX.kmz.torrent))
158. Lynchburg, VA - last updated 11-May-2007, 63 transmitters (40.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Lynchburg_VA.kmz.torrent))
159. Waco, TX - last updated 11-May-2007, 75 transmitters (70.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Waco_TX.kmz.torrent))
160. Merced, CA - last updated 11-May-2007, 92 transmitters (53.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Merced_CA.kmz.torrent))
161. Longview, TX - last updated 11-May-2007, 44 transmitters (36.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Longview_TX.kmz.torrent))
162. Fort Smith, AR - last updated 11-May-2007, 59 transmitters (33.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Fort_Smith_AR.kmz.torrent))
163. Clarksville, TN - last updated 11-May-2007, 67 transmitters (47.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Clarksville_TN.kmz.torrent))
164. Chico, CA - last updated 11-May-2007, 84 transmitters (30.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Chico_CA.kmz.torrent))
165. Springfield, IL - last updated 11-May-2007, 49 transmitters (37.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Springfield_IL.kmz.torrent))
166. Myrtle Beach, SC - last updated 11-May-2007, 65 transmitters (45.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Myrtle_Beach_SC.kmz.torrent))
167. Houma, LA - last updated 11-May-2007, 61 transmitters (36.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Houma_LA.kmz.torrent))
168. Laredo, TX - last updated 11-May-2007, 16 transmitters ( 7.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Laredo_TX.kmz.torrent))
169. Richland, WA - last updated 11-May-2007, 105 transmitters (58.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Richland_WA.kmz.torrent))
170. Cedar Rapids, IA - last updated 19-May-2007, 48 transmitters (48.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Cedar_Rapids_IA.kmz.torrent))
171. Lake Charles, LA - last updated 19-May-2007, 78 transmitters (38.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Lake_Charles_LA.kmz.torrent))
172. Lafayette, IN - last updated 19-May-2007, 60 transmitters (47.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Lafayette_IN.kmz.torrent))
173. Elkhart, IN - last updated 19-May-2007, 68 transmitters (51.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Elkhart_IN.kmz.torrent))
174. Medford, OR - last updated 19-May-2007, 190 transmitters (45.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Medford_OR.kmz.torrent))
175. Champaign, IL - last updated 19-May-2007, 60 transmitters (44.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Champaign_IL.kmz.torrent))
176. Mansfield, OH - last updated 19-May-2007, 102 transmitters (75.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Mansfield_OH.kmz.torrent))
177. Tyler, TX - last updated 19-May-2007, 35 transmitters (21.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Tyler_TX.kmz.torrent))
178. Las Cruces, NM - last updated 19-May-2007, 87 transmitters (30.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Las_Cruces_NM.kmz.torrent))
179. Fargo, ND - last updated 19-May-2007, 29 transmitters (26.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Fargo_ND.kmz.torrent))
180. Sioux Falls, SD - last updated 19-May-2007, 60 transmitters (53.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Sioux_Falls_SD.kmz.torrent))
181. Fort Walton Beach, FL - last updated 19-May-2007, 89 transmitters (42.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Fort_Walton_Beach_FL.kmz.torrent))
182. Topeka, KS - last updated 19-May-2007, 56 transmitters (50.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Topeka_KS.kmz.torrent))
183. Burlington, VT - last updated 19-May-2007, 82 transmitters (68.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Burlington_VT.kmz.torrent))
184. St Cloud, MN - last updated 19-May-2007, 138 transmitters (91.0 MB download torrent (http://www.tvfool.com/kmz/torrent/St_Cloud_MN.kmz.torrent))
185. Bellingham, WA - last updated 19-May-2007, 44 transmitters (29.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Bellingham_WA.kmz.torrent))
186. Tuscaloosa, AL - last updated 19-May-2007, 68 transmitters (44.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Tuscaloosa_AL.kmz.torrent))
187. Redding, CA - last updated 19-May-2007, 111 transmitters (36.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Redding_CA.kmz.torrent))
188. Barnstable, MA - last updated 19-May-2007, 49 transmitters (39.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Barnstable_MA.kmz.torrent))
189. Benton Harbor, MI - last updated 19-May-2007, 97 transmitters (81.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Benton_Harbor_MI.kmz.torrent))
190. Yuma, AZ - last updated 19-May-2007, 37 transmitters (20.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Yuma_AZ.kmz.torrent))
191. Charlottesville, VA - last updated 19-May-2007, 99 transmitters (48.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Charlottesville_VA.kmz.torrent))
192. Jackson, MI - last updated 19-May-2007, 111 transmitters (93.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Jackson_MI.kmz.torrent))
193. Joplin, MO - last updated 19-May-2007, 81 transmitters (35.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Joplin_MO.kmz.torrent))
194. Lima, OH - last updated 19-May-2007, 82 transmitters (57.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Lima_OH.kmz.torrent))
195. Athens, GA - last updated 19-May-2007, 71 transmitters (41.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Athens_GA.kmz.torrent))
196. Wheeling, WV - last updated 19-May-2007, 99 transmitters (56.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Wheeling_WV.kmz.torrent))
197. Bryan, TX - last updated 19-May-2007, 38 transmitters (25.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Bryan_TX.kmz.torrent))
198. Janesville, WI - last updated 19-May-2007, 89 transmitters (63.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Janesville_WI.kmz.torrent))
199. Parkersburg, WV - last updated 19-May-2007, 61 transmitters (35.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Parkersburg_WV.kmz.torrent))
200. Bloomington, IL - last updated 19-May-2007, 56 transmitters (42.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Bloomington_IL.kmz.torrent))
201. Jacksonville, NC - last updated 19-May-2007, 41 transmitters (29.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Jacksonville_NC.kmz.torrent))
202. Terre Haute, IN - last updated 19-May-2007, 78 transmitters (60.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Terre_Haute_IN.kmz.torrent))
203. Eau Claire, WI - last updated 19-May-2007, 40 transmitters (30.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Eau_Claire_WI.kmz.torrent))
204. Panama City, FL - last updated 19-May-2007, 57 transmitters (23.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Panama_City_FL.kmz.torrent))
205. Santa Fe, NM - last updated 19-May-2007, 77 transmitters (49.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Santa_Fe_NM.kmz.torrent))
206. Monroe, LA - last updated 19-May-2007, 57 transmitters (33.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Monroe_LA.kmz.torrent))
207. Decatur, AL - last updated 19-May-2007, 84 transmitters (55.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Decatur_AL.kmz.torrent))
208. Rocky Mount, NC - last updated 19-May-2007, 61 transmitters (55.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Rocky_Mount_NC.kmz.torrent))
209. Florence, AL - last updated 19-May-2007, 70 transmitters (28.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Florence_AL.kmz.torrent))
210. Punta Gorda, FL - last updated 19-May-2007, 81 transmitters (39.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Punta_Gorda_FL.kmz.torrent))
211. Pueblo, CO - last updated 19-May-2007, 86 transmitters (31.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Pueblo_CO.kmz.torrent))
212. Wichita Falls, TX - last updated 19-May-2007, 72 transmitters (29.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Wichita_Falls_TX.kmz.torrent))
213. Jamestown, NY - last updated 19-May-2007, 70 transmitters (40.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Jamestown_NY.kmz.torrent))
214. Yuba City, CA - last updated 19-May-2007, 89 transmitters (50.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Yuba_City_CA.kmz.torrent))
215. Dothan, AL - last updated 19-May-2007, 82 transmitters (38.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Dothan_AL.kmz.torrent))
216. State College, PA - last updated 19-May-2007, 61 transmitters (29.0 MB download torrent (http://www.tvfool.com/kmz/torrent/State_College_PA.kmz.torrent))
217. Columbia, MO - last updated 19-May-2007, 41 transmitters (23.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Columbia_MO.kmz.torrent))
218. Greenville, NC - last updated 25-May-2007, 60 transmitters (51.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Greenville_NC.kmz.torrent))
219. Steubenville, OH - last updated 25-May-2007, 94 transmitters (56.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Steubenville_OH.kmz.torrent))
220. Texarkana, AR - last updated 25-May-2007, 47 transmitters (31.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Texarkana_AR.kmz.torrent))
221. Billings, MT - last updated 25-May-2007, 69 transmitters (30.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Billings_MT.kmz.torrent))
222. Altoona, PA - last updated 25-May-2007, 69 transmitters (40.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Altoona_PA.kmz.torrent))
223. Waterloo, IA - last updated 25-May-2007, 51 transmitters (48.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Waterloo_IA.kmz.torrent))
224. La Crosse, WI - last updated 25-May-2007, 49 transmitters (34.5 MB download torrent (http://www.tvfool.com/kmz/torrent/La_Crosse_WI.kmz.torrent))
225. Dover, DE - last updated 25-May-2007, 108 transmitters (65.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Dover_DE.kmz.torrent))
226. Abilene, TX - last updated 25-May-2007, 63 transmitters (28.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Abilene_TX.kmz.torrent))
227. Alexandria, LA - last updated 25-May-2007, 77 transmitters (43.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Alexandria_LA.kmz.torrent))
228. Wausau, WI - last updated 25-May-2007, 44 transmitters (33.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Wausau_WI.kmz.torrent))
229. Florence, SC - last updated 25-May-2007, 62 transmitters (43.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Florence_SC.kmz.torrent))
230. Glens Falls, NY - last updated 25-May-2007, 90 transmitters (47.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Glens_Falls_NY.kmz.torrent))
231. Rochester, MN - last updated 25-May-2007, 62 transmitters (47.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Rochester_MN.kmz.torrent))
232. Sioux City, IA - last updated 25-May-2007, 57 transmitters (50.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Sioux_City_IA.kmz.torrent))
233. Flagstaff, AZ - last updated 25-May-2007, 34 transmitters (19.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Flagstaff_AZ.kmz.torrent))
234. Albany, GA - last updated 25-May-2007, 83 transmitters (51.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Albany_GA.kmz.torrent))
235. Bloomington, IN - last updated 25-May-2007, 79 transmitters (67.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Bloomington_IN.kmz.torrent))
236. Sharon, PA - last updated 25-May-2007, 118 transmitters (78.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Sharon_PA.kmz.torrent))
237. Williamsport, PA - last updated 25-May-2007, 125 transmitters (54.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Williamsport_PA.kmz.torrent))
238. Muncie, IN - last updated 25-May-2007, 88 transmitters (73.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Muncie_IN.kmz.torrent))
239. Grand Junction, CO - last updated 25-May-2007, 199 transmitters (39.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Grand_Junction_CO.kmz.torrent))
240. Auburn, AL - last updated 25-May-2007, 60 transmitters (41.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Auburn_AL.kmz.torrent))
241. Lawton, OK - last updated 25-May-2007, 97 transmitters (38.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Lawton_OK.kmz.torrent))
242. Decatur, IL - last updated 25-May-2007, 57 transmitters (41.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Decatur_IL.kmz.torrent))
243. Goldsboro, NC - last updated 25-May-2007, 78 transmitters (65.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Goldsboro_NC.kmz.torrent))
244. Sheboygan, WI - last updated 25-May-2007, 55 transmitters (50.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Sheboygan_WI.kmz.torrent))
245. Anniston, AL - last updated 25-May-2007, 60 transmitters (35.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Anniston_AL.kmz.torrent))
246. Hattiesburg, MS - last updated 25-May-2007, 44 transmitters (18.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Hattiesburg_MS.kmz.torrent))
247. Iowa City, IA - last updated 25-May-2007, 72 transmitters (60.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Iowa_City_IA.kmz.torrent))
248. Sherman, TX - last updated 25-May-2007, 82 transmitters (60.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Sherman_TX.kmz.torrent))
249. Danville, VA - last updated 25-May-2007, 72 transmitters (58.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Danville_VA.kmz.torrent))
250. Jackson, TN - last updated 25-May-2007, 72 transmitters (41.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Jackson_TN.kmz.torrent))
251. Sumter, SC - last updated 25-May-2007, 49 transmitters (37.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Sumter_SC.kmz.torrent))
252. San Angelo, TX - last updated 25-May-2007, 52 transmitters (23.1 MB download torrent (http://www.tvfool.com/kmz/torrent/San_Angelo_TX.kmz.torrent))
253. Gadsden, AL - last updated 25-May-2007, 82 transmitters (49.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Gadsden_AL.kmz.torrent))
254. St Joseph, MO - last updated 25-May-2007, 40 transmitters (42.9 MB download torrent (http://www.tvfool.com/kmz/torrent/St_Joseph_MO.kmz.torrent))
255. Cumberland, MD - last updated 25-May-2007, 101 transmitters (45.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Cumberland_MD.kmz.torrent))
256. Kokomo, IN - last updated 25-May-2007, 60 transmitters (49.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Kokomo_IN.kmz.torrent))
257. Lawrence, KS - last updated 25-May-2007, 56 transmitters (49.9 MB download torrent (http://www.tvfool.com/kmz/torrent/Lawrence_KS.kmz.torrent))
258. Grand Forks, ND - last updated 25-May-2007, 23 transmitters (29.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Grand_Forks_ND.kmz.torrent))
259. Missoula, MT - last updated 25-May-2007, 68 transmitters (17.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Missoula_MT.kmz.torrent))
260. Bismarck, ND - last updated 25-May-2007, 28 transmitters (21.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Bismarck_ND.kmz.torrent))
261. Owensboro, KY - last updated 25-May-2007, 54 transmitters (36.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Owensboro_KY.kmz.torrent))
262. Elmira, NY - last updated 4-Jun-2007, 128 transmitters (51.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Elmira_NY.kmz.torrent))
263. Bangor, ME - last updated 4-Jun-2007, 44 transmitters (28.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Bangor_ME.kmz.torrent))
264. Lewiston, ME - last updated 4-Jun-2007, 39 transmitters (27.4 MB download torrent (http://www.tvfool.com/kmz/torrent/Lewiston_ME.kmz.torrent))
265. Dubuque, IA - last updated 4-Jun-2007, 59 transmitters (58.8 MB download torrent (http://www.tvfool.com/kmz/torrent/Dubuque_IA.kmz.torrent))
266. Rapid City, SD - last updated 4-Jun-2007, 39 transmitters (30.2 MB download torrent (http://www.tvfool.com/kmz/torrent/Rapid_City_SD.kmz.torrent))
267. Pittsfield, MA - last updated 4-Jun-2007, 94 transmitters (65.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Pittsfield_MA.kmz.torrent))
268. Pine Bluff, AR - last updated 4-Jun-2007, 37 transmitters (33.6 MB download torrent (http://www.tvfool.com/kmz/torrent/Pine_Bluff_AR.kmz.torrent))
269. Victoria, TX - last updated 4-Jun-2007, 48 transmitters (13.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Victoria_TX.kmz.torrent))
270. Jonesboro, AR - last updated 4-Jun-2007, 61 transmitters (37.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Jonesboro_AR.kmz.torrent))
271. Cheyenne, WY - last updated 4-Jun-2007, 73 transmitters (26.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Cheyenne_WY.kmz.torrent))
272. Great Falls, MT - last updated 4-Jun-2007, 46 transmitters (23.0 MB download torrent (http://www.tvfool.com/kmz/torrent/Great_Falls_MT.kmz.torrent))
273. Corvallis, OR - last updated 4-Jun-2007, 126 transmitters (62.5 MB download torrent (http://www.tvfool.com/kmz/torrent/Corvallis_OR.kmz.torrent))
274. Pocatello, ID - last updated 4-Jun-2007, 157 transmitters (38.7 MB download torrent (http://www.tvfool.com/kmz/torrent/Pocatello_ID.kmz.torrent))
275. Casper, WY - last updated 4-Jun-2007, 24 transmitters (19.1 MB download torrent (http://www.tvfool.com/kmz/torrent/Casper_WY.kmz.torrent))
276. Enid, OK - last updated 4-Jun-2007, 67 transmitters (44.3 MB download torrent (http://www.tvfool.com/kmz/torrent/Enid_OK.kmz.torrent))


* The Anchorage coverage maps are not valid because the SRTM terrain data does not extend above 60 degrees north latitude



Change log:
21-Oct-2007
· Fixed broken links

16-Jun-2007
· Updated Las Vegas, Columbus, Charlotte, New Orleans, Salt Lake City, Greensboro, Austin, Nashville, Providence, Raleigh, Hartford, Buffalo, Memphis, West Palm Beach, Jacksonville, Rochester, Grand Rapids, Oklahoma City, Louisville, Richmond, Greenville, Dayton, Fresno, Birmingham, Honolulu, Albany, Tucson, Tulsa, Syracuse, Omaha, Albuquerque, Knoxville, El Paso, Bakersfield, Allentown, Harrisburg, Scranton, Toledo, Baton Rouge, Youngstown, Springfield, Sarasota, Little Rock, McAllen, Stockton, Charleston, Wichita, Mobile, Columbia, Colorado Springs, Fort Wayne, Daytona Beach, Lakeland, Johnson City, Lexington, Augusta, and Melbourne MSAs
· Updates include fixes for some transmitter records, the inclusion of network affiliation in the information balloons, other feature enhancements that have been added in recent weeks, and any updates that have been entered into the FCC database

4-Jun-2007
· Added Elmira, Bangor, Lewiston, Dubuque, Rapid City, Pittsfield, Pine Bluff, Victoria, Jonesboro, Cheyenne, Great Falls, Corvallis, Pocatello, Casper, and Enid MSAs
· Updated New York, Los Angeles, Chicago, Washington Baltimore, San Francisco, Philadelphia, Boston, Detroit, Dallas, Houston, Atlanta, Miami, Seattle, Phoenix, Minneapolis, Cleveland, San Diego, St Louis, Denver, Tampa, Pittsburgh, Portland, Cincinnati, Sacramento, Kansas City, Milwaukee, Orlando, Indianapolis, San Antonio, and Norfolk MSAs
· Updates include fixes for some transmitter records, the inclusion of network affiliation in the information balloons, other feature enhancements that have been added in recent weeks, and any updates that have been entered into the FCC database

25-May-2007
· Added Greenville, Steubenville, Texarkana, Billings, Altoona, Waterloo, La Crosse, Dover, Abilene, Alexandria, Wausau, Florence, Glens Falls, Rochester, Sioux City, Flagstaff, Albany, Bloomington, Sharon, Williamsport, Muncie, Grand Junction, Auburn, Lawton, Decatur, Goldsboro, Sheboygan, Anniston, Hattiesburg MS, Iowa City, Sherman, Danville, Jackson, Sumter, San Angelo, Gadsden, St Joseph, Cumberland, Kokomo, Lawrence, Grand Forks, Missoula, Bismarck, and Owensboro MSAs

19-May-2007
· Added Cedar Rapids, Lake Charles, Lafayette, Elkhart, Medford, Champaign, Mansfield, Tyler, Las Cruces, Fargo, Sioux Falls, Fort Walton Beach, Topeka, Burlington, St. Cloud, Bellingham, Tuscaloosa, Redding, Barnstable, Benton Harbor, Yuma, Charlottesville, Jackson, Joplin, Lima, Athens, Wheeling, Bryan, Janesville, Parkersburg, Bloomington, Jacksonville, Terre Haute, Eau Claire, Panama City, Santa Fe, Monroe, Decatur, Rocky Mount, Florence, Punta Gorda, Pueblo, Wichita Falls, Jamestown, Yuba City, Dothan, State College, and Columbia MSAs

11-May-2007
· Added Evansville, New London, Savannah, Tallahassee, Erie, Columbus, South Bend, Anchorage, Ocala, Binghamton, Charleston, Fort Collins, Naples, Lincoln, San Luis Obispo, Duluth, Portland, Lubbock, Odessa, Roanoke, Wilmington, Johnstown, Green Bay, Asheville, Yakima, Gainesville, Amarillo, Lynchburg, Waco, Merced, Longview, Fort Smith, Clarksville, Chico, Springfield, Myrtle Beach, Houma, Laredo, and Richland MSAs

7-May-2007
· Added Spokane, Pensacola, Canton, Saginaw, Salinas, Santa Barbara, Shreveport, Lafayette, Beaumont, York, Corpus Christi, Reading, Rockford, Provo, Visalia, Biloxi, Davenport, Appleton, Peoria, Huntsville, Hickory, Reno, Brownsville, Montgomery, Springfield, Eugene, Macon, Fort Pierce, Huntington, Killeen, Fayetteville AR, Fayetteville NC, and Utica MSAs

2-May-2007
· Added Daytona Beach, Lakeland, Johnson City, Lexington, Augusta, Melbourne, Lancaster, Chattanooga, Des Moines, Kalamazoo, Lansing, Modesto, Fort Myers, Jackson, Boise City, and Madison MSAs
· Harrisburg_PA.kmz had a corrupted coverage map overlay for WHP-DT, so a fixed version of the file has been posted. If you have a corrupted version of the file, please delete it and download the fully working version. Torrent seeders should also delete the old torrent+data and get the new one.

28-Apr-2007
· Added Allentown, Harrisburg, Scranton, Toledo, Baton Rouge, Youngstown, Springfield, Sarasota, Little Rock, McAllen, Stockton, Charleston, Wichita, Mobile, Columbia, Colorado Springs, and Fort Wayne MSAs

26-Apr-2007
· Added Greenville, Dayton, Fresno, Birmingham, Honolulu, Albany, Tucson, Tulsa, Syracuse, Omaha, Albuquerque, Knoxville, El Paso, and Bakersfield MSAs

19-Apr-2007
· Added Austin, Nashville, Providence, Raleigh, Hartford, Buffalo, Memphis, West Palm Beach, Jacksonville, Rochester, Grand Rapids, Oklahoma City, Louisville, and Richmond MSAs

16-Apr-2007
· Added Las Vegas, Columbus, Charlotte, New Orleans, Salt Lake City, and Greensboro MSAs
· Fixed callsign parsing such that some previously missed transmitters are now included

11-Apr-2007
· Added Pittsburgh, Portland, Cincinnati, Sacramento, Kansas City, Milwaukee, Orlando, Indianapolis, San Antonio, and Norfolk MSAs.

6-Apr-2007
· Fixed bug causing several transmitters to be left out of each set. For all the latest, please download the file(s) again.
· Added Atlanta, Miami-Ft. Lauderdale, Seattle, Phoenix, Minneapolis-St. Paul, Cleveland, San Diego, St. Louis, Denver, and Tampa MSAs.
· Dallas_FtWorth filenames have been shortened to just Dallas.
· MSA centroids have been re-defined according to US Census Bureau standards, so the included set of transmitters per metro may have changed.

30-Mar-2007
· Added Houston MSA

29-Mar-2007
· Updated Chicago with new enhancements and some additional transmitters
· Added Washington-Baltimore, San Francisco, Philadelphia, Boston, Detroit, and Dallas-Ft. Worth MSAs.

28-Mar-2007
· Added New York and Los Angeles packages. Chicago package remains the same (to be updated soon).
· Clicking on a transmitter icon now brings up a balloon filled with key vitals and a link to the FCC. Any packages released after today should include this enhancement.




About the maps:

They DO take into account the transmitter power, antenna pattern, and height (according to the FCC)
They DO account for propagation losses due to terrain
They DO account for curvature of the Earth
They represent the expected signal strength near ground level
They DO NOT take into account your antenna gain, amps, elevated installation, or receiver sensitivity
They DO NOT account for building obstructions or indoor penetration
They DO NOT account for multipath


In very rough terms, the colors can be broken down as follows (not related to Antennaweb):

- White is extremely strong. Beware of signal overload on amps.
- Red-yellow-green are all quite strong. You can expect reasonable coverage with an indoor antenna.
- Cyan is where it's advisable to move the antenna up to the second floor or attic.
- Blue is where it's probably necessary to install a good antenna on the roof.
- Purple is quite weak and you really have to work at it for any chance of reception.

Please understand that this is a simulation and can only be treated as a rough approximation. Reception at your location is affected by many factors such as multipath, antenna gain, receiver sensitivity, buildings, and trees - which are not taken into account. Your mileage may vary.


Additional comments:

The coverage maps are not initially turned on when the file is loaded. You need to expand the folders to select the coverage maps to view.


The terrain variations are easier to see if you set the terrain exaggeration to 3 (max) in the Google Earth options.


FYI, the standard coverage maps are created with roughly 500 meter resolution at ground level. In order to truly understand the reception issues at a particular location (e.g., the roof of your house), it's better to look at an analysis such as a radar plot (http://www.tvfool.com/index.php?option=com_content&task=view&id=13&Itemid=45) since it is simulated at much higher resolution and is specific to a location in 3D space (lat, lon, and height). On a single page, you can simultaneously see the signal strength of all nearby channels for your exact location.
http://www.tvfool.com/images/radar_thumb.png (http://www.tvfool.com/index.php?option=com_content&task=view&id=13&Itemid=45)


If you notice any errors, please let me know. If any data has been incorrectly extracted from the FCC database, they should be corrected for future simulations.


Best regards,
Andy

Great idea.

This is a terrific addition to GoogleEarth...although it would help if the display box listed
the real channel number...and maybe ERP...and a link to FCC dB....

At first glance, looks okay for L.A., Riverside, San Diego & Tijuana.

However, I couldn't find K47FL in FCC TVQ database.
(Colocated with KDUG-LP, a few miles NE of Murrietta, CA).

Historic Call Search feature in www.fccinfo.com revealed K47FL to be K12PO,
which is in the FCC database.

FYI: My son receives K12PO (on CH12) as a low power repeater for San Diego's KUSI,
so I'm familiar with it's location....thankfully in VHF band, cuz it would overload his UHF Preamp....

This shotgun approach to station location is a real pain.....
At least we can now readily see where these potential problems are located.....

Nice. I had been using Google Earth to map the transmitters in my area. Assuming yours is accurate, it is apparent that I suck at the Internet. ;) KIMT and KYIN for example - I had both transmitters marked but one as KIMT and the other as KYIN, whereas your list has one marked as their digital transmitters and the other for their analog.

There are a LOT of transmitters marked in the file. I would advise those with slightly slower machines or with less than 1GB of memory to not turn on the listing until you zoom in to your general area first. Makes things much quicker.

Thanks for making the file available!

Perhaps break it up into ten different sections???

Looks great. From what I know about VA : tidewater, NoVa, SW all work.
Thanks for all the effort.

Great idea, and thanks for putting it together.

...it would help if the display box listed the real channel number...and maybe ERP...and a link to FCC dB....
That's a great idea! Consider it done in the next update.



However, I couldn't find K47FL in FCC TVQ database. (Colocated with KDUG-LP, a few miles NE of Murrietta, CA).

Historic Call Search feature in www.fccinfo.com revealed K47FL to be K12PO, which is in the FCC database.
Thanks for catching this!

I looked into this and in order to fix it, I would need to pull in the FCC's call sign tracking database, which I do not currently do. Apparently, the callsign database gets updated without corresponding indicators in all the other databases, so I'll need to do an extra level of cross-referencing to get the real callsign. For now, it means that any callsigns that have been renamed since the last recorded transmitter application (license, construction permit, STA, etc.) will have it's old callsign instead of the latest one. This will go on the to-do list pending other changes I have in the works.



This shotgun approach to station location is a real pain.....
At least we can now readily see where these potential problems are located.....
The next file will have the callsigns sorted in alphabetical order. At least that will make it easier to locate a specific channel.



Best regards,
Andy

Perhaps break it up into ten different sections???
I think I'll follow a plan of making coverage maps (plus transmitter icons) for the major MSAs. This would let people pick the specific transmitters and maps for their area without having to view all the transmitters at one time.

I will probably still maintain the nation-wide transmitter-only file for those people who don't need the maps since that file is small by itself. In regards to making multiple regional versions, I'll have to think about it some more. For now my energy is focused on improving the map generation software.

If you have any great ideas about how the nation-wide database should be split, please let me know.

Best regards,
Andy

KIMT and KYIN for example - I had both transmitters marked but one as KIMT and the other as KYIN, whereas your list has one marked as their digital transmitters and the other for their analog.
I wouldn't necessarily assume my data is correct because all I do is snarf the FCC's database from their web site. The FCC database are full of little mistakes, missing data, and multiple records per callsign (with no clear way of telling which one is actually the correct one), so my software has to make several assumptions and "guess" which records to believe and use. It's always good to check against more definitive sources (like talking to the broadcast engineer) to fix any errors.

If anyone reports corrections back to me, I will add it to my set of FCC "overrides" so that all future output will use the fixed data (all my tools use the same TV database parsing routines -- transmitter lists, coverage maps, radar plots, etc.).

Best regards,
Andy

...

If you have any great ideas about how the nation-wide database should be split, please let me know.

Best regards,
Andy

What about splitting by station class: full power analog & digital, Class A & LP, and then translators as a third layer.

What about splitting by station class: full power analog & digital, Class A & LP, and then translators as a third layer.
Analog and digital should be distinct. Some people are looking for digital-only, and others are looking for analog-only (until 2009 anyway). Aside from that the maintainer of the file won't have to make another special release just because the analogs get shut off.

Thanks everyone for all the great comments and suggestions. Just so you know, I've revised Post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) to include new packages for New York and Los Angeles coverage maps.

Have fun!

Best regards,
Andy

Thanks everyone for all the great comments and suggestions. Just so you know, I've revised Post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) to include new packages for New York and Los Angeles coverage maps.

Have fun!

Best regards,
Andy

Hi Andy,

Nice. Check your private messages; I'd be happy to host the Chicago DMA one. Could you send it to me (read your PM I sent ya). Thanks for doing this! Can I put in a request for Rockford and Milwaukee? Rockford won't take long. :D

Hi Andy,

Nice. Check your private messages; I'd be happy to host the Chicago DMA one. Could you send it to me (read your PM I sent ya). Thanks for doing this! Can I put in a request for Rockford and Milwaukee? Rockford won't take long. :D
Gilbert,

I sent the Chicago file (from last week, not the new one I'm about to post) to your email address already. It should have been in your inbox on Monday. If you didn't receive it, I wonder if it was because of the 14 MB attachment.

When the updated Chicago file is ready, I'll send it to the same address, but this time the file will be even bigger. If you have any alternative places to send the file, I can try that too. If all else fails, you can always try downloading it via BiTorrent.

I think the new Chicago file will be ready tonight, so I'll give it a try.

Best regards,
Andy

Gilbert,

I sent the Chicago file (from last week, not the new one I'm about to post) to your email address already. It should have been in your inbox on Monday. If you didn't receive it, I wonder if it was because of the 14 MB attachment.

When the updated Chicago file is ready, I'll send it to the same address, but this time the file will be even bigger. If you have any alternative places to send the file, I can try that too. If all else fails, you can always try downloading it via BiTorrent.

I think the new Chicago file will be ready tonight, so I'll give it a try.

Best regards,
Andy

Looks like my spamcatcher ate it. I sent you a private PM. Thanks for doing this!

FYI, the top 10 MSA coverage maps have been made available in post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) . I also took the liberty of updating the FCC database in post #1 (http://www.avsforum.com/avs-vb/showthread.php?p=10061605&&#post10061605) to include today's FCC data (3/30) plus the added transmitter data in the pop-up balloon when an icon is clicked.

Best regards,
Andy

Very, very cool stuff here. Thanks for putting it together!

I was looking at the Washington-Baltimore kmz file and it is missing a number of local stations such WTTG-DT Fox 5 (DT 36) and WUSA-DT CBS 9 (DT 34) both at 1000 kW. Was this intended to be a sample list of selected stations? Or were they overlooked when extracting stations from the FCC database?

I see what appears to be a typo entry: WJAL (DT 39) which looks to be an old lower power entry for WJLA-DT ABC 7 (DT 39) which is currently at 1000 kW. WDCA 50 has changed it's call letters to WDCW CW 50, but obviously changing call letters makes it hard to track through the database.

WHUT-DT PBS 32 (DT 33) is in the FCC database and is authorized to go at 100 kW, but is not on the air digitally - at all However, it should be included so people can see the reception map for it whenever it finally does go live.

Digital stations that I see missing from the DC-Baltimore list:
WMPB MPT 67, DT=29 Baltimore
WUSA CBS 9, DT=34 Washington
WTTG Fox 5, DT=36, Washington
WNUV CW 54, DT=40, Baltimore
WUTB MNT 24, DT=41, Baltimore <-- Station is still at STA power of 530 watts, love to see the coverage map for 530 watts. :D
WMPT MPT 22, DT=42, Annapolis or Owings Mills, MD
WPXW Ion/Pax 66, DT=43, Manassas, VA
WWPB MPT 31, DT=44, Hagerstown, MD (may not fall into the DMA)
WBFF Fox 45, DT=46, Baltimore
WNVC Mhz 57, DT=57, Fairfax, VA

You can also check the 1st post in the Washington-Baltimore thread for a list of the digital stations in the area, so maybe my list is redundant. There are enough people who live in the fringes of the greater Washington-Baltimore area that these maps will be very useful. Again, thanks for going to the trouble to do this!!!

Thanks for the Philly area. I second the very, very cool stuff comment.

- Can you explain the color mapping, e.g. what are the signal levels for each color and units (dBuV)?
- Can you give some insight as to how you processed the database?

Some missing digital stations:
WNJS-DT, channel 22, 197 kW, HAAT = 266 m, Camden NJ (east of Philadelphia)
WNJT-DT, channel 43, 46 kW, HAAT = 46m, Trenton NJ (northeast of Philadelphia)

We're using a 100 km radius for Philadelphia area local coverage. The FCC query: http://www.fcc.gov/fcc-bin/tvq?state=&call=&arn=&city=&chan=&cha2=69&serv=&type=0&facid=&list=2&dist=100&dlat2=39&mlat2=57&slat2=7&dlon2=75&mlon2=9&slon2=51&size=9

I was looking at the Washington-Baltimore kmz file and it is missing a number of local stations such WTTG-DT Fox 5 (DT 36) and WUSA-DT CBS 9 (DT 34) both at 1000 kW. Was this intended to be a sample list of selected stations? Or were they overlooked when extracting stations from the FCC database?

I see what appears to be a typo entry: WJAL (DT 39) which looks to be an old lower power entry for WJLA-DT ABC 7 (DT 39) which is currently at 1000 kW. WDCA 50 has changed it's call letters to WDCW CW 50, but obviously changing call letters makes it hard to track through the database.

WHUT-DT PBS 32 (DT 33) is in the FCC database and is authorized to go at 100 kW, but is not on the air digitally - at all However, it should be included so people can see the reception map for it whenever it finally does go live.

Digital stations that I see missing from the DC-Baltimore list:
WMPB MPT 67, DT=29 Baltimore
WUSA CBS 9, DT=34 Washington
WTTG Fox 5, DT=36, Washington
WNUV CW 54, DT=40, Baltimore
WUTB MNT 24, DT=41, Baltimore <-- Station is still at STA power of 530 watts, love to see the coverage map for 530 watts. :D
WMPT MPT 22, DT=42, Annapolis or Owings Mills, MD
WPXW Ion/Pax 66, DT=43, Manassas, VA
WWPB MPT 31, DT=44, Hagerstown, MD (may not fall into the DMA)
WBFF Fox 45, DT=46, Baltimore
WNVC Mhz 57, DT=57, Fairfax, VA

You can also check the 1st post in the Washington-Baltimore thread for a list of the digital stations in the area, so maybe my list is redundant. There are enough people who live in the fringes of the greater Washington-Baltimore area that these maps will be very useful. Again, thanks for going to the trouble to do this!!!
It looks like most, if not all, of the missing transmitters you're reporting are due to a bug in my code. My analysis shows that about 800 transmitters (out of about 13,000) were being omitted at a particular stage in the processing, causing them to be left out of the final MSA package. I've corrected the problem, but I'll need to re-process the metros and post new files.

For the changed callsigns that you mentioned, it looks like both old and new callsigns are entered and still marked valid in the FCC database. I will leave both old and new callsigns in the file for now since it looks like there are substantially different transmitter specifications for some of them. Until I can figure out how to properly filter out the invalid entries, I'll continue to include all records marked as "current" in the FCC database.

I'll post a new set of files in a couple of days (mostly due to processing time), so I hope you'll be able to check the new file once it's available. The FCC database ftp site also seems to be down at the moment.

I'm also putting in the "override" for WUTB at 530 Watts. Their STA is 5 years old! If you find out that they've gone to full power, please let me know so that I can revise my collection of FCC database "patches".



Thanks for uncovering all these errors! Please check back for updates in a few days.



Best regards,
Andy

- Can you explain the color mapping, e.g. what are the signal levels for each color and units (dBuV)?
Since I use a more conservative version of Longley-Rice propagation than the FCC, I can't give a direct mapping to the FCC's levels. FYI, in the L-R models, I use F(99,99) as opposed to F(50,90), used by the FCC (if you don't do any RF modeling, then you don't need to care about this). I hope that the following three-part answer will help a little in understanding the maps.

1) If you're comparing these maps with the FCC's contour maps, then the UHF DTV 41 dBu curve will be right around the cyan colored band. For high VHF, the FCC's DTV 36 dBu curve should be between the cyan and green bands. For low VHF, the FCC's DTV 28 dBu curve should be right around the green band. I think you'll find these levels match the FCC service contours pretty well, except that these maps follow the terrain details more accurately.

2) If you're interested in estimating OTA reception ease/difficulty, I'd roughly break it down into the following groups. White-red-yellow-green are all quite strong and I would expect reasonable indoor coverage. Cyan is where it's advisable to move the antenna up to the second floor or attic. Blue is where it's probably necessary to install a good antenna on the roof. Purple is quite weak and is where DXers or dedicated OTA enthusiasts need to work at getting their signal. Of course, these are very rough estimates since multipath, antenna gain, receiver sensitivity, buildings, trees, and other effects are not factored into the simulation.

3) Technically, the maps represent signal levels about 15 to 20 dB lower than what the FCC uses because of the difference in modeling parameters. My own test experience has shown that the FCC modeling parameters are too optimistic, and other "experts" and organizations have come to similar conclusions as well. I've found the F(99,99) parameters to track reality much better. In the end, this doesn't make all that much difference (other than a level shift) because even if the FCC used the same modeling parameters, they simply would have selected a different threshold value (e.g., instead of 41 dBu, they might have used 25 dBu).



- Can you give some insight as to how you processed the database?
I download the CDBS files from the FCC web (or ftp) site. That comes as several individual files that "sort-of" make a relational database. I parse those files, making the necessary cross-references, and then try to extract the records that I believe are the best representation of the real world. The hueristics for guessing the right records is the tricky part since many transmitters have multiple records and there's limited information available about things like STA extension dates, construction dates, etc.

The two key pieces that come out of the CDBS files are 1) transmitter details (i.e., channel, power, height, antenna rotation, etc.), and 2) the antenna pattern used.

<<< off-topic alert >>>
BTW, it's an often overlooked fact that many coordinates in the FCC database are specified in NAD27 coordinates instead of WGS84. If the coordinates are not converted, this could lead to position errors of up to a couple hundred meters depending on location.
<<< end off-topic alert >>>



Some missing digital stations:
WNJS-DT, channel 22, 197 kW, HAAT = 266 m, Camden NJ (east of Philadelphia)
WNJT-DT, channel 43, 46 kW, HAAT = 46m, Trenton NJ (northeast of Philadelphia)

We're using a 100 km radius for Philadelphia area local coverage. The FCC query: http://www.fcc.gov/fcc-bin/tvq?state=&call=&arn=&city=&chan=&cha2=69&serv=&type=0&facid=&list=2&dist=100&dlat2=39&mlat2=57&slat2=7&dlon2=75&mlon2=9&slon2=51&size=9
I believe the missing stations are due to a bug recently discovered. See my earlier post for a bit more of an explanation. Check back in a couple days and I'll probably have a new set of files available that fix the oversight.



Best regards,
Andy

I tried to download your file and Google Earth is giving me a permission denied error when I try to open it, any ideas? I'm using XP, logged in with Admin rights.

any ideas? I'm using XP
"fdisk". ;)

But seriously, when one OS doesn't do what you want it to do having a dual (or triple or quad or more) boot system is very useful.

I tried to download your file and Google Earth is giving me a permission denied error when I try to open it, any ideas? I'm using XP, logged in with Admin rights.

Hey Matt. It will probably help you get your question answered if you were to specify which file you were trying to load into Google Earth. ;)

Rudy

mjones73 - The error message is not correct, it's a path problem and can't find the file. I had the same problem with the transmitter file from Post #1.

Put the .kmz file into Google Earth's default folder, e.g. c:\Program Files\Google\Google Earth\ and in "My Documents". One of those 2 folders is the correct one- will sort that out later. Restart, problem gone (fingers crossed).

Update: After you open the .kmz file, it goes to the "Temporary Places" folder. Right-click on the "Temporary Places" folder and select "Save to My Places." To make it permanent, select File-> Save My Places. This will save everything to the default "My Places" folder: C:\Documents and Settings\<username>\Application Data\Google\GoogleEarth.

mjones73 - The error message is not correct, it's a path problem and can't find the file.
So that's what that was. After I got a similar message I just went to File->Open and it worked that way.

I'll post a new set of files in a couple of days (mostly due to processing time), so I hope you'll be able to check the new file once it's available. The FCC database ftp site also seems to be down at the moment.

I'm also putting in the "override" for WUTB at 530 Watts. Their STA is 5 years old! If you find out that they've gone to full power, please let me know so that I can revise my collection of FCC database "patches".

Thanks for uncovering all these errors! Please check back for updates in a few days.
Does the FCC periodically clean up it's database? It seems we still have quite a few stations out there that have gone the their full licensed power on their digital signal, but the STA entry is still there. Or is updating the database for STA vs licensed power a responsibility of the broadcast station?

If you know a station is still at STA, but there is also a full power spec for it, have you thought about providing two entries for that digital station? One with the call sign with a STA (WXYZ-DT (36) STA) notation, the other entry with the call sign with a CP or Full Power notation. A lot of work, I'm sure, and probably confusing to some. But potentially useful to someone who is looking at whether they can get the station at STA power and what antenna they would need to get the station when it does go full power.

If you are looking to update the database, in the DC-Baltimore DMA, I know of only three stations (other than LPs or TXs) that have not gone full power on the digital signal:

WUTB-DT My 24 (41) in Baltimore - still at 530 watts STA. The word is that they will go full power in May (maybe). The station recently started to send out a 720p signal, but everything is SD and stretched to 16:9! Why the FCC allowed them to delay boosting their power this long beyond the July, 2006 deadline escapes me. It is a Fox owned station, they can't claim poverty. No tower permit problem that I have heard of.
WHUT-DT PBS / Howard University 32 (33) - not on the air, but has had authorization for years to go on the air at 100 kW. No word at all, when they will start broadcasting digitally.
WHAG-DT NBC 25 (55) in Hagerstown, MD. Still at 0.9 kW, owned by Nexstar broadcasting which asked the FCC if it could delay going full power for WHAG-DT until the fall of 2008!

Also, WETA-DT PBS 26 (27) is currently broadcasting from Arlington, VA. It is to move to the same tower as WUSA-DT, WJLA-DT in NW DC with an increase in height and power to 90 kW. Another case where it would be useful to have both locations shown on the map so people can see what the signal reception areas should be after WETA-DT moves. But again, possibly confusing and more work.

Thanks again for al the work you are putting into this!

FCC Reference URLs (for those reading this thread who want more info):
FM and TV Service Contours: http://www.fcc.gov/ftp/Bureaus/MB/Databases/fm_tv_service_areas/service_contour_data/readme.html
FM and TV Propagation Curves: http://www.fcc.gov/mb/audio/bickel/curves.html
Antenna Height Above Average Terrain (HAAT) Calculator: http://www.fcc.gov/mb/audio/bickel/haat_calculator.html
CDBS database: http://www.fcc.gov/mb/databases/

Andy-
Since I use a more conservative version of Longley-Rice propagation... I use F(99,99) as opposed to F(50,90)...(if you don't do any RF modeling, then you don't need to care about this). As a matter of fact, I do work with RF propagation models, but not in commercial broadcast. I understand that the FCC L-R model is somewhat antiquated. Do you use HAAT directly or some other height in your model?

2) If you're interested in estimating OTA reception ease/difficulty, I'd roughly break it down into the following groups. White-red-yellow-green are all quite strong... Cyan ...move the antenna up... Blue ... antenna on the roof. Purple...weak. One of the commenters in the Philly OTA thread mentioned that your colors roughly match the http://antennaweb.org color map. I can't verify right now since the site is down.

Your info is very informative and appreciated. Thanks for doing this.
(Suggestion: Put your location in your user profile. It's very helpful to know where your "local" home is.)

Does the FCC periodically clean up it's database? It seems we still have quite a few stations out there that have gone the their full licensed power on their digital signal, but the STA entry is still there. Or is updating the database for STA vs licensed power a responsibility of the broadcast station?

If you know a station is still at STA, but there is also a full power spec for it, have you thought about providing two entries for that digital station? One with the call sign with a STA (WXYZ-DT (36) STA) notation, the other entry with the call sign with a CP or Full Power notation. A lot of work, I'm sure, and probably confusing to some. But potentially useful to someone who is looking at whether they can get the station at STA power and what antenna they would need to get the station when it does go full power.
Officially, STAs are supposed to last for 180 days from the date of issue. The only way to continue using the STA is to get renewals. The CDBS files contain some information about "last updated" dates for each record, but that information does not seem to be maintained for all cases. When trying to identify the "correct" record for each broadcaster, I look at STA expiration dates, CP and LIC grant dates, "current" or "archive" flags, and other hints from the database that clue me in on which records are most likely to match reality.

It does look like old records in the database get cleaned up from time to time. Many transmitters have had several (sometimes over a dozen) records filed over the last few decades, yet only the more recent records (usually no more than about 3) are flagged as "current".

For now, I think the best thing to do is just maintain one active record per transmitter (as opposed to keeping all the possible flavors). It seems that in the majority of the cases, I'm getting the correct record, and for each of the cases I'm not, I can simply enter an "override" to get the correct entry. Once we figure out where all the "exception" cases are, we should end up with something that is a pretty close match to the current real-world snapshot of the RF environment.



If you are looking to update the database, in the DC-Baltimore DMA, I know of only three stations (other than LPs or TXs) that have not gone full power on the digital signal:

WUTB-DT My 24 (41) in Baltimore - still at 530 watts STA. The word is that they will go full power in May (maybe). The station recently started to send out a 720p signal, but everything is SD and stretched to 16:9! Why the FCC allowed them to delay boosting their power this long beyond the July, 2006 deadline escapes me. It is a Fox owned station, they can't claim poverty. No tower permit problem that I have heard of.
WHUT-DT PBS / Howard University 32 (33) - not on the air, but has had authorization for years to go on the air at 100 kW. No word at all, when they will start broadcasting digitally.
WHAG-DT NBC 25 (55) in Hagerstown, MD. Still at 0.9 kW, owned by Nexstar broadcasting which asked the FCC if it could delay going full power for WHAG-DT until the fall of 2008!

Also, WETA-DT PBS 26 (27) is currently broadcasting from Arlington, VA. It is to move to the same tower as WUSA-DT, WJLA-DT in NW DC with an increase in height and power to 90 kW. Another case where it would be useful to have both locations shown on the map so people can see what the signal reception areas should be after WETA-DT moves. But again, possibly confusing and more work.

The fixed set of files is processing as we speak, so we'll have to double check on these when the new files are available.

I think this will have to be an iterative process. Although it might not be totally right each time, I hope we're getting closer on each pass. The maps need to be refreshed occasionally anyway, just to keep up with changes in the FCC database, so any "overrides" we put in along the way will make each iteration of the files that much better!



Thanks again for keeping an eye out for details. Please keep up the work on checking the results. We'll all end up with better results with everyone's combined diligence.



Best regards,
Andy

I'd like to complement and thank Andy, as this is one of the most useful tools I've seen for OTA reception.

Topic is stuck, and title edited.

As a matter of fact, I do work with RF propagation models, but not in commercial broadcast. I understand that the FCC L-R model is somewhat antiquated.
Longley-Rice is old (evolved during the 1950s), but it's probably one of the most realistic long-range models out there. There are LOTS of modeling methodologies in common use like free space loss, Fresnel zone, Hata, CCIR, Walfisch-Ikegami, and a thousand others. Most of these are empirical models, meaning that lots of test data was collected to compute the best coefficients that make the model fit reality the best.

The thing that makes L-R so useful is that it's fairly closely tied to the basic laws of physics. L-R computes propagation loss by considering the physical electromagnetic properties (permittivity and permeability) of the terrain and the air. It integrates the effects of groundwave, diffraction, Earth curvature, and tropospheric scatter over any given terrain profile. Instead of simply looking at a few points of signal obstruction, the model actually accumulates the effects at every step along the terrain profile. This means, for example, that a large rounded hill will behave differently than an equally high sharp, knife-edge, mountain peak.

The "empirical" aspect of the model comes in the form of assumptions made about the terrain composition. Propagation losses will be different over sand, water, ferrous rock, tropical rainforest, etc. The engineers working on the models came up with seven different terrain composition profiles for a variety of conditions (desert, tundra, marine, continental, etc.).

The laws of physics hasn't changed since the models were developed, so when people refer to the "outdated" aspect of L-R, I think they are mostly refering to the way in which the model is used as opposed to the accuracy of the modeling equations. The FCC picked F(50,90) to model their TV service contours. They also made several assumptions about a consumer's antenna gain, receiver sensitivity, usable SNR, and resistance to multipath when they came up with their service contours. Many of those assumptions came from the analog TV studies that were done in the 1950s and 60s, and haven't translated so well for digital TV reception. When it comes to modeling, signal strength is still signal strength, even if your link budget is allocated all wrong.



Do you use HAAT directly or some other height in your model?
Depending on where you look, the FCC specifies transmitter height in meters above mean sea level (AMSL), above ground (AGL), and HAAT. When a broadcaster files an application with the FCC, I assume they will either know the AMSL or AGL value very accurately since that's what they can measure with a GPS receiver or read directly off the tower blueprints. HAAT is computed in a rather complicated way that is dependent on the surrounding terrain data. I actually don't think the FCC's terrain database is all that accurate, so I don't put much stock in the HAAT numbers they publish. I think they use this value in generating their service contour plots, but I don't use it anywhere in my models. I will always use either the AMSL value or the AGL value, depending on which one is filled in.



One of the commenters in the Philly OTA thread mentioned that your colors roughly match the http://antennaweb.org color map. I can't verify right now since the site is down.
If you're talking about the colored pie charts they put out, that definitely wasn't my intent. I actually don't like those pie charts because they are not very helpful and they are sometimes misleading. There are a lot of cases where a "long range" or "finge" antenna is the right choice even when the user is very close to the transmitter. There are simply too many variations of antennas (e.g., with/without amp, UHF/VHF, Yagi/LPDA/microstrip/loop/dipole/T2FD/etc.) to collapse it down into a half dozen application codes since there are so many situation-specific problems that each antenna is suited for.

I'd rather have everyone forget about antennaweb for a moment and just look at the signal levels they're working with. I think most of us are sophisticated enough to look at a few maps and tables to figure out what we need without having everything reduced down to a single pie icon for us. :)



Best regards,
Andy

without having everything reduced down to a single pie icon for us
http://img241.imageshack.us/img241/3268/homersimpsonohnoow3.jpg

Just trying to add some more fun to the thread. :)

I'm trying to learn all I can about OTA reception before purchasing an antenna. I live in central NJ in 07748 on fishhawk dr. Most of the transmitters are in the direction of the Empire State building and are 20-30 miles from my house. Antennaweb said I would get no digital stations at all and only 7 or so analog ones - all purple. So I suspected I was in a problem area since 20-30 miles shouldn't normally be a problem.

Andy's google earth app is giving me more optimistic results. My house seems to be always on the fringe of two colors. For the stronger stations like WNBC, I'm right on the green/cyan fringe. For weaker stations I'm in the blue/purple fringe. How accurate do you think this is? I'm on the back side (from the transmitters) of a smooth sloping hill. The hill tops out at about 210' sea level and has line of sight and I'm at 140', maybe a quarter of a mile away. I have a ranch house and I'm in a wooded area having very large (60'-70') tulip trees. It is these trees that have me most concerned about reception.

I must say this google earth stuff has been excellent in visualizing how terrain effects reception. If anyone can make a recommendation for my situation I'd very much appreciate it. Thanks.

I'm trying to learn all I can about OTA reception before purchasing an antenna. I live in central NJ in 07748 on fishhawk dr. Most of the transmitters are in the direction of the Empire State building and are 20-30 miles from my house. Antennaweb said I would get no digital stations at all and only 7 or so analog ones - all purple. So I suspected I was in a problem area since 20-30 miles shouldn't normally be a problem.
Antennaweb.org is very conservative on digital reception. With antennaweb.org, enter your exact address and under the options link add an antenna height of 100' or more to see what digital stations show up. If entering zip code only, I often add 300' to 500' or even more to get a more complete list of possible digital stations for other people. If you need more help, post to the antenna reception sticky thread or start a new thread in the reception hardware forum. Don't want this sticky thread to get too far off-track, although your post is perfectly valid as you point out the different results you get using the default settings at antennaweb.org.

Hey, keebs1973, some stations (at least WABC 7 and WNET 13) will be moving back to the VHF frequency band in 2009, so note that when you buy your VHF/UHF combo antenna (wink, wink).

Antennaweb.org is very conservative on digital reception.It's also VERY basic and unfortunately, just like using I.E., most think that is the only choice.

Try 2150 instead;
http://www.avsforum.com/avs-vb/showthread.php?p=7625830#post7625830
and compare Google Earth and the above database with this.

All the files have been reprocessed to fix a bug with missing transmitters. Several more MSAs have been added as well. If anyone is a regular in any of the MSA specific OTA threads, could you do me a favor and let the other threads know that their maps are available? Thanks!



BTW, bandwidth demands for these files will be high initially, so I encourage everyone to SEED the files for as long as possible and to be patient. If we all do our part, the entire community will benefit. Your contribution will be appreciated, really!



Best regards,
Andy

All the files have been reprocessed to fix a bug with missing transmitters. Several more MSAs have been added as well. If anyone is a regular in any of the MSA specific OTA threads, could you do me a favor and let the other threads know that their maps are available?
Thanks for posting the revised files. I have been looking at the maps for the DC and Baltimore stations. Neat stuff! Also useful to include the low power stations out in the Shenandoah valley and the West Virginia pan handle. Shows the interference overlap between WRC-DT NBC 4 (48) in DC and WAZW-LP 48 analog out in Winchester. This has caused problems for people who want to get WRC-DT but live too close to WAZW-LP. I may post a couple of sample snapshots to the Washington-Baltimore thread.

Also, thanks for expanding the data sets to the top 20 markets. Must have been a lot of work!

Andy - Just posted the update in the Philly OTA thread. Looks like the bug was fixed. Thanks for the explanation of the L-R rationale for terrains as I don't normally deal with propagation over terrain.

I would suggest adding an explanation to post #2 for the color mappings. Some of the people viewing this thread do not understand the technical details, but they are familiar with the AntennaWeb.org pie chart. Consider a modification of post #22, intended for a "general" audience:

The colors shown in the map are not the same as Anntenaweb and can roughly be broken down as follows:
- White-red-yellow-green are all quite strong. You can expect reasonable coverage with an indoor antenna.
- Cyan is where it's advisable to move the antenna up to the second floor or attic.
- Blue is where it's probably necessary to install a good antenna on the roof.
- Purple is quite weak and you really have to work at it for any chance of reception.

Please understand that this is a simulation and can only be treated as a rough approximation. Reception at your location is affected by many factors such as; multipath, antenna gain, receiver sensitivity, buildings, trees - which are not taken into account. Your mileage may vary.

Is it possible to add the Harrisburg, PA transmitters (WHP, WHTM, WITF) to the Philidelphia or Baltimore file? The rest of the Harrisburg area transmitters are included: WGAL, WPMT, and WGCB in the Baltimore file; WLYH, WPMT, and WGCB in the Philidelphia file.

I want to thank you for this useful tool.

Andy - Just posted the update in the Philly OTA thread. Looks like the bug was fixed. Thanks for the explanation of the L-R rationale for terrains as I don't normally deal with propagation over terrain.

I would suggest adding an explanation to post #2 for the color mappings. Some of the people viewing this thread do not understand the technical details, but they are familiar with the AntennaWeb.org pie chart. Consider a modification of post #22, intended for a "general" audience:
Thanks! and done... The original post now includes your color code description.

Best regards,
Andy

Is it possible to add the Harrisburg, PA transmitters (WHP, WHTM, WITF) to the Philidelphia or Baltimore file? The rest of the Harrisburg area transmitters are included: WGAL, WPMT, and WGCB in the Baltimore file; WLYH, WPMT, and WGCB in the Philidelphia file.

I want to thank you for this useful tool.
My computer is still very busy number crunching for other MSAs right now. Harrisburg is number 66 on the list, so I'm afraid it will be a while before I can get around to it. I'm really strapped for processing horsepower right now, so everyone will just need to be patient.

Best regards,
Andy

Well, is there any way that other people could help do your crunching for this? I'd be willing to help out if possible. I'm running a Linux machine if that makes any difference, though I could get into Windows a bit to help you out.

Also, there's a station missing from your DC coverage maps, though it doesn't show up on the FCC site either... W42CK in Hagerstown. It does exist, it is on the air (I saw it yesterday), and there's nothing on the FCC site to indicate that the license has been canceled, it just doesn't appear on any search results.

http://www.recnet.com/cdbs/fmq.php?facid=25042&arch=Y&jaws=0

They appear to be operating with the facilities at the bottom of the page.

http://svartifoss2.fcc.gov/cgi-bin/ws.exe/prod/cdbs/forms/prod/cdbsmenu.hts?context=25&appn=100988435&formid=303&fac_num=25042

That's their renewal, which was granted.

EDIT: P.S. I'm seeding NYC, Philly, and DC/Baltimore, and may download more of them later.

- Trip

My computer is still very busy number crunching for other MSAs right now. Harrisburg is number 66 on the list, so I'm afraid it will be a while before I can get around to it. I'm really strapped for processing horsepower right now, so everyone will just need to be patient.

Best regards,
Andy

Alright, thats okay.

Thanks for all you do.

Sigh. B-i-t-t-o-r-r-e-n-t.

Nope...passing on this one.

Hey Matt. It will probably help you get your question answered if you were to specify which file you were trying to load into Google Earth. ;)

Rudy

That would be the file attached in the first post on the thread.

GeekGirl, thank you for the help.

All the files have been reprocessed to fix a bug with missing transmitters. Several more MSAs have been added as well. If anyone is a regular in any of the MSA specific OTA threads, could you do me a favor and let the other threads know that their maps are available? Thanks!



BTW, bandwidth demands for these files will be high initially, so I encourage everyone to SEED the files for as long as possible and to be patient. If we all do our part, the entire community will benefit. Your contribution will be appreciated, really!



Best regards,
Andy
Andy,
I appreciate all your work producing these predictions. I have the files for New York and Boston which includes the stations in Providence and Long island I can get. If you get it to it on your list, Hartford would fill in the rest of my stations. I am redownloading the Boston file to see your updates. To get an updated version do I have to redownload the whole file or is their a way to get just the new part. I haven’t had any other experience with Bitorrent. What does seed mean? For some reason I can only see the top few lines of each of Bitorrent’s FAQ pages and there is no scroll bar available.
John

What does seed mean? For some reason I can only see the top few lines of each of Bitorrent’s FAQ pages and there is no scroll bar available Seeding means to offer your file for sharing with others on the internet. The rest of the details go OT for this thread.

Something is wrong with your web browser. You should be able to see scroll bars at this URL: http://www.utorrent.com/beginners-guide.php. Check out the other tabs at the top for answers to all your questions. If you are using the browser that came with your PC, try increasing the display resolution- maybe the scroll bars are off-screen.

Azureus is a popular BT client and the one I use personally.

http://azureus.sourceforge.net/
Azureus : Java ********** Client

There's an excellent Wiki page as well.

http://www.azureuswiki.com/index.php/Azureus_FAQ
Azureus FAQ - AzureusWiki

Wondering where Milwaukee would be on the list, or if it's too far down to get this kind of excellent treatment. :) This is a great tool, and MUCH appreciated!

If you notice any errors, please let me know. If any data has been incorrectly extracted from the FCC database, they should be corrected for future simulations.
Best regards,
Andy

Hi Andy,

Fantastic job! Chicago has two errors: WJJA-DT Kenosha is at full power now; they're not on their 6 kw STA. Also, WYIN-TV analog is not at 5 million watts on Sears; they're stuck in northwest Indiana on WYIN-DT's tower.

Also, this is a great tool to help people point their antennas and know what kind of reception to get. It would be outsanding to do all the markets. Is there any way I can help in getting them all online? How hard is it to do, and how long does it take per market to do?

Gilbert

Got any hackers here that could do a clone of the seti@home thing to distribute the workload for making these using idle time? I'd run a node if there were such a thing.

(note if anyone's interested, I don't use Windows and won't use Java)

It's not horsepower that is needed to make the things - its manually massaging the info from the FCC database.

He's obviously doing it by DMA ranking and up to #20.

As you don't use Windows or Java, it would take more time to make a client to run the programming then it would take to actually run the programming.

ANSI C, Perl, etc. Just because it's not Windows doesn't mean it's hard and not portable.

The Longley-Rice propagation model source code is available from NIST, free of copyright. Written in FORTRAN, now ported to C/C++. http://flattop.its.bldrdoc.gov/itm.html. GNU C/C++ and FORTRAN compilers are available on the PC. However, that's just one small part of the big picture.

I've implemented some of the ITU atmospheric propagation models and it's a LOT of work just to get things right. I work in MATLAB and Excel (yes, you can do this in Excel's VBA if you are determined). Coding isn't the problem, it's the extensive knowledge needed to put an end-to-end model together that fits your application.

Take a look at the previous posts where the L-R model is discussed. Considerable care was taken to use an accurate model, not what the FCC says. It reflects the efforts of an experienced RF engineer who knows how to work with terrestrial communications (satellite, like DirecTV or Dish, uses different models). You really have to understand both ends of the RF link, all the geography in between, and what it means for a TV tuner. (I'm leaving out all the parameters needed- far too many for the purpose of this discussion.)

I'm also willing to help, but I think the best thing to do is to wait. Andy's got a lot on his plate just to get the software stable (bug fixing). Let him decide if he wants to distribute an .exe and have others help "crunch". Of course, it's a bit of work to put a package together (with test cases for verification).

Of course, it's a bit of work to put a package together (with test cases for verification).
It might be worth doing in the long run though, the whole planet could be done with enough people donating enough time. I wasn't thinking it would be a solution for next week or something, more like next year or beyond. :)

It might be worth doing in the long run though, the whole planet could be done with enough people donating enough time. I wasn't thinking it would be a solution for next week or something, more like next year or beyond. :)

Considering what I have seen from people keeping the torrent open so others can d/l the data, I can say without a doubt the effort would be a huge waste of time.

Chicago has two errors: WJJA-DT Kenosha is at full power now; they're not on their 6 kw STA. Also, WYIN-TV analog is not at 5 million watts on Sears; they're stuck in northwest Indiana on WYIN-DT's tower.
Thanks! Both have been fixed for any simulations generated after today. I'll post an updated transmitter file in post #1.



Also, this is a great tool to help people point their antennas and know what kind of reception to get. It would be outsanding to do all the markets. Is there any way I can help in getting them all online? How hard is it to do, and how long does it take per market to do?
The most helpful thing to do for now is set up a computer somewhere to always seed the entire collection of files. The more permanent seeds we have the faster everyone can download. The first 20 MSAs add up to 1 GB already and I have another 10 MSAs ready to go. Getting this much data out to hundreds of downloaders will take a healthy torrent community.



As for processing assistance, I've already considered many things. Yes, the source can compile under either Windows or Linux. I've done it and I run simulations on a good mix of both platforms. I've even put some thought into ideas like clusters and distributed clusters (e.g., BOINC).

Source code distribution will be way too tricky at this point because the code has been optimized for speed and multiple processors using OpenMP. The GNU compiler won't officially support OpenMP until version 4.2, which hasn't been released yet. Fedora Core 6 has actually back-ported OpenMP support into their 4.1.1 compiler. The other commonly found compilers that support OpenMP are Microsoft's Visual Studio 2005 and Intel's Compiler 9.x, both of which are commercial products that the average person probably doesn't own.

The greatest limitation for distributing the processing is the data set. The North American terrain data is about 9.1 GB. There are other pieces like the FCC database (64 MB) and my database patch info, but they're all small in comparison. Even if source or binary distributions were made public, or even if I converted it into a distributed cluster project, the size of the terrain dataset would be the limiting factor in how quickly the processing could be spread out. That's an even bigger problem than simply distributing the 1 GB worth of kmz files.

I'm OK with doing the processing for now. I can roughly crunch about 3 metros per day on an Athlon 64 X2 3800+ (that's dual core) with 2 GB RAM and plenty of disk space. I can let the processing run on its own for days/weeks/months. Once the files are done processing, I need to take care of the administrative tasks such as packaging the files for distribution and updating the appropriate servers / torrents / message boards, etc.

Actually, the simplest way to speed things up right now would be to put all the processing on the latest high end 8-core machines that are hitting the mainstream server market right now. The faster and greater number of cores would probably be able to run through the processing at least 5 times faster than my current machine. I could then just do the administrative tasks in large batches and run through all the top MSAs (there are 276 defined by the US Census Bureau) in under a month.

As the broadcasters start to change around their transmitter facilities and shut off their analog stations, I'm sure it would also be great to have quarterly updates (or more frequently depending on available crunching power) over the next two years.

Alternatively, I could turn additional crunching power on doing higher resolution maps, since the available data supports doing much finer detail than what I've had to settle with. I would have loved to distribute files with enough detail to look down to your house level, but alas, the computational load increases exponentially, so this may have to wait for a few more years of Moore's Law to elapse.



In the end, I believe that it behooves us all to become better informed consumers, so I certainly appreciate everyone's willingness to help and make use of this data. I think the best ways to help right now are:

#1. Create as many permanent torrent seeders as possible for all the files.
#2. Let everyone know where to find the files and how to get them. Having useful data lying around is no good unless people know it exists and know how to use it.
#3. Check the data for errors and updates. Being mis-informed can sometimes be worse than being un-informed. :)
(#4) If you happen to have an 8-core Core 2 server lying around, pm me for my mailing address. ;)



Best regards,
Andy

Got any hackers here that could do a clone of the seti@home thing to distribute the workload for making these using idle time? I'd run a node if there were such a thing.
There are tons of projects that have followed suit... Check out BOINC.

Andy

I've updated the transmitter file in post #1. It includes the transmitter fixes mentioned by sebenste and also updates everything to the latest FCC database image.

MSAs 21 thru 30 have finished processing, but have not been posted yet. I will try to get those posted tomorrow.

Best regards,
Andy

Andy - add me to the list of people who greatly appreciate your work. If you ever get to a point to explain the "engineering" behind it, please do so. This is very intriguing.

[Engineering Mode On]
I'm wondering how you did this. My initial thoughts are calculating the relative distance from the transmitter (distance, angle) for each point on the grid, sorting according to angle (0 to 360 deg), then walking around a radius along a point-point path towards an end point (circle) some distance away until the signal level falls below a threshold. All while tracking the delta-h parameters for L-R as well as the link budget. 500 meter (30 arc-second) resolution, angles / distances use great-circle reckoning (spherical trig for radius of earth, etc.). Then, create color maps, a smoothed .png file to overlay into Google Earth, and build a kmz file. All of this automated.

No wonder you need optimized, multi-core support.
[Engineering Mode Off]

I've posted your update on the Philly OTA thread.

An interesting point on the height of the icons being the transmitter antenna height. In the Philly area, we have the local OTA channels in an antenna farm. By turning on all the icons and tilting the view until it's almost horizontal, you can actually see where these antennas are on the towers.

This feature is useful for someone having problems receiving a channel, but others in the area are OK. It can help place the blame (or not) on the height of the transmitter. Very insightful.

The most helpful thing to do for now is set up a computer somewhere to always seed the entire collection of files. The more permanent seeds we have the faster everyone can download. The first 20 MSAs add up to 1 GB already and I have another 10 MSAs ready to go. Getting this much data out to hundreds of downloaders will take a healthy torrent community.

I'm seeding with my connection at 60KB/s. My connection is capable of more, but I don't want to upset others in my household.

I was in New Jersey over the weekend and seeded with my grandparents' 200KB/s upload rate.

I actually ran out of disk space trying to acquire them all. I've now cleared some video off my hard drive and will continue to seed the new ones as soon as you make them available.

The greatest limitation for distributing the processing is the data set. The North American terrain data is about 9.1 GB. There are other pieces like the FCC database (64 MB) and my database patch info, but they're all small in comparison. Even if source or binary distributions were made public, or even if I converted it into a distributed cluster project, the size of the terrain dataset would be the limiting factor in how quickly the processing could be spread out. That's an even bigger problem than simply distributing the 1 GB worth of kmz files.

I'm OK with doing the processing for now. I can roughly crunch about 3 metros per day on an Athlon 64 X2 3800+ (that's dual core) with 2 GB RAM and plenty of disk space. I can let the processing run on its own for days/weeks/months. Once the files are done processing, I need to take care of the administrative tasks such as packaging the files for distribution and updating the appropriate servers / torrents / message boards, etc.

Within the next three months, I'm planning to get a new laptop with a Core 2 Duo and 2GB of RAM. If you'd like me to crunch some once I get that, I can do it. I'd be willing to download the terrain data, all 9.1GB of it, if told where to acquire it from. My ISP doesn't really care how much I pull down.

Actually, the simplest way to speed things up right now would be to put all the processing on the latest high end 8-core machines that are hitting the mainstream server market right now. The faster and greater number of cores would probably be able to run through the processing at least 5 times faster than my current machine. I could then just do the administrative tasks in large batches and run through all the top MSAs (there are 276 defined by the US Census Bureau) in under a month.

Why are you using MSAs and not DMAs? Just wondering. Also, where might one find a complete list of MSAs so that one might know when his/her market will fall in the order?

As the broadcasters start to change around their transmitter facilities and shut off their analog stations, I'm sure it would also be great to have quarterly updates (or more frequently depending on available crunching power) over the next two years.

Alternatively, I could turn additional crunching power on doing higher resolution maps, since the available data supports doing much finer detail than what I've had to settle with. I would have loved to distribute files with enough detail to look down to your house level, but alas, the computational load increases exponentially, so this may have to wait for a few more years of Moore's Law to elapse.

Also to be considered is how much strain it would put on users whose computers would have to render such maps. But it does sound like a fantastic idea.

#1. Create as many permanent torrent seeders as possible for all the files.

I'm doing my part.

#2. Let everyone know where to find the files and how to get them. Having useful data lying around is no good unless people know it exists and know how to use it.

I'll post about it in my DMA as soon as it is available.

#3. Check the data for errors and updates. Being mis-informed can sometimes be worse than being un-informed. :)

Did you fix the one missing station I mentioned, W42CK?

(#4) If you happen to have an 8-core Core 2 server lying around, pm me for my mailing address. ;)

Can't help you there, sorry.

Your work is greatly appreciated.

- Trip

The most helpful thing to do for now is set up a computer somewhere to always seed the entire collection of files. The more permanent seeds we have the faster everyone can download. The first 20 MSAs add up to 1 GB already and I have another 10 MSAs ready to go. Getting this much data out to hundreds of downloaders will take a healthy torrent community.

I've got a sort of seedbox that runs nearly 24/7 and I've been seeding the SF file since it was first posted and started seeding all the rest last night. Looks like there's about 2-6 seeds per file currently. BTW, do you have some sort of burst mode, or limit, on your upload connection? I was getting about 600kB DL speed at first, then it dropped to below 60kB and less for the duration. Just curious.

Do you know if Zerotracker is setup for RSS feeds? If you change the torrents at all(update etc.) then an RSS plugin for the client can automatically DL and start seeding the new file without any manual input.

I'm seeding with my connection at 60KB/s. My connection is capable of more, but I don't want to upset others in my household.

I was in New Jersey over the weekend and seeded with my grandparents' 200KB/s upload rate.


You might want to check your firewall because I don't see anything even close to that on the uploads.

I have supplied around 3.5 Gig of uploads for these at speeds in triple digits and seem to be supplying 95% up the uploads for the persons feed. If there was another 260KB/s or more out there, the tracker is doing its job properly and the firewall set up properly, there is no way I would be supplying 95% - 100% of the file size to people.

Andy,

I haven't had a chance to try this out yet, but it looks great!

I've got a web hosting plan with a ridiculous amount of storage and bandwidth that I'm not even coming close to using. Unfortunately, it looks like I'm not allowed to do webseeding. However, I'd be happy to mirror the files, since there are those out there afraid of torrents.

Since this is your project, I'll let you decide if you want to go that route. Let my know via PM, and we can work out the details.

You might want to check your firewall because I don't see anything even close to that on the uploads.

I have supplied around 3.5 Gig of uploads for these at speeds in triple digits and seem to be supplying 95% up the uploads for the persons feed. If there was another 260KB/s or more out there, the tracker is doing its job properly and the firewall set up properly, there is no way I would be supplying 95% - 100% of the file size to people.

Sure enough, you were right. I had the UDP port open for it but not the TCP port. It should be better now.

Also, turned out iptables was blocking traffic as well. I've now opened up my firewall for it too. Sorry!

- Trip

Sure enough, you were right. I had the UDP port open for it but not the TCP port. It should be better now.

Also, turned out iptables was blocking traffic as well. I've now opened up my firewall for it too. Sorry!

- Trip

I must admit that torrents have come a long way since I last fired one up - in fact the old version of bt I had still installed would not even work with the current trackers.

After downloading a new client, for the first 24 hours I could not figure out why I had literally no upload going to help out with the few complete markets i could get - and most of the downloads were taking 24-48 hours to find someone on line with the file - and then it would come trickling in with single digit speeds. So i knew I could get the copies out at a fast speed if I could get complete copies - but it just sat there with virtually no upload speed.

So then I did some searching and found out that now you have to open up some other ports besides 1080 that you did not have to do 5 years ago.

Easy mistake - but I knew there was no way there was 260+ Kbps of upload bandwidth sitting out there :D

Connected to two peers right now and it doesn't appear that either is "clever", or have port forwarding set up. The below link explains port forwarding and has a whole slew of settings for just about ever router imaginable.

http://www.portforward.com/english/routers/port_forwarding/routerindex.htm
PortForward.com - Free Help Setting up Your Router or Firewall

OK. I was finally able to push the next ten MSAs out to the servers and update post #2. Would someone be kind enough to put out notices in the OTA threads for the respective markets?



BTW, there's the list of the top 100 metros (using 2000 census numbers) to give you an idea of how much processing is yet to come...

Rank MSA Population
1 New York--Northern New Jersey--Long Island, NY--NJ--CT--PA 21,199,865
2 Los Angeles--Riverside--Orange County, CA 16,373,645
3 Chicago--Gary--Kenosha, IL--IN--WI 9,157,540
4 Washington--Baltimore, DC--MD--VA--WV 7,608,070
5 San Francisco--Oakland--San Jose, CA 7,039,362
6 Philadelphia--Wilmington--Atlantic City, PA--NJ--DE--MD 6,188,463
7 Boston--Worcester--Lawrence, MA--NH--ME--CT 5,819,100
8 Detroit--Ann Arbor--Flint, MI 5,456,428
9 Dallas--Fort Worth, TX 5,221,801
10 Houston--Galveston--Brazoria, TX 4,669,571
11 Atlanta, GA 4,112,198
12 Miami--Fort Lauderdale, FL 3,876,380
13 Seattle--Tacoma--Bremerton, WA 3,554,760
14 Phoenix--Mesa, AZ 3,251,876
15 Minneapolis--St. Paul, MN--WI 2,968,806
16 Cleveland--Akron, OH 2,945,831
17 San Diego, CA 2,813,833
18 St. Louis, MO--IL 2,603,607
19 Denver--Boulder--Greeley, CO 2,581,506
20 Tampa--St. Petersburg--Clearwater, FL 2,395,997
21 Pittsburgh, PA 2,358,695
22 Portland--Salem, OR--WA 2,265,223
23 Cincinnati--Hamilton, OH--KY--IN 1,979,202
24 Sacramento--Yolo, CA 1,796,857
25 Kansas City, MO--KS 1,776,062
26 Milwaukee--Racine, WI 1,689,572
27 Orlando, FL 1,644,561
28 Indianapolis, IN 1,607,486
29 San Antonio, TX 1,592,383
30 Norfolk--Virginia Beach--Newport News, VA--NC 1,569,541
31 Las Vegas, NV--AZ 1,563,282
32 Columbus, OH 1,540,157
33 Charlotte--Gastonia--Rock Hill, NC--SC 1,499,293
34 New Orleans, LA 1,337,726
35 Salt Lake City--Ogden, UT 1,333,914
36 Greensboro--Winston-Salem--High Point, NC 1,251,509
37 Austin--San Marcos, TX 1,249,763
38 Nashville, TN 1,231,311
39 Providence--Fall River--Warwick, RI--MA 1,188,613
40 Raleigh--Durham--Chapel Hill, NC 1,187,941
41 Hartford, CT 1,183,110
42 Buffalo--Niagara Falls, NY 1,170,111
43 Memphis, TN--AR--MS 1,135,614
44 West Palm Beach--Boca Raton, FL 1,131,184
45 Jacksonville, FL 1,100,491
46 Rochester, NY 1,098,201
47 Grand Rapids--Muskegon--Holland, MI 1,088,514
48 Oklahoma City, OK 1,083,346
49 Louisville, KY--IN 1,025,598
50 Richmond--Petersburg, VA 996,512
51 Greenville--Spartanburg--Anderson, SC 962,441
52 Dayton--Springfield, OH 950,558
53 Fresno, CA 922,516
54 Birmingham, AL 921,106
55 Honolulu, HI 876,156
56 Albany--Schenectady--Troy, NY 875,583
57 Tucson, AZ 843,746
58 Tulsa, OK 803,235
59 Syracuse, NY 732,117
60 Omaha, NE--IA 716,998
61 Albuquerque, NM 712,738
62 Knoxville, TN 687,249
63 El Paso, TX 679,622
64 Bakersfield, CA 661,645
65 Allentown--Bethlehem--Easton, PA 637,958
66 Harrisburg--Lebanon--Carlisle, PA 629,401
67 Scranton--Wilkes-Barre--Hazleton, PA 624,776
68 Toledo, OH 618,203
69 Baton Rouge, LA 602,894
70 Youngstown--Warren, OH 594,746
71 Springfield, MA 591,932
72 Sarasota--Bradenton, FL 589,959
73 Little Rock--North Little Rock, AR 583,845
74 McAllen--Edinburg--Mission, TX 569,463
75 Stockton--Lodi, CA 563,598
76 Charleston--North Charleston, SC 549,033
77 Wichita, KS 545,220
78 Mobile, AL 540,258
79 Columbia, SC 536,691
80 Colorado Springs, CO 516,929
81 Fort Wayne, IN 502,141
82 Daytona Beach, FL 493,175
83 Lakeland--Winter Haven, FL 483,924
84 Johnson City--Kingsport--Bristol, TN--VA 480,091
85 Lexington, KY 479,198
86 Augusta--Aiken, GA--SC 477,441
87 Melbourne--Titusville--Palm Bay, FL 476,230
88 Lancaster, PA 470,658
89 Chattanooga, TN--GA 465,161
90 Des Moines, IA 456,022
91 Kalamazoo--Battle Creek, MI 452,851
92 Lansing--East Lansing, MI 447,728
93 Modesto, CA 446,997
94 Fort Myers--Cape Coral, FL 440,888
95 Jackson, MS 440,801
96 Boise City, ID 432,345
97 Madison, WI 426,526
98 Spokane, WA 417,939
99 Pensacola, FL 412,153
100 Canton--Massillon, OH 406,934

Best regards,
Andy

Bah, my market's not even on the list! (It's Roanoke, VA) Oh well...

I'm going to try to pull them down later today, but I'm not going to be home and my laptop will be with me, so I'll be seeding again this evening.

- Trip

Update - its clear that there is more bandwidth is now available as I do not seem to be supplying virtually all the upload in the past 12-18 hours and the load seems to be cut in half - thanks for checking the firewall settings.

OK. I was finally able to push the next ten MSAs out to the servers and update post #2. Would someone be kind enough to put out notices in the OTA threads for the respective markets?


Is there a reason you went back to Census designation instead of Television DMAs? Television DMAs would seem to give the truest indication of the largest number of people that could actually benefit from the software.

For example, Trip in Va's Roanoake, which is not even in the Top 100 Census rank is market # 68 using Television DMAs due to larger areas served with Television DMAs and the larger population when all those areas are considered (such as the inclusion of Charlottesville and Blacksburg into the Roanoake DMA).

http://www.avsforum.com/avs-vb/showthread.php?t=719690


http://img45.imageshack.us/img45/4417/roanokedmacz3.jpg (http://imageshack.us)

OK. I was finally able to push the next ten MSAs out to the servers and update post #2. Would someone be kind enough to put out notices in the OTA threads for the respective markets?


Done for Cincinnati thread, Thanks Andy!

BTW, I haven't tried these tools yet, as I'm on dial-up connection, but I'm sure others in this area will find this very useful!

For example, Trip in Va's Roanoake, which is not even in the Top 100 Census rank is market # 68 using Television DMAs due to larger areas served with Television DMAs and the larger population when all those areas are considered (such as the inclusion of Charlottesville and Blacksburg into the Roanoake DMA).

Charlottesville is its own DMA. In fact, it shares WVIR NBC29 with Harrisonburg on the other side of the mountains.

Blacksburg, however, is part of the Roanoke DMA.

I've got another question for the mods... why is this in the Hardware Forum and not the Local Reception forum? I'm sure there are some people who never check this forum (I'm one of them) and this is much more applicable to the Local Reception forum.

- Trip

Update - its clear that there is more bandwidth is now available as I do not seem to be supplying virtually all the upload in the past 12-18 hours and the load seems to be cut in half - thanks for checking the firewall settings.
Looks like there is currently 3 seeds for each of the newly posted files, I'm guessing Andy, you and me. Someone in Cincinnati must have a nice pipe as I was feeding them at 75kBs while the other 9 were in the teens to single digits.

Update - its clear that there is more bandwidth is now available as I do not seem to be supplying virtually all the upload in the past 12-18 hours and the load seems to be cut in half - thanks for checking the firewall settings.

No problem, I'm glad to do my part! I'm now uploading at 90 KB/s.

I just checked my list, and when I'm done pulling down the last three new files, I will be seeding 47 files, 17 albums from Jamendo in addition to the 30 markets.

- Trip

Looks like there is currently 3 seeds for each of the newly posted files, I'm guessing Andy, you and me. Someone in Cincinnati must have a nice pipe as I was feeding them at 75kBs while the other 9 were in the teens to single digits.

Well, mine is up on the new files as well and it appears the torrents are finally working as designed :D

http://img45.imageshack.us/img45/1855/torrent041207mf8.jpg (http://imageshack.us)

Charlottesville is its own DMA. In fact, it shares WVIR NBC29 with Harrisonburg on the other side of the mountains.

Blacksburg, however, is part of the Roanoke DMA.

I've got another question for the mods... why is this in the Hardware Forum and not the Local Reception forum? I'm sure there are some people who never check this forum (I'm one of them) and this is much more applicable to the Local Reception forum.

- Trip

My mistake - I thought they were combined together - however, as shown from the above map - the DMA does cover much more area and people than the Census MSA.

Looks like there is currently 3 seeds for each of the newly posted files, I'm guessing Andy, you and me. Someone in Cincinnati must have a nice pipe as I was feeding them at 75kBs while the other 9 were in the teens to single digits.

Download at 75kBs is easy, uploading at that speed is a different story :) Once all my downloads are done, I am sure my upload speed will increase for people as well.

Looks good at my end as well. Indianapolis jumps to 7 seeds somehow very quickly it appears, not sure how that happened.

Regarding the the files, you mentioned being created by DMA, I agree, and although it's a minor quibble, it would be nice if they were named "DMA-XXX-City" it would be easier to keep track of them, especially if one is seeding over 200 other torrents already. It has nothing to do with the mechanics of the files or their transfer, it would just make them easier to locate in the client.

Download at 75kBs is easy, uploading at that speed is a different story :) Once all my downloads are done, I am sure my upload speed will increase for people as well.
That's what I was saying, I was feeding the one peer at 75kBs upload.

Normally, I can get up to 600kBs download speed, but rarely over 100kBs for uploads. :)

Looks good at my end as well. Indianapolis jumps to 7 seeds somehow very quickly it appears, not sure how that happened.

Regarding the the files, you mentioned being created by DMA, I agree, and although it's a minor quibble, it would be nice if they were named "DMA-XXX-City" it would be easier to keep track of them, especially if one is seeding over 200 other torrents already. It has nothing to do with the mechanics of the files or their transfer, it would just make them easier to locate in the client.

Agreed.

For example, Sarasota is #72 and Lakeland is #83 in the Census MSA, yet both are part of the Tampa DMA and served by the Tampa Stations (with the exception of perhaps 2 stations between the 2 markets), so as Andy gets to the higher number markets, this will become a problem which would be eliminated by using the DMA markets as there is no overlap.

Also, I agree with your file naming for ease of use.

Well, In Southwest Ohio area the Cincinnati+Dayton DMA's (and most of the transmitter sites) are close enough together, given the way the population is distrubted(mostly in the metro areas as well as a good amount along I-75 corridor between Dayton+Cincinnati) the majority of population in either DMA is well within the coverage area of stations in both markets. I'm in Cincinnati DMA, for example -- 27~39 miles from The Cincinnati sticks, but only 12~14 miles from the Dayton TV "antenna farm" ... Portions of Northern KY and SE IN are involved as well ....

So, in this particular case, I'm not so sure I agree a "by DMA ranking" would necessarily equate to the greatest number of people benefiting in some way from the software ...

Wouldn't expect that to be the case in general but would think there may be other similar situations with some other DMA's out there ....

I am also wondering what all is included in the Cincinnati file, as there certianly not 53 analog+digital(including LP's) stations(or apps for different individual proposed facilties/etc) transmitting from within Cincinnati DMA. I think Andy had said he had gotten rid of duplicate entires (such as old STA's/etc) ... In Cincinnati AND Dayton DMA, for example there are currently 24 analogs(including LPs/translators/etc) on air or with CP's or licensed, 15 digitals, and several LD CP's or apps for flash cut or digital companion channels .... That doesn't quite add up to 53, but it's closer than what is the case with just Cincinnati! (unless perhaps FM is included in this as well )...

For example, Sarasota is #72 and Lakeland is #83 in the Census MSA, yet both are part of the Tampa DMA and served by the Tampa Stations (with the exception of perhaps 2 stations between the 2 markets),

Maybe I'm missing something .... I'm confused concerning why that would be a problem ... For instance, in that case Wouldn't the folks in the Sarasota or Lakeland market just use the Tampa file?

[update:] Well, excepting for any stations in those DMA's that aren't included in the Tampa file, such as perhaps the 2 stations you refer to?

Maybe I'm missing something .... I'm confused concerning why that would be a problem ... For instance, in that case Wouldn't the folks in the Sarasota or Lakeland market just use the Tampa DMA file?
Well, since there is already an accepted convention for categorizing these areas, the DMA system, why not just use it for these maps as well?

Maybe Andy is trying to add more to some to cut down on the total number of files. Instead of 210 separate files, maybe only 125-150.

Maybe I'm missing something .... I'm confused concerning why that would be a problem ... For instance, in that case Wouldn't the folks in the Sarasota or Lakeland market just use the Tampa DMA file?

[update:] Well, excepting for any stations in those DMA's that aren't included in the Tampa file, such as perhaps the 2 stations you refer to?

Thats the point....they should.

But when Andy hit market #72, all the sudden, will he reprocess all the Tampa Stations, or put up a duplicate file of the Tampa File, or just have a hole in the numbering.

And the stations I am referring to, WWSB and WMOR are in the Tampa file.

That's why we should be on DMA nows.


Maybe Andy is trying to add more to some to cut down on the total number of files. Instead of 210 separate files, maybe only 125-150.

Using Census MSA instead of Television DMA would add more files because of the embedded Census markets in 1 Television DMA.

Seattle is only showing one seed - mine - all the others have around 5 or so. I have uploaded close to 300Meg of Seattle (or 7-8 people at least). Am I using the wrong file or tracker for Seattle?

That's why we should be on DMA nows.


Oh, I agree ... Just saying, along the lines of the "fewer number of files" thing Kennan mentioned, right now *perhaps* the way he's doing it may allow for more folks to beneifit until more of the DMA's are posted ....

I don't know if that is the case, again I'm on dialup connection so can't tell yet what all is in the cincinnati file ;-) -- From that perspective, I'd of course rather have smaller files+say, the Cincinnati+Dayton transmitters in seperate files (and that very well may be the way it is, so I should probably shut up until I know, anyway ;)

I am also wondering what all is included in the Cincinnati file, as there certianly not 53 analog+digital(including LP's) stations(or apps for different individual proposed facilties/etc) transmitting from within Cincinnati DMA. I think Andy had said he had gotten rid of duplicate entires (such as old STA's/etc) ... In Cincinnati AND Dayton DMA, for example there are currently 24 analogs(including LPs/translators/etc) on air or with CP's or licensed, 15 digitals, and several LD CP's or apps for flash cut or digital companion channels .... That doesn't quite add up to 53, but it's closer than what is the case with just Cincinnati! (unless perhaps FM is included in this as well )...

He's listing all stations within 100km of a given location. So in the Cincinnati file, I found Cincinnati, Dayton, WWHO, WLEX, WAVE-TV, and some other odd stations.

- Trip

Seattle is only showing one seed - mine - all the others have around 5 or so. I have uploaded close to 300Meg of Seattle (or 7-8 people at least). Am I using the wrong file or tracker for Seattle?
I'm showing 5 seeds in the swarm for Seattle, but currently no peers. There will always be those folks who will download, and then delete the torrent in which case that particular seed is gone. They may be doing it unintentionally.

T



Using Census MSA instead of Television DMA would add more files because of the embedded Census markets in 1 Television DMA.
Yeah, I didn't even think about that part of the equation, I just assumed he was doing in a way to create less files, apparently not. Guess will have to wait and see what his thoughts are. :)

He's listing all stations within 100km of a given location. So in the Cincinnati file, I found Cincinnati, Dayton, WWHO, WLEX, WAVE-TV, and some other odd stations.

- Trip

Something like that was what I was thinking might be the case, and presumably would have been, more or less, whether it was done by MSA or DMA ...

So, until Dayton gets done, Sounds like this file will also still be quite useful for The Dayton metro area folks - Sounds like they'll be missing most of Columbus area stations until Dayton or Columbus(the latter becomes easier for East Dayton folks) gets done, but they'll have info on pretty much everything else they'll want/need. One exception in some cases might be WIPB Muncie, IN if it's not already in Cincinnati file(probably isn't, as I think it would be beyond 100Km from Cincinnati).

Those in Dayton DMA(mostly in less populated areas) To the North or west will still have The Dayton/Cincinnati stations available in the Cincinnati file, but will have to wait for Dayton for the stations in other adjacent markets(Ft. Wayne, Lima/etc) .....

And, sounds like the one Cincinnati file will be perfect for my location, as well as anyone in South Dayton area ... For instance, WAVE 3(analog) is 95 miles out from me, but on a 1800+ foot stick -- I'm about 20 miles or so outside the (FCC) predicted Grade B contour -- Certianly not a "Grade B" signal much of the time, but I get it reliably, and well enough I can watch their KY Derby Coverage ;-) ..

He's listing all stations within 100km of a given location. So in the Cincinnati file, I found Cincinnati, Dayton, WWHO, WLEX, WAVE-TV, and some other odd stations.

- Trip


And in Tampa there are stations North and East of Orlando!!!! - and stations towards Gainsville that I have never heard of or received, thus, another reason why it should be the Television DMA, not the Census MSA.

And in Tampa there are stations North and East of Orlando!!!! - and stations towards Gainsville that I have never heard of or received, thus, another reason why it should be the Television DMA, not the Census MSA.

If Census MSA involves more markets, and thus more files+thus smaller geographical regions, then assuming the same method is used with either, you would get Less "out of market" stations per area/market with MSA than would be the case with DMA. In other words, if DMA were being used, and that's the only thing that were to change about the way it's being done, and in any specific case the DMA areas are larger than the MSA, there would probably be *more* out of market stations in the file/larger files/etc.

I think what you are advocating was what I was wondering about, earlier, and that would be to include only the stations that are transmitting *within* the DMA. The method being used however seems to be more along the lines of what is receivable within *any* point of the MSA.

As I agreed with you earlier, I thought it might be better to go with including the transmitters in the file that were *only* transmitting from locations within the DMA (or MSA although I certianly think DMA would certianly be better choice here) itself, but the more that I think about it I'm not so sure.

What would be good about it is that there would be no duplicate info on the same transmitter in different files. What might not be so good is that the user would have to sort out which DMA outside his own to download to get info on all the stations he/she may be able to receive, and it might be a bit time consuming in some cases for Andy to sort out what goes where. You might not think so, but for example, we have a TBN here ... WKOI-DT ... It's Community of License is Richmond, Indiana, and it's considered to be in Dayton market. However, it actually transmits from within Cincinnati market, about right between Richmond, Dayton and Cincinnati.

What is good about the way it is being done (whether DMA or MSA), I think, is that a user in "Tampa" DMA is pretty well assured to get info on all the stations he/she may be able to receive, no matter what market they are actually in, or where exactly in the DMA the receiving location is located. For instance, if you were in NE Polk County(Within Tampa DMA on the map I looked at), perhaps you may be able to receive those stations NE of orlando, ETC, even though that's not the case in Hillsborough County.

Also, as I pointed out is the case here regarding the cincinnati file+the Dayton folks, especially when the transmitting locations in adjacent markets are relatively close together , this way the Cincinnati file is also quite useful to a good number of folks who are located outside of the MSA (or DMA if that's what had been used) boundries ....

Using the same method he is now, but with DMA instead of MSA, would mean fewer, larger files as you pointed out, and, I would think less duplication of the same transmitters in "different" DMA files as well.

So, as with many things, there are advantages and disadvantages no matter how you do it, unless perhaps there could be a way the data could be downloaded on a receive location specific basis, where only stations within a certian distance from the specific receive location was downloaded ....

FYI, the standard coverage maps are created with roughly 500 meter resolution at ground level. In order to truly understand the reception issues at a particular location (e.g., the roof of your house), it's better to look at an analysis such as my radar plots since they are simulated at much higher resolution and are specific to a location in 3D space.


I'm sorry if I missed this somewhere -- just want to make sure -- so wanted to ask --- I'm assuming the terrain data used for the coverage maps is something more precise than what we get when we're using Google Earth "alone"?

Regardless of the answer to that, As what might be a good example, below, I'm curious if you think the terrain resolution issue might signficantly effect my results with these tools, or the radar plot, as you had done one of those for me, previously.

Attached below as "topoatjeff.jpg", is a screenshot from delorme's topo USA, showing a bit of the "close in" terrain at my location. I have a marker for the antenna location. I have measured with an altimeter here, and the 802FT reading for elevation here matches what altimeter says, perfectly. Also, As far as I can tell, the contour lines are accurate, as shown on right, each contour line is a 20Ft elevation increment, with the one marked 800FT being the lowest. What you can't see is that indeed, much of the terrain (especially to East/SE) in my area(just not right where I'm at, LOL) is indeed fairly flat, at around 850~860FT, or "gently" rising within a mile or so to 900 feet. It does go lower+get more hilly in spots to the South and SW.

I do notice that The Google Earth terrain info shown for my exact location shows 856FT Elevation, which is over 50FT higher than the correct value. If I move the mouse pointer around, it would appear the terrain very near my location would be "almost" flat -- However, if I measure with the ruler and go with the pointer a little over a km directly east, it shows Lower Elevation(gradually going down to a little less than 800 Feet at one point), while in reality, in that area, the elevation actually rises to almost 900 Feet, and is pretty much "flat as a pancake" as they say, in that area!

So, it appears to me that for my location at least, for some reason, the google Earth Terrain data seems quite incorrect(unless I'm doing something wrong somewhere, although I don't think anything I have set should have changed that).

Note that concerning the below, I'm certianly not trying to draw any conclusions from this regarding these tools, as I fully understand your comments about this not being something that can take all aspects of someone's antenna setup/etc into account. Still, I think it's interesting, and thought I'd post some of it, as I thought it possible you, or others might think so as well ....

Looking at some of the coverage maps+based on my reception results with a fairly decent outdoor antenna setup, it does seem in some cases the maps may be showing something more optimistic than what seems to be occuring, in one case, seemingly signifcantly so. For example, it shows Green/yellow for LP station WRCX-LP Dayton(approx 13 miles distant), and yet that one is fairly weak, and interestingly enough, seems to vary greatly in signal strength regarding moving the antenna up or down a few feet, and oddly enough due to various weather/temperature changes ... I know that sounds very odd, but I have observed it carefully the past couple of years, and it is certianly the case .... The worst case is between about 32F and 45F, warmer or colder, and it comes in much better ....

As another example(but less signifcantly), it shows WWHO/DT Columbus(69 Miles) in Purple/Blue, although I usually don't see it at all(it is in direction where terrain is higher than antenna about 300ft away from antenna), and generally requires fairly significant "tropo" enhancement to receive them.

However, On the other hand, I haven't spent a lot of time with it yet, but the two above examples are the only two which I can detirmine seem "more optimistic" on the map than what seems to be occuring in reality(more or less, since antenna is at 35FT AGL, not ground level+has a good amount of gain/etc).

For example, the signal map for W20CL(Is shown in file as W47BC, their old callsign, otherwise it looks OK), Springfield, OH shows purple for my location, blue at the higher elevations(the real higher elevations) near me, and non-existant(no shading) in some of the lowest, most terrain obsstructed areas. (note that it is in same direction as WRCX-LP), and indeed, I receive them right along those lines -- With my best antenna setup, it is fairly weak+snowy (BTW, nothing really changed in this regard when they moved from 47 to 20 a little over a year ago). Also attached is W20CLatjeffs.jpg, showing this.

The coverage maps for the stations from the weaker stations from the South(Cincinnati LP's and more distant stations as well - Wave 3 for example seem to be either right on the money , or quite conservative.

For example, This one seems to be so close to being "right on the money" that I'm pretty blown away by it .... Attached as "wkonatjeffs.jpg" is portion of screenshot from GoogleEarth, with the WKON 52 (analog - 78 Miles) map up. As you can see, we have "purple", and "nothing" in my area, no shading "specifically" at my location(which I've marked with a probably not very visable black arrow) --- However -- My reception of this station is as follows : It's allways there, in a sense, but only to the extent under "dead band" or "normal" conditions that it is constantly popping in and out "above" and "behind" the snow .... I think, it seems to me this portion of the coverage map represents that sort of likelyhood, perfectly.

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


Again, Thanks for all the work on this, It's Fun to play with!

But, if he includes all transmitters within 100km, then that info is duplicated many more times - and makes the updated files bigger and the total size of the files bigger.

As you can load every .kmz file at the same time, there is no downside to just including TV Stations in their Television DMA, which is what I still would suggest.

It appears 3 people are downloading via dialup from me - so for them the smaller the file the better.

But again, its his program and he can do it how he likes - its just that a suggestions.

^ Yep, all good points ....

Certianly took me a while to D/L the 47MB Cincinnati file via dialup, but it did go smoothly right at ~5.5Kb/s download the entire time .... just turns out to be the case in my particular case/given my location that I wanted almost everything in there anyway :-)

Just saying, there's some good things about the other ways to do it as well --

Guess I'm just glad to see these nice L-R coverage maps available to folks, no matter how it's done, I think it should be really helpful in our local threads, especially I'd think for areas like mine, where terrain can sometimes be quite an issue ...

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

Anyway, I'm having too much fun with this stuff, looking at the weaker LP's in the area ...

Attached as w20cl.jpg is screencapture of that station(39 miles) to go with the portion of coverage map for them for my location I posted in last post ....

Attached as w36dgjeffs.jpg is portion of coverage area map for W36DG, with arrow+label showing my location ...

Attached as w36dgpic.jpg is screenshot of W36DG (27 Miles) ....

Never quite figured out why they need a full power TBN, and two LP translators that are both pretty much within(or almost so) the full service stations coverage area, though ...

Might as well use these analogs to see how well the antenna is working while their still on the air :-)

But, if he includes all transmitters within 100km, then that info is duplicated many more times - and makes the updated files bigger and the total size of the files bigger.

As you can load every .kmz file at the same time, there is no downside to just including TV Stations in their Television DMA, which is what I still would suggest.

It appears 3 people are downloading via dialup from me - so for them the smaller the file the better.



Something else I thought of in support of that way of doing it as well ... Since these files will be changing (New Low power digitals, some stations moving around the dial after analog shut off), it might be more convienent+efficient to do it per file per station DMA only .... Especially, as you note, for those of us who are still on dial up ... For instance, there might be times I might only need(or want) to "redownload" the Dayton or Cincinnati file in such cases ...

sorry for all the multiple posts, but figured I ought to go ahead and get to it while I have some time .... Also, was going to do this via PM to Andy, but decided to go ahead and post just in case it was any use for others, or if others in this area had any thoughts/suggestions about the below, or any additional corrections/etc ....

Cincinnati/Dayton area corrections for cincinnati.kmz file :

#1). We seem to be missing a few things, all involving LP's. A few of these are Low power digital CP's and presumably could be on the air quite soon.

So, I thought it was Strange that we have in the file :

W27CT Digital - This is a App for CP for Digital Companion channel on 6 - Note: W27CT has yet to make it on air with analog, the analog CP expired about a month ago, shortly beforehand they filed amendment ...

WWRD-LP 32 (analog) - The entry for them in the file is for their CP to move to 32, which they haven't done yet.

W36DG Digital - This is a CP for Flash Cut on 36, they are currently operating analog W36DG on 36.

W66AQ analog application to move to 22+repurpose WKEF 22's analog facilities(presumably for after analog shut off). This application has not been granted by FCC as of yet.

My thoughts ... Certianly don't see any problems with these being in the file, and I think W36DG's CP should definitely be in there as it is, as they could flash cut to digital at any time ....


But, we don't have in the file :


W23DM-D Digital - This is CP for Digital companion channel on 23 for W56AM

W24DG-D Digital - This is CP for Digital Companion channel on 24 for W20CL (formerly W47BC).

WOTH-LD Digital - This is CP for digital companion channel on 47 for WOTH-LP(25).

WWRD-LP 55 (analog) - This is where WWRD-LP is currently transmitting, with Licensed facilites.

W66AQ 66 (analog) - This is W66AQ's current licensed facilties on channel 66 - What is in the file is an application(analog) for them to move to 22 and repurpose WKEF 22's analog facilities -- The app has not been granted by FCC, and if it ever happens, I would think it would have to be for after analog shut off. The current facilites on 66 are much different than what the application for 22 facilities involve.

"NEW" - (File # BDCCDBDCCDTL-20070403ACT /CDBS CDBS Application ID No.: 1178688 ) - This is a new App for a CP for Digital companion channel on 20 for WBQC-CA - I presume this will soon show up at FCC TV query as "WBQC-LD" instead of "new". Note: There were mutual exclsuivity issues involving this app, and according the the application+attached exhibits it seems they've now solved that issue to some extent and have thus been able to move to the next step and file a App for CP. Note: This application was accepted by FCC on 4/3/07. "NOTE" : By the way There is another "new" app for digital in FCC database in this area as well, for digital companion channel for W56AT, Augusta, KY -- However, apparently they have not yet gotten to the stage where they can file a "CP app" yet ....

Note: What we don't have in the file, listed above does show up in FCC TV query, -- However, I noticed using CDBS search page and searching for the File # for the "new" app for digital companion channel for WBQC-LD/ I can't find it/it doesn't show up -- the same is true if you try to search for that by file # in TV query. I did not try anything similar for the others on the above list.


My thoughts - I'm thinking these really should be in the file ... Especially the 3 Low power digitals with current construction permits, suppose it doesn't matter as much about the "apps only" yet .... I'd like WWRD-LP 55 and W66AQ current licensed facilites in there as well(If I recall correctly, for instance it's different antenna pattern than the 32 CP for WWRD-LP, and W66AQ current facilites is very different from their application for 22), but, WWRD-LP really should be moving to 32, soon(or filing digital application/etc), as the analog CP for 32 expires in October of this year.

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

#2). WKRC-DT is shown with 330KW ERP facilties, which I think involves an expired STA. We talked about this one before in Dayton thread,to refresh, the 330KW ERP STA was for temporary Low power last summer due to a failure of transmitter component, according to one of their engineer's who posted info about it on Cincinnati thread last Summer. He said(they told FCC this as well in exhibit attached to the STA application)it would be fixed within 8 weeks or so. I assume it was fixed, and I assume they are currently operating licensed facilities at 800KW ERP, but can't say for certian.

My thoughts: I suppose the a little than 3db difference probably doesn't really matter much .... They'll be moving to 12 in 2 years as well ....

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

#3). Incorrect callsigns : note/update : I realize Andy mentioned this issue earlier just wanted to be as complete as possible.....


Incorrect callsign for W36DG (on 36) analog -- Their old callsign, W61DE is shown for their analog facilities(but with correct info concerning their current analog operation on 36. Note: They moved from 61 to 36 over a year ago+FCC issued a new callsign for the new channel # at that time.

Incorrect callsign for W20CL (on 20) analog - Their old callsign, W47DE is shown for their analog facilties(but with correct info concerning ther current analog operation on 20.) Note: They moved from 61 to 36 over a year ago+FCC issued a new callsign for the new channel # at that time.

My thoughts : Probably doesn't matter too much, unless perhaps there's an additional problem going on here Andy is not aware of that might be a problem elsewhere ...

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

#4) - The rest

I'm pretty sure WAVE 3/WLEX, WBLU-LP, WWHO/DT and WKON info in the file is correct, otherwise I don't have any knowledge of the other non Cincinnati/Dayton stations in the file. I can confirm as of around 2000, W17AY, Seaman, OH was on the air, I don't know about what the present situation is with them.

As mentioned in earlier post, I'm a bit puzzled by the seemingly "optimistic" predictions for my location for WRCX-LP+WWHO(analog and digital), but I have no "concrete" evidence to support that anything is wrong, there. Given the distance+very nearby(and steep) terrain obstruction situation in that direction, And that the WWHO prediction for my location is(as expected, I just expected it to be a bit worse than it is) not an optimistic one to begin with, I would venture to guess(a WAG that is) there is probably nothing really "wrong" there ...

I am still puzzled about the WRCX-LP situation, however, and my best WAG on that one is perhaps it's somewhat possible the Station's facilities in the "real world" may possibly not quite match the info on the facilitity. Since, from what I can tell(and that is rather limited in terms of accuracy as well), there seems to be good evidence the modeling concerning the other stations seems to be working just fine concerning reception from my location, It certianly doesn't seem likely to me there is a problem here with the software itself ... So, Just one of those "puzzling things" to think about, I suppose ....

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

#6) Summary

That of course looks like a longer list than it actually is, at least "importance wise" - For instance, probably a number of folks would be interested in the WOTH and WBQC digital coverage when(or before) they get on air. Im also quite interested to see W24DG-D CP for digital companion channel for W20CL in there , as it is going to be co-channel with WCVN-DT 24, Covington, KY, and I'd think W23DM-D should be in there as well, although it's footprint will likely be quite small .....

It would also be nice to have the maps for WWRD-LP and W66AQ current facilities they are actually using to broadcast, although it's nice(and interesting to look at them) to have the maps for the CP's and apps they are not using yet as well.

Otherwise, For the most part I'd think what happens with the analog LP's not in the file, or whether their callsigns show up correctly/etc probably isn't of a lot of interest to folks these days ;-)

Everything else looks good For cincinnati/Dayton, from what I can tell ...

Re Height "Errors".

The SRTM Topographic database is in the GPS "Geoid" coordinate system,
which reports "height" relative to how well an egg "fits" the earth's surface:
http://en.wikipedia.org/wiki/WGS_84
Depending on where you are in the world, this can result in a GPS Receiver
"height" reading of up to +/- 200 feet while standing on the beach.
Some GPS Receivers can apply a height correction to convert to AMSL....

Very few Topo maps are in GPS (WGS-84) coordinates for both LAT/LONG and Height---check the fine print.

FCC antenna coordinates are listed in either NAD27 or NAD83 "Ellipsoid" coordinates:
http://en.wikipedia.org/wiki/NAD83

Height may be calculated SEPARATELY via surveyor techniques relative to
nearest AMSL (Avg Mean Sea Level) shoreline.....
As is usually shown on Topo maps....cuz it's "more accurate"...

I am trying to pull the file down in the first post and b i t t o r r e n t is telling me it isn't available. Is the file broken or has it been moved somewhere else?

Re Height "Errors".


Yes, but I'm not sure this explains Google Earth's terrain data showing something "downhill" that's actually "uphill" so to speak .... I.e. -- In one spot where it's flat and elevation is actually about 880FT ASL, it's showing 800FT where terrain is higher, and 865 feet in a spot about a KM west at the bottom of a steep hill where terrain is lower ....

Edit : Or then again, maybe it does, I dunno, it's making my head hurt to think about it .... think I'll stick to USGS Topo maps and similar if I'm hiking or orienteering and want to know if I'm going to be going up or down, and want to know where the "BM" markers are .... :-)

Update :

Another example -- Local airport field is 650FT ASL ... Exactly what my Topo Maps show ... As you might imagine, the runway is quite flat. In fact The biggest elevation change on the entire airport complex is no more than about 3 feet difference or so ...

Google Earth however shows quite an elevation change on the Main Runway, which is a bit over 1 mile long ... It shows the runway elevation at 694FT at one end, 656FT in the middle, and 688FT on the other end ....

On the other hand, I checked several other locations, such as The elevation(at ground level of course) for several of the tower locations in the area, and most of those seem correct.

I am trying to pull the file down in the first post and b i t t o r r e n t is telling me it isn't available. Is the file broken or has it been moved somewhere else?
Which file? All 30 MSA's look good on my end. The only files in the first post are zip or exe.

Never mind. I found my error.

I do see that WGHP High Point, NC has listed both the analog and digital AUX antennas and not the main antennas.

I also see that WBTV Charlotte, NC analog's AUX site is also listed not the main with the digital.

Thanks for all the great suggestions, everybody!

Since the topic of MSA vs. DMA has been discussed a bit, I thought I'd throw in my two cents worth...



As I understand it, DMAs are defined by dividing the entire country (except for a few parts of Alaska) into 210 non-overlapping polygons. These are mostly divided along county lines, but exceptions are made in some cases. DMA's are generally associated with an urban center, and individual counties are assigned to DMAs according to which television transmitters serve the majority of the audience. For example, if 45% of the audience is served by DMA X channels, 35% is served by DMA Y channels, and 20% is served by DMA Z channels, then that county is assigned to DMA X. This is done throughout the country, even in places with sparse population. Television coverage and audience demographics may change from year to year, but I believe the DMA definitions are kept the same for consistency. The primary purpose of these definitions is to divide the country into mostly independent units for allocating advertising resources.



The Census Bureau defines MSAs as urban groupings that are "socially and economically related" (e.g., where people commute to/from work). These are also defined as non-overlapping polygons mostly split along county lines and sometimes split along city boundaries. Any group that consists of 50,000 or more people is considered a metro. They also define "micro" areas as groups that consist of 10,000 or more people. These polygons do not encompass the entire country because they do not extend into areas of sparse population. The primary purpose of these definitions is to clump population centers into "islands" that have their own social and economic micro-culture.



Both systems are somewhat arbitrary in how they combine or separate some neighboring cities. This can have a big impact on where your particular city is ranked among all the other groups. I don't think either ranking system is any "better" than the other.



There are tons of pros and cons to using either definition, but I'll just comment on a few of the issues that I've thought about...



1) Both systems place boundaries around the audience, and not the transmitters. In a many cases, the audience will be served by transmitters that are outside of their DMSA (I'll abbreviate DMA/MSA). Also, many broadcast facilities are specifically designed to serve multiple DMSAs, so these shouldn't really be "owned" by just one DMSA.

2) Since both systems define boundaries along county lines, this probably puts a good percentage of transmitters "pretty close" to or "on" the line straddling two DMSAs. That's because county lines often follow natural geographic boundaries (e.g., ridgelines) and that's also where many transmitters are built because it gives them a good vantage point. The allocation of a transmitter to one DMSA or another is somewhat arbitrary depending on which side of an imaginary line it falls on.

3) Since DMAs completely blanket the country (and there are only 210 of them), individual DMAs can be quite large. That can be a pro or a con depending on how you look at it, but not everyone realizes just how big some of these chunks can be.

4) One advantage of the DMA approach is that 100% of the transmitters would be included by at least one of the 210 DMAs. Processing all 279 MSAs, on the other hand, does not guarantee that 100% of the transmitters have been included somewhere. DMAs make sure everyone is taken care of, even if they live in sparsely populated areas. The slight disadvantage here is that each DMA's map set would include a lot more transmitters that don't matter to the majority of people. In other words, the files would get significantly bigger to satisfy a small percentage of customers.



5) There's a somewhat philosophical discussion of what transmitter groupings work better:
a) Assign every transmitter to exactly one DMSA. This way, if every map set for the country were loaded at the same time, there would be no duplication of data. This means that your local DMSA's map set might not include some of the transmitters that serve you because they belong to neighboring DMSAs.
b) Or, for any given DMSA, include all the transmitters that can potentially be received. For the complete national data set, this means that some transmitters will be included multiple times. But it also means that if you download your local DMSA's map set, you'll probably have all the coverage maps you need without having to download neighboring DMSA data sets. If you live "in-between" DMSAs, then you'll probably need to download multiple data sets no matter what.
c) The reason this debate even exists is because we need to choose a happy middle ground that helps make this data easy to use and understand for as many people as possible. In theory, we could have one file per transmitter, or we could have all 13,192 maps in a single file, representing opposite ends of the spectrum. However, it's far more useful to the average person if the data is selectively grouped and filtered to include the information they want and minimize the information they don't want. It's sort-of like an information theory "signal-to-noise" ratio, if you will...



In regards to certain practical implementation details:

6) Both systems define areas as polygons. I do not have any of those polygon definitions in my possession, nor do I have any automated means for my software to extract transmitter data based on arbitrary polygons. This means that even if I wanted to, there's no way for me to really divide transmitters into polygon groupings right now.

7) I don't have access to Nielsen's DMA definition data since they are a commercial company that sells the data. Census data is freely downloadable.

8) The Census Bureau defines what they call the centroid of the population for each MSA. It's the weighted-average location for all the people within an MSA. What I do today is analyze all the transmitters within 125 km of the MSA centroid and package that as the MSA's map set. The 125 km radius was chosen to make sure that just about all the interesting transmitters were included for "spread-out" MSAs like Los Angeles. This is probably overkill for some of the geographically smaller MSAs, but it makes my life a lot easier if I don't need to make adjustments to optimize each and every MSA's transmitter set. The Census data makes it easy for me since they already define a point that's at the heart of each population cluster.



Closing Remarks

Both DMAs and MSAs are all about the people rather than the transmitters. Transmitters are often located far away from the audiences they serve because that's usually the easiest way to get higher and serve the maximum audience possible. I think even Nielsen must know that some transmitters serve more than one DMA. Splitting transmitters along DMSA boundaries is somewhat arbitrary and was not the intended purpose of those definitions.

In an ideal world, it would be best to custom build map sets for every user's location. That way everybody gets the maps they want and none of the ones they don't. That's not practical due to processing and data distribution limits, so some compromises must be made.

I'm mostly interested optimizing the ease of use for this data. For that reason, I'm opposed to forcing every transmitter to belong to only one data set. I'd prefer to have the majority of individuals only download one file and be satisfied. This will cause some transmitters to be included multiple times in the cumulative data set, but I think that's a small price to pay for improved convenience to the average user. For people who actually live within the boundaries of an MSA, I think the current scheme should do a good job of providing all the maps they need without requiring additional downloads.

That still leaves a lot of people who do not live in or near an MSA. Using the DMA partitioning scheme would fix that, but I'm pretty sure that will make each of the files a lot bigger and a bit more difficult to navigate. I'm still open to the idea, but right now I don't think it's in the best interest of the majority to go with these larger files and longer processing times. I have very limited resources, so I'd like to make the most out of what I've got and help as many people as possible.

This probably doesn't bode well for people living in-between or far away from MSAs, but I've had to make some hard choices about how to balance resource utilization with maximum public benefit.



I'll continue to give this some thought, but there's really no perfect solution other than making custom map sets for everyone. Again, thanks for the comments an suggestions...



Best regards,
Andy

First, I should note, although I have mentioned it, I should stress I am not necessarily concerned with the accuracy of the terrain data used by GoogleEarth itself as I have other more accurate tools to use for applications for which that is important.

I'm only interested, here, in the possible issues involved regarding the resolution+accuracy of terrain data used for the L-R Modelling/coverage maps themselves. And, it's potential effects on the modelling for my location, or other locations which at this point I'm thinking might possibly require more detailed/accurate terrain info for more accurate results to occur in some circumstances. Also, I would point out the reasons why I'm interested in this is mostly #1), to better understand+hopefully, better interpet results from the maps for locations involving terrain such as(or similar to) my location, as I think that might be useful. And perhaps to some extent, #2) As perhaps a bit of an example as a "cautionary tale" to folks trying to interpet results in similar circumstances.

I came across some perhaps better examples than I provided earlier concerning my interest in this as it relates to my specific location. I'll provide some of these in this post, and the next "part II" post, following.

Attached below as wptoatjeffs.jpg is what it shows for my location+nearby for WPTO 14(analog), Oxford, Ohio. I can't say with any "exacting" certianty, but I do believe the transmitting facilities being utilized by WPTO matches the info in FCC site+the info used, here.

Attached below as wpto14pic.jpg is screenshot of my WPTO14 Reception. Keep in mind, this is with use of a XG91, outdoors(tower mounted) at 35FT AGL(about 838FT ASL), aimed at WPTO transmitter - This aiming produces best results, BTW. Note that WPTO is also noticably weaker/snowier when leaves are on trees, leaves are not yet on trees, at present. The leaves coming on trees have similar effect regarding the signal strengths from The Cincinnati LP's+WCVN 54 analog, except that it doesn't effect WBQC-CA/WOTH-LP in a visable fashion because their signals are apparently a bit stronger.

Attached below as wptoelprofile.jpg is elevation profile between my antenna(at left) to WPTO using topo software. I do believe the representation of terrain here is fairly(if not quite) accurate. I'm providing this only to hopefully illustrate to some degree the severity of the terrain obstruction regarding LOS signal path. Of course, this does *NOT* represent the behavior of VHF/UHF signal propagation along the signal path, and it's also squeezing 18 miles of terrain into a few inches space, so in that regard from a RF standpoint on UHF where the signals will "hug" the surface of Earth and bumps on it rather than getting "driven into the ground", it probably looks worse than it is. Nevertheless, I have no doubt attenuation by terrain is likely quite an issue, here in this case. Note that For the antenna heights, I used the scale shown at left and a little measuring and the antenna height above sea level info for WPTO from FCC site, so it's not going to be exactly accurate, but should be fairly close -- Also Since this doesn't take curvature of earth into account, I've drawn a lower line in to *VERY* roughly estimate effect of curvature of earth on the LOS path. I make no claims as to the accuracy of that.

Note that the green shading for much of the map in my area for WPTO 14 is quite similar at my location+nearby area to what is the case with the maps for most of Cincinnati area full service stations(all but WCVN). Cincinnati stations(and WPTO digital) are in different direction than WPTO, and terrain isn't nearly as much of an issue for them. The distance is farther to Cincinnati but, excepting W36DG and WCVN, the transmitting antennas are much higher as well. Although the maps don't show it, in reality(and I can't think of a good way to demonstrate just how much difference), WPTO 14 signal is actually much weaker than the Cincinnati Full service stations(excepting WCVN), here, and weaker than a couple of the LP's(WBQC-CA and WOTH-LP).

Also, I show Blue or Blue~cyan/Cyan for Cincinnati LP's WBQC-CA, WOTH-LP and W36DG -- which seems more accurate, although(with same antenna mentioned earlier) WBQC-CA is allways "snow free" perfect analog reception, and WOTH-LP is very close to that as well. The terrain profiles with topo software are similar for those LP's to what I'm attaching to next post for WCVN, except that they are around 8~10 miles closer to me and the transmitting antennas for WBQC+WOTH are several hundred feet higher.

I was going to attach more examples showing the maps+screenshot examples of reception of stations such as WXIX(full service hi-power - "perfect" analog reception), and WOTH-LP(Low power but excellent pretty much snow free reception), but I think the description in these last 3 paragraphs as well as the earlier graphics I posted for W36DG(which is the weakest of the Cincinnati LP's here) should suffice. And, besides, we all know what "pristine" analog OTA reception without any snow/ghosts/etc looks like anyway, so that's not much fun, other than before DTV/HD when actually watching TV ;)

Attached below as WCVNatjeffs.jpg shows the map for WCVN 54 at/near my location. As you can see, it's blue shading for me. I think this is much more accurate regarding the reception I'm actually getting from them than is the case with WPTO 14. I can say with reasonable certianty that the facilities used for WCVN likely match FCC site info+what is used for the file. I can also add this tidbit, although unrelated to this -- One of their engineers has told us that, currently the beam tilt is greater for WCVN (More RF energy "focused" at nearby population) than for WCVN-DT(more RF energy towards Horizon).

Attached below as wcvn54pic.jpg shows my actual reception of WCVN. If it is not apparent in comparsion with the WPTO screenshot I provided in last post -- As you should be able to see, it is very similar to WPTO 14 reception, yet the map shading shows green for WPTO, and Blue for WCVN.

Attached below as wcvn54profile.jpg is elevation profile to WCVN, which was done the same way as noted in last post for WPTO 14. The purple line as my "guess" for the effects of Earth's curvature is to be disregarded, as its nothing more than a WAG ....

Attached below as WCVNatjeffs.jpg shows the map for WCVN 54 at/near my location. As you can see, it's blue shading for me. I think this is much more accurate regarding the reception I'm actually getting from them than is the case with WPTO 14. I can say with reasonable certianty that the facilities used for WCVN likely match FCC site info+what is used for the file. I can also add this tidbit, although unrelated to this -- One of their engineers has told us that, currently the beam tilt is greater for WCVN (More RF energy "focused" at nearby population) than for WCVN-DT(more RF energy towards Horizon).

Attached below as wcvn54pic.jpg shows my actual reception of WCVN. If it is not apparent in comparsion with the WPTO screenshot I provided in last post -- As you should be able to see, it is very similar to WPTO 14 reception, yet the map shading shows green for WPTO, and Blue for WCVN.

Attached below as wcvn54profile.jpg is elevation profile to WCVN, which was done the same way as noted in last post for WPTO 14. The purple line as my "guess" for the effects of Earth's curvature is to be disregarded, as its nothing more than a WAG ....

Hey Jeff,

Great posts and the pictures really made me think about what could be causing your difficulties receiving WPTO.

Without being there, I would have to say that it is the XG-91 causing the problem, at least in part. I'm not bashing the XG-91; I wish it was constructed more strongly than it is, but now that I have seen people on here show me what it can do, I am quite impressed by that antenna!

But I do know the XG does somewhat better receiving the upper UHF channels than the low ones. And channel 14, on that antenna, is pushing the design limit. If you used a ChannelMaster 4228, I'd bet it would be better. And, it also explains your reception on channel 54. I'd also guess the ChannelMaster 4228 wouldn't get it in quite as well as you do.

Using my 4228, I have 4 full-power analogs at channel 50 and above here in the Chicago area that I get: 50, 60, 62 and 66. Once you hit 60 and see 62 and 66, you can tell that the performance of the antenna is significantly diminishing, as has been proven in tests by the chief engineer at KSL-DT. The channels get snowier as you go up from 50...and I use very good quad-shielded RG-6 and a ChannelMaster 7777 preamp, so I know I'm not getting loss from my cable of any significance. Also, the resolution of the data made is such that areas of problems on a block-by block scale won't show up. In fact, that would be impossible to do with local effects such as housing and trees, that possibly can't be taken into account without running the program on a mainframe to crunch all the data! :)

Finally, as you pointed out, beam tilt means a lot as well. We had a 150 kw analog station on channel 28 in Chicago that you could get watchable all the way out to Creston, Illinois...72 miles west of Chicago. That was because on their beam tilt, they could run over 300 kw. In my attic, in a small river valley 60 miles west of Chicago, they were pretty much cable TV quality in terms of reception. I would think more stations would run a .5 degree beam tilt or higher...because blasting a signal into space and to areas which can't get the signal normally really does nobody any good. Except for us DX'ers, so I don't mind. :D

And of course, as always, these are approximations that the FCC agrees are the best (or of least regret). Like you, they are fascinating and raise some great questions!

Did you fix the one missing station I mentioned, W42CK?

Thanks! It's fixed as of today (4/14). At first, I couldn't tell why this channel was excluded because I could certainly see in in the FCC's data files. Then, upon more detailed inspection, it turned out that this record had been tagged as an "archive" record, meaning that it is not supposed to be active any more. I think this tag was mistakenly put there since the data definitely shows the expiration date for this has been extended until 2012. I put in another database "patch" in my local overrides database to fix this mistake.



But, we don't have in the file:

W23DM-D Digital - This is CP for Digital companion channel on 23 for W56AM

W24DG-D Digital - This is CP for Digital Companion channel on 24 for W20CL (formerly W47BC).

WOTH-LD Digital - This is CP for digital companion channel on 47 for WOTH-LP(25).

WWRD-LP 55 (analog) - This is where WWRD-LP is currently transmitting, with Licensed facilites.
It looks like these transmitters were overlooked because their application records have the callsign listed as "NEW" instead of their actual call sign. I've modified the code to dig in other places to try and find the correct callsigns and it looks like these particular transmitters are now correctly imported. It looks like you've uncovered a new class of missing data in the FCC database that I can now work-around in the code. This change seems to have found the correct callsigns for several other transmitters as well.



WKRC-DT is shown with 330KW ERP facilties, which I think involves an expired STA. We talked about this one before in Dayton thread,to refresh, the 330KW ERP STA was for temporary Low power last summer due to a failure of transmitter component, according to one of their engineer's who posted info about it on Cincinnati thread last Summer. He said(they told FCC this as well in exhibit attached to the STA application)it would be fixed within 8 weeks or so. I assume it was fixed, and I assume they are currently operating licensed facilities at 800KW ERP, but can't say for certian.
Thanks for the update! It's been patched for the next update.



Incorrect callsign for W36DG (on 36) analog -- Their old callsign, W61DE is shown for their analog facilities(but with correct info concerning their current analog operation on 36. Note: They moved from 61 to 36 over a year ago+FCC issued a new callsign for the new channel # at that time.

Incorrect callsign for W20CL (on 20) analog - Their old callsign, W47DE is shown for their analog facilties(but with correct info concerning ther current analog operation on 20.) Note: They moved from 61 to 36 over a year ago+FCC issued a new callsign for the new channel # at that time.
The code change put in for the earlier missing LP transmitters also seems to have uncovered the correct callsigns for these transmitters as well. There does seem to be a lot of good that's come out of the change, but it's also possible that new kinds of errors have been created due to this change.



I'll post an updated master transmitter file in post #1 a little later to include all these fixes. We'll just need to keep an eye out to make sure none of the previously correct entries got screwed up by the latest fix.



Thanks for all the great input!



Best regards,
Andy

I'm assuming the terrain data used for the coverage maps is something more precise than what we get when we're using Google Earth "alone"?
I do not know where Google Earth gets their terrain data. What I use is the "finished" SRTM data that has been further cleaned up by the folks at CGIAR. This terrain data is available in 3-arc second (~90m) and 1-arc second (~30m) resolutions. The raw data was collected from the Space Shuttle using synthetic aperature radar techniques to measure the "first reflected signal" off the objects on Earth. This means that buildings, trees, and other objects present at the time of data collection actually count as part of the terrain (sounds strange, but it's not as bad as you think).

Prior to this data being collected, there really weren't any good sources of high resolution terrain data available to the public. USGS topo maps existed and other lower resolution terrain data was available, but they were not very detailed and sometimes had mistakes. My first hand experience while hiking and off-roading can attest to the fact that USGS topo maps are not always accurate.

The FCC has their own terrain data set that they use for license evaluation. I believe their data was created by tracing the elevation contours on topo maps. At one point, I downloaded their entire terrain data set and used it in my modeling tools. However, I discovered several differences between their data and the SRTM data and decided that the SRTM data set seemed more correct. Since then, I have given up on using the FCC's terrain data.

Even though the SRTM data is based on "first reflection" heights, it is still of higher resolution and better quality than most of the other sources I've come across. The absolute vertical accuracy of the data is good to within about 10 meters (2-sigma) throughout North America. Much higher resolution data sets exist, but none of them are free.



With regards to the coverage maps, the terrain profile density and density of simulated cells had to be limited in order to make them finish processing in a reasonable amount of time. With the current processing resolution, the maps provide enough detail to look at coverage at the neighborhood level (~300 m). The current maps should NOT be used to draw conclusions for a specific address since the detail simply isn't there. BTW, it takes roughly 8 hours to process one metro's data set at this resolution. If I were to generate the same maps at the highest resolution supported by the terrain data, it would take about 2 weeks to generate one metro (and the files would be about 500 MB).

My radar plots, on the other hand, are computed using the full resolution of the terrain data.



I hope that helps.



Best regards,
Andy

They are fascinating and raise some great questions!

Yes -- Appreciate the comments+thoughts!

I should say, I'm probably going to end up doing it a bit with this post, but I don't want to go off too much onto a tangent for this thread concerning such issues as more details on antenna setup used here(performance characteristics of various antennas, use of preamps, notch filters/etc and/or why and exactly how I am using those) or concerning my observations of the "RF environment" at this location(and/or how I've made those observations) and the effects of various factors on reception here.

As, I'd think(My personal thoughts anyway) we probably want this thread to be more about the Maps+helping folks to use them/etc than it perhaps should be about our antennas, as there are other threads that are probably better suited for that ... But, that's just my opinion, FWIW ....

As for my WPTO reception, to put it another way+take the XG91's performance characteristics out of the equation for this example(I couldn't however think of a good way to provide comparative screenshots/etc of this, which is why I used the XG91 for those) --- the map shows "green" for WPTO, but, any attempt to, say, use an "indoor" antenna, (such as say such as UHF loop or Folded dipole("bowtie") such as the sort used to come "free" with small TV's), under best of circumstances(such as in this case, say near a 2nd story window with "regular glass" facing WPTO analog or near ground level outdoors) results in extremely weak reception of WPTO - such as something along the lines of the W20CL screenshot I posted earlier, perhaps a bit worse. Which would also lead me to believe the signal is signficantly weaker at this location than is predicted by the map in this case. This sort of "barely there" reception with such indoor/etc. antennas is the same(pretty much) for WCVN, and in that case, Andy's maps do seem to indicate that much more accurately. Just FYI, Note that FCC contour methodolgy (or the prediction from the "ardman.net" site which I don't think is available any longer), Says I'm within WPTO analog "Grade A" signal contour.

OTOH, as noted previously, The "green" I get seems much more accurate regarding Most Cincinnati full service digital stations maps(and probably regarding the green for their analog counterparts as well), as for instance, they *can* be recieved rather reliably with a UHF folded dipole(+VHF rabbit ears for the VHF station) placed near a 2nd story south facing window, which is the best case "scenerio" for indoor antenna reception, here -- Reception of the analog counterparts involved with that sort of setup "seems" somewhat a bit less than stellar in most cases on UHF(meaning a bit snowy, generally), generally fairly decent on VHF.

I will also note I've used other antennas, such as from '93 to 2004, a RS VU210 mounted in the same spot as XG91 is currently. The situation was roughly the same as the examples I've provided for WCVN/WPTO with the XG91(and the UHF section on VU210 isn't the best performer on Hi-UHF frequencies), I've allways expected mostly due to to more severe terrain losses concerning WPTO.

I should also probably mention, although it is certainaly sometimes(rarely) an issue, Co-Channel WCMH-DT 14, Columbus (78 Miles from me right off back side of antenna when aimed at WPTO) was not an issue at the time when I took the WPTO 14 screenshot, and usually isn't an issue given use of directional antenna+ proper antenna aiming for WPTO, and would also point out again that this issue with WPTO existed before WCMH-DT came on air.

That being said, (given proper antenna aiming of course) I do see WCMH-DT fairly often, especially in the spring/summer+fall months(The drier winter months are generally not conducive to temperature inversions+enhanced "troposcattering" conditions in this region ), including with the XG91 .... But, the F/B ratio with XG91 seems to be good enough that it is quite rare for WCMH-DT to "snow up" WPTO with antenna aimed right at WPTO ... It has happened on occasion, however probably more often with VU210 ... I've used CM4228 as well, but only for a short testing period(and a different, less desireable mounting location than XG91 or VU210 previously) so I can't really comment/compare accurately about it+WPTO reception other than to say it was worse due to other factors involved ....

As for Dx'ing can't pass up an oppurtinity to talk a bit about it :-) , so, I will add that I've noticed the directions which are the most "terrain obstructed" here, defintely cuts down on Tropo Scattering/ducting logs here in those directions compared to directions that are not as obstructed by nearby terrain, especially the higher the frequency involved/generally when the terrain obstruction is of the "nearby+steep" variety where the ground is higher than my antenna as nearby as 300~600 feet distant). But, from what I can tell, that isn't a significant issue for signals via Sporadic E propagation ... I expect this is due(basically) to the "tropo" DX signals (troposcatter or ducting) being propagated closer to the earth's surface+coming in at "lower angles" so to speak than is the case with E-skip, which is coming in at much higher angles(usually) from E layer of ionosphere ...

Typically, for instance, (except under very "dead band" conditions for "tropo" which occurs most often at it's "worst" during the drier, winter months at this location) it's fairly common to see weak, fluttery signals from stations such as WBXX 20, Crossville, TN (220 Miles) popping in and out above the snow on a regular basis due to "everyday" scattering of signals in the lower regions of earth's atmosphere ... It helps that WBXX is in one of my least "terrain obstructed" directions, and it also helps, I would imagine that their tower is on a mountain, over 5000FT above sea level ... But, on UHF anyway, that sort of thing never happens on a regular basis from stations at similar distances(or even distances at 100~150 Miles) in more terrain obstructed directions ....

We'll just need to keep an eye out to make sure none of the previously correct entries got screwed up by the latest fix.


Yes. Probably also a good idea for us to keep a good eye on the FCC TV query+CDBS info, as you never know when they might change how they do this or that regarding the Apps/cp's etc ..... especially perhaps for the relatively new LP digital stuff ....

Anyway, thanks for getting on the corrections so quickly ...


What I use is the "finished" SRTM data that has been further cleaned up by the folks at CGIAR. This terrain data is available in 3-arc second (~90m) and 1-arc second (~30m) resolutions.


First, thanks for the detailed info! I remember reading about that and the shuttle missions involved.

Thought it might be interesting to take a look at what the SRTM data shows for my location. so, Downloaded the CGIAR 90m data for my area+looked at it a bit with DLGV viewer available from a download link from USGS website. I'm familar with this sort of thing as in late 98 I recall I had looked at/downloaded several 7.5 Minute quads I was interested in from some of the DEM SDTS data USGS had available for download at that time ....

Of course, it looks quite accurate for my area, and it's very interesting to look at --So much so, I might have to look for some of the 30m data. Anyway, it's showing 247.9 Meters elevation for location of base of tower for my antenna(well, more or less), or in other words, about 813 Feet ASL ... That's only 10~11 feet different than USGS topo quad, or Delorme USA shows, or a pilot friend's "caibrated" altimeter when we checked it (all three of the latter sources indicated 802~803 Feet ASL for the same location) .....

Attached as srtmjeff.jpg is a "zoomed in" view near my location using the SRTM data --- I've drawn in arrows to indicate to show what is not only the "direction" the stream course runs that carved the small, steep valley I'm in, but also, as it just so turns out, generally, the direction of most of The Dayton and Cincinnati Transmitters ..... The far left of yellow line is my antenna location, and this line is for a elevation profile for the first 2 km or so to WWHO ....

Attached as wwhofirst2km.jpg is the elevation profile for the yellow line drawn in the other file attached to this message ... My location is at left ... Although the elevation change itself isn't that drastic if say, you are used to climbing mountains ... Nevertheless, it should hopefully better illustrate than my earlier examples just how "steep" some of the terrain involved is .....


My first hand experience while hiking and off-roading can attest to the fact that USGS topo maps are not always accurate.


Oh yes, I've certianly ran into some, what I'll call "oddites" in that regard as well ... Neverthess, most of the time I've been quite impressed with the accuracy of the USGS topo quads ....


With regards to the coverage maps, the terrain profile density and density of simulated cells had to be limited in order to make them finish processing in a reasonable amount of time. With the current processing resolution, the maps provide enough detail to look at coverage at the neighborhood level (~300 m). The current maps should NOT be used to draw conclusions for a specific address since the detail simply isn't there.

BTW, it takes roughly 8 hours to process one metro's data set at this resolution. If I were to generate the same maps at the highest resolution supported by the terrain data, it would take about 2 weeks to generate one metro (and the files would be about 500 MB).


Understood+I hope I'm not being too "persistant" with this because as it was, I had already read other posts of yours where you detailed this information as well as the info on your radar plots --

So, I Hope I can explain this properly/well enough -- I'd read your info about 300M resolution earlier as well, and suppose what I'm trying to do with this entire exercise is to at least get a better "feel" for what that (300m resolution) Means in regards of accuracy for locations similar to mine, particuarly so regarding steep vertical rises ... Also, I was hoping that posting some of the examples I have/etc might help others who are interested in these maps, including perhaps in a more overall sense regarding applications for them and ways they can be utilized vs. related to their accuracy in some, specific circumstances.

The reasons for this is not so much for myself, as I'm already quite aware of the effects of the nearby terrain/etc. on the RF environment on VHF/UHF at my location(although it's very fun to look at the maps+the terrain/topo data and look at it in a little different way as well), but to hopefully be able to better interpet results to some extent for others/other locations I'm not as familiar with .... Such as when someone new comes to our local threads and asks about what his/her reception might be like, but doesn't necessarily want to spend much time/effort investigating for themselves ....

For instance ... If you look at the some of the screenshots I provided from your coverage maps, the elevation profiles/etc, as well as the screenshot of SRTM data attached to this message, regarding locations in the "deeper" valley(at lower elevation) just to my S+SSW , it's very obvious that that particular terrain feature appears to be better "modeled" regarding the effects of it on VHF/UHF signals ... In fact, I've seen very similar results with other Longely rice studies with other (commercial)software for that particular terrain feature ... However, although the similar terrain feature involved for my location is very similar to that(and actually "part of it"), the "gouge in the earth" involved, so to speak, is a bit less pronounced here ....


My radar plots, on the other hand, are computed using the full resolution of the terrain data.


Understood as well -- please correct me if I'm wrong, but The thing is, I don't think we have access to those radar plots other than asking you to do them for us, on an individual basis .... Personally, I think that's asking too much of you (as in going beyond the call of duty) for everyone interested to ask you to run one of those for them for their particular location, especially when you're already going way beyond the "call of duty" to provide these coverage maps etc ...

That being said, you had ran a radar plot for my location previously, but It was a digital only plot --- and, If you do happen to get some spare time, I would certianly be interested in seeing the results for analog for my location as well as well, especially regarding WPTO 14(analog) and the LP's in the area in this case, given the detail I provided on it here regarding the maps/etc - note that WPTO digital transmits currently from a different location, In Cincinnati(WXIX tower specifically, as is correctly show) ....

Ideally, of course, if it is/were possible, I think it would be a great thing if the radar plot could be implemented in such a way that it could be made available as a web-based tool for users to use ..... Just a thought, FWIW ...

BTW, I'm not sure if you had seen it as it got "bumped" to the bottom of page on the thread at the time, but, just in case you missed it, I *did* respond to your last message in Dayton Thread ...


I hope that helps.


Oh yes, Thanks!

Andy,
This is outstanding. Thank you so much. I eagerly await Columbus, OH!

Ideally, of course, if it is/were possible, I think it would be a great thing if the radar plot could be implemented in such a way that it could be made available as a web-based tool for users to use ..... Just a thought, FWIW ...


Never mind my comments+request in last post for radar plot for analog for my location ---- Found this via the "update link" in the new 4/14 transmitter file from first post - Duh! - Nice work, Andy !!!!!! :

http://www.tvfool.com/index.php?option=com_content&task=view&id=13&Itemid=45

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

Results Updated/corrected at 3:25pmEDT : Made some errors when I orginally posted this(such as looking at the results for W36DG digital CP rather than their current analog facilities), and Decided to just attach my radar plot results below as jeffsradarplot.jpg (note : I resampled the image to 600x341/converted to jpg so it could be attached here+be a bit "smaller", and ran a unsharpen filter to hopefully make text more legible because of the resampling)

Although I think (for whatever reasons), WPTO turns out to be a bit "worse" than that, and WCVN a bit better, This(and what it says for other stations in the area) certianly seems much more accurate ....

Update: I also now see the link to the radar plots (experimental) updated a couple of days ago in first posts - Sorry I missed that before posting the stuff in last message about it, again D-U-H !

...please correct me if I'm wrong, but The thing is, I don't think we have access to those radar plots other than asking you to do them for us, on an individual basis...

That being said, you had ran a radar plot for my location previously, but It was a digital only plot --- and, If you do happen to get some spare time, I would certianly be interested in seeing the results for analog for my location as well as well, especially regarding WPTO 14(analog) and the LP's in the area in this case, given the detail I provided on it here regarding the maps/etc - note that WPTO digital transmits currently from a different location, In Cincinnati(WXIX tower specifically, as is correctly show)

Ideally, of course, if it is/were possible, I think it would be a great thing if the radar plot could be implemented in such a way that it could be made available as a web-based tool for users to use ..... Just a thought, FWIW ...
Yes, I was hoping to turn the radar plots into an self-serve tool that everyone could use. In various posts in other threads, I mentioned that I'd start working on it, and I have. Things are very experimental at this point, but you can try the work-in-progress at this link (http://www.tvfool.com/). A friend of mine was willing to set up and host this experimental site for me, so if you get a chance, please let him know what a valuable service he is providing. If he sees enough demand for the site, he may be willing to keep it up indefinitely.

There's still a lot of work to be done, but you should be able to serve-up your own radar plots now. This is at an alpha-level of testing, so don't be too surprised if there are a lot of bugs. Let me know if it works for you.

Best regards,
Andy

^ Andy,

I think you may have missed my post a few minutes before your last one, LOL -- sorry :-)

Functionally, it appears to be working well and rather quickly, too -- You'll find some notes in last post regarding my radar plot results+some of the weaker stations ... At first, I accidently plugged in Meters above sea level(approx 255 Meters) for antenna height instead of Meters above ground, that certianly gave some interesting results+was easy enough to start over+plug in the correct value (approx 11 meters) ...


if you get a chance, please let him know what a valuable service he is providing. If he sees enough demand for the site, he may be willing to keep it up indefinitely.


Will do! Is the best way to do that via the "contact us" links on the site ?

Will do! Is the best way to do that via the "contact us" links on the site ?
Probably, since I'm sure he'd prefer to keep his email private. I believe the webadmin messages will be directed to his attention.

Best regards,
Andy

Andy,

#1) . should note I'd made some errors regarding some of the info from my radar plot results, and edited my earlier post accordingly, including adding attachment to the full radar plot results ...

#2), Just finished checking the updates for Cincinnati/Dayton area transmitters in the 4/14 transmitter file from first post ...

The corrections look good, including the WKRC-DT ERP fix+addition of the digital LP CP's - Only oddities that are still there from my earlier corrections list is :

WWRD-LP 55 (current analog facilities) Not shown, but the info for their CP for 32 is - Scroll down here for the info for channel 55 for their current licensed facilities :

http://www.fcc.gov/fcc-bin/tvq?call=WWRD&list=0

W66AQ - current analog facilites on 66 Not shown, but the info for their application for 22 is.
Scroll down here for the info +see the channel 66 entry for info on their current licensed ch 66 facilites :

http://www.fcc.gov/fcc-bin/tvq?call=W66AQ&list=0

WWRD-LP 55 (current analog facilities) Not shown, but the info for their CP for 32 is

W66AQ - current analog facilites on 66 Not shown, but the info for their application for 22 is.
Thanks! Both of these have been fixed for all future simulations. I'll update post #1 shortly.

Best regards,
Andy

The next 6 MSAs have been added to post #2 and seeded.

Best regards,
Andy

Andy,
I joined this forum for the primary purpose of being able to use google earth to view local TV station transmitter locations but when I attempt to download the file, FCC_TV_2007-04-16.kmz.zip, I get an error message stating that the site cannot be found.
Please advise.
Thanks,
Tulsa8144
Please use my email address to respond.

Lots of luck with that.

There is a problem with AVS and files such as that when you click on them, it says file not found. I have no idea why - ask a mod.

Go to the link, right click and choose save target to:

Select a place to save it (like your desktop) and let it go.

Andy,
I joined this forum for the primary purpose of being able to use google earth to view local TV station transmitter locations but when I attempt to download the file, FCC_TV_2007-04-16.kmz.zip, I get an error message stating that the site cannot be found.
Please advise.
Thanks,
Tulsa8144
Please use my email address to respond.
As HDTVFanAtic says, right clicking and using "Save Target As..." seems to work, while regular clicking does not. If you continue to have problems, you can also download the file from here (http://www.tvfool.com/index.php?option=com_content&task=view&id=16&Itemid=46).

Best regards,
Andy

I got the Sacramento file downloaded and opened it up in Google Earth. I see all the stations in the Sacramento region plotted and labeled. When I click on a station in the "Tx Select" folder the image briefly goes light and then back to normal contrast but no colored transmitter plot is displayed. I tried adjusting the Layer Transparency but it doesn't do anything. Am I missing something or does the Mac version of Google Earth have a bug in it?

I got the Sacramento file downloaded and opened it up in Google Earth. I see all the stations in the Sacramento region plotted and labeled. When I click on a station in the "Tx Select" folder the image briefly goes light and then back to normal contrast but no colored transmitter plot is displayed. I tried adjusting the Layer Transparency but it doesn't do anything. Am I missing something or does the Mac version of Google Earth have a bug in it?
I can't say for certain as I don't have a system to test that on at the moment. However, I would suggest trying to move the kmz file to a different location and trying again. The kmz file contains several png files, one for each coverage map, and those files need to be extracted to a temporary location in order to be viewed. Some people have had problems because the kmz file was put in a location (e.g., their desktop) that did not have write privileges for creating the temporary files. Moving the file to a different location helped in most cases.

Another thing to try is dragging the package out of "Temporary Places" and putting it in "My Places" within the folder structure of Google Earth. This should copy all the relevant files and links into a separate location that should not have any issues with file access privileges.

I hope this helps. I will try to test this on a similar platform in the next few days. If I discover what the problem might be, I'll let you know.

Best regards,
Andy

Coverage maps have been expanded to another 14 metros. That covers the top 50 MSAs, so far! :)

Best regards,
Andy

I can't say for certain as I don't have a system to test that on at the moment. However, I would suggest trying to move the kmz file to a different location and trying again. The kmz file contains several png files, one for each coverage map, and those files need to be extracted to a temporary location in order to be viewed. Some people have had problems because the kmz file was put in a location (e.g., their desktop) that did not have write privileges for creating the temporary files. Moving the file to a different location helped in most cases.

Another thing to try is dragging the package out of "Temporary Places" and putting it in "My Places" within the folder structure of Google Earth. This should copy all the relevant files and links into a separate location that should not have any issues with file access privileges.

I hope this helps. I will try to test this on a similar platform in the next few days. If I discover what the problem might be, I'll let you know.

Best regards,
Andy

I took a fresh look at it this morning. I forgot that when I use the Bit Torrent program to download the file that it makes me save it as Sacramento.* not Sacramento.kmz. Google Earth does not recognize a .* file so I changed it to Sacramento.kmz. Then Google Earth will open it but no transmitter overlays.

I discovered what the transparent white screen is. If I view all of northern and central California at the same time and click on a tranmitter, I get a large white tranparent square overlay for about 1 second and it disappears. This only appears the first time I click on a different transmitter. Subsequent selection of the same transmitter displays nothing. Also FWIW, inside the large white square is a large dim circle broken at the top and bottom with one arrow on each half of the broken circle.

I going to look into your directory location idea. I did move it so I'm unsure if that is a problem or not.

Thanks for your help,

Chuck

Coverage maps have been expanded to another 14 metros. That covers the top 50 MSAs, so far! :)

Best regards,
Andy

Kudos for your efforts. This is an extremely well thought out addition to Google Earth! I hope you continue rolling out additional DMAs (#98 Johnstown-Altoona-State College, PA) is of particular interest to me.
Best wishes.

Andy...

I finally was able to study the files in google last evening for Rochester and Buffalo, Ny.

Awesome...unbelievable.

when you get to the syracuse, ny dma, please add Utica, Binghamton, Ithaca, watertown, ny towers within. those towns are very small and towards the end of the dma listing.

thanks so much.

Rick

That covers the top 50 MSAs, so far! :)

And Greenville-Spartanburg-Anderson SC is #51. :( So I'll just have to wait for the next batch.

Your maps for Charlotte do correlate well with my experience in receiving (or not receiving) those stations. They indicate that my strongest signal should be WBTV-DT (blue-green), which I can in fact receive pretty reliably 24/7. Next come WCNC-DT, WJZY-DT and WMYT-DT (light blue) which I can usually receive reliably in the evening and at night, but sometimes have dropouts during the day. The rest are dark blue or violet, and I can get them only at night, and even then only when tropospheric enhancement kicks in strongly enough.

(This is with a Radio Shack VU-190XR on the roof, and a CM 7777 pre-amp.)

jt...time to add the 91xg to the setup and use the rs for vhf.

just reversed my antennas a few weeks ago. I may replace the hd8200p with a wade vip306 for vhf/fm. it is 29" shorter than the 8200p and a tadd better on vhf/fm. getting a quote on monday.

As I noted before the transmitter overlays do not work on the Mac but I have a PC too so I downloaded Google Earth for the PC. Using the PC I read the .kmz files over my local network from the Mac. They work fine on the PC so I don't think it's the files. Must be a Google Earth bug in the Mac version.

Like everyone else I'm finding this amazing! As I suspected nearly every station I receive is magenta or purple and in some cases no color at all. A pair of 91XGs, a preamp, and the antennas 62' up are pulling a rabbit out of the hat for me. :)

Andy, if you understand what's not working in the Mac version perhaps you can report it to Google. I don't have a clue what the problem is.

the transmitter overlays do not work on the Mac

The overlays work fine on the Mac in my office, an older G4 (800 MHz?) running the latest version of OS X 10.4. I haven't tried to run Google Earth at home (OS X 10.3.9) because I have only a dialup connection here.

time to add the 91xg to the setup and use the rs for vhf

I've been thinking about the 91XG for a long time, but just haven't had the time to make arrangements with an installer. But now spring semester is almost over, and after I turn in final grades next week I'll probably go ahead and do it before my wife and I start traveling this summer.

I want to replace my rusty old mast while I'm at it, and ditch the Radio Shack monster for a high-VHF antenna because I don't need low VHF any more.

The overlays work fine on the Mac in my office, an older G4 (800 MHz?) running the latest version of OS X 10.4. I haven't tried to run Google Earth at home (OS X 10.3.9) because I have only a dialup connection here.


Interesting. I'm using an older G4 also (Dual 867 MHz Mirrored Doors) with OS X 10.4.8. Seems unlikely but maybe I need 10.4.9. I don't think this makes any difference but where do you have your .kmz files stored?

When I click on a tansmitter I get the large white square which I now assume is the bounds of the overlay. I see the same thing on the PC. When that disappears the overlay is supposed to appear in its place but it doesn't.

I don't think this makes any difference but where do you have your .kmz files stored?

Mine are on the desktop because I was too lazy to move them after I downloaded them. Let me try moving them into a proper folder inside my Documents folder... yep, still works!

When I click on a tansmitter I get the large white square which I now assume is the bounds of the overlay.

I don't get that white square at all. The radiation pattern comes up immediately when I click the button for one of the transmitters in the "Tx maps On/Off" folder.

How many colors do you have your display set for, in System Preferences? Mine is set to "Millions".

Interesting. I'm using an older G4 also (Dual 867 MHz Mirrored Doors) with OS X 10.4.8. Seems unlikely but maybe I need 10.4.9. I don't think this makes any difference but where do you have your .kmz files stored?

When I click on a tansmitter I get the large white square which I now assume is the bounds of the overlay. I see the same thing on the PC. When that disappears the overlay is supposed to appear in its place but it doesn't.

Even better...download the latest version of Google Earth. They fixed bugs with it last week.

I don't get that white square at all. The radiation pattern comes up immediately when I click the button for one of the transmitters in the "Tx maps On/Off" folder.

How many colors do you have your display set for, in System Preferences? Mine is set to "Millions".

You need to be in a wide view mode, like about 300 miles vertically and horizontally and it only appears for 2 seconds or less and only the first time you click on a TX. Same thing on the PC. I think it only appears when you initially load the overlay.

I shouldn't have any display problems, millions of colors on a Dell 2405FPW LCD.

Even better...download the latest version of Google Earth. They fixed bugs with it last week.

That must be the PC version. I downloaded again and the version is January 30, same as I'm using.

These sorts of software problems are very frustrating. At least I can run it on the other computer.

Interesting. I'm using an older G4 also (Dual 867 MHz Mirrored Doors) with OS X 10.4.8. Seems unlikely but maybe I need 10.4.9. I don't think this makes any difference but where do you have your .kmz files stored?

When I click on a tansmitter I get the large white square which I now assume is the bounds of the overlay. I see the same thing on the PC. When that disappears the overlay is supposed to appear in its place but it doesn't.
I checked on a few Macs and none of them seem to be having the problem. I'm beginning to suspect this is more of a video card or driver issue. Do you know what graphics card you have?

My suspicion is that the texture maps may be too big for your graphics card or driver to handle. Some cards (esp. older ones) have limits on how much memory they can store for a texture map. The images used for the overlays are roughly 1600x1600 pixels. It's possible that your graphics system has an artificial limit (e.g., 1024x1024) that prevents the overlay from being loaded, but I would think any modern 3D card and driver should be able to handle this without a problem. Google Earth's documentation implies that the program itself is capable of handling at least 2000x2000 images without any problems.



There are a few experiments that are probably worth trying:

1) Try minimizing the memory and 3D complexity that needs to be processed by the graphics card. In the Google Earth options, set the Detail Area to "Small", set Texture Colors to "16 bit", enable Texture compression, set Anisotropic Filtering to "Off", and set Terrain Quality to its lowest setting. It this works, then it means there's a memory size limitation with the graphics card / driver.

2) Try creating your own image overlays in different sizes. If you're able to import a 2000x2000 image as an overlay, then the problem is not with the graphics rendering part of Google Earth. If that doesn't work, then you should try several smaller sizes until you find one that works.



The files work on all the Macs I've tried, so I'm not sure that I have anything else useful to add.

I hope this helps!

Best regards,
Andy

I checked on a few Macs and none of them seem to be having the problem. I'm beginning to suspect this is more of a video card or driver issue. Do you know what graphics card you have?

The video card is a GeForce4 MX with 32MB of RAM. Apparently it is the video card even though none of your suggestions made any difference. I discovered though that the 3D function in Google Earth doesn't work either. This card is supposed to support 3D but I guess it's too old, 5 years now. Someday I'll upgrade this computer but not until OS X 10.5 comes out. In the meantime I'll just use the PC for Google Earth.

Thanks for your help.

Another 14 MSAs have been added to the list (check post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) for updates). That brings our total to 64 MSAs! :)

Best regards,
Andy

Andy, I noticed a mistake in the Denver MSA. You have digital stations KCNC 4, KRMA 6, KUSA 9, and KTVD 20 ( i used the virtual channels, I dont remember the real channels) shown at their final locations that are still under construction while in reality they are still running on their STA from downtown at low power. KMGH 7 is shown downtown so I used its map to approximate the coverage for the other channels.

Also for those of us that dont do torrents ( I had a friend get Denver for me) I have a website with disk space and bandwidth to burn and would be happy to host some of the files with your permission.

Andy, I noticed a mistake in the Denver MSA. You have digital stations KCNC 4, KRMA 6, KUSA 9, and KTVD 20 ( i used the virtual channels, I dont remember the real channels) shown at their final locations that are still under construction while in reality they are still running on their STA from downtown at low power. KMGH 7 is shown downtown so I used its map to approximate the coverage for the other channels.

Also for those of us that dont do torrents ( I had a friend get Denver for me) I have a website with disk space and bandwidth to burn and would be happy to host some of the files with your permission.
Thanks for the updates!

I will incorporate your fixes into an updated transmitter database in post #1 shortly. It will also go into effect for simulations done after today.

BTW, I don't suppose these are related to the debate over Lookout Mountain. If you ever get word that the issues have been resolved, then please let me know and I can update the database again.



As for file hosting, I'd welcome any spare resources... Keep in mind, though, that the files are tens of megabytes each. The collections of MSAs so far has reached 3 GB and we'll get to about 12 GB by the time we're done with the first pass. You might want double-check what kind of disk space and bandwidth you're able to support. The choice to use torrents was for bandwidth efficiency since it was clear early-on that these files would be big and that demand would be too much for my limited resources. BTW, it would be alot easier if someone could mirror the entire collection since that makes it easier to automate the process of distribution and updates. Think about it and PM me if you want to discuss further details. Either way, the offer is greatly appreciated.



Best regards,
Andy

Hi Andy,

Is it possible to add an experimental antenna?

http://www.avsforum.com/avs-vb/showthread.php?p=9877270&&#post9877270

In talking with the engineer at the station (WVPT), they say this should approximate the viewing area of W50CM, but I can't seem to recieve it.

W50CM is in the Richmond.kmz file.

It would be very helpful to visualize the pattern of this station.

Thanks for all you are doing!

Hi Andy,

Is it possible to add an experimental antenna?

http://www.avsforum.com/avs-vb/showthread.php?p=9877270&&#post9877270

In talking with the engineer at the station (WVPT), they say this should approximate the viewing area of W50CM, but I can't seem to recieve it.

W50CM is in the Richmond.kmz file.

It would be very helpful to visualize the pattern of this station.

Thanks for all you are doing!
Sure, I can try to help, although I'm not sure what it is that you'll looking for. My understanding is that WVPT is no longer using their STA (expired in April 2006?).

If you're looking for the regular WVPT coverage maps, they should be showing up in the next few weeks. It should be included in the Roanoke, Lynchburg, and Charlottesville MSAs. At the rate the number crunching is going, the first of these should make it through the queue in about about 2 weeks. There's a lot of computation involved, so even with around the clock number crunching, I'm afraid that's as fast I can get them out.

If they are planning a new translator, is there an FCC record somewhere that would contain the antenna details (e.g., location, height, power, frequency, antenna pattern), since that's what I need to simulate a coverage map?

Best regards,
Andy

Sure, I can try to help, although I'm not sure what it is that you'll looking for. My understanding is that WVPT is no longer using their STA (expired in April 2006?).

If you're looking for the regular WVPT coverage maps, they should be showing up in the next few weeks. It should be included in the Roanoke, Lynchburg, and Charlottesville MSAs. At the rate the number crunching is going, the first of these should make it through the queue in about about 2 weeks. There's a lot of computation involved, so even with around the clock number crunching, I'm afraid that's as fast I can get them out.

If they are planning a new translator, is there an FCC record somewhere that would contain the antenna details (e.g., location, height, power, frequency, antenna pattern), since that's what I need to simulate a coverage map?

Best regards,
Andy

I'm somewhat familiar with this situation.

There's no actual record for it, as it's acting as a digital booster from what I can tell (and I don't think the FCC is licensing these outside of experimental authority yet). Apparently they're doing 8 watts from the same location as W50CM, though I don't know if that's 8 watts ERP or 8 watts on the ground. I should hope it's the latter. It's definitely on channel 11.

http://svartifoss2.fcc.gov/cgi-bin/ws.exe/prod/cdbs/pubacc/prod/app_det.pl?Application_id=612948

There's no technical data on it but that's the experimental permit...

- Trip

I'm somewhat familiar with this situation.

There's no actual record for it, as it's acting as a digital booster from what I can tell (and I don't think the FCC is licensing these outside of experimental authority yet). Apparently they're doing 8 watts from the same location as W50CM, though I don't know if that's 8 watts ERP or 8 watts on the ground. I should hope it's the latter.

http://svartifoss2.fcc.gov/cgi-bin/ws.exe/prod/cdbs/pubacc/prod/app_det.pl?Application_id=612948

There's no technical data on it but that's the experimental permit...

- Trip
This record lists a facility ID this is the same as their main transmitter. Is there any way to tell where they're actually transmitting from?


BTW, if W50CM is used as a reference map, it's probably about 25 to 35 dB stronger (I don't know if WVPT is including any antenna gain) than an 8 watt transmitter. This means that you'd have to shrink the coverage area by approximately 2 "color bands", perhaps a little more. So instead of purple, blue, cyan, green, yellow, red, white, the ouside fringe would begin around where cyan is now. Probably only the yellow, red, and white areas on the current map would actually get a decent signal. Looking at it from the larger scale, it looks like the coverage extent would be pulled in to about 60% from where W50CM is today.


Best regards,
Andy

Thanks for the updates!

I will incorporate your fixes into an updated transmitter database in post #1 shortly. It will also go into effect for simulations done after today.

BTW, I don't suppose these are related to the debate over Lookout Mountain. If you ever get word that the issues have been resolved, then please let me know and I can update the database again.





Best regards,
Andy

Yes, the transmitter issues are directly related to the Lookout Mountain battle, fortunately that is over but it will still take over a year to build the new tower and facilities. The low power downtown transmitters will continue until then, and there is some doubt whether 7 and 9 will go full power until Feb 2009 since they are going back to channels 7 and 9. I'll let you know of any changes.

Another 17 metros have finished processing and are now available (see post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) for updates). That brings the total to 81 metros so far! :)


Best regards,
Andy

Awesome Andy! I've started pulling them down right now and plan to start seeding these as they finish today. Due to the fact that I'm switching from Azureus to KTorrent, the only previous markets I'm still seeding are Richmond, Raleigh, and Greensboro, but I'm going to seed all of these that are provided today.

Could I bother you to find out what number Roanoke is on your list of MSAs? I'd just like to know where in the order it is coming, so I know when to expect it. =P I'm quite anxious to see what your maps of my market look like.

Thanks!

- Trip

WHP-DT's map (Harrisburg, PA) does not work for me. I'm getting a large red X.

- Trip

Another 17 metros have finished processing and are now available (see post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) for updates). That brings the total to 81 metros so far! :)
Best regards,
Andy

I've been trying to download Stockton_CA.kmz for the last 24 hours with no luck. This morning I tried several others in the last batch of 17 and none will download. I tried some of the older files and they will download. Any idea what the problem is with the last batch?

Thanks

I've been trying to download Stockton_CA.kmz for the last 24 hours with no luck. This morning I tried several others in the last batch of 17 and none will download. I tried some of the older files and they will download. Any idea what the problem is with the last batch?

Thanks
I just started them at 11am PDT and they seem to be downloading fine, each one having a minimum of 4 seeds with some having 7.

I just started them at 11am PDT and they seem to be downloading fine, each one having a minimum of 4 seeds with some having 7.

Yes, now it's working!

WHP-DT's map (Harrisburg, PA) does not work for me. I'm getting a large red X.

- Trip

I'm also seeing the WHP bug that Trip reported earlier. The large red "X" shows up on my machine following a GE error dialog box:
“Unsupported image format: Harrisburg_PA.kmz/Harrisburg_PA-WHP-DT_D_38.10273x-79.81963x42.58800x-73.91809.png”

Having said that, overall this is an excellent job of coding. The predictions, especially for the Pittsburgh stations are nearly spot on to my actual reception in the Laurel Mountains of western Pennsylvania.

WHP-DT's map (Harrisburg, PA) does not work for me. I'm getting a large red X.

- Trip
I'm also seeing the WHP bug that Trip reported earlier. The large red "X" shows up on my machine following a GE error dialog box:
“Unsupported image format: Harrisburg_PA.kmz/Harrisburg_PA-WHP-DT_D_38.10273x-79.81963x42.58800x-73.91809.png”

Having said that, overall this is an excellent job of coding. The predictions, especially for the Pittsburgh stations are nearly spot on to my actual reception in the Laurel Mountains of western Pennsylvania.
Thanks for catching this! It looks like the png file got corrupted in the compression process. The file has been replaced with a fully working version in post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) as MSA number 66.

If you downloaded this file earlier or if you're helping seed this file, please delete the old torrent+data and download the new one.

Best regards,
Andy

Another 16 metros have been added, bringing the total to 97! Also note that a fixed version of the Harrisburg, PA file has also been posted. You can find all the updates in post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219). :)

Best regards,
Andy

Could I bother you to find out what number Roanoke is on your list of MSAs? I'd just like to know where in the order it is coming, so I know when to expect it. =P I'm quite anxious to see what your maps of my market look like.
Sure! It looks like Roanoke is at number 150. At the rate things are going, I think we'll get there in just over a week. :)


Thanks for all the great feedback. Please let me know if there's anything else that needs to be fixed or can be improved.


Best regards,
Andy

Coverage maps for another 33 metros have been processed and made available in post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219). That brings the total to 130 metros! :)



Best regards,
Andy

Coverage maps for another 33 metros have been processed and made available in post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219). That brings the total to 130 metros! :)



I've said it before, but it bears repeating: this is some very nice work!
I was wondering why you decided to break down the maps by MSA instead of DMA?
(Which brings me to my ultimate question, how soon might we see the Johnstown-Altoona-State College, PA maps? :) )

PA_MainyYak,

You might want to check out earlier in this thread regarding our discussion of the DMA vs MSA issue, as well as andy's explanation concering why he decided to do it that way.

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

Andy + all,

Since I'm posting, thought I should follow up on some of my previous posts in this thread regarding, say my "puzzlement" concerning why a couple of stations(particularly WPTO) seem weaker than the model suggests :

Having seen some info from a study GeekGirl posted some info on in another thread regarding attenuation effects on VHF/UHF of Trees :

I realized that, noting differences in attenuation "seasonally" (leaves on trees vs. leaves off trees - my rough observations here seems to suggest about 3~5db difference leaves on trees vs off, or perhaps a bit more on higher UHF frequencies) isn't quite enough, as I failed to take into account the "wood" part of the tree, or the other 65% or so of the attenuation involved according to conclusions fro that study ....

So, given, particularly in WPTO's direction, given the "edge of a thick woods" begins just about 20Feet from antenna(in other directions the edge of the woods is generally 200FT or farther away, with a tree here or there a bit closer), and that given in that same direction not too far distant there is a fairly large house on top of hill while my antenna is at "bottom" of hill :

I expect all the trees, vegatation+perhaps the house may account for most, if not all of the "difference" betweeen what the model seems to indicate+what I'm experiencing with them, and a couple of other stations, vs in other cases when the model seems quite conservative ....

The model accounts for the following of course, but I'm also thinking perhaps the terrain and relatively low transmitting antenna height of WPTO (analog) vs. most other stations in area(particularly WKOI/DT in nearly same direction) + issues not accounted for in the modelling --- all the trees(and maybe the nearby house on the hill in that direction) ---- all contribute "together" to make things significantly weaker than predicted for WPTO as well ....

The same is probably true as well, but to a lesser extent perhaps regarding similar observations I didn't post in too much detail about, concerning a couple of analog LP's in another direction, one of which has directional antenna pattern that only squirts 8 watts my way from 13 miles from a relatively "low" antenna height ...

This record lists a facility ID this is the same as their main transmitter. Is there any way to tell where they're actually transmitting from?


BTW, if W50CM is used as a reference map, it's probably about 25 to 35 dB stronger (I don't know if WVPT is including any antenna gain) than an 8 watt transmitter. This means that you'd have to shrink the coverage area by approximately 2 "color bands", perhaps a little more. So instead of purple, blue, cyan, green, yellow, red, white, the ouside fringe would begin around where cyan is now. Probably only the yellow, red, and white areas on the current map would actually get a decent signal. Looking at it from the larger scale, it looks like the coverage extent would be pulled in to about 60% from where W50CM is today.


Best regards,
Andy
Thanks! That is the explanation I was looking for. WVPT engineers seem to think they have the same coverage as W50CM with their digital repeater.

I'm in the "green", and W50CM comes in with a little snow (and a CM4228), and I've never been able to lock the digital signal. My tuner pauses at channel 11, but I've never received an image.

PA_MainyYak,

You might want to check out earlier in this thread regarding our discussion of the DMA vs MSA issue, as well as Andy's explanation concerning why he decided to do it that way.

...

:o [removes foot from mouth]
Yup, the topic is covered quite extensively. Now it all makes sense.
Thanks.

Hmm... Andy has not posted an update.

Well, MSAs up to 168 are now up on his website: http://www.tvfool.com

- Trip

Coverage maps for another 39 metros have been processed and seeded (see post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) for updates). That brings the total metro count to 169! :)



BTW, the signal analysis tool was also updated last night. Channel network affiliation is now included as part of the report. Several other formatting changes have also been incorporated. Visit http://www.tvfool.com/ to try out the latest changes.



Best regards,
Andy

There's an explanation of background colors, but I'm not seeing any. Still a kickass tool though! :)

TV Fool comments now in the Official TV Fool forum thread: http://www.avsforum.com/avs-vb/showthread.php?p=10531803#post10531803

Coverage maps for another 48 metros have been processed and added to the list (see post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) for updates). That brings the total to 217 metros! :)



Best regards,
Andy

They look fantastic! The ones I've pulled down anyway, I've had no ability to pull all of them as I don't have the disk space. =P

I'm just posting because I wanted to make a request. Would it be possible, once you've finished cycling through the various MSAs, to do maps that are divided by state and by analog/digital? As an insane person, I feel a need to have every station available to me, but I want to do this without duplication, primarily due to disk space concerns. (I can't be the only one. If I am, I'm more insane than I thought.) I think that dividing the maps up by having each state separate with separate analog and digital maps for each state would be a good way to accomplish this.

Let me know, and thanks in advance.

- Trip

Hey Andy, I live in Lebanon, NH and I just downloaded the Burlington, VT map. It looks great but I also have the Boston, MA, Portland, ME, and Albany, NY, and between these four there is one tiny area of stations that were left out. Basically WNNE and WVTA are the only major stations in this area around Claremont, NH-Windsor, VT but there are also a few translators. This area is included in the Burlington DMA and it would be awesome if you could add these to the database.

Also, W27CP from White River Junction, VT is missing. I've been waiting so long for this, good work! :)

They look fantastic! The ones I've pulled down anyway, I've had no ability to pull all of them as I don't have the disk space. =P

I'm just posting because I wanted to make a request. Would it be possible, once you've finished cycling through the various MSAs, to do maps that are divided by state and by analog/digital? As an insane person, I feel a need to have every station available to me, but I want to do this without duplication, primarily due to disk space concerns. (I can't be the only one. If I am, I'm more insane than I thought.) I think that dividing the maps up by having each state separate with separate analog and digital maps for each state would be a good way to accomplish this.

Let me know, and thanks in advance.

- Trip
After the first pass is done, I've been thinking about ways to cover the remaining transmitters and alternate ways of dividing the data. I was thinking more along the lines of latitude longitude cells. Each of these rectangular areas would be non-overlapping and it should be fairly easy for everyone to tell which grids they need. That avoids the problem of having huge size discrepancies as in Rhode Island compared to Texas. I'm still contemplating all the possible ways to package the maps in a way that is the easiest to use for everyone.

BTW, it's probably a good time to get a bigger hard drive. I just bought a new computer for my parents (replacing a 5 year old dinosaur) and the smallest drives available on new systems were like 80 gigs. I got them 160 gigs because it was only like $20 more. I was amazed (and pretty happy) to see that the prices have come down quite a bit. 250 gig drives are going for about $60 these days, so the disk space cost to hold the entire US coverage map collection (roughly 12 gigs) is only about $3. :)

Best regards,
Andy

Hey Andy, I live in Lebanon, NH and I just downloaded the Burlington, VT map. It looks great but I also have the Boston, MA, Portland, ME, and Albany, NY, and between these four there is one tiny area of stations that were left out. Basically WNNE and WVTA are the only major stations in this area around Claremont, NH-Windsor, VT but there are also a few translators. This area is included in the Burlington DMA and it would be awesome if you could add these to the database.

Also, W27CP from White River Junction, VT is missing. I've been waiting so long for this, good work! :)
FYI, the Glenn Falls MSA is due out this week and it will include the stations you mentioned. This file should cover the last of the transmitters in your area. It will actually cover your area better than the Albany file, so you won't need to load that file once the Glenn Falls file becomes available.

W27CP just barely missed the cutoff for the Burlington file. It will be included in the Glenn Falls file.

The CPUs are definitely busy around the clock crunching maps, so please be patient for one more week. :)

Best regards,
Andy

After the first pass is done, I've been thinking about ways to cover the remaining transmitters and alternate ways of dividing the data. I was thinking more along the lines of latitude longitude cells. Each of these rectangular areas would be non-overlapping and it should be fairly easy for everyone to tell which grids they need. That avoids the problem of having huge size discrepancies as in Rhode Island compared to Texas. I'm still contemplating all the possible ways to package the maps in a way that is the easiest to use for everyone.

Sounds good!

BTW, it's probably a good time to get a bigger hard drive. I just bought a new computer for my parents (replacing a 5 year old dinosaur) and the smallest drives available on new systems were like 80 gigs. I got them 160 gigs because it was only like $20 more. I was amazed (and pretty happy) to see that the prices have come down quite a bit. 250 gig drives are going for about $60 these days, so the disk space cost to hold the entire US coverage map collection (roughly 12 gigs) is only about $3. :)

Best regards,
Andy

I'm getting a new laptop for college in the next two months, and I fully plan to have at least 250GB total storage (either one hard drive or a combination of two). Until then, I'm limping along with the laptop I have with its 80GB drive (60GB /home partition). I have a 160GB external drive as well, and a good number of the files I've pulled down are on that now since I've completely run out of disk space about 20 times.

And I've got another thought too. Puerto Rico, Guam, Virgin Islands, is there terrain data for those places? It might be an idea to come up with maps for those as well at some point.

- Trip

FYI, the Glenn Falls MSA is due out this week and it will include the stations you mentioned. This file should cover the last of the transmitters in your area. It will actually cover your area better than the Albany file, so you won't need to load that file once the Glenn Falls file becomes available.

W27CP just barely missed the cutoff for the Burlington file. It will be included in the Glenn Falls file.

The CPUs are definitely busy around the clock crunching maps, so please be patient for one more week. :)

Best regards,
Andy

Thanks Andy! :)

44 additional MSAs have been added to the list at www.tvfool.com

I won't have time to update the posts here until I get back from the long weekend, so if you want to d/l the MSAs before then, go to the tvfool website. Sorry for the inconvenience.

Best regards,
Andy

tvfool.com appears to be down... :(

This is awesome. Thanks man.

afiggatt on the Philly OTA thread just posted a link to an FCC engineering report for WPVI's (ABC) DTV channel allocation. The appendices (Exhibits) show examples of actual FCC contour plots. FCC URL: http://gullfoss2.fcc.gov/prod/ecfs/retrieve.cgi?native_or_pdf=pdf&id_document=6518723091. Note: If the link doesn't work in Firefox, try IE. Actual URL: http://gullfoss2.fcc.gov/prod/ecfs/retrieve.cgi?native_or_pdf=pdf&id_document=6518723091

I've attached 2 plots showing the comparison of how the FCC views coverage area vs. Google Earth (the towns don't show up at this scale, go by geography). Note that the FCC coverage area extends to the purple area on Google Earth. The purple area is where reception is extremely difficult so don't expect to receive it without a really big antenna.

Andy has been explaining since start of the thread that the FCC's Longley-Rice propagation model parameters are not realistic and that his model uses different parameters to adjust for that. You can see this impact in the plots.

Also note in the FCC report that they use HAAT (Height Above Average Terrain) for antenna height, while Andy's model uses height Above Ground Level (AGL) and AMSL (Above Mean Sea Level). The antenna hasn't moved, it's just how many different ways you can measure the same thing.

Note- The FCC plot is rotated because the AVS forum upload bounced the aspect ratio (1024x768 is good, 768x1024 is not!).

Update: Nitewatchman has posted a reference of the FCC modeling process on the TV Fool forum thread: http://www.avsforum.com/avs-vb/showthread.php?p=10648925&&#post10648925. The extension of the FCC contour into the purple area may not be that significant on these plots, but I still think it's an interesting apples vs. apples comparison.

The Transmitter Icons file has been updated to reflect the latest submitted data corrections and an updated snapshot of the FCC database (see post #1 (http://www.avsforum.com/avs-vb/showthread.php?p=10061605&&#post10061605) for details). Unfortunately, the file size is now slighly larger than the allowed attachment limit on AVS Forum of 500KB. The latest file can always be downloaded directly from the tvfool (http://www.tvfool.com/index.php?option=com_content&task=view&id=16) website.



Coverage maps for another 44 metros have been processed and seeded (see post #2 (http://www.avsforum.com/avs-vb/showthread.php?p=10127219&&#post10127219) for details). That brings the total metro count to 261! :)



Best regards,
Andy

The Transmitter Icons file has been updated to reflect the latest submitted data corrections and an updated snapshot of the FCC database (see post #1 (http://www.avsforum.com/avs-vb/showthread.php?p=10061605&&#post10061605) for details). Unfortunately, the file size is now slighly larger than the allowed attachment limit on AVS Forum of 500KB. The latest file can always be downloaded directly from the tvfool (http://www.tvfool.com/index.php?option=com_content&task=view&id=16) website.



Coverage maps for another 44 metros have been processed and seeded That brings the total metro count to 261! :)



Best regards,
Andy

Thanks Andy! This is a invaluable tool. I can see broadcasters using this also, though I don't think the FCC will accept such items submitted to them with Google Earth in the corner. ;)

I also work in broadcasting, but I work for a station located in Roswell, NM in South Eastern NM. We run as a satellite of KRQE in Albuquerque, but produce locally originated news for the SE. I can't find KBIM, it's licensed to Roswell and serves three major cities in the area from the middle of nowhere. Along with several translators in the mountains and along the high plains near West Texas border. I tried to see if I might be able to see our main transmitter and translators using nearby markets, like Amarillo, Lubbock, Midland-Odessa, and El Paso. But I guess the distance is too great, I only get a few translators in NM along the eastern edge, none of them mine..

What MSA version are you using? I can't seem to line it up to your list, I found some, but they were at least 10 market sizes off from your list. Near as I can tell, Roswell is in the mid 500's, just above the 50k limit of Metro, not macro. Out in the west it gets difficult because the areas are so vast between major metro's. Are you going to group Roswell with other cities like Hobbs, NM, Carlsbad NM, Clovis NM etc..? Otherwise it's going to be a long time before I see SE NM on this list. How far down the metro list are you going to go? 300, 400, 500?? Or reach the 50k limit of the MSA?

Thanks for doing this, it's simply amazing what people are coming up with Google Earth, and I think this is among the best uses ever for it! I can't thank you enough!

Marcus
Roswell, NM

Another 15 metros have been added to the list. That brings the total to 276 metros!

Additionally, the top 30 metros have been reprocessed and updated. This includes some fixes for transmitters, network affiliation in the info balloon, other features and enhancements that have been added in the past several weeks, and general updates that have been recorded in the FCC database.

Best regards,
Andy

My first time using a torrent client, but I cannot seem to get anything going on the Topeka file. Can someone else try it to even see if it is available? I know this will not be a popular file, but it will be interesting to take a look at.


thanks

Well, my suspicions were correct. Torrents are blocked here. Any other way to get the info?

Well, my suspicions were correct. Torrents are blocked here. Any other way to get the info?
If you haven't got a router or have one with the proper ports opened, it's likely the default b*i*t*t*o*r*r*e*n*t ports are blocked by your ISP. Try setting the client to use a random port.

(why is the board blocking that word??)

I just noticed that your site has a list of what stations appear on each map (the "Call Letters" section). This made it very easy for me to realize that the maps are missing a number of stations. Either that or there are errors in the call letter lists.

First of all, since there's neither Beckley nor Bluefield WV, there is no map of WOAY-4/50 ABC in Oak Hill/Beckley, WV. I think the rest of the stations in that DMA are represented in the Roanoke, VA map but that one is not.

Further, I find that WYMT-57/12 in Hazard, KY has no map, despite the fact that Hazard's PBS station, WKHA, is in the Johnson City, TN map.

Next, I don't think Tupelo or Columbus, MS have maps, as evidenced by every station in that market missing (WCBI, WTVA, WKDH, WLOV, WMAB). The only station that does appear is WMAE, which is in three different maps based in other states.

I also could not find a map for KLFY-10/56 despite it being licensed to Lafayette, LA which does have a map.

I could not find a map for Tyler's CBS affiliate, KYTX-19/18.

I'm rather amazed that the whole northern half of Michigan seems to have no maps. Traverse City/Cadillac, Sault Ste. Marie/Cheboygan, and Marquette/Calumet all appear to not have maps of any of their stations.

Hastings/Grand Island, NE has no maps based on KHAS/KHGI/KTVG and others all missing.

I just chose a few stations from the eastern half or so of the US at random to get these. There are probably more stations missing.

I guess I'm just wondering if you're going to be doing those maps by coordinates in order to get them all.

- Trip

I just noticed that your site has a list of what stations appear on each map (the "Call Letters" section). This made it very easy for me to realize that the maps are missing a number of stations. Either that or there are errors in the call letter lists.

First of all, since there's neither Beckley nor Bluefield WV, there is no map of WOAY-4/50 ABC in Oak Hill/Beckley, WV. I think the rest of the stations in that DMA are represented in the Roanoke, VA map but that one is not.

Further, I find that WYMT-57/12 in Hazard, KY has no map, despite the fact that Hazard's PBS station, WKHA, is in the Johnson City, TN map.

Next, I don't think Tupelo or Columbus, MS have maps, as evidenced by every station in that market missing (WCBI, WTVA, WKDH, WLOV, WMAB). The only station that does appear is WMAE, which is in three different maps based in other states.

I also could not find a map for KLFY-10/56 despite it being licensed to Lafayette, LA which does have a map.

I could not find a map for Tyler's CBS affiliate, KYTX-19/18.

I'm rather amazed that the whole northern half of Michigan seems to have no maps. Traverse City/Cadillac, Sault Ste. Marie/Cheboygan, and Marquette/Calumet all appear to not have maps of any of their stations.

Hastings/Grand Island, NE has no maps based on KHAS/KHGI/KTVG and others all missing.

I just chose a few stations from the eastern half or so of the US at random to get these. There are probably more stations missing.

I guess I'm just wondering if you're going to be doing those maps by coordinates in order to get them all.

- Trip
You're right that the current packaging arrangement leaves some channels out of the picture.

Yes, I do plan on having another set of coverage maps based on coordinate grids. I first want to bring all the existing sets up to the same set of standards (transmitter fixes, inclusion of network affiliation, etc.). Once that is done, I will begin the processing for the grid format. The processing machines are definitely still running around the clock and I suspect I'll start the grid processing in about 15 days.

The grid arranged files will end up being much larger and many people will probably need to download multiple files, however, this will have the advantage of including every possible transmitter and will not have any overlap. My guess is that for most people (living in or near the MSA centers) the metro based files will be more convenient and smaller. For anyone further out or in more sparsely populated areas, the grid files will be the better option.

Best regards,
Andy

Andy,

If you use Nielsen's DMA's you won't lose transmitters and you will only have 210 files.

Andy,

If you use Nielsen's DMA's you won't lose transmitters and you will only have 210 files.
Yes, I realize this. This has been mentioned before and I do like the idea. However, I still have a few issues with using DMAs:

1) The data is proprietary and I don't plan on purchasing any geo-referenced DMA boundary data. Everything else I'm using (terrain, transmitter specs, antenna patterns, modeling algorithms, map datum conversions, network affiliation, etc.) is public domain information.

2) DMA boundaries are intended to surround/identify the audience, not the transmitters. As such, many transmitters are actually right along the DMA boundaries. Many transmitters are designed to serve more than one DMA and thus their coverage maps really ought to be included in multiple files rather than arbitrarily limited to just one. I don't think it's quite fair to say that DMAs are non-overlapping, because I think that several transmitters (at least their coverage maps) rightfully belong in multiple DMAs. Even Nielsen struggles with this issue every year.

3) DMA boundaries are mostly along county lines (with a few exceptions). This makes their outlines rather complex polygons/curves. From a programming point of view, these arbitrary shapes are harder to deal with. If not done right, this could lead to gaps between polygons/curves, overlapping regions, or other anomalies. Figuring out which DMA every transmitter "belongs to" is a non-trivial task.

4) DMAs are generally large (much larger than MSAs) and some of them are really huge. This increases the amount of extra information that gets included in each file and increases the amount of "clutter" in each file beyond what it already is today.



Bottom line is that even DMAs (if I could do them) are still not perfect.

In an ideal world, I'd like to make custom map sets per person. In theory, using the results from a radar plot analysis, it should be possible to determine all the transmitters within detectable range of a particular address and then package only the coverage maps that matter. If this were possible, then anybody at any location could get all the coverage maps they want and none of the ones they don't. For that matter, the radar plot analysis results might as well be included as part of the kmz file. :) Of course, this is all just speculation since we're a long ways off from anything that fancy.



Sorry to disappoint, but thanks for the suggestion anyway!



Best regards,
Andy

I have some comments/suggestions which I don't want to detract from the overall quality and excellence of the TV Fool website tool. I also compliment you on adding the Canadian channels.

General Comments:
The channel listings apparently are limited to a total of 33 stations. While I recognize that this is more than adequate in terms of getting into some really low Rx(dBm), this limitation leaves off a channel I receive, not full time, but usually at night, and precludes any listings for "tropo" at my location. My zip code is 80126 and the station in question is KGWN-DT, transmit channel 30, from Cheyenne, WY. Is there any way to expand this 33 channel limit by perhaps limiting it to Rx(dBm) values rather than the 33 total?

You also do not list the religious channels network affiliations, e.g. TBN, LeSea, etc. Examples of these stations for my zip code include KRMT, KWHD, and KDEO. They are either shown with no affiliation or are designated as Independent. While I don't watch religious programming, listing these network affiliations would help folks decide whether they want to try to get the channel or could care less about it.

Comments about zip code 80126:
Stations KJBS-LD and KPXH-LP, both digital, are shown as receivable by me via LOS on channel 13. While I don't believe either of these stations are on the air as of this date, I cannot locate a file for KJBS-LD in the FCC database (perhaps I'm not looking in the right place) and it seems strange to me that two stations would be LOS on the same channel. Is this data correct?

KDEV-LP analog, which is in Denver, is shown with no network affiliation. It is affiliated with a small network named RTV (Retro TV) which has been started by its owners with 18 stations around the country including stations in Denver, Buffalo, NE Ohio, etc. KDEV-DT digital 11, which is in Cheyenne, Wy, which I do receive, is shown as affiliated with ABC. KDEV dropped the ABC affiliation about 2 years ago.

Two stations appear in my digital listing on channel 39, K39JN and K49IB with the same data. I believe the FCC database is messed up for this station and that it is, in fact, one station, not two.

Comments about zip code 14779:
This location is where my parents live and is limited to comments regarding analog. WICU is listed as tropo reception. This station is received 24-7 with just a little snow. Other stations received but not listed include WPSU, CBLT, and CHCH. These stations are also received 24-7. CHCH reception is similar to WICU, WPSU and CBLT are a little snowier. Also not listed is CFTO which I would rate as a tropo reception situation. Is there some reason that these stations, coming from all directions except the east, do not appear in the listing? If you use zip code 14202, downtown Buffalo, CHCH is listed as tropo reception. That location is approximately 56 miles closer to the Hamiliton, ONT transmitter than zip code 14779 and I know for fact is receivable with rabbit ears 24-7.

Finally, WKBW's analog Rx(dBm) is shown as -21.4. I believe this is the ERP of their auxiliary transmitter. Their full time transmitter is 97.7 kW so it appears your program picked up the incorrect data from the FCC database.

Any comments, fixes, etc. are appreciated.

57 metro packages have been reprocessed and posted. Updates include fixes for some transmitter records, the inclusion of network affiliation in the information balloons, other feature enhancements that have been added in recent weeks, and any updates that have been entered into the FCC database.

Best regards,
Andy

The channel listings apparently are limited to a total of 33 stations. While I recognize that this is more than adequate in terms of getting into some really low Rx(dBm), this limitation leaves off a channel I receive, not full time, but usually at night, and precludes any listings for "tropo" at my location. My zip code is 80126 and the station in question is KGWN-DT, transmit channel 30, from Cheyenne, WY. Is there any way to expand this 33 channel limit by perhaps limiting it to Rx(dBm) values rather than the 33 total?
Thanks for all the great comments!



The current limit is based on the assumption that most vBulletin based forums place image size limits on any message attachments. The current format targets a size of 800x600 which should allow trouble-free posting to most forums. I might consider increasing the limit to something like 800x800, since many forums actually seem to allow this. I'll need to do some comparison testing on a few popular forums to see what formats are allowed.



You also do not list the religious channels network affiliations, e.g. TBN, LeSea, etc. Examples of these stations for my zip code include KRMT, KWHD, and KDEO. They are either shown with no affiliation or are designated as Independent. While I don't watch religious programming, listing these network affiliations would help folks decide whether they want to try to get the channel or could care less about it.
I agree. It would be great to have more detailed network affiliation information on every channel. Unfortunately, the database that I'm using does not contain that information. All the databases I use (transmitters, antenna patterns, terrain, coordinate conversions, network affiliations, etc.) are available from free sources and are in a format (or can be converted to a format) that is easy for my software to parse. If you are aware of any free nation-wide databases that map call letters to network affiliations and is more complete than what I have, then please let me know and I'll try to incorporate it.



Stations KJBS-LD and KPXH-LP, both digital, are shown as receivable by me via LOS on channel 13. While I don't believe either of these stations are on the air as of this date, I cannot locate a file for KJBS-LD in the FCC database (perhaps I'm not looking in the right place) and it seems strange to me that two stations would be LOS on the same channel. Is this data correct?
I'm not seeing this in the current data, so it's possible that the FCC has fixed or removed something. The FCC database is in a constant state of change, so sometimes errors show up and later go away. I take new snapshots of the FCC database fairly frequently, so errors that are present one week might be gone the next. It really depends on what the FCC was changing at the moment the snapshot was taken.

If there is a persistent error that doesn't seem to go away, then I will usually intervene by putting my own "override" entry in my local database of FCC fixups. If you notice any consistently wrong entries, please let me know and I'll add the appropriate corrections.



KDEV-LP analog, which is in Denver, is shown with no network affiliation. It is affiliated with a small network named RTV (Retro TV) which has been started by its owners with 18 stations around the country including stations in Denver, Buffalo, NE Ohio, etc. KDEV-DT digital 11, which is in Cheyenne, Wy, which I do receive, is shown as affiliated with ABC. KDEV dropped the ABC affiliation about 2 years ago.
Thanks for the info! This seems to be another shortcoming of the network affiliation database that I'm using. I'll make a note for KDEV and change the network affiliation on the next round of updates.



Two stations appear in my digital listing on channel 39, K39JN and K49IB with the same data. I believe the FCC database is messed up for this station and that it is, in fact, one station, not two.
This probably happens from time to time. Since many stations are changing channel assignments, I think the FCC is having a hard time keeping up with call letter changes and database updates. FYI, there seems to be over 14,000 active TV transmitters in the FCC database, so that could easily mean they need to deal with a few hundred updates every month. These kinds of errors might eventually fix themselves (when the FCC gets around to it) or I can use my software to patch the records if the correct data is known.



Comments about zip code 14779:
This location is where my parents live and is limited to comments regarding analog. WICU is listed as tropo reception. This station is received 24-7 with just a little snow. Other stations received but not listed include WPSU, CBLT, and CHCH. These stations are also received 24-7. CHCH reception is similar to WICU, WPSU and CBLT are a little snowier. Also not listed is CFTO which I would rate as a tropo reception situation. Is there some reason that these stations, coming from all directions except the east, do not appear in the listing? If you use zip code 14202, downtown Buffalo, CHCH is listed as tropo reception. That location is approximately 56 miles closer to the Hamiliton, ONT transmitter than zip code 14779 and I know for fact is receivable with rabbit ears 24-7.
Two comments:

1) When a channel is listed as "Tropo" is means that atmospheric reflection is predicted to be the dominant signal path. As long as the Rx_dBm is still high enough, the channel might still be pefectly watchable. Under the right conditions (e.g., being next to a hill), it might be possible to have poor diffracted signal power (not enough diffraction over the hill), yet relatively strong tropospheric signal (because it's approaching from a much higher angle).

2) Address lookups are not always accurate, especially if you entered limited information like zip-code only. Even exact address lookups can be off because the street number references can be offset by quite a bit in some neighborhoods. In wide-open flat areas, this probably makes very little difference, but in hilly areas, even small errors in location can make a big difference in reception. An error of just 100 meters might make the difference between being blocked by mountain or having a LOS view to a transmitter. To make sure you're getting the best possible analysis, I'd recommend entering exact coordinates (e.g., from a GPS) rather than using the address lookup. The more hilly the area, the more important this becomes.



WKBW's analog Rx(dBm) is shown as -21.4. I believe this is the ERP of their auxiliary transmitter. Their full time transmitter is 97.7 kW so it appears your program picked up the incorrect data from the FCC database.
Thanks for catching this! I'll make the correction in the next round up updates.



Thanks again for all the constructive comments. If you notice anything else, please let me know! :)



Best regards,
Andy

If you are aware of any free nation-wide databases that map call letters to network affiliations and is more complete than what I have, then please let me know and I'll try to incorporate it.


Don't mean to "butt in" on this ... But, in case of it's of any use .... The info available at following URL is the only one I'm aware of -- I'm not completely sure about the "free" aspect of it involving use of the data in that capacity, but you should be able to easily ask the author, if necessary. (who posts(or did) on AVSforum, BTW) ...

http://www.w9wi.com/

Why is taking so long for my new bit torrent to download Albuquerque TV market? :(

It's just doing nothing not a peep on downloading.

I just wish there is a way to get the files directly.......

Any ideas to fix this problems?

Thanks!!

6-17-07

Why is taking so long for my new bit torrent to download Albuquerque TV market? :(

It's just doing nothing not a peep on downloading.
Make sure you've got the right ports open if you've got a router or a "personal firewall". The default ports are 6881-6889 I think. If that doesn't fix it your ISP might be blocking the ports for you, the only thing you can do is change the port your client uses.

Various CLUTTER LOSS corrections to the Longley-Rice Irregular Terrain Model
were stipulated in FCC-00-185, R&O to Establish Improved ILLR Model, May2000:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-00-185A1.pdf

This was in response to various studies that indicated that the ILLR model was somewhat
underestimating the path loss (esp in urban areas)---at least partially due to the underlying
propagation statistics database being developed many years ago before "urban sprawl"....

Many commercial propagation prediction models include location specific clutter loss corrections.

Does TVFool include any Clutter Loss corrections to the ILLR model?

So much for bit torrent it's just doing nothing for me, so I am giving up bittrorrent for the time being so I will have to wait for a new website that is non bitTorrrent. :p

I will keep eye on the TVfools's website for any new updates.

Have fun TV Dxings!!! :D

6-24-07

In TVFool results, RX_dBm is clearly too low, indicating that it's not “calibrated” correctly.
This was discussed earlier, where andy.s.lee indicated that it did not include
antenna gain....but was in the ball park of what he saw on a Spectrum Analyer.

A ViewBandWidth setting of 100 kHz would only see a portion of the 5380 kHz
wide ATSC waveform as it scans across the spectrum, resulting in a dBm level
that was too LOW by 10*log(5380/100) = 17.3 dB.

Typical HDTV sensitivity is in range of –78 to –84 dBm and best Preamp sensitivity
is about –89 dBm. Hence, the minimum RX_dBm levels are about 20 dB too low….
give or take an (unspecified) Receive Antenna Gain assumption….

=================================
TVFool does not accept Receive Antenna Gain, Preamp Specs, Cable Loss, et. al.
(suggestion for future development).
Hence I modified my Radio-Mobile spreadsheet calculator to determine Fade Margin,
Adjacent Channel interference and check for Preamp and HDTV/STB Overload….
and to conduct “what if” exercises….

The received signal level (in dBm units) at the output of the Receive Antenna is:
TX_KW (ERP in dBm units) – Total Path Loss (dB) + RX Antenna Gain (dBi)

Hence, TVFool can be used to determine Total Path Loss (in dB units) as follows:
TX_KW (ERP in dBm units) – RX_dBm – Lsa
Where Lsa is a “fudge factor” chosen to MATCH Radio-Mobile’s Path Loss.

================================
For Line-Of-Sight paths, Lsa = 19.5 dB (+/- 3 dB).
With additional confirmation via “Free Space” calculator.
This is equivalent to a ViewBandWidth of 60 kHz....

For most Diffraction paths, Lsa = 27 dB (+/- 3 dB).
It is thus far unknown why an additional 6.5 dB correction is needed…..

However, for a few “Extreme” paths, Lsa = 34 to 40 dB.
It is thus far unknown why an even higher correction is needed....
or what makes these particular paths "different".....
I didn't see any particular correlation with range or 1path vs 2path cases....

================================
Calculations were performed to determine an initial Lcorr “raw fudge factor” for
a large number of stations in Los Angeles area for numerous user locations.
This was then used to determine how well the chosen (averaged) Lsa
correction factors fit the data. [Self fulfilling prophecy....]

The below gif file shows Lcorr versus Range and the chosen Lsa "correction" averages
when trying to match TVFool Path Loss calculations to those from Radio-Mobile.

================================
The above Lsa = 19.5 dB correction is a starting point for using TVFool to estimate
signal levels for Line-Of-Sight paths….

But until we pin down why the “fudge factor” isn’t a constant, I would not
rely on TVFool calculations to determine signal levels for Diffraction paths.

The RX_dBm colorized criteria stipulated in TVFool are still useful to determine
how difficult a particular location will be....
However, the signal levels aren't accurately “calibrated” and don’t include the effects
of Antenna Gain, Preamps and Cable Loss.

=================================
In the spreadsheet, I compare Radio-Mobile, TVFool and antennaweb to
actual User Reports. As we all well know, antennaweb hugely under-predicts performance.

I’ve seen enough User Reports (for L.A., San Diego and other areas) to
FINALLY ENDORSE RADIO-MOBILE results, when used with the spreadsheet calculator.
[Which was the original intent in doing this "collection".]

But as usual with computer models that pretend to represent reality....YMMV....
Esp. when it comes to guestimating such unknowns as indoor/attic attenuation, etc.....

I am posting the 60+ page spreadsheet in the LOS ANGELES reception thread,
where we can discuss individual results....

holl_ands- That's one heck of a spreadsheet. I downloaded it from the LA thread: http://www.avsforum.com/avs-vb/showthread.php?p=10976888#post10976888. At this point, it's very confusing how you declare the models "correlated" with your fudge factor offsets, but I need some time to digest. I'll let Andy et al answer about the Longley-Rice model, I don't think it's a simple comparison using F(50,xx) when Andy's model uses F(99,99). You also need to consider terrain modeling resolution.

There are some areas in which you are arbitrarily assigning values, such as clutter and tree loss. Some references that may help you on trees:
Report: http://www.its.bldrdoc.gov/isart/art99/slides99/vog/vog_s.pdf
URL: http://www.its.bldrdoc.gov/isart/art99/slides99/ (last report at bottom)

Thanks for the Tree attenuation info....I haven't paid too much attention to this particular "assumption".

I also have a stack of reports re indoor attenuation....and an incomplete stack re clutter loss...
The hard part is trying to boil this down to some easy to use equation or "rule of thumb"....

And BTW, I have one BIG pine tree 20-feet from the house but have no practical means to accurately
"survey" it's location wrt interior antenna locations and incoming signal azimuth...
So it's hunt and peck among a very limited set of possible positions to try to avoid it...

For L.A. & S.D., I use hi-rez SRTM-1 terrain, else I let R-M find SRTM-3 via built-in on-line download.
Initially, I did some comparisons and found less than a few dB difference for "normal" paths.
In R-M, I also find differences of less than a few dB, depending on range scale changes.
My location is not "normal" due to 60-foot hill in backyard that's not resolved by SRTM-3.
For most "flat-landers" it shouldn't make much difference.

Discrepancy between R-M and TVFool re KVCR-DT to RudyG path may be terrain database related.
The PROFILE shows a single hill causing diffraction, but it only extends 15m above LOS.
R-M calculates 16 dB diffraction loss vice unexpectedly high 30 dB for TVFool.

For KVMD-DT to twelvepbrs path, R-M PROFILE indicates LOS signal clears the single hill by 46 m.
R-M calculated Diffraction Loss was a believable 2 dB, whereas TVFool calculated 35 dB
(after applying Lsa = 19.5 dB (LOS) correction factor to RX_dBm).

I can do some reruns to see if variability of Lsa correction factor is terrain database related.

=========================================
Where did andy.s.less stipulate he used F(99,99)?

OET-72 (et. al.) stipulates F(50,50) for ILLR (Individual mode) in order to determine if a user qualifies
for SHVIA waiver, whereas OET-69 stipulates F(50,90), e.g. 50% of locations, 90% of the time,
to calculate DTV station interference effects, and F(50,50) for analog station interference.

Hence, I used F(50,50) for all calculations, after verifying that F(50,90) and F(50,99) only
required a few more dB.
[Comparisons are in RudyG for LOS path and Bri for extended range, Diffraction path.]

The difference between F(99,99) and F(50,50) should be what I call "Fade Margin".
I can redo some runs with F(99,99), but the MD-PA case I just checked showed 20 dB difference,
which is consistent with what I found when I first investigated this issue.

F(99,99) with zero Fade Margin seems equivalent to F(50,50) with Fade Margin criteria of 20 dB
for "GOOD" performance. It's a difference in philosophy wrt how to use these models....
I'ld like to know if I have "half-a-chance" of receiving a station, while also knowing how much more
Gain (Fade Margin) I need to build into the system to improve long term reliability.

And R-M also has a THIRD parameter called percentage of "situations"....huh????

Where did andy.s.less stipulate he used F(99,99)?In the 3rd page of this thread: http://www.avsforum.com/avs-vb/showthread.php?p=10182808&&#post10182808.

If you want even more info about trees, there's a whole thread on it (which is where I originally posted the reference info): http://www.avsforum.com/avs-vb/showthread.php?p=10450784&&#post10450784. I've got a stand of 80' pine trees between me and the Philly transmitters, so I'm sensitive to the problem.

There's also a TV Fool thread, but it hasn't been active lately: http://www.avsforum.com/avs-vb/showthread.php?t=841787.

Skim through these threads from the beginning and you'll see a number of discussions relating to modeling accuracy. I think you'll find that there are a number of people trying to match reality to a model (any model!). They'll throw every type of test equipment to the problem at hand, from high-end spectrum analyzers to calibrated receivers, variable attenuators, and antennas. Then, a tree gets in the way and messes up everything. Or it rains. Not to mention multipath.

The fun part of Google Earth is that it's the first time that people who aren't RF savvy can actually "see" the RF. That's a big time huge help. If you can figure out your signal strength to within 10 dB at your house, it's an easy step to figure out what you need for an antenna. It's the last 10 dB or so that is open for many, many hours of engineering discussion.

Thanks for pointing out F(99,99)--deja vu, now I remember--it was April's Fool....
Unfortunately, I remembered it (incorrectly) as F(50,99)...
I gotta add another line to the spreadsheet....

Wish I had stumbled across the TVFool comment thread sooner....
Beats me why there are two separate threads.....

holl_ands- Some background info, as Radio-Mobile is new to me (correct me if I'm wrong). I think you are referring to the freeware written by VE2DBE (ham radio operator, Quebec, Canada) http://www.cplus.org/rmw/english1.html. This site is loaded with lots of free RF propagation info, including links to terrain models.

I have never used it, but the reference links are excellent:
"How to": http://www.cplus.org/rmw/howto.html
Free terrain data downloads: http://www.cplus.org/rmw/dataen.html

Various CLUTTER LOSS corrections to the Longley-Rice Irregular Terrain Model
were stipulated in FCC-00-185, R&O to Establish Improved ILLR Model, May2000:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-00-185A1.pdf

This was in response to various studies that indicated that the ILLR model was somewhat
underestimating the path loss (esp in urban areas)---at least partially due to the underlying
propagation statistics database being developed many years ago before "urban sprawl"....

Many commercial propagation prediction models include location specific clutter loss corrections.

Does TVFool include any Clutter Loss corrections to the ILLR model?
No, the model is not including any urban clutter loss. There are several issues with modeling losses in urban/suburban/rural areas:

1) Urban clutter data is not easy to come by. In general, city planning and building blueprints are not readily available in an electronic format. Most clutter data needs to be collected manually by a survey team.

2) The construction material, arrangement, and RF properties are essentially unknown, so even with the best clutter data available, you can't really tell how "reflective" and "transparent" the clutter is at various frequencies. At best, only rough generalizations can be made and the clutter is usually generalized into a half dozen or so approximate types (e.g., residential, light suburban, dense suburban, light urban, etc.).

3) Clutter loss estimators are stochastic models that have empirically derived coefficients that make the model fit experimental data as best they can. Models like Hata, Walfisch/Ikegami, and CCIR/ITU estimate the net signal degradation, which may include the effects of attenuation, multipath, fading, etc. The relative contributions of each type of signal degradation is specific to each situation, but the models can only make generalization about what the "average" total signal loss will be if the environment is very similar to the design specification of the model. To give you an idea of how much variability there can be in how and what you are simulating, these models can disagree with each other by as much as 30 dB after only 1 km. They'll differ by even more over greater distances.

4) There are too many environmental factors that change clutter loss effects. Even if you had an army of field technicians to create a very detailed clutter database and drive every block of an entire metro to calibrate all the parameters, the entire map would change as soon as it rained, snowed, or the seasons changed. The water content of the buildings, street surfaces, trees, and ground are constantly changing, so the error margins on these models will be huge (~20 dB or more) due to a dynamic environment.



My overall opinion is that clutter loss modeling has the potential to bring the predicted signal strengths a little closer to the actual average seen by users, but due to the lack of high quality clutter data, it's mostly impractical to apply today. If "bad" clutter data is applied to the model, you might end up adding more error to the model rather than reducing it.



The normal Longley-Rice ITM is a "naked Earth" model. As long as that is understood by everyone, I think the tool can be very useful as-is.

Modeling is merely a tool to help us understand general trends and "big picture" issues. We are a long ways away from having dB-accurate modeling. The data to support such an attempt doesn't exist. Adding layers of sophistication to the model might help, but it's a tradeoff with diminishing returns. It is usually more practical and more useful to make real measurements to understand things beyond what the models can tell us.



Many forms of high accuracy signal prediction have been attempted over the years. People have tried all kinds of approaches from the purely hypothetical (ray tracing/3D modeling) to purely empirical (drive testing/calibration with interpolation/extrapolation). My previous two companies did a fair amount of work in the latter category. With a lot of effort, it's possible to get very accurate results for a specific location under specific conditions at a specific time. However, it's extremely difficult to make this work for generic cases that can be at any place/condition/time.



Going slightly off-topic... One of the main complaints about the FCC's use of the Longley-Rice model is that the margins they specify for "acceptable" coverage is not high enough, especially in urban environments. The parameters they use indirectly determine the amount of broadcast power allowed for each transmitter and this, in turn, has left a lot of people with fairly poor or unreliable reception. The problem has more to do with multipath rather than clutter loss (a subtle, but important distinction). Sixth generation ATSC tuners will improve on this somewhat. There are also some changes in the ongoing AVSB discussions that might help as well.



This is definitely an interesting area of study, and I suspect that over time we will see some improvements in this area. For now, each individual will need to estimate their own "fudge factors" for their surrounding urban clutter.

Best regards,
Andy

F(99,99) with zero Fade Margin seems equivalent to F(50,50) with Fade Margin criteria of 20 dB
for "GOOD" performance. It's a difference in philosophy wrt how to use these models....
I'ld like to know if I have "half-a-chance" of receiving a station, while also knowing how much more
Gain (Fade Margin) I need to build into the system to improve long term reliability.

And R-M also has a THIRD parameter called percentage of "situations"....huh????
holl_ands, thanks for the great discussion. It's great to see some interesting science on the subject.



Let me start by explaining a few things about the L-R model and then the interpretation of the TV Fool output.



The 99/99 parameters for the L-R model are the confidence and reliability percentages, respectively. These represent the spatial (what they call "situations") and temporal (i.e., Rayleigh & Ricean fading) variations in the actual signal strength. They are both affected by another parameter called the "radio climate".

Nobody has precice ground composition for every inch of terrain, plus the EM characteristics of the Earth change over time naturally (rain, snow, foliage, etc.). Since the propagation loss will vary with location and time (sand, water, ferrous rock, ice, forrest, etc.) the model generalizes this to an "average" composite terrain composition and provides a statistical distribution of how the signal will vary in the real world. This is where the radio climate comes in. The developers of the L-R model went through a lot of effort to come up with the statistics for the following seven radio climates:

- Equatorial
- Continental subtropical
- Maritime tropical
- Desert
- Continental temperate
- Maritime temperate over land
- Maritime temperate over sea

Most of the US falls into the category of continental temperate and that is the model used by TV Fool. However, you can still expect noticeable differences between places like the Gulf of Mexico vs. the rocky mountains in Colorado.

The F(99,99) model means that roughly 99% of the time, your signal is expected to be equal or higher than the specified dBm. Another way to look at it is that the signal level is expected to get down to the specified dBm levels in only 1% of the cases.

This is NOT an estimate of the "time-averaged" signal power like you might see on a spectrum analyzer. It's more like a lower bound for the "near worst case" reception conditions. The average signal power is generally going to be quite a bit higher than the specified value. How much higher depends a lot on how your particular environment differs from the model specified by the radio climate.

This is not quite the same as simply adding a higher fade margin because the computed loss comes out a little differently in the four reception zones (LOS, 1Edge, 2Edge, Tropo). Depending on where you live and the time of year, your environment might be significantly better or worse than the "average" radio climate. It should be quite rare for anyone to actually get down to the F(99,99) predicted power levels because it's a conservative estimate by definition.



The reason the F(99,99) model was chosen over the F(50,50) or F(50,90) was because it seemed to "track" real-world measurements better if you disregard the offset. The correlation coefficient came out better for the F(99,99) model compared to others. I compared data for hundreds of collected data points, but even then, that only represents a small percentage of all possible locations/conditions that can occur nation-wide. Still, I was convinced that F(99,99) was a more useful model than the others. Other people have moved along similar trends (e.g., http://www.dielectric.com/broadcast/longley-rice.asp).



For the typical end-user (consumer who just bought a TV and is not an RF engineer), the absolute levels of the predictions and any offsets they may contain don't really matter.

For the technical types, it's true that the predicted values are lower than what you might expect, but that is by design for the reasons specified above.



BTW, what coordinates and height were you entering into RM for each of the transmitters? The kmz file with the Transmitter Icons should have the same coordinates and height information (either AGL or AMSL) that should match the values used by the radar plot generator. That's probably the best way to make sure we're comparing apples to apples since the conversion from NAD27 to WGS84 is non-trivial and there are several different ways of interpreting height out of the FCC database.



Thanks for all the great data and input! This is fantastic stuff.

Best regards,
Andy

Right now, my primary concern is to somehow "calibrate" what you call "RX_dBm" so that
users can calculate the REAL dBm (and dBmV) levels at Preamp and HDTV input.

For Line-Of-Sight paths, I calculated "RX_dBm" represents the receive
signal level at the output of a -19.5 dBi antenna (yes, that's a minus sign).
[By comparison to Free Space equation and R-M.]

If you don't want to incorporate a (short) list of alternative antennas
(hdtvprimer.com has a link to xls source file), then at least postulate
0 dBd (and/or 0 dBi) and let the user add their own antenna gain curve.

If you determine to keep it as it is, please relabel it "RX_dBx"....x, for unknown....

============================
With a REAL dBm and/or dBmV value, a user can determine which
Preamps are most suitable in their location.
And can see if they need to take action to lower the input level to their HDTV.
And ATTEMPT to calculate a usable Preamp plus Distribution Amplifier system (good luck...)

The effect of different antennas can also be assessed, including effects of
cochannel and adjacent channel EMI.

In my son's system, the Preamp improves overall Noise Figure by a whopping 10 dB.

Any realistic prediction must include (at least) the effects of antenna gain
and overall Noise Figure.

================================
FYI: A more readable version of the above O. Bendov paper can be found here:
http://www.tvantenna.tv/papers/paper1999.asp

Right now, my primary concern is to somehow "calibrate" what you call "RX_dBm" so that
users can calculate the REAL dBm (and dBmV) levels at Preamp and HDTV input.

For Line-Of-Sight paths, I calculated "RX_dBm" represents the receive
signal level at the output of a -19.5 dBi antenna (yes, that's a minus sign).
[By comparison to Free Space equation and R-M.]
That's a great idea! Just a few comments...



1) Using the free-space model as a reference is being overly optimistic. The air (density & humidity) and the ground (permissivity & permittivity) will be responsible for some significant loss even in a line-of-sight situation.

The free-space equation will always underestimate real-world LOS path loss by quite a bit simply because the Earth's surface is very different than the vacuum of space. The deviation between the free-space model and the real-world grows with distance, but as a general rule of thumb, the free-space model is about 10-15 dB too optimistic at UHF frequencies in open environments.

I'd be interested in seeing a comparison between my model and the F(99,99) model from Radio Mobile. As long as all the inputs are the same (tx/rx coordinates, heights, terrain profile, etc.), I'd expect the results to come out substantially the same. I've run the published L-R test vectors through my code and have generated the correct results, but it's always good to have additional independent checks for implementation correctness.

For an additional data point, here's how the free-space model compares to some other well-known models. The Hata Open and Walfisch-Ikegami LOS models essentially represent the most basic, flat, unobstructed LOS environments. I'm not sure if the free-space model is the right one to be using as the baseline for comparing TV Fool, Radio Mobile, and the real world.

http://home.comcast.net/~andy.s.lee/public/model_compare.png



2) "Calibration" usually represents a specific geographic area at a specific time. The composition of the terrain and its electromagnetic properties change depending on what part of the country your are in and depending on the season (changes in ground moisture, foliage, average humidity, etc.).

You would need to have a large and diverse calibration dataset in order to avoid biasing the parameters to a specific place and time. The optimum correction factors for Southern California will probably be different than the ones for Florida, New York, Colorado, etc. And they will vary throughout the year.

What you're really measuring is how each particular environment differs from the original "average" continental temperate radio climate data included with the Longley-Rice algorithm. Each location will be a little different, but hopefully, after collecting a lot of data, you'd end up approximating the same bell-curves that were included with the model!



3) In order to calibrate the model to reality, you need to be using a calibrated measurement system and be very careful about the collection environment. Antenna gain is generally not flat across the operational band, and the same is true for pre-amps. Impedance mismatches, internal reflections, cables, and connectors can contribute a few more dB of variable losses.

The entire RF chain (antenna, connectors, cables, amps, spectrum analyzer/meter/etc.) should be placed in an anechoic chamber in its final assembled form and checked for gain across its operational spectrum using a calibrated reference transmitter. The true gain of the system might be several dB different than any published gain values (or antenna simulations) and will vary across the spectrum. Uncalibrated measurements will mess-up the perceived difference between measured vs. simulated power.

Additionally, the area surrounding the field test points needs to be carefully screened for undesirable effects. Things like the antenna mast, guy wires, foil-backed insulation in the roof, and other objects can distort your antenna pattern and/or cause multipath fading. If you're not careful, the antenna gain and measured power might not represent the ideal system you were hoping to measure.



BTW, are the 19.5, 27, and 34-40 dB offsets you're using relative to free-space path loss or something else? I'm not sure if I'm reading the information correctly.



Thanks for all the great info!



Best regards,
Andy

Andy - Just an observation that the Path Loss chart is for 2,350 MHz. You need to be careful about valid frequency ranges. Hata is between 150 MHz and 1.5 GHz (according to Wikipedia).

Sounds like you also need to agree on common OTA channels. Low, mid, high is always good.

Andy - Just an observation that the Path Loss chart is for 2,350 MHz. You need to be careful about valid frequency ranges. Hata is between 150 MHz and 1.5 GHz (according to Wikipedia).

Sounds like you also need to agree on common OTA channels. Low, mid, high is always good.
I didn't generate that chart, so unfortunately, I didn't have anything more appropriate to show in the UHF band.

The reason Hata is only recommended for those frequencies is because the coefficents they derived were based on data collections in those frequency ranges. Extrapolating that to 2.4 GHz is taking the model beyond the point where you could say it was based on real data, so all bets are off regarding its accuracy.

However, regardless of the frequency, all the models tend to asymtotically approach a similar curve as you reduce the "clutter" and approximate a LOS path. It was enough to show that many empirically derived RF models (L-R, Hata, WI, etc.) predict at least 10 dB more loss than free-space loss alone.

I think it's fair to say that F(99,99) over-estimates path loss (it is a near worst-case model, after all) and that the free-space model under-estimates path loss. Saying that there is a 19.5 dB difference between the two doesn't really address the question of which one is closer to reality or what's the average offset between measured data and each of the respective models.

My own experience over the last few years has been that the F(99,99) model correlates well with reality, but has an offset that is about 10 dB lower than reality (under Rx_dBm). It seemed like a better choice than F(50,90), which did not match reality quite as well and also resulted in dBm values that were about 10 dB too high.

In most cases, there is about a 20 dB difference between F(50,90) and F(99,99), but that doesn't always hold true in the 1Edge, 2Edge, and Tropo receivability zones. F(50,90) tends to be too generous in these cases while F(99,99) tends to keep things closer to reality.

Best regards,
Andy

Good thing I didn't waste more than 16 hours doing this with overlays from antennaweb(dot)org and google earth. I felt like a I was a U.S. reconnaissance imagery engineer, searching for IRBM's with my google earth. Thanks so much for taking away the daunting task of finding these tower locations. Sometimes I forget my own advice to others. Google it! You can be the first person to have this idea!, Right?!

RIGHT!

Thanks again.

These are transmitter placemarks and coverage maps that have been created for viewing in Google Earth. Individual packages per metro will be made available here. The purpose of these files is to help you visualize the TV "environment" within the 3D virtual world of Google Earth and perhaps help you understand some of the factors that affect your ability to receive OTA broadcasts.

The result should be something like this:
http://home.comcast.net/~andy.s.lee/public/WGN_Screen_Shot.jpg
With the full 3D capabilities of Google Earth, you can "fly around" and explore the transmitters and coverage maps interactively.



Requirements:

Google Earth 4.0 or later (free download from here (http://earth.google.com/download-earth.html))
A very good 3D graphics card
Lots of RAM
Fast internet connection
********** client for downloading the files

Note: To avoid burdening the forum servers and for better download speeds, I am distributing these files via **********. If you need help with downloading torrents, try reading this FAQ (http://www.utorrent.com/beginners-guide.php). Some popular free ********** clients includeuTorrent (http://www.utorrent.com/) (Windows)
Azureus (http://azureus.sourceforge.net/) (Java, any platform)
**********/Mainline (http://www.**********.com/) (Python, any platform)




If you are looking for a specific coverage map, you can try search through the master callsign list at tvfool.com (http://www.tvfool.com/index.php?option=com_content&task=view&id=31).

Metropolitan Statistical Areas (MSAs):

1. New York, NY - last updated 4-Jun-2007, 126 transmitters (59.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/New_York_NY.kmz.torrent))
2. Los Angeles, CA - last updated 4-Jun-2007, 169 transmitters (64.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Los_Angeles_CA.kmz.torrent))
3. Chicago, IL - last updated 4-Jun-2007, 88 transmitters (61.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Chicago_IL.kmz.torrent))
4. Washington D.C. - Baltimore, MD - last updated 4-Jun-2007, 91 transmitters (68.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Washington_Baltimore_MD.kmz.torrent))
5. San Francisco, CA - last updated 4-Jun-2007, 104 transmitters (83.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/San_Francisco_CA.kmz.torrent))
6. Philadelphia, PA - last updated 4-Jun-2007, 97 transmitters (55.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Philadelphia_PA.kmz.torrent))
7. Boston, MA - last updated 4-Jun-2007, 84 transmitters (64.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Boston_MA.kmz.torrent))
8. Detroit, MI - last updated 4-Jun-2007, 100 transmitters (83.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Detroit_MI.kmz.torrent))
9. Dallas - Ft. Worth, TX - last updated 4-Jun-2007, 57 transmitters (53.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Dallas_TX.kmz.torrent))
10. Houston, TX - last updated 4-Jun-2007, 63 transmitters (46.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Houston_TX.kmz.torrent))
11. Atlanta, GA - last updated 4-Jun-2007, 63 transmitters (41.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Atlanta_GA.kmz.torrent))
12. Miami - Ft. Lauderdale, FL - last updated 4-Jun-2007, 75 transmitters (28.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Miami_FL.kmz.torrent))
13. Seattle, WA - last updated 4-Jun-2007, 60 transmitters (41.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Seattle_WA.kmz.torrent))
14. Phoenix, AZ - last updated 4-Jun-2007, 59 transmitters (32.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Phoenix_AZ.kmz.torrent))
15. Minneapolis - St. Paul, MN - last updated 4-Jun-2007, 43 transmitters (50.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Minneapolis_MN.kmz.torrent))
16. Cleveland, OH - last updated 4-Jun-2007, 72 transmitters (49.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Cleveland_OH.kmz.torrent))
17. San Diego, CA - last updated 4-Jun-2007, 73 transmitters (22.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/San_Diego_CA.kmz.torrent))
18. St. Louis, MO - last updated 4-Jun-2007, 40 transmitters (37.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/St_Louis_MO.kmz.torrent))
19. Denver, CO - last updated 4-Jun-2007, 150 transmitters (69.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Denver_CO.kmz.torrent))
20. Tampa, FL - last updated 4-Jun-2007, 67 transmitters (30.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Tampa_FL.kmz.torrent))
21. Pittsburgh, PA - last updated 4-Jun-2007, 82 transmitters (52.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Pittsburgh_PA.kmz.torrent))
22. Portland, OR - last updated 4-Jun-2007, 100 transmitters (51.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Portland_OR.kmz.torrent))
23. Cincinnati, OH - last updated 4-Jun-2007, 54 transmitters (47.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Cincinnati_OH.kmz.torrent))
24. Sacramento, CA - last updated 4-Jun-2007, 69 transmitters (43.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Sacramento_CA.kmz.torrent))
25. Kansas City, MO - last updated 4-Jun-2007, 42 transmitters (43.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Kansas_City_MO.kmz.torrent))
26. Milwaukee, WI - last updated 4-Jun-2007, 74 transmitters (57.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Milwaukee_WI.kmz.torrent))
27. Orlando, FL - last updated 4-Jun-2007, 104 transmitters (57.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Orlando_FL.kmz.torrent))
28. Indianapolis, IN - last updated 4-Jun-2007, 52 transmitters (42.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Indianapolis_IN.kmz.torrent))
29. San Antonio, TX - last updated 4-Jun-2007, 83 transmitters (51.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/San_Antonio_TX.kmz.torrent))
30. Norfolk, VA - last updated 4-Jun-2007, 66 transmitters (42.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Norfolk_VA.kmz.torrent))
31. Las Vegas, NV - last updated 16-Jun-2007, 128 transmitters (35.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Las_Vegas_NV.kmz.torrent))
32. Columbus, OH - last updated 16-Jun-2007, 65 transmitters (47.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Columbus_OH.kmz.torrent))
33. Charlotte, NC - last updated 16-Jun-2007, 54 transmitters (45.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Charlotte_NC.kmz.torrent))
34. New Orleans, LA - last updated 16-Jun-2007, 63 transmitters (38.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/New_Orleans_LA.kmz.torrent))
35. Salt Lake City, UT - last updated 16-Jun-2007, 280 transmitters (57.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Salt_Lake_City_UT.kmz.torrent))
36. Greensboro, NC - last updated 16-Jun-2007, 67 transmitters (54.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Greensboro_NC.kmz.torrent))
37. Austin, TX - last updated 16-Jun-2007, 92 transmitters (59.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Austin_TX.kmz.torrent))
38. Nashville, TN - last updated 16-Jun-2007, 62 transmitters (43.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Nashville_TN.kmz.torrent))
39. Providence, RI - last updated 16-Jun-2007, 97 transmitters (72.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Providence_RI.kmz.torrent))
40. Raleigh, NC - last updated 16-Jun-2007, 76 transmitters (65.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Raleigh_NC.kmz.torrent))
41. Hartford, CT - last updated 16-Jun-2007, 90 transmitters (62.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Hartford_CT.kmz.torrent))
42. Buffalo, NY - last updated 16-Jun-2007, 91 transmitters (58.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Buffalo_NY.kmz.torrent))
43. Memphis, TN - last updated 16-Jun-2007, 61 transmitters (44.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Memphis_TN.kmz.torrent))
44. West Palm Beach, FL - last updated 16-Jun-2007, 79 transmitters (31.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/West_Palm_Beach_FL.kmz.torrent))
45. Jacksonville, FL - last updated 16-Jun-2007, 60 transmitters (32.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Jacksonville_FL.kmz.torrent))
46. Rochester, NY - last updated 16-Jun-2007, 103 transmitters (63.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Rochester_NY.kmz.torrent))
47. Grand Rapids, MI - last updated 16-Jun-2007, 70 transmitters (45.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Grand_Rapids_MI.kmz.torrent))
48. Oklahoma City, OK - last updated 16-Jun-2007, 64 transmitters (43.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Oklahoma_City_OK.kmz.torrent))
49. Louisville, KY - last updated 16-Jun-2007, 47 transmitters (37.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Louisville_KY.kmz.torrent))
50. Richmond, VA - last updated 16-Jun-2007, 73 transmitters (55.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Richmond_VA.kmz.torrent))
51. Greenville, SC - last updated 16-Jun-2007, 138 transmitters (62.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Greenville_SC.kmz.torrent))
52. Dayton, OH - last updated 16-Jun-2007, 89 transmitters (69.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Dayton_OH.kmz.torrent))
53. Fresno, CA - last updated 16-Jun-2007, 71 transmitters (36.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fresno_CA.kmz.torrent))
54. Birmingham, AL - last updated 16-Jun-2007, 72 transmitters (47.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Birmingham_AL.kmz.torrent))
55. Honolulu, HI - last updated 16-Jun-2007, 33 transmitters ( 7.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Honolulu_HI.kmz.torrent))
56. Albany, NY - last updated 16-Jun-2007, 85 transmitters (46.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Albany_NY.kmz.torrent))
57. Tucson, AZ - last updated 16-Jun-2007, 37 transmitters (24.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Tucson_AZ.kmz.torrent))
58. Tulsa, OK - last updated 16-Jun-2007, 54 transmitters (37.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Tulsa_OK.kmz.torrent))
59. Syracuse, NY - last updated 16-Jun-2007, 112 transmitters (73.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Syracuse_NY.kmz.torrent))
60. Omaha, NE - last updated 16-Jun-2007, 71 transmitters (51.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Omaha_NE.kmz.torrent))
61. Albuquerque, NM - last updated 16-Jun-2007, 55 transmitters (46.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Albuquerque_NM.kmz.torrent))
62. Knoxville, TN - last updated 16-Jun-2007, 123 transmitters (47.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Knoxville_TN.kmz.torrent))
63. El Paso, TX - last updated 16-Jun-2007, 37 transmitters (22.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/El_Paso_TX.kmz.torrent))
64. Bakersfield, CA - last updated 16-Jun-2007, 106 transmitters (29.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Bakersfield_CA.kmz.torrent))
65. Allentown, PA - last updated 16-Jun-2007, 153 transmitters (82.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Allentown_PA.kmz.torrent))
66. Harrisburg, PA - last updated 16-Jun-2007, 96 transmitters (52.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Harrisburg_PA.kmz.torrent))
67. Scranton, PA - last updated 16-Jun-2007, 137 transmitters (52.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Scranton_PA.kmz.torrent))
68. Toledo, OH - last updated 16-Jun-2007, 86 transmitters (64.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Toledo_OH.kmz.torrent))
69. Baton Rouge, LA - last updated 16-Jun-2007, 92 transmitters (52.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Baton_Rouge_LA.kmz.torrent))
70. Youngstown, OH - last updated 16-Jun-2007, 107 transmitters (73.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Youngstown_OH.kmz.torrent))
71. Springfield, MA - last updated 16-Jun-2007, 120 transmitters (89.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Springfield_MA.kmz.torrent))
72. Sarasota, FL - last updated 16-Jun-2007, 85 transmitters (40.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Sarasota_FL.kmz.torrent))
73. Little Rock, AR - last updated 16-Jun-2007, 41 transmitters (38.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Little_Rock_AR.kmz.torrent))
74. McAllen, TX - last updated 16-Jun-2007, 38 transmitters (16.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/McAllen_TX.kmz.torrent))
75. Stockton, CA - last updated 16-Jun-2007, 101 transmitters (79.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Stockton_CA.kmz.torrent))
76. Charleston, SC - last updated 16-Jun-2007, 42 transmitters (22.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Charleston_SC.kmz.torrent))
77. Wichita, KS - last updated 16-Jun-2007, 27 transmitters (21.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Wichita_KS.kmz.torrent))
78. Mobile, AL - last updated 16-Jun-2007, 50 transmitters (29.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Mobile_AL.kmz.torrent))
79. Columbia, SC - last updated 16-Jun-2007, 47 transmitters (39.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Columbia_SC.kmz.torrent))
80. Colorado Springs, CO - last updated 16-Jun-2007, 109 transmitters (56.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Colorado_Springs_CO.kmz.torrent))
81. Fort Wayne, IN - last updated 16-Jun-2007, 67 transmitters (46.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fort_Wayne_IN.kmz.torrent))
82. Daytona Beach, FL - last updated 16-Jun-2007, 67 transmitters (36.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Daytona_Beach_FL.kmz.torrent))
83. Lakeland, FL - last updated 16-Jun-2007, 117 transmitters (59.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lakeland_FL.kmz.torrent))
84. Johnson City, TN - last updated 16-Jun-2007, 126 transmitters (47.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Johnson_City_TN.kmz.torrent))
85. Lexington, KY - last updated 16-Jun-2007, 42 transmitters (28.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lexington_KY.kmz.torrent))
86. Augusta, GA - last updated 16-Jun-2007, 46 transmitters (36.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Augusta_GA.kmz.torrent))
87. Melbourne, FL - last updated 16-Jun-2007, 69 transmitters (34.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Melbourne_FL.kmz.torrent))
88. Lancaster, PA - last updated 2-May-2007, 105 transmitters (73.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lancaster_PA.kmz.torrent))
89. Chattanooga, TN - last updated 2-May-2007, 58 transmitters (34.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Chattanooga_TN.kmz.torrent))
90. Des Moines, IA - last updated 2-May-2007, 44 transmitters (35.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Des_Moines_IA.kmz.torrent))
91. Kalamazoo, MI - last updated 2-May-2007, 93 transmitters (68.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Kalamazoo_MI.kmz.torrent))
92. Lansing, MI - last updated 2-May-2007, 114 transmitters (91.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lansing_MI.kmz.torrent))
93. Modesto, CA - last updated 2-May-2007, 88 transmitters (59.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Modesto_CA.kmz.torrent))
94. Fort Myers, FL - last updated 2-May-2007, 41 transmitters (16.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fort_Myers_FL.kmz.torrent))
95. Jackson, MS - last updated 2-May-2007, 46 transmitters (35.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Jackson_MS.kmz.torrent))
96. Boise City, ID - last updated 2-May-2007, 60 transmitters (36.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Boise_City_ID.kmz.torrent))
97. Madison, WI - last updated 2-May-2007, 80 transmitters (62.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Madison_WI.kmz.torrent))
98. Spokane, WA - last updated 7-May-2007, 70 transmitters (45.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Spokane_WA.kmz.torrent))
99. Pensacola, FL - last updated 7-May-2007, 55 transmitters (27.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Pensacola_FL.kmz.torrent))
100. Canton, OH - last updated 7-May-2007, 103 transmitters (70.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Canton_OH.kmz.torrent))
101. Saginaw, MI - last updated 7-May-2007, 64 transmitters (34.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Saginaw_MI.kmz.torrent))
102. Salinas, CA - last updated 7-May-2007, 49 transmitters (27.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Salinas_CA.kmz.torrent))
103. Santa Barbara, CA - last updated 7-May-2007, 71 transmitters (24.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Santa_Barbara_CA.kmz.torrent))
104. Shreveport, LA - last updated 7-May-2007, 62 transmitters (34.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Shreveport_LA.kmz.torrent))
105. Lafayette, LA - last updated 7-May-2007, 83 transmitters (41.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lafayette_LA.kmz.torrent))
106. Beaumont, TX - last updated 7-May-2007, 57 transmitters (25.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Beaumont_TX.kmz.torrent))
107. York, PA - last updated 7-May-2007, 98 transmitters (74.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/York_PA.kmz.torrent))
108. Corpus Christi, TX - last updated 7-May-2007, 65 transmitters (23.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Corpus_Christi_TX.kmz.torrent))
109. Reading, PA - last updated 7-May-2007, 131 transmitters (78.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Reading_PA.kmz.torrent))
110. Rockford, IL - last updated 7-May-2007, 63 transmitters (40.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Rockford_IL.kmz.torrent))
111. Provo, UT - last updated 7-May-2007, 403 transmitters (66.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Provo_UT.kmz.torrent))
112. Visalia, CA - last updated 7-May-2007, 93 transmitters (45.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Visalia_CA.kmz.torrent))
113. Biloxi, MS - last updated 7-May-2007, 64 transmitters (39.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Biloxi_MS.kmz.torrent))
114. Davenport, IA - last updated 7-May-2007, 63 transmitters (48.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Davenport_IA.kmz.torrent))
115. Appleton, WI - last updated 7-May-2007, 39 transmitters (29.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Appleton_WI.kmz.torrent))
116. Peoria, IL - last updated 7-May-2007, 63 transmitters (56.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Peoria_IL.kmz.torrent))
117. Huntsville, AL - last updated 7-May-2007, 52 transmitters (28.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Huntsville_AL.kmz.torrent))
118. Hickory, NC - last updated 7-May-2007, 113 transmitters (65.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Hickory_NC.kmz.torrent))
119. Reno, NV - last updated 7-May-2007, 101 transmitters (29.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Reno_NV.kmz.torrent))
120. Brownsville, TX - last updated 7-May-2007, 35 transmitters (15.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Brownsville_TX.kmz.torrent))
121. Montgomery, AL - last updated 7-May-2007, 73 transmitters (50.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Montgomery_AL.kmz.torrent))
122. Springfield, MO - last updated 7-May-2007, 69 transmitters (42.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Springfield_MO.kmz.torrent))
123. Eugene, OR - last updated 7-May-2007, 134 transmitters (40.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Eugene_OR.kmz.torrent))
124. Macon, GA - last updated 7-May-2007, 43 transmitters (34.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Macon_GA.kmz.torrent))
125. Fort Pierce, FL - last updated 7-May-2007, 46 transmitters (17.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fort_Pierce_FL.kmz.torrent))
126. Huntington, WV - last updated 7-May-2007, 45 transmitters (25.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Huntington_WV.kmz.torrent))
127. Killeen, TX - last updated 7-May-2007, 62 transmitters (43.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Killeen_TX.kmz.torrent))
128. Fayetteville, AR - last updated 7-May-2007, 89 transmitters (44.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fayetteville_AR.kmz.torrent))
129. Fayetteville, NC - last updated 7-May-2007, 84 transmitters (76.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fayetteville_NC.kmz.torrent))
130. Utica, NY - last updated 7-May-2007, 97 transmitters (64.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Utica_NY.kmz.torrent))
131. Evansville, IN - last updated 11-May-2007, 40 transmitters (30.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Evansville_IN.kmz.torrent))
132. New London, CT - last updated 11-May-2007, 102 transmitters (78.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/New_London_CT.kmz.torrent))
133. Savannah, GA - last updated 11-May-2007, 36 transmitters (20.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Savannah_GA.kmz.torrent))
134. Tallahassee, FL - last updated 11-May-2007, 64 transmitters (37.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Tallahassee_FL.kmz.torrent))
135. Erie, PA - last updated 11-May-2007, 52 transmitters (25.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Erie_PA.kmz.torrent))
136. Columbus, GA - last updated 11-May-2007, 46 transmitters (29.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Columbus_GA.kmz.torrent))
137. South Bend, IN - last updated 11-May-2007, 104 transmitters (83.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/South_Bend_IN.kmz.torrent))
138. Anchorage, AK* - last updated 11-May-2007, 84 transmitters (28.6 MB download torrent*)
139. Ocala, FL - last updated 11-May-2007, 86 transmitters (43.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Ocala_FL.kmz.torrent))
140. Binghamton, NY - last updated 11-May-2007, 121 transmitters (62.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Binghamton_NY.kmz.torrent))
141. Charleston, WV - last updated 11-May-2007, 49 transmitters (26.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Charleston_WV.kmz.torrent))
142. Fort Collins, CO - last updated 11-May-2007, 122 transmitters (55.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fort_Collins_CO.kmz.torrent))
143. Naples, FL - last updated 11-May-2007, 32 transmitters (13.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Naples_FL.kmz.torrent))
144. Lincoln, NE - last updated 11-May-2007, 72 transmitters (51.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lincoln_NE.kmz.torrent))
145. San Luis Obispo, CA - last updated 11-May-2007, 51 transmitters (21.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/San_Luis_Obispo_CA.kmz.torrent))
146. Duluth, MN - last updated 11-May-2007, 47 transmitters (36.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Duluth_MN.kmz.torrent))
147. Portland, ME - last updated 11-May-2007, 39 transmitters (26.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Portland_ME.kmz.torrent))
148. Lubbock, TX - last updated 11-May-2007, 78 transmitters (28.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lubbock_TX.kmz.torrent))
149. Odessa, TX - last updated 11-May-2007, 59 transmitters (25.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Odessa_TX.kmz.torrent))
150. Roanoke, VA - last updated 11-May-2007, 66 transmitters (48.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Roanoke_VA.kmz.torrent))
151. Wilmington, NC - last updated 11-May-2007, 47 transmitters (30.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Wilmington_NC.kmz.torrent))
152. Johnstown, PA - last updated 11-May-2007, 94 transmitters (54.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Johnstown_PA.kmz.torrent))
153. Green Bay, WI - last updated 11-May-2007, 30 transmitters (28.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Green_Bay_WI.kmz.torrent))
154. Asheville, NC - last updated 11-May-2007, 155 transmitters (67.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Asheville_NC.kmz.torrent))
155. Yakima, WA - last updated 11-May-2007, 139 transmitters (53.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Yakima_WA.kmz.torrent))
156. Gainesville, FL - last updated 11-May-2007, 71 transmitters (33.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Gainesville_FL.kmz.torrent))
157. Amarillo, TX - last updated 11-May-2007, 92 transmitters (36.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Amarillo_TX.kmz.torrent))
158. Lynchburg, VA - last updated 11-May-2007, 63 transmitters (40.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lynchburg_VA.kmz.torrent))
159. Waco, TX - last updated 11-May-2007, 75 transmitters (70.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Waco_TX.kmz.torrent))
160. Merced, CA - last updated 11-May-2007, 92 transmitters (53.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Merced_CA.kmz.torrent))
161. Longview, TX - last updated 11-May-2007, 44 transmitters (36.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Longview_TX.kmz.torrent))
162. Fort Smith, AR - last updated 11-May-2007, 59 transmitters (33.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fort_Smith_AR.kmz.torrent))
163. Clarksville, TN - last updated 11-May-2007, 67 transmitters (47.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Clarksville_TN.kmz.torrent))
164. Chico, CA - last updated 11-May-2007, 84 transmitters (30.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Chico_CA.kmz.torrent))
165. Springfield, IL - last updated 11-May-2007, 49 transmitters (37.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Springfield_IL.kmz.torrent))
166. Myrtle Beach, SC - last updated 11-May-2007, 65 transmitters (45.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Myrtle_Beach_SC.kmz.torrent))
167. Houma, LA - last updated 11-May-2007, 61 transmitters (36.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Houma_LA.kmz.torrent))
168. Laredo, TX - last updated 11-May-2007, 16 transmitters ( 7.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Laredo_TX.kmz.torrent))
169. Richland, WA - last updated 11-May-2007, 105 transmitters (58.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Richland_WA.kmz.torrent))
170. Cedar Rapids, IA - last updated 19-May-2007, 48 transmitters (48.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Cedar_Rapids_IA.kmz.torrent))
171. Lake Charles, LA - last updated 19-May-2007, 78 transmitters (38.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lake_Charles_LA.kmz.torrent))
172. Lafayette, IN - last updated 19-May-2007, 60 transmitters (47.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lafayette_IN.kmz.torrent))
173. Elkhart, IN - last updated 19-May-2007, 68 transmitters (51.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Elkhart_IN.kmz.torrent))
174. Medford, OR - last updated 19-May-2007, 190 transmitters (45.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Medford_OR.kmz.torrent))
175. Champaign, IL - last updated 19-May-2007, 60 transmitters (44.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Champaign_IL.kmz.torrent))
176. Mansfield, OH - last updated 19-May-2007, 102 transmitters (75.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Mansfield_OH.kmz.torrent))
177. Tyler, TX - last updated 19-May-2007, 35 transmitters (21.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Tyler_TX.kmz.torrent))
178. Las Cruces, NM - last updated 19-May-2007, 87 transmitters (30.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Las_Cruces_NM.kmz.torrent))
179. Fargo, ND - last updated 19-May-2007, 29 transmitters (26.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fargo_ND.kmz.torrent))
180. Sioux Falls, SD - last updated 19-May-2007, 60 transmitters (53.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Sioux_Falls_SD.kmz.torrent))
181. Fort Walton Beach, FL - last updated 19-May-2007, 89 transmitters (42.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Fort_Walton_Beach_FL.kmz.torrent))
182. Topeka, KS - last updated 19-May-2007, 56 transmitters (50.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Topeka_KS.kmz.torrent))
183. Burlington, VT - last updated 19-May-2007, 82 transmitters (68.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Burlington_VT.kmz.torrent))
184. St Cloud, MN - last updated 19-May-2007, 138 transmitters (91.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/St_Cloud_MN.kmz.torrent))
185. Bellingham, WA - last updated 19-May-2007, 44 transmitters (29.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Bellingham_WA.kmz.torrent))
186. Tuscaloosa, AL - last updated 19-May-2007, 68 transmitters (44.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Tuscaloosa_AL.kmz.torrent))
187. Redding, CA - last updated 19-May-2007, 111 transmitters (36.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Redding_CA.kmz.torrent))
188. Barnstable, MA - last updated 19-May-2007, 49 transmitters (39.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Barnstable_MA.kmz.torrent))
189. Benton Harbor, MI - last updated 19-May-2007, 97 transmitters (81.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Benton_Harbor_MI.kmz.torrent))
190. Yuma, AZ - last updated 19-May-2007, 37 transmitters (20.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Yuma_AZ.kmz.torrent))
191. Charlottesville, VA - last updated 19-May-2007, 99 transmitters (48.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Charlottesville_VA.kmz.torrent))
192. Jackson, MI - last updated 19-May-2007, 111 transmitters (93.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Jackson_MI.kmz.torrent))
193. Joplin, MO - last updated 19-May-2007, 81 transmitters (35.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Joplin_MO.kmz.torrent))
194. Lima, OH - last updated 19-May-2007, 82 transmitters (57.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lima_OH.kmz.torrent))
195. Athens, GA - last updated 19-May-2007, 71 transmitters (41.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Athens_GA.kmz.torrent))
196. Wheeling, WV - last updated 19-May-2007, 99 transmitters (56.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Wheeling_WV.kmz.torrent))
197. Bryan, TX - last updated 19-May-2007, 38 transmitters (25.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Bryan_TX.kmz.torrent))
198. Janesville, WI - last updated 19-May-2007, 89 transmitters (63.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Janesville_WI.kmz.torrent))
199. Parkersburg, WV - last updated 19-May-2007, 61 transmitters (35.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Parkersburg_WV.kmz.torrent))
200. Bloomington, IL - last updated 19-May-2007, 56 transmitters (42.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Bloomington_IL.kmz.torrent))
201. Jacksonville, NC - last updated 19-May-2007, 41 transmitters (29.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Jacksonville_NC.kmz.torrent))
202. Terre Haute, IN - last updated 19-May-2007, 78 transmitters (60.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Terre_Haute_IN.kmz.torrent))
203. Eau Claire, WI - last updated 19-May-2007, 40 transmitters (30.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Eau_Claire_WI.kmz.torrent))
204. Panama City, FL - last updated 19-May-2007, 57 transmitters (23.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Panama_City_FL.kmz.torrent))
205. Santa Fe, NM - last updated 19-May-2007, 77 transmitters (49.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Santa_Fe_NM.kmz.torrent))
206. Monroe, LA - last updated 19-May-2007, 57 transmitters (33.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Monroe_LA.kmz.torrent))
207. Decatur, AL - last updated 19-May-2007, 84 transmitters (55.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Decatur_AL.kmz.torrent))
208. Rocky Mount, NC - last updated 19-May-2007, 61 transmitters (55.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Rocky_Mount_NC.kmz.torrent))
209. Florence, AL - last updated 19-May-2007, 70 transmitters (28.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Florence_AL.kmz.torrent))
210. Punta Gorda, FL - last updated 19-May-2007, 81 transmitters (39.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Punta_Gorda_FL.kmz.torrent))
211. Pueblo, CO - last updated 19-May-2007, 86 transmitters (31.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Pueblo_CO.kmz.torrent))
212. Wichita Falls, TX - last updated 19-May-2007, 72 transmitters (29.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Wichita_Falls_TX.kmz.torrent))
213. Jamestown, NY - last updated 19-May-2007, 70 transmitters (40.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Jamestown_NY.kmz.torrent))
214. Yuba City, CA - last updated 19-May-2007, 89 transmitters (50.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Yuba_City_CA.kmz.torrent))
215. Dothan, AL - last updated 19-May-2007, 82 transmitters (38.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Dothan_AL.kmz.torrent))
216. State College, PA - last updated 19-May-2007, 61 transmitters (29.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/State_College_PA.kmz.torrent))
217. Columbia, MO - last updated 19-May-2007, 41 transmitters (23.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Columbia_MO.kmz.torrent))
218. Greenville, NC - last updated 25-May-2007, 60 transmitters (51.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Greenville_NC.kmz.torrent))
219. Steubenville, OH - last updated 25-May-2007, 94 transmitters (56.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Steubenville_OH.kmz.torrent))
220. Texarkana, AR - last updated 25-May-2007, 47 transmitters (31.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Texarkana_AR.kmz.torrent))
221. Billings, MT - last updated 25-May-2007, 69 transmitters (30.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Billings_MT.kmz.torrent))
222. Altoona, PA - last updated 25-May-2007, 69 transmitters (40.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Altoona_PA.kmz.torrent))
223. Waterloo, IA - last updated 25-May-2007, 51 transmitters (48.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Waterloo_IA.kmz.torrent))
224. La Crosse, WI - last updated 25-May-2007, 49 transmitters (34.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/La_Crosse_WI.kmz.torrent))
225. Dover, DE - last updated 25-May-2007, 108 transmitters (65.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Dover_DE.kmz.torrent))
226. Abilene, TX - last updated 25-May-2007, 63 transmitters (28.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Abilene_TX.kmz.torrent))
227. Alexandria, LA - last updated 25-May-2007, 77 transmitters (43.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Alexandria_LA.kmz.torrent))
228. Wausau, WI - last updated 25-May-2007, 44 transmitters (33.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Wausau_WI.kmz.torrent))
229. Florence, SC - last updated 25-May-2007, 62 transmitters (43.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Florence_SC.kmz.torrent))
230. Glens Falls, NY - last updated 25-May-2007, 90 transmitters (47.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Glens_Falls_NY.kmz.torrent))
231. Rochester, MN - last updated 25-May-2007, 62 transmitters (47.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Rochester_MN.kmz.torrent))
232. Sioux City, IA - last updated 25-May-2007, 57 transmitters (50.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Sioux_City_IA.kmz.torrent))
233. Flagstaff, AZ - last updated 25-May-2007, 34 transmitters (19.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Flagstaff_AZ.kmz.torrent))
234. Albany, GA - last updated 25-May-2007, 83 transmitters (51.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Albany_GA.kmz.torrent))
235. Bloomington, IN - last updated 25-May-2007, 79 transmitters (67.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Bloomington_IN.kmz.torrent))
236. Sharon, PA - last updated 25-May-2007, 118 transmitters (78.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Sharon_PA.kmz.torrent))
237. Williamsport, PA - last updated 25-May-2007, 125 transmitters (54.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Williamsport_PA.kmz.torrent))
238. Muncie, IN - last updated 25-May-2007, 88 transmitters (73.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Muncie_IN.kmz.torrent))
239. Grand Junction, CO - last updated 25-May-2007, 199 transmitters (39.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Grand_Junction_CO.kmz.torrent))
240. Auburn, AL - last updated 25-May-2007, 60 transmitters (41.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Auburn_AL.kmz.torrent))
241. Lawton, OK - last updated 25-May-2007, 97 transmitters (38.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lawton_OK.kmz.torrent))
242. Decatur, IL - last updated 25-May-2007, 57 transmitters (41.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Decatur_IL.kmz.torrent))
243. Goldsboro, NC - last updated 25-May-2007, 78 transmitters (65.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Goldsboro_NC.kmz.torrent))
244. Sheboygan, WI - last updated 25-May-2007, 55 transmitters (50.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Sheboygan_WI.kmz.torrent))
245. Anniston, AL - last updated 25-May-2007, 60 transmitters (35.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Anniston_AL.kmz.torrent))
246. Hattiesburg, MS - last updated 25-May-2007, 44 transmitters (18.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Hattiesburg_MS.kmz.torrent))
247. Iowa City, IA - last updated 25-May-2007, 72 transmitters (60.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Iowa_City_IA.kmz.torrent))
248. Sherman, TX - last updated 25-May-2007, 82 transmitters (60.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Sherman_TX.kmz.torrent))
249. Danville, VA - last updated 25-May-2007, 72 transmitters (58.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Danville_VA.kmz.torrent))
250. Jackson, TN - last updated 25-May-2007, 72 transmitters (41.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Jackson_TN.kmz.torrent))
251. Sumter, SC - last updated 25-May-2007, 49 transmitters (37.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Sumter_SC.kmz.torrent))
252. San Angelo, TX - last updated 25-May-2007, 52 transmitters (23.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/San_Angelo_TX.kmz.torrent))
253. Gadsden, AL - last updated 25-May-2007, 82 transmitters (49.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Gadsden_AL.kmz.torrent))
254. St Joseph, MO - last updated 25-May-2007, 40 transmitters (42.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/St_Joseph_MO.kmz.torrent))
255. Cumberland, MD - last updated 25-May-2007, 101 transmitters (45.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Cumberland_MD.kmz.torrent))
256. Kokomo, IN - last updated 25-May-2007, 60 transmitters (49.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Kokomo_IN.kmz.torrent))
257. Lawrence, KS - last updated 25-May-2007, 56 transmitters (49.9 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lawrence_KS.kmz.torrent))
258. Grand Forks, ND - last updated 25-May-2007, 23 transmitters (29.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Grand_Forks_ND.kmz.torrent))
259. Missoula, MT - last updated 25-May-2007, 68 transmitters (17.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Missoula_MT.kmz.torrent))
260. Bismarck, ND - last updated 25-May-2007, 28 transmitters (21.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Bismarck_ND.kmz.torrent))
261. Owensboro, KY - last updated 25-May-2007, 54 transmitters (36.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Owensboro_KY.kmz.torrent))
262. Elmira, NY - last updated 4-Jun-2007, 128 transmitters (51.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Elmira_NY.kmz.torrent))
263. Bangor, ME - last updated 4-Jun-2007, 44 transmitters (28.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Bangor_ME.kmz.torrent))
264. Lewiston, ME - last updated 4-Jun-2007, 39 transmitters (27.4 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Lewiston_ME.kmz.torrent))
265. Dubuque, IA - last updated 4-Jun-2007, 59 transmitters (58.8 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Dubuque_IA.kmz.torrent))
266. Rapid City, SD - last updated 4-Jun-2007, 39 transmitters (30.2 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Rapid_City_SD.kmz.torrent))
267. Pittsfield, MA - last updated 4-Jun-2007, 94 transmitters (65.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Pittsfield_MA.kmz.torrent))
268. Pine Bluff, AR - last updated 4-Jun-2007, 37 transmitters (33.6 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Pine_Bluff_AR.kmz.torrent))
269. Victoria, TX - last updated 4-Jun-2007, 48 transmitters (13.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Victoria_TX.kmz.torrent))
270. Jonesboro, AR - last updated 4-Jun-2007, 61 transmitters (37.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Jonesboro_AR.kmz.torrent))
271. Cheyenne, WY - last updated 4-Jun-2007, 73 transmitters (26.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Cheyenne_WY.kmz.torrent))
272. Great Falls, MT - last updated 4-Jun-2007, 46 transmitters (23.0 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Great_Falls_MT.kmz.torrent))
273. Corvallis, OR - last updated 4-Jun-2007, 126 transmitters (62.5 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Corvallis_OR.kmz.torrent))
274. Pocatello, ID - last updated 4-Jun-2007, 157 transmitters (38.7 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Pocatello_ID.kmz.torrent))
275. Casper, WY - last updated 4-Jun-2007, 24 transmitters (19.1 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Casper_WY.kmz.torrent))
276. Enid, OK - last updated 4-Jun-2007, 67 transmitters (44.3 MB download torrent (http://home.comcast.net/~andy.s.lee/public/Enid_OK.kmz.torrent))


* The Anchorage coverage maps are not valid because the SRTM terrain data does not extend above 60 degrees north latitude



Change log:
16-Jun-2007
· Updated Las Vegas, Columbus, Charlotte, New Orleans, Salt Lake City, Greensboro, Austin, Nashville, Providence, Raleigh, Hartford, Buffalo, Memphis, West Palm Beach, Jacksonville, Rochester, Grand Rapids, Oklahoma City, Louisville, Richmond, Greenville, Dayton, Fresno, Birmingham, Honolulu, Albany, Tucson, Tulsa, Syracuse, Omaha, Albuquerque, Knoxville, El Paso, Bakersfield, Allentown, Harrisburg, Scranton, Toledo, Baton Rouge, Youngstown, Springfield, Sarasota, Little Rock, McAllen, Stockton, Charleston, Wichita, Mobile, Columbia, Colorado Springs, Fort Wayne, Daytona Beach, Lakeland, Johnson City, Lexington, Augusta, and Melbourne MSAs
· Updates include fixes for some transmitter records, the inclusion of network affiliation in the information balloons, other feature enhancements that have been added in recent weeks, and any updates that have been entered into the FCC database

4-Jun-2007
· Added Elmira, Bangor, Lewiston, Dubuque, Rapid City, Pittsfield, Pine Bluff, Victoria, Jonesboro, Cheyenne, Great Falls, Corvallis, Pocatello, Casper, and Enid MSAs
· Updated New York, Los Angeles, Chicago, Washington Baltimore, San Francisco, Philadelphia, Boston, Detroit, Dallas, Houston, Atlanta, Miami, Seattle, Phoenix, Minneapolis, Cleveland, San Diego, St Louis, Denver, Tampa, Pittsburgh, Portland, Cincinnati, Sacramento, Kansas City, Milwaukee, Orlando, Indianapolis, San Antonio, and Norfolk MSAs
· Updates include fixes for some transmitter records, the inclusion of network affiliation in the information balloons, other feature enhancements that have been added in recent weeks, and any updates that have been entered into the FCC database

25-May-2007
· Added Greenville, Steubenville, Texarkana, Billings, Altoona, Waterloo, La Crosse, Dover, Abilene, Alexandria, Wausau, Florence, Glens Falls, Rochester, Sioux City, Flagstaff, Albany, Bloomington, Sharon, Williamsport, Muncie, Grand Junction, Auburn, Lawton, Decatur, Goldsboro, Sheboygan, Anniston, Hattiesburg MS, Iowa City, Sherman, Danville, Jackson, Sumter, San Angelo, Gadsden, St Joseph, Cumberland, Kokomo, Lawrence, Grand Forks, Missoula, Bismarck, and Owensboro MSAs

19-May-2007
· Added Cedar Rapids, Lake Charles, Lafayette, Elkhart, Medford, Champaign, Mansfield, Tyler, Las Cruces, Fargo, Sioux Falls, Fort Walton Beach, Topeka, Burlington, St. Cloud, Bellingham, Tuscaloosa, Redding, Barnstable, Benton Harbor, Yuma, Charlottesville, Jackson, Joplin, Lima, Athens, Wheeling, Bryan, Janesville, Parkersburg, Bloomington, Jacksonville, Terre Haute, Eau Claire, Panama City, Santa Fe, Monroe, Decatur, Rocky Mount, Florence, Punta Gorda, Pueblo, Wichita Falls, Jamestown, Yuba City, Dothan, State College, and Columbia MSAs

11-May-2007
· Added Evansville, New London, Savannah, Tallahassee, Erie, Columbus, South Bend, Anchorage, Ocala, Binghamton, Charleston, Fort Collins, Naples, Lincoln, San Luis Obispo, Duluth, Portland, Lubbock, Odessa, Roanoke, Wilmington, Johnstown, Green Bay, Asheville, Yakima, Gainesville, Amarillo, Lynchburg, Waco, Merced, Longview, Fort Smith, Clarksville, Chico, Springfield, Myrtle Beach, Houma, Laredo, and Richland MSAs

7-May-2007
· Added Spokane, Pensacola, Canton, Saginaw, Salinas, Santa Barbara, Shreveport, Lafayette, Beaumont, York, Corpus Christi, Reading, Rockford, Provo, Visalia, Biloxi, Davenport, Appleton, Peoria, Huntsville, Hickory, Reno, Brownsville, Montgomery, Springfield, Eugene, Macon, Fort Pierce, Huntington, Killeen, Fayetteville AR, Fayetteville NC, and Utica MSAs

2-May-2007
· Added Daytona Beach, Lakeland, Johnson City, Lexington, Augusta, Melbourne, Lancaster, Chattanooga, Des Moines, Kalamazoo, Lansing, Modesto, Fort Myers, Jackson, Boise City, and Madison MSAs
· Harrisburg_PA.kmz had a corrupted coverage map overlay for WHP-DT, so a fixed version of the file has been posted. If you have a corrupted version of the file, please delete it and download the fully working version. Torrent seeders should also delete the old torrent+data and get the new one.

28-Apr-2007
· Added Allentown, Harrisburg, Scranton, Toledo, Baton Rouge, Youngstown, Springfield, Sarasota, Little Rock, McAllen, Stockton, Charleston, Wichita, Mobile, Columbia, Colorado Springs, and Fort Wayne MSAs

26-Apr-2007
· Added Greenville, Dayton, Fresno, Birmingham, Honolulu, Albany, Tucson, Tulsa, Syracuse, Omaha, Albuquerque, Knoxville, El Paso, and Bakersfield MSAs

19-Apr-2007
· Added Austin, Nashville, Providence, Raleigh, Hartford, Buffalo, Memphis, West Palm Beach, Jacksonville, Rochester, Grand Rapids, Oklahoma City, Louisville, and Richmond MSAs

16-Apr-2007
· Added Las Vegas, Columbus, Charlotte, New Orleans, Salt Lake City, and Greensboro MSAs
· Fixed callsign parsing such that some previously missed transmitters are now included

11-Apr-2007
· Added Pittsburgh, Portland, Cincinnati, Sacramento, Kansas City, Milwaukee, Orlando, Indianapolis, San Antonio, and Norfolk MSAs.

6-Apr-2007
· Fixed bug causing several transmitters to be left out of each set. For all the latest, please download the file(s) again.
· Added Atlanta, Miami-Ft. Lauderdale, Seattle, Phoenix, Minneapolis-St. Paul, Cleveland, San Diego, St. Louis, Denver, and Tampa MSAs.
· Dallas_FtWorth filenames have been shortened to just Dallas.
· MSA centroids have been re-defined according to US Census Bureau standards, so the included set of transmitters per metro may have changed.

30-Mar-2007
· Added Houston MSA

29-Mar-2007
· Updated Chicago with new enhancements and some additional transmitters
· Added Washington-Baltimore, San Francisco, Philadelphia, Boston, Detroit, and Dallas-Ft. Worth MSAs.

28-Mar-2007
· Added New York and Los Angeles packages. Chicago package remains the same (to be updated soon).
· Clicking on a transmitter icon now brings up a balloon filled with key vitals and a link to the FCC. Any packages released after today should include this enhancement.




About the maps:

They DO take into account the transmitter power, antenna pattern, and height (according to the FCC)
They DO account for propagation losses due to terrain
They DO account for curvature of the Earth
They represent the expected signal strength near ground level
They DO NOT take into account your antenna gain, amps, elevated installation, or receiver sensitivity
They DO NOT account for building obstructions or indoor penetration
They DO NOT account for multipath


In very rough terms, the colors can be broken down as follows (not related to Antennaweb):

- White is extremely strong. Beware of signal overload on amps.
- Red-yellow-green are all quite strong. You can expect reasonable coverage with an indoor antenna.
- Cyan is where it's advisable to move the antenna up to the second floor or attic.
- Blue is where it's probably necessary to install a good antenna on the roof.
- Purple is quite weak and you really have to work at it for any chance of reception.

Please understand that this is a simulation and can only be treated as a rough approximation. Reception at your location is affected by many factors such as multipath, antenna gain, receiver sensitivity, buildings, and trees - which are not taken into account. Your mileage may vary.


Additional comments:

The coverage maps are not initially turned on when the file is loaded. You need to expand the folders to select the coverage maps to view.


The terrain variations are easier to see if you set the terrain exaggeration to 3 (max) in the Google Earth options.


FYI, the standard coverage maps are created with roughly 500 meter resolution at ground level. In order to truly understand the reception issues at a particular location (e.g., the roof of your house), it's better to look at an analysis such as a radar plot (http://www.tvfool.com/index.php?option=com_content&task=view&id=13&Itemid=45) since it is simulated at much higher resolution and is specific to a location in 3D space (lat, lon, and height). On a single page, you can simultaneously see the signal strength of all nearby channels for your exact location.
http://home.comcast.net/~andy.s.lee/public/radar_thumb.png (http://www.tvfool.com/index.php?option=com_content&task=view&id=13&Itemid=45)


If you notice any errors, please let me know. If any data has been incorrectly extracted from the FCC database, they should be corrected for future simulations.


Best regards,
Andy

Can you package this all up into one file, but break it down in the single file in the tree structure.

Anybody else have Permission denied errors trying to access this data in google earth?

Car Dude

From an earlier post in this thread:http://www.avsforum.com/avs-vb/showpost.php?p=10184745&postcount=26

The error message is not correct, it's a path problem and can't find the file. I had the same problem with the transmitter file from Post #1.

Put the .kmz file into Google Earth's default folder, e.g. c:\Program Files\Google\Google Earth\ and in "My Documents". One of those 2 folders is the correct one- will sort that out later. Restart, problem gone (fingers crossed).

Update: After you open the .kmz file, it goes to the "Temporary Places" folder. Right-click on the "Temporary Places" folder and select "Save to My Places." To make it permanent, select File-> Save My Places. This will save everything to the default "My Places" folder: C:\Documents and Settings\<username>\Application Data\Google\GoogleEarth.

Can you package this all up into one file, but break it down in the single file in the tree structure.

I'll put together a file that includes all the kmz files as a single download. I'm not sure that folders are necessary as each kmz file is a self-contained item. The resulting collection should just be one folder with 276 files in it.

It'll take a few days for me to get the files ready and I'll post an announcement when it's available.

Best regards,
Andy

Thanks GeekGirl! Works now!

Car Dude

I'll put together a file that includes all the kmz files as a single download. I'm not sure that folders are necessary as each kmz file is a self-contained item. The resulting collection should just be one folder with 276 files in it.

It'll take a few days for me to get the files ready and I'll post an announcement when it's available.

Best regards,
Andy
OK, anybody that has bandwidth and disk space to burn can now download the entire 276 Metro collection as a single torrent. I posted an announcement here (http://www.tvfool.com/index.php?option=com_content&task=view&id=40&Itemid=59).

Best regards,
Andy

Andy,

Long time listener, first time caller...

Thank you for all of your hard work. I have been looking for an RF Visualization tool using Google Earth.

I have read your posts, and this process seems to be quite labor intensive in nature.

I am trying to model RF propigation near Seattle for a private wireless network. The terrain is quite rugged in this area.

Would you please share any information concerning the compilation process and any supporting software that you are using.

Thank you once again for your assistance,

Mark

Andy,

Long time listener, first time caller...

Thank you for all of your hard work. I have been looking for an RF Visualization tool using Google Earth.

I have read your posts, and this process seems to be quite labor intensive in nature.

I am trying to model RF propigation near Seattle for a private wireless network. The terrain is quite rugged in this area.

Would you please share any information concerning the compilation process and any supporting software that you are using.

Thank you once again for your assistance,

Mark

Hi Mark!

The basic propagation modeling logic is quite simple. I use the Longley-Rice Irregular Terrain Model, I add some information about the transmitter (power, radiation pattern, height, etc.), the receiver, and some terrain data, and run through the computation. For the most part, all the input data is freely available to the public. The transmitter data and antenna patterns come directly from the FCC web site. The terrain data comes from the Shuttle Radar Topography Mission (SRTM).

With these basic building blocks, it's simply a matter of applying the Longley-Rice computation many times to generate radar plots, create coverage maps, or analyze the data in various ways (e.g., examine interference, optimize for height/power/range, etc.). FYI, in order to generate all the coverage maps available on tvfool.com, the computation had to be applied hundreds of billions of times (thank goodness for Moore's Law making this all possible on a limited budget).

The same principle applies to any wide-area propagation modeling problem. This method does a decent job of predicting large-scale (terrain limited) propagation effects, but does not model local effects (i.e., buildings, trees, multipath losses, etc.). There are other well-known models that can be applied to account for those specific cases. For large-scale modeling purposes, the basic Longley-Rice methodology can be applied to a wide variety of "broadcast" services (e.g., microwave, cellular, FM. WiFi, etc.) or can be combined with other modeling techniques when local effects also need to be considered.



The tools I use to generate radar plots and Google Earth packages are all self-made custom software. I'm sorry, but I don't have any ready-ro-run application I can point you to. My collection of tools cover a wide variety of functions since I use them for all kinds of propagation analyses and simulations in my line of work, but for the basic generation of Google Earth overlays, here are some very useful resources that helped me get started:

- L-R ITM reference (http://flattop.its.bldrdoc.gov/itm.html)
- FCC database (http://www.fcc.gov/mb/databases/cdbs/)
- SRTM terrain (http://www2.jpl.nasa.gov/srtm/)
- NADCON (http://www.ngs.noaa.gov/TOOLS/Nadcon/Nadcon.html)
- libpng, zlib (http://www.libpng.org/pub/png/libpng.html)
- KML reference (http://code.google.com/apis/kml/documentation/kml_tags_21.html)

Your approach to propagation analysis will depend on what you want to understand about the setup and how often you'll need to run various simulations. For example, coverage maps are far more computationally heavy compared to a specific point-to-point analysis since every "map" actually consists of thousands to millions of points that need to be evaluated. You'll need to think about what's necessary or appropriate for the problem you are trying to solve. I would need a better understanding of your specific requirements in order to offer any useful guidance.

I hope this helps!

Best regards,
Andy

Andy,

Thank you for pointing me in the right direction.

We have a customer that wants Wi-Fi or Wi-Max coverage in the mountainous terrain here in Washington.

Buildings and structures are not a large concern for this proposal.

We are trying to provide some basic coverage modeling to determine the cost worthiness of our proposal.

I am sure that your work will eventually turn into a commercialized product.

The only thing that I have seen that is close is the Terrain Analysis software from http://www.softwright.com

Thank you once again for your assistance,

Mark

You should also check out RADIO MOBILE (free, runs under Windows):
http://www.cplus.org/rmw/english1.html
See post #198 above re Excel spread sheet I posted re statistical signal level calibration.
It includes Gain/Loss due to Antena, Preamp, Cable/Splitters, Noise Figure, et.al.

and SPLAT! (free, runs under Linux):
http://www.qsl.net/kd2bd/splat.html

Thanks Holl_ands,

I have downloaded Radio Mobile and I have seen splat.

I can't believe that we must endure 1980's quality graphics in 2007.

The products that Andy is producing are professional.

I may be forced to utilize a freeware product for this deadline, but I will continue to research this Google Earth overlay technology.

Thanks again,

Mark

Andy;

I downloaded the Montgomery, Alabama, MSA info, but it displays on Google Earth as being the Birmingham, Alabama, MSA. Is there a file problem here, or am I doing something wrong?

Andy - "nevermind"

I see now that there are a series of radio buttons to turn on and off the coverage of each station in the MSA. I had not seen those when I first brought up the file on Google Earth. Now I see how it works. Thanks for the fantastic work.

Sorry if this is off topic. I have 2 PCs connected on a wireless network and then through a dsl router.

PC 1 is able to access www.tvfool.com, access the Bit Torrent files and download the coverage map for San Francisco.

PC 2 can never access www.tvfool.com or view the link in the second post to http://www.tvfool.com/kmz/torrent/San_Francisco_CA.kmz.torrent.

I get an error message in Firefox saying 'The connection to the server was reset while the page was loading.' I then ran a tracert to www.tvfool.com from PC 2. It always times out after about 14 hops.

I see some others in this thread have had trouble linking to the torrents. PC2 access all other web sites without a problem. I have flushed the dns cache etc.

As above PC 1 sees www.tvfool.com and the torrent fine. Thoughts? Both PCs are running same software firewalls/security software. PC1 is running XP SP2 and PC 2 is running XP Media Center Edition.

none of the torrents have seeds...any mirrors?

none of the torrents have seeds...any mirrors?

Hi Lkr,

All the kmz files were recently updated and all the torrents have been replaced. If your *.torrent file is more than a week old, you might be trying to download off the old torrent. All the seeds have been migrated to the new set of files and therefore you need the corresponding new *.torrent file(s). Try removing your existing torrent and downloading the latest version from here (http://www.tvfool.com/index.php?option=com_content&task=view&id=15).

The new torrents are being seeded and it looks like several people are actively downloading them as we speak.

I hope this solves your problem.

Best regards,
Andy

I think I'm going to have give up on getting any new files. I've been trying on and off for a week to download Los Angeles and the best I can get is that it tells me 14 days to download it. I was successful last summer in getting some files but no longer. Is there no alternative? How about purchasing a DVD with the files you need?

I think I'm going to have give up on getting any new files. I've been trying on and off for a week to download Los Angeles and the best I can get is that it tells me 14 days to download it. I was successful last summer in getting some files but no longer. Is there no alternative? How about purchasing a DVD with the files you need?

Sorry about that. Demand for the updated files has been unexpectedly high. The limited number of initial seeds that I have running are having a hard time keeping up with all the requests. Download speeds should improve as the demand dies down and as the number of friendly peers start to take some of the burden off the main servers. If you remain patient, I'm sure things will get better soon.

I apologize for the inconvenience.

Best regards,
Andy

Andy,

Just downloaded the Philly area and the "Complete Collection of Transmitter Icons". Great stuff. Keep going. Just one "glitch". There seem to be blank names in the first few entries of these files:

FCC_TV_2007-12-07 / Transmitters / Digital
1st entry: Called "no_name", but marker is tagged CBLNTV5, Michigan area.

FCC_TV_2007-12-07 / Transmitters / Analog
1st entry: 0.5 mi SE of Philadelphia, PA marker
2nd entry: Mexico, SW of Juarez

Philadelphia_PA / Transmitters / Analog
1st entry: 0.5 mi SE of Philadelphia, PA marker

The 1st blank entry for the FCC Complete and Philly analog transmitters map to the same point.

Andy,

Just downloaded the Philly area and the "Complete Collection of Transmitter Icons". Great stuff. Keep going. Just one "glitch". There seem to be blank names in the first few entries of these files:

FCC_TV_2007-12-07 / Transmitters / Digital
1st entry: Called "no_name", but marker is tagged CBLNTV5, Michigan area.

FCC_TV_2007-12-07 / Transmitters / Analog
1st entry: 0.5 mi SE of Philadelphia, PA marker
2nd entry: Mexico, SW of Juarez

Philadelphia_PA / Transmitters / Analog
1st entry: 0.5 mi SE of Philadelphia, PA marker

The 1st blank entry for the FCC Complete and Philly analog transmitters map to the same point.

Thanks for the heads up!

I actually noticed the same thing in the previous set of released files, except that in that case, the mystery transmitter was in Los Angeles.

The last time I looked at it, it was caused by a transmitter marked as "NEW". It looked like it was a recently entered application of some kind that was not given a proper callsign designation. In fact, there can be many records like this at any given time within in the FCC database.

I believe that eventually the records get updated callsigns, but it's annoying that they occasionally show up as transmitters with a null name.

I'll probably make some changes to ignore these "partially-defined" transmitters in the next round of updates.

Best regards,
Andy

I've been trying on and off since my last post to download 2 files. I have partial files but I can't complete them. Maybe Bit Torrent is great for movies where lots of people are sharing them but it certainly isn't working for this. Maybe Google would be willing to host all the files? Bandwidth wise these files must be a drop in the bucket compared to what they use everyday.

Chuck

I've been trying on and off since my last post to download 2 files. I have partial files but I can't complete them. Maybe Bit Torrent is great for movies where lots of people are sharing them but it certainly isn't working for this. Maybe Google would be willing to host all the files? Bandwidth wise these files must be a drop in the bucket compared to what they use everyday.

Chuck

Out of curiosity, are you a Comcast customer? They have reportedly been tampering with torrent traffic by disrupting connections between peers.

If you are being subjected to this kind of tampering, you might be able to fix it by forcing your torrent client to use encryption on its connections. In uTorrent, the way to do this is go to the Options->Preferences->Bit Torrent dialog and set the outgoing protocol encryption to "Forced".

The down side of this is that you'd only be able to connect to other torrent clients that understand this kind of encryption. Fortunately, most of the mainstream clients (including Azureas and Mainline) support this, so you should still have a good number of peers available to send files to you.

Best regards,
Andy

Out of curiosity, are you a Comcast customer? They have reportedly been tampering with torrent traffic by disrupting connections between peers.

No, I have WildBlue.

I was finally able to get Los Angeles this morning but I had to restart Bit Torrent 6 times because it kept stopping.

I'm still trying for Medford, OR. It only added 2% while LA was finishing.

Chuck

I'm still trying for Medford, OR. It only added 2% while LA was finishing.


I was finally able to finish Medford this morning. This is the first time I've seen 2 peers for it and the download was fast, completing in 2 minutes.

Chuck

Once they all finish downloading, I'm going to seed most of the files for eastern/central PA:
Williamsport
Harrisburg
Allentown
Scranton
Philadelphia

And I've got one more, but that's at home and I'm at work (no torrents here!). I've been reading information for a while, have a background in electronics/radio/PCs, but just signed up for the forums today. I have my coupons for DTV converters, and with them/because of them, I am learning all sorts of new things about TV broadcasting and reception. I hope at some point to be able to not just leech all the information everyone else has, but to also contribute what I know. Hopefully it'll be useful to someone.

This information and the work put into it is amazing, and I thank you greatly for your time and effort!

Welcome, you sound like the kind of person we could use more of ...

And yes, you will be amazed and astounded by what you find here.
Frank

Welcome, you sound like the kind of person we could use more of ...

And yes, you will be amazed and astounded by what you find here.
Frank


Okay, forgot to restart Harrisburg and Allentown, so working on d/l'ing them still, but seeding Philly, Scranton, and Williamsport.

Thanks for this bit of awesomeness.

subscribing

subscribing

You can do that without leaving a comment. Just sayin.

Not much activity for a while, but someone over on the Philly area OTA thread just validated your analysis tool. It was kind of cool that he couldn't receive certain channels, but was OK on others. Your TV Fool web site showed why (terrain).

From about here: http://www.avsforum.com/avs-vb/showthread.php?p=13971665#post13971665 (original problem is back 6 posts).

For want of a 15MB file…

For whatever reason, BIt Torrent has been useless for me. I can see the seeds, get conformation and then nothing. Have reset router, etc. Perhaps it is Wildblue service. Anyway I am not impressed and very frustrated with this method of delivery.

Having screwed with this for a week, I just wonder if someone here could send me the file--

Missoula_MT.kmz.

You would be helping someone in a deep fringe area in Montana.

PM me if you could help. Thank You!

For want of a 15MB file…

For whatever reason, BIt Torrent has been useless for me. I can see the seeds, get conformation and then nothing. Have reset router, etc. Perhaps it is Wildblue service. Anyway I am not impressed and very frustrated with this method of delivery.

Having screwed with this for a week, I just wonder if someone here could send me the file--

Missoula_MT.kmz.

You would be helping someone in a deep fringe area in Montana.

PM me if you could help. Thank You!


Griz,
Have you tried other torrent clients? I'm not a huge Bit Torrent fan myself. One excellent alternative is this one from Sourceforge (http://azureus.sourceforge.net/), used to be called Azureus, that now goes by the pronouncable name Vuze. Another one worth investigating is uTorrent (http://www.utorrent.com/download.php).

If nobody gets to you with the actual file, you might want to consider one of these. Good luck.

For whatever reason, BIt Torrent has been useless for me. I can see the seeds, get conformation and then nothing. Have reset router, etc. Perhaps it is Wildblue service.

BTW, one trick that can fool some of the ISP torrent screens is to force protocol encryption on your connections. This masks the traffic so that the ISPs traffic sniffers cannot identify it as torrent traffic. uTorrent, Azureus, and Mainline all support this feature.

As an example, in uTorrent, you can enable this under Options->Preferences->Bit Torrent->Protocol Encryption. Configure the outgoing encryption setting to "Forced".

If this alleviates the problem, then it's almost certain that your ISP is snooping and selectively disrupting your traffic. If they are doing this, you should let them know it is a bad policy (and it makes you wonder what else they're snooping and manipulating). Selectively blocking traffic is the equivalent of the phone company telling you who you can call, what you can say, or how you say it. A web search for "net neutrality" will yield a lot more information on the subject and why this kind of filtering is a bad thing.

If this does not fix the problem, PM me and I'll get the file to you some other way.

Best regards,
Andy

For want of a 15MB file…

For whatever reason, BIt Torrent has been useless for me. I can see the seeds, get conformation and then nothing. Have reset router, etc. Perhaps it is Wildblue service. Anyway I am not impressed and very frustrated with this method of delivery.

Having screwed with this for a week, I just wonder if someone here could send me the file--

Missoula_MT.kmz.

You would be helping someone in a deep fringe area in Montana.

PM me if you could help. Thank You!
I also had no problems with uTorrent, but I hear some ISPs cause torrent grief. I am far from an expert. If you need, I can capture and send via AOL IM, Yahoo IM, or Windows Messenger. I did that for someone else on this group once. PM me to set-up if needed. I need to download first and then we connect and upload (if I remember what we did). /Dan

Thanks guys for your suggestions . Tried several, NO JOY! I suspect my ISP [Wildblue Satellite] is playing some part in this as they have metering schemes for downloads.

If that 15mb Missoula_MT.kmz could be posted somewhere, I could grab it in a few minutes.

Howdy

IF this is a help [and it sure would be to me], I have a FTP account to which the .Kmz file could be sent.

Missoula_MT.kmz 15Mb

If you can do this.. PM me and I will give you the FTP details.

Thanks much!

Griz

Where download maps for Puerto Rico in tvfool

Where download maps for Puerto Rico in tvfool

Unfortunately, at present, we are unable to provide downloadable Google Earth coverage maps for all transmitters in all cities. For the cities without pre-packaged kmz files, the best we can offer for now is the online maps.

Best regards,
Andy