FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: REGISTERED CELLULAR ANTENNA STRUCTURE LOCATIONS IN FLORIDA - FEBRUARY 2017 Geodataset Name: CELLUR_FEB17 Geodataset Type: SHAPEFILE Geodataset Feature: Point Feature Count: 972 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): Federal Communications Commission SCALE OF ORIGINAL SOURCE MAPS: Unknown GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: CELLUR_FEB17.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
Shape
|
4 | Geometry |
LICENSEE
|
55 | String |
CALLSIGN
|
10 | String |
LOCNUM
|
8 | Double |
LAT_DMS
|
10 | String |
LATDIR
|
1 | String |
LON_DMS
|
10 | String |
LONDIR
|
1 | String |
LOCADD
|
80 | String |
LOCCITY
|
20 | String |
LOCCOUNTY
|
15 | String |
LOCSTATE
|
2 | String |
NEPA
|
1 | String |
TOWREG
|
8 | Double |
SUPSTRUC
|
8 | Double |
ALLSTRUC
|
8 | Double |
STRUCTYPE
|
10 | String |
LIC_ID
|
8 | Double |
LATDD
|
8 | Double |
LONDD
|
8 | Double |
DESCRIPT
|
10 | String |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
LICENSEE |
Represents the legal entity that is issued a license and may not represent the name for which service is marketed/provided. |
|
CALLSIGN |
A combination of letters and numbers that identify an FCC license. |
|
LOCNUM |
The number associated to the location by the Universal Licensing System (ULS). This number must be used to reference the location on all applications submitted via ULS. |
|
LAT_DMS |
Latitude associated with this location in degrees, minutes (e.g., 13'), and seconds (e.g., 10") and are referenced in NAD83 (North American Datum 1983) |
|
LATDIR |
Latitude cardinal direction associated with this location |
|
LON_DMS |
Longitude associated with this location in degrees, minutes (e.g., 13'), and seconds (e.g., 10") and are referenced in NAD83 (North American Datum 1983) |
|
LONDIR |
Longitudinal cardinal direction associated with this location |
|
LOCADD |
Physical address of the cellular structure. |
|
LOCCITY |
City in which the cellular structure is located. |
|
LOCCOUNTY |
County in which the cellular structure is located |
|
LOCSTATE |
State in which the cellular structure is located. |
|
NEPA |
Compliance with the National Environmental Policy Act
|
|
TOWREG |
Tower registration number. |
|
SUPSTRUC |
The height above ground level to the highest point of the supporting structure only in meters. |
|
ALLSTRUC |
The overall height above ground level of the entire antenna structure to the highest point, including any appurtenances, in meters. (Includes antennas, dishes, obstruction lighting, etc.) |
|
STRUCTYPE |
The code for the type of structure on which the antenna is or will be mounted. |
|
LIC_ID |
A masked Taxpayer Identification Number (TIN). In the Universal Licensing System (ULS) an entity's TIN is not provided to the public. However, the public will see a Licensee ID number (masked TIN) that they can use for application and license searches |
|
LATDD |
Latitude in Decimal Degrees. |
|
LONDD |
Longitude in Decimal Degrees. |
|
DESCRIPT |
GeoPlan added field based on CALLSIGN |
|
FGDLAQDATE |
The date GeoPlan aquired the data from the source. |
|
AUTOID |
Unique ID added by GeoPlan |
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. |
GeoPlan relied on the integrity of the attribute information within the original data. |
As you use the cellular structure location data, be aware that the database may reflect uncorrected facility reporting errors. |
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. |
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 |
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. |
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 |
Federal Communications Commission: http://www.fcc.gov/ Wireless Telecommunications Bureau: http://wireless.fcc.gov/index.htm |
In 2012, the FCC stopped releasing its data as spatial data. Everything is released in databases now with associated .dat files for download. Downloaded Cellular 47 CFR Part 22 from (http://wireless.fcc.gov/antenna/index.htm? job=uls_transaction&page=weekly) in February 2017. - Opened and formatted LO.dat in Excel. Added field names using the FCC Database Field Definitions File: (http://wireless.fcc.gov/uls/documentation/pa_ddef50.pdf) and cellur_jun12. Saved coordinate fields as LATD, LATM, LATS, LATDIR, LOND, LONM, LONS, and LONDIR - Saved as .csv file - Opened .csv in ArcMap and exported to a dbase table - Added LATDD and LONDD fields using type = double. These fields will be used to house the coordinates in decimal degrees. These field names were chosen to mimic the coordinate fields in cellur_jun12 - Used field calculator to convert coordinate fields from DMS to DD. The equation for latitude (LATDD) was: ( [LATS] /3600) + ( [LATM] /60) + [LATD] The equation for longitude (LONDD) was: ( [LONS] /3600) + ( [LONM] /60) + [LOND] - Generated XY data using the LATDD and LONDD fields. The projection was defined as WGS 1984. CELLUR shapefile - Projected the event layer to Albers_Harn using project tool and exported out as shapefile - Clipped projected shapefile to the state of Florida - Opened and formatted EN.dat in Excel. Added field names using the FCC Database Field Definitions File and cellur_jun12. Deleted fields not present in cellur_jun12. Saved as .csv files. - EN file brought into ArcMap and joined with the cellur_jan17 feature class using TOWREG field. Exported out joined files to a new feature class - Edited the feature class attribute table to mimic cellur_jun12 - Added descript field based on Call Sign originally from LO.dat (CALLSIGN in shapefile) - Added FGDLAQDATE based on the date GeoPlan acquired the data - Added a LAT_DMS and LON_DMS field based on combination of LATD, LATM, LATS, LOND, LONM, and LONS then deleted those field because they are not present in the previous CELLUR shapefile - Restructured table and uppercased all fields Notes: When the FCC generated this data set spatially in the past they only included lat/lon in DMS. Previously the seconds included no decimal places and now they do include 1 decimal place. Now that we are generating the spatial locations from this data the improved accuracy has resulted is a visible shift that varies anywhere from 1-36 meters. Process Date: 20170209 |
Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 1st Standard Parallel 24 0 0.000 2nd Standard Parallel 31 30 0.000 Central Meridian -84 00 0.000 Latitude of Projection's Origin 24 0 0.000 False Easting (meters) 400000.00000 False Northing (meters) 0.00000
DATA SOURCE CONTACT (S):
Name: Abbr. Name: Address: Phone: Web site: E-mail: Contact Person: Phone: E-mail: |
Federal Communications Commission FCC 445 12th St. SW Washington, D.C. 20554 888-225-5322 |
Name: FLORIDA GEOGRAPHIC DATA LIBRARY Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture Building PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html