Notice: This page is out of date! Redirecting to the new PSC homepage in 10 seconds.
Please update your bookmarks.
Click here if the page does not load.

FCC Antenna Structure Registration for Kentucky

Frequently-anticipated questions:


What does this data set describe?

    Title: FCC Antenna Structure Registration for Kentucky
    Abstract:
    The Kentucky Public Service Commission (PSC) has downloaded and extracted the Kentucky data on Antenna Structure Registration from the Federal Communication Commission's (FCC) web site. The PSC takes no responsibility for the accuracy or completeness of the data. To promote air safety, the Federal Communications Commission (FCC) requires owners to register antenna structures more than 200 feet in height or located near an airport with the FCC. An antenna structure can be free-standing, built specifically to support or act as an antenna, or it can be mounted on another object such as a building, bridge, smoke stack, or tree. Because the Antenna Structure Registration requirements only apply to those antenna structures that may create a hazard to air navigation (either by their height or proximity to an airport), the registration files do not contain a comprehensive record of all antenna structures. Contacts for the structures are contained in a separate table that can be linked to the GIS data.

  1. How should this data set be cited?

    US Federal Communications Commi, extracted and processed by the Kentucky P, August 11, 2002, FCC Antenna Structure Registration for Kentucky:,.

    Online Links:

    • \\PSCNT3\GIS_Library\Telecomm\Shape\antennas.shp

    This is part of the following larger work.

    .

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -89.067220
    East_Bounding_Coordinate: -82.170000
    North_Bounding_Coordinate: 39.107220
    South_Bounding_Coordinate: 36.519720

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: August 11, 2002
    Currentness_Reference: publication date

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • Entity point (1754)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000000. Longitudes are given to the nearest 0.000000. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

  7. How does the data set describe geographic features?

    ANTENNAS.dbf
    Latitude - longitude decimal degree coordinates for structures.

    FID
    Unique Record Identifying Number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Geometry of features. (Source: ESRI)

    Coordinates defining the features.

    LATITUDE
    Latitude in Decimal Degrees, NAD 83.

    LONGITUDE
    Longitude in Decimal Degrees, NAD 83.

    REGISTRATI
    FCC Registration Number.

    REG
    Street Address or Description of Location.

    SITE_STR
    City Where Structure is Located.

    SITE_CITY
    Application Purpose Code.

    APP_CODE
    Application Purpose Code Definition.

    APPLICATIO
    Date Registration Issued.

    ISSUED
    Status of Structure, "Granted" or "Constructed."

    STATUS
    Type of Structure Code.

    STRUCT_COD
    Type of Structure Description.

    STRUCTURE
    Date Structure Constructed.

    CONSTRUCTE
    FAA Study Number.

    FAA_STUDYN
    Date FAA Determination Issued.

    FAA_DATE
    Height above ground to the highest point of the supporting structure only (without appurtenances) in feet.

    HEIGHTFT
    Elevation above mean sea level of the ground at the antenna structure site in feet.

    ELEVFT
    Overall height above ground level (AGL) of the entire antenna structure to the highest point, including any appurtenances such as antennas, dishes, and obstruction lighting in feet.

    AGL_FT
    Overall height above mean sea level (AMSL) in feet; total of ElevFT and AGL_FT.

    AMSL_FT


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

  3. To whom should users address questions about the data?

    Ruth A. Rowles
    Kentucky Public Service Commission
    GIS Manager
    P.O. Box 615
    Frankfort, KY 40601
    502-564-3940 (voice)
    502-564-1582 (FAX)
    rarowles@ky.gov


Why was the data set created?

The Kentucky Public Service Commission uses this as basic reference information for its regulatory responsibilities concerning the construction of cellular antenna towers.


How was the data set created?

  1. From what previous works were the data drawn?

    FCC ASR (source 1 of 1)
    US Federal Communications Commission, August 11, 2002, FCC Antenna Structure Registration.

    Online Links:

    Other_Citation_Details:
    The original files for the data for Antenna Structure Registration are found on the web site: <http://www.fcc.gov/cgi-bin/wtbdatadump.pl>. An explanation of the Antenna Structure Registration system is found on the FCC web site for the Universal Licensing System, <http://www.fcc.gov/wtb/antenna/infoCenter/aboutasr.html>.
    Type_of_Source_Media: online
    Source_Contribution:
    The Kentucky data is derived from the FCC Antenna Structure registration data files, RA (registation data) and CO (tower coordinates.) All registrations are filed via FCC Form 854.

  2. How were the data generated, processed, and modified?

    Date: Whenever new data is downloaded. (process 1 of 1)
    The following procedures were performed: 1) All records were selected from the CO (Coordinates) file that had a Kentucky site address and those records were joined to the RA (Registration) file. 2) The coordinates were processed into decimal degrees NAD 83. The original coordinates were in NAD83, expressed as DD MM SS.S. However, most of the data is expressed as DD MM SS. 3) Some records were eliminated. This includes those records for coordinates for the center of an array of towers, so that just the tower coordinates are included in the database. In addition those antenna structures with a status of cancelled, terminated, or dismantled were deleted from the database. This leaves a registration database with antenna structures that have been constructed or have been granted permission for construction. 4) There are four fields for height. The data was initially recorded in meters and has been converted to feet. 5) Two tables were created: AntennaR, which contains location coordinates and structure information for each antenna, and AntContR, which includes several contacts for each structure with name, address, phone, and e-mail data. 6) Point coordinates from AntennaR were plotted as an event theme in ArcView 3.2 and converted to a shapefile.


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

  2. How accurate are the geographic locations?

    The coordinates were processed into decimal degrees NAD 83. The original coordinates were in NAD 83, expressed as DD MM SS.S, which means that the data base allows for a positional accuracy of plus or minus ten feet. However, most of the data is expressed as DD MM SS, so the positional accuracy is generally plus or minus one hundred feet.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

  5. How consistent are the relationships among the observations, including topology?


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Use_Constraints:
Credit should be given to the Federal Communications Commission for the data and to the Kentucky Public Service Commission for processing. The Kentucky Public Service Commission takes no responsibility for the accuracy or completeness of the data. All critical information should be independently verified. Users should be aware that the data is downloaded periodically and may not be the most up-to-date information available through the FCC.

  1. Who distributes the data set? (Distributor 1 of 1)

    Ruth Rowles
    Kentucky Public Service Commission
    GIS Manager
    P. O. Box 615
    Frankfort, KY 40601
    502-564-3940 (voice)
    502-564-1582 (FAX)
    rarowles@ky.gov
  2. What's the catalog number I need to order this data set?

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: September 13, 2002

Metadata author:
Ruth A. Rowles
Kentucky Public Service Commission
GIS Manager
P.O. Box 615
Frankfort, KY 40601
502-564-3940 (voice)
502-564-1582 (FAX)
rarowles@ky.gov
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Metadata extensions used:


Generated by mp version 2.7.3 on Fri Sep 13 12:04:43 2002


Disclaimer
Return to PSC Home Page
Return to PSC GIS Data
Revised May 15, 2003