Home » Forum

CLOSED: FCC.gov/Developer - Data Quality


The reboot.fcc.gov project has ended. All related public feedback forums have been closed.*

Found an error in the data? Share issues of data quality to make our data sets more useful for the community

How can we improve FCC data quality?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Consumer Broadband Test API Wireline Data Issues

    For any lat/long search, data for these three attributes is not available:
    1) wirelineMaxDownload
    2) wirelineMaxUpload
    3) wirelineTests
    In spite of that, there is data for wirelineAvgDownload and wirelineAvgUpload.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. License View CSV File documentation, Header and Row Formats do not match

    The documentation (word) file that describes the format does not document several fields that are included in the header line of the CSV file. And there are 85 fields in the header (first line), but the remaining lines of CSV data have 89 elements!

    Given that I am attempting to write a parser for this CSV file this is causing me fits!

    Is there any way to clean up the documentation so that it matches the actual format, and maybe get the header line to match the actual body of the data since CSV is all about a 1-to-1 match…

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Full License View Data CSV format zip file may be corrupted

    The file "fcc-license-view-data-csv-format.zip" appears to be corrupted. It is not readable/decompressable on various machines running WIndows 7 and XP.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Petitions for Special Relief

    Public Notices listing petitions for special relief should be returned in FCC search results and the Report Nos. should be returned in an EDOCS search. The ability to locate such documents is important to due diligence research.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Database for abusive communications

    An e911 dataset should be compiled and maintained in database form, such that an abusive originating ID is associated with the victim's ID. The dataset can be related to case files for orders of protection. An e911 interface for reporting abusive SMS communications might also be helpful.

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

CLOSED: FCC.gov/Developer - Data Quality

Feedback and Knowledge Base