API Ideas
At the FCC we are committed to opening our data. Share you thoughts and ideas on new data sets to unlock, and new web services the FCC should offer.
-
10 votes
-
Equipment Authorizations
Daily OET Equipment Authorizations should be available in different media including RSS feeds, and should distinguish between new grants and other actions.
7 votes -
Antenna Reception
I would like to be able to call your ota antenna reception database with coordinates, or additionally, and address/city and receive reception from the local ota stations, with details about those locations (location etc.).
5 votes -
Add full database dump to API?
Rather than hammer the API for all the broadband speed test results, it would be handy to have access to a complete dump of the entire database. (API or gzipped download of a snapshot) This would help people interesting in making heat maps of broadband rates across the US for example.
5 votes -
3 votes
-
Frequency Allocation Call
Add a call to the license view API that allows the user to query a frequency and get the owner of the license (or at least allocated use) for that frequency.
3 votes -
API to return Census Data
API to return Census Data for Lat/Long at the block tract county state level or national level. Different call parameters in the API to display different levels of detail/certain data.
3 votes -
Internet and cell phone usage
Have the ability to run reports by county on cell phone and internet usage.
3 votes -
3 votes
-
Documentation to the Equiptment Authorization API
Better documentation of the Equiptment Authorization API... And just about everything. Full data can only be found many wasteful HTTP calls as is documented via the source, but without proper documentation, it's impossible to find search restrictions.
3 votes -
F(50,50) calculus
a web service with the fm calculus of f(50,50)
3 votes -
Coverage Area Data
I would like to call an API by providing a callsign, and get a list of all the zipcodes that are reached by that stations broadcast signal. The zipcodes that are returned should have at least 90% strong signal coverage.
3 votes -
ability to submit phone number to do not call list
We need an API that accepts a phone number to add to the Do Not Call list. It would also be nice to be able to report offending telemarketers.
2 votes -
CDBS API
CDBS API
Provide an full API to the CDBS data. Given a call sign, I should be able to have engineering data, ownership information, call sign history, etc returned. An API would be a great adjunct to increasing documentation for the download of CDBS data.
2 votes -
FRN validation
Via web services api created to identify FRN(s) for given licensee. Should be able to send FRN or licensee name
receive back from FCC FRN and licensee name2 votes
