This dataset contains locations from the antenna structures database that are required to register with the Federal Communications Commission (FCC). The FCC requires owners to register those antenna structures which generally are more than 60.96 meters (200 feet) in height or located near an airport. This is an update to the antreg_aug18 layer.
Serve as base information for use in GIS systems for general planning, analytical, and research purposes. It is not intended for engineering work or to legally define reservation boundaries, FCC licensee data or FCC market boundaries.
publication date
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government or the Federal Communications Commission (FCC). No warranty expressed or implied is made by the FCC as to the accuracy of the data and related materials. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the FCC in the use of this data, or related materials.
445 12th St. SW
Federal Communications Commission
GeoPlan relied on the integrity of the attribute information within the original data.
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology
This data is provided 'as is' by GeoPlan and is complete to our knowledge.
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Spatial and Attribute Information
In 2012 the FCC stopped releasing tower and antenna locations as spatial data. Data layers are available as databases with associated .dat files. GeoPlan downloaded the Antenna Structure Registrations from http://wireless.fcc.gov/antenna/index.htm?job=uls_transaction&page=weekly in August 2019. During the QA/QC process GeoPlan performed the following steps: - Opened and formatted the CO.dat file in Excel. Added field names using the FCC Database Field Definitions File: http://wireless.fcc.gov/uls/documentation/patower-2.xls. Saved coordinate fields as LATD, LATM, LATS, LAT_DIR, LOND, LONM, LONS, and LON_DIR - Saved the CO.dat file to a CSV and Exported to .dbf using ArcMap. - Filtered .dbf to contain only records located in Florida. (Using field Structure_State Code from RA.dat - Added LATDD and LONDD fields as type = double - Used field calculator to convert coordinate fields from DMS to DD. The equation for latitude was: ( [LATS] /3600) + ( [LATM] /60) + [LATD] The equation for longitude was: ( [LONS] /3600) + ( [LONM] /60) + [LOND] - Generated XY data using the LATDD and LONDD fields. The projection was defined as WGS 1984. - Exported XY events to shapefile. - Fields LATD, LATM, LATS, LAT_DIR, LOND, LONM, LONS, and LON_DIR were deleted. - Projected the new shapefile to NAD83 HARN using the WGS_1984_(ITRF00)_To_NAD_1983 + NAD_1983_To_HARN_Florida transformation - Opened and formatted EN.dat and RA.dat files in Excel. Added field names using the FCC Database Field Definitions File and previous fgdl versions of antreg. Deleted fields not present in previous versions. - Saved the EN and RA dat files as CVS files and exported to .dbf files using ArcMap. - EN and RA .dbf files brought into ArcMap and joined with the antreg feature class using REGNUM field. - Edited the feature class attribute table to match previous fgdl versions. - Added field MGRS by using the Convert Coordinate Notation tool and choosing output coordinate format as MGRS. - Added field GOOGLEMAP by concatenating: https://www.google.com/maps/place/ and the MGRS ID - Added descript field based on Entity from EN.dat file. - Added FGDLAQDATE based on the date GeoPlan acquired the data. - Restructured table and uppercased all fields. - 5 records did not have spatial information and were removed. These records were REGNUM = 1020589, 1035349, 1035350, 1035351, 1049473 Field Changes - Previous fields LAT_DMS and LON_DMS have been renamed to LAT and LON. - Previous fields DD_TEMP and DD_TEMP0 have been renamed to LATDD and LONDD. - Removed fields LAT_DIR and LON_DIR Notes: When the FCC generated this data set spatially in the past they limited the lat/long fields to 4 decimals. Now that we are generating the spatial locations the decimals have been left to the default value of the field type of double. The result is a visible shift of 1-3 meters.
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
Esri
FCC Registration Number.
FCC
The FCC assigned file number of the application.
FCC
Date of FCC Registration Permit.
FCC
The exact geographic location latitude of the structure in degrees (e.g., 42), minutes (e.g., 13'), and seconds (e.g., 10").
FCC
The exact geographic location longitude of the structure in degrees (e.g., 42), minutes (e.g., 13'), and seconds (e.g., 10").
FCC
Geographic location (latitude) in decimal degrees.
GeoPlan
Geographic location (longitude) in decimal degrees.
GeoPlan
Structure Height. Overall height above ground.
FCC
Structure Address. The address where the structure is located.
FCC
Structure City. The city in which the structure is located.
FCC
Structure State. The state in which the structure is located.
FCC
FAA Study Number. A unique number assigned by the Federal Aviation Administration (FAA) pertaining to an antenna site/structure. This number is issued during the processing of FAA Form 7640-1 "Notice of Proposed Construction or Alteration."
FCC
Advisory Circulars. The FCC generally assigns painting and lighting requirements, at registration, according to the FAA's "determination" for a structure.
FCC
FCC ID Number (L Number). A unique 9-digit number (the letter 'L' followed by 8 numeric digits) assigned by the FCC to represent the Taxpayer Identification Number (TIN) of the individual or business entity who filed the application.
FCC
Name of Contact.
FCC
Address for contact.
FCC
Post Office Box for contact.
FCC
City for contact.
FCC
State for contact.
FCC
Zip code for contact.
FCC
Military Grid Reference System (MGRS) Coordinate of the Facility. The MGRS is the geocoordinate standard used by NATO militaries for locating points on the earth. The MGRS provides a means to represent any location on the surface of the Earth using an alphanumeric string. Hierarchical references are based on the Universal Transverse Mercator (UTM) coordinate system. The MGRS is used for the entire earth. http://mgrs-data.org/
GeoPlan
Webpage hyperlink to location in Google Maps.
GeoPlan
GeoPlan added description field based on ENTITY.
GeoPlan
The date FGDL aquired the data from the source.
GeoPlan
Unique ID added by GeoPlan
GeoPlan
431 Architecture PO Box 115706
The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The University of Florida GeoPlan Center shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials. A note about data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: http://geoplan.ufl.edu/education.html
445 12th St. SW Portals I Room 6227