If you really want to do something like this, here's a copy and paste from my notes file. Warning that the fcc_all.db is going to be huge so it's strongly recommended to only pull out one or two states of sites at a time.
0. data source is http://reboot.fcc.gov/license-view a. CSV and pipe delimited text files are linked on right side, along with data dictionary and data sample b. the CSV actual comma delimited text file is rather useless, because of the number of entity names and description fields that also contain commas. therefore we want to use the pipe delimited file. c. consult the data dictionary DOC file for a detailed description of all columns, this is provided on the license-view FCC ULS page. local copy here. [[File:Fcc-license-view-data-dictionary.doc|thumbnail]] 1. download fcc-license-view-data-pipe-delimited-format.zip , this file should be about 1.1GB zipped 2. unzip fcc-license-view-data-pipe-delimited-format.zip , the unzipped TXT file should be about 11GB 3. you should now have the file fcc_lic_vw_pipe.txt which is delimited using pipes 3b. use "pragma table_info(table_name); to see contents of table 4. create empty database with table fccinfo by doing the following: a. sqliteman b. create new file as fcc_all.db c. create table fccdata d. create 84 columns matching columns in header of fcc_lic_vw_pipe.txt file example of columns to create for FCC ULS: sqlite> .fullschema CREATE TABLE fccdata ( "license_id" INTEGER, "source_system" TEXT, "callsign" TEXT, "facility_id" INTEGER, "frn" INTEGER, "lic_name" TEXT, "common_name" TEXT, "radio_service_code" TEXT, "radio_service_desc" TEXT, "rollup_category_code" TEXT, "rollup_category_desc" TEXT, "grant_date" TEXT, "expired_date" TEXT, "cancellation_date" TEXT, "last_action_date" TEXT, "lic_status_code" TEXT, "lic_status_desc" TEXT, "rollup_status_code" TEXT, "rollup_status_desc" TEXT, "entity_type_code" TEXT, "entity_type_desc" TEXT, "rollup_entity_code" TEXT, "rollup_entity_desc" TEXT, "lic_address" TEXT, "lic_city" TEXT, "lic_state" TEXT, "lic_zip_code" INTEGER, "lic_attention_line" TEXT, "contact_company" TEXT, "contact_name" TEXT, "contact_title" TEXT, "contact_address1" TEXT, "contact_address2" TEXT, "contact_city" TEXT, "contact_state" TEXT, "contact_zip" INTEGER, "contact_country" TEXT, "contact_phone" TEXT, "contact_fax" TEXT, "contact_email" TEXT, "market_code" TEXT, "market_desc" TEXT, "channel_block" TEXT, "loc_type_code" TEXT, "loc_type_desc" TEXT, "loc_city" TEXT, "loc_county_code" TEXT, "loc_county_name" TEXT, "loc_state" TEXT, "loc_radius_op" TEXT, "loc_seq_id" TEXT, "loc_lat_deg" INTEGER, "loc_lat_min" INTEGER, "loc_lat_sec" INTEGER, "loc_lat_dir" TEXT, "loc_long_deg" INTEGER, "loc_long_min" INTEGER, "loc_long_sec" INTEGER, "loc_long_dir" TEXT, "hgt_structure" INTEGER, "asr_num" INTEGER, "antenna_id" TEXT, "ant_seq_id" TEXT, "ant_make" TEXT, "ant_model" TEXT, "ant_type_code" TEXT, "ant_type_desc" TEXT, "azimuth" INTEGER, "beamwidth" INTEGER, "polarization_code" TEXT, "frequency_id" TEXT, "freq_seq_id" TEXT, "freq_class_station_code" TEXT, "freq_class_station_desc" TEXT, "power_erp" TEXT, "power_output" TEXT, "frequency_assigned" INTEGER, "frequency_upper_band" INTEGER, "unit_of_measure" TEXT, "tolerance" INTEGER, "emission_id" TEXT, "emission_seq_id" TEXT, "emission_code" TEXT, "ground_elevation" INTEGER ); e. save empty template database as fcc_template.db f. keep fcc_template.db with all rows empty to use as a template for future imports, do not modify further 4b. if necessary, use sqliteman to edit the columns for the fcc_template.db fccdata table, ensuring that numeric-only columns are described as INTEGER 5a. copy the fcc_template.db file with empty 84 columns to new file fcc_all.db 5b. sqlite3 fcc_all.db a. .headers on b. .mode csv c. .separator | d. .show e. .import fcc_lic_vw_pipe.txt fccdata f. this will take CPU usage to 100% on one core and take a rather long time! the finished fcc_all.db file will be approximately 15GB in size or larger. g. .quit or you can do the above on one line for non-interactive import: sqlite3 -header -csv -separator '|' fcc_all.db '.import fcc_lic_vw_pipe.txt fccdata' On Thu, Aug 4, 2016 at 4:47 AM, Andreas Wiatowski <andr...@silowireless.com> wrote: > Does anyone know if there is an antenna/frequency database that I can > search for cellular frequencies and tower locations used…including antenna > down tilt and azimuth? > > I tried looking around the FCC databases but could not find one that gives > me that kind of information. > > Any help is appreciated. > > Cheers, > > Andreas Wiatowski, CEO > Silo Wireless Inc. > 519-449-5656 x-600 > >
