In response to many requests for radio service area data, the Audio Division of the Media Bureau, Federal Communications Commission (FCC), releases predicted service contour data points on a regular basis. Generally, updated files are posted to the FCC's website by approximately 10:00 AM each day, Eastern time. These zipped files are available at the following directory locations (include capital letters and underscores as shown):
- By http: https://transition.fcc.gov/Bureaus/MB/Databases/fm_service_contour_data/
- By ftp: ftp://ftp.fcc.gov/pub/Bureaus/MB/Databases/fm_service_contour_data/
The data is contained in one large file:
The file contains data for active records (licenses, construction permits, applications) as shown in the FM Query. (Contour data for archived authorizations is not retained due to space limitations and low usage.)
Using the FCC's F(50,50) propagation curves, distances to the FM service contours are generated from the effective radiated power in a given direction, and the radial antenna height above the average elevation of that same radial. See FM Propagation Curves and Antenna Height Above Average Terrain (HAAT) Calculations for additional information on this process.
USERS TAKE NOTE: The files are LARGE! We recommend using a broadband connection, making sure your system has enough disk space to handle these files. Current data files, unzipped, may be on the order of 200 MB in size.
Because of its large size and layout, it can be difficult to find a viewer capable of displaying the entire text file at one time. However, the structure of the file is straightforward. The first line in the file is a header line; it may be used or discarded as needed. The number columns represent azimuths referenced to True North. Keep in mind that the data for 360° will be the same as that at 0° azimuth (so 360° is not included here), but a 360° value may be needed to close the polygons created by these contour data latitudes and longitudes.
First (header) line:
After that, each line of these formatted text files is constructed as follows:
285006 |FM |5a5d859443754f8aaa16c1b6063ebeb7 |01|37.36881 ,-122.08494|37.41278 ,-122.08398|37.41279 ,-122.08301| ... (continuing up to 359 azimuthal latitude, longitude points, with an ending as follows) ... |37.41276 ,-122.08495|^|
where the leftmost record number represents the LMS database application number.. The record's service is listed in the next field, followed by the LMS database application ID. After that is the site number for the record (this will always be 01 for the FM band services; this field maintains the same file structure as the TV contours data.) This is followed by the NAD83/WGS84 coordinates ("|latitude, longitude|") of the station's or application's transmitter site. Then there are 360 |latitude, longitude| pairs, with the first coordinate pair corresponding to the contour location at 0 degrees (true north) from the transmitter site, and continuing clockwise at 1 degree intervals to 359 degrees. The end of record characters "|^|" finish the line (to help users detect broken lines). This makes each line 7,633 characters long (including the end-of-line characters); Code to read these lines should be written with the long record length in mind. West longitudes and south latitudes are referenced by negative numbers -- in keeping with the conventions of most GIS systems. Regretfully, we cannot honor requests to provide this data in alternative formats.
To associate specific service contour records with the proper station or application data, match the application ID number or LMS application ID the record with the corresponding data in the LMS database. Alternatively, (and certainly much easier than deciphering the LMS tables structures) use the FM Query with the output type set to create a "pipe-delimited text file" -- that output can then be parsed in accordance with the fields description file at https://www.fcc.gov/media/radio/am-fm-tv-textlist-key to obtain the data most commonly sought by users. Using the FM Query searches also has the advantage of allowing users to winnow out unwanted station records. For example, an FM Query search for all the licensed Low Power FM (LPFM) stations (service code FL) in Arkansas will exclude station records in other states and services, as well as construction permits and application records.
It must be noted that the station contours here do not always reflect the same predicted field strength value. For FM stations, the following table may help:
|Channels 201 to 220
Noncommercial educational [NCE] FM stations
|60 dBu (1 mV/m)|
|Channels 221 to 300
Commercial FM stations, and occasional NCE stations, Zone II
|60 dBu (1 mV/m)|
|Channels 221 to 300
Commercial FM stations, occasional NCE stations,
and Class B station in Zones I, I-A
|Channels 221 to 300
Commercial FM stations, occasional NCE stations, and all Class B1 stations in Zones I, I-A
|Channels 200 to 300
LPFM stations [FL], translator [FX],
and auxiliary (backup) stations [FS]
|60 dBu (1 mV/m)|
|All Canadian stations in the database||54 dBu|
For more information about FM station classes, see the FM Classes page.
FM service contours usually do not define the outer limit of service. In most cases, a radio station may be received at locations outside (and sometimes well outside) the service contours given in these files. Within the service contour, reception is generally protected from interference caused by other stations on the same channel or adjacent channels or frequencies. Outside of that contour, interference may occur from other stations. It simply is not possible to protect each station out to the point at which it cannot be heard by anyone. Doing so would result in far fewer stations available to listeners. The Commission's rules represent a balance between very few stations with no interference between them, and great numbers of stations with small service areas and severe mutual interference.
Finally, USE OF THESE CONTOUR DATA FILES IS AT THE USERS' SOLE RISK, and the FCC nor the Federal Government is responsible for errors or omissions, late posting of data, or any consequences thereof. No restrictions are set on the use of this data. The FCC does not guarantee that the contour data here will correspond to the contour data considered during the processing of given applications. Users should take note that this contour data is only generated once for each application ID number, shortly after the application is posted to the FM Query, so that the possibility exists that subsequent corrections to the LMS databases might not be reflected in the service contours herein. (However, amendments to electronically filed applications will have a new application ID number, and so new contour data will be generated for that amendment.) Archived records will not be corrected, any such records are retained for reference purposes only. Lastly, a database of FM interfering contours will not be generated.
Dale Bickel email@example.com
Senior Electronics Engineer
Audio Division, Media Bureau
Federal Communications Commission
Similar data for other broadcast services:
- TV Service Contour Data Points
- AM broadcast service contour data is not available, and we have no time frame for posting this information.
For more information on AM and FM radio broadcasting, please visit the Audio Division website, and the Broadcast Radio Links page.
For more information on Television broadcasting, please visit the Video Division website.
FCC > Media Bureau > Audio Division, (202) 418-2700, and Video Division, (202) 418-1600.