As part of the FCC’s Broadband Data Collection (BDC), service providers, governments, and other entities can submit bulk crowdsource information in response to the fixed broadband availability data reported by broadband providers. The FCC will use crowdsource data to verify and supplement the data published on the National Broadband Maps. For information on how crowdsource data differs from challenges, please see the “Differences between Bulk Fixed Availability Challenge Data and Crowdsource Data” article.
Submitting Bulk Crowdsource Data
All entities submitting bulk fixed crowdsource data must upload data files in the BDC system. More information about how to prepare these files is discussed in a separate article, “How to Format Bulk Fixed Challenge or Crowdsource Data.” The data files must identify the locations and provider that are the subject of the crowdsource data and the reason for the submission, using one of the reasons listed below:
- Provider failed to schedule a service installation within 10 business days of a request.
- Provider did not install the service at the agreed-upon time.
- Provider requested more than the standard installation fee to connect the location.
- Provider denied the request for service.
- Provider does not offer the technology at the location.
- Provider does not offer the speed(s) shown on the National Broadband Map for purchase at the location.
- The actual speed of the service does not match its advertised speed.
- No wireless or satellite signal is available at the location.
- New, non-standard equipment is required to connect the location.
- Missing provider.
Note that “the actual speed of the service does not match its advertised speed” is a reason that can be submitted for crowdsource data but not challenges. Filers interested in sharing speed test results should use this reason code.
Filers of bulk fixed crowdsource data may, but are not required to, provide evidence supporting the information in their submission.
Bulk Fixed Crowdsource Methodology
All entities submitting bulk fixed availability crowdsource data must enter information, in a web form in the BDC system, about the methodology used to collect their data. There are three options:
- Knowledge of Infrastructure. The information could be based on knowledge or observations of where network facilities and plant exist, such as on-the-ground examination of broadband infrastructure, building permits, or rights-of-way.
- Information Collected from Individual Consumers. This option would be based on information collected from individual consumers about their broadband service.
- Any methodology not based on the first two options. With this option, contact details must be provided for the individual associated with each challenge.
The fields that must be entered in the web form are listed in the table below. Note that if methodology is “Information Collected from Individual Consumers” or “Other,” then the contact information fields listed below are not collected via this form but will be collected in the upload file.
Knowledge of Infrastructure
The methodology and source of the information contained within the bulk fixed crowdsource data.
- Value must be one of the following:
• Knowledge of Infrastructure
• Information Collected from Individual Consumers
Narrative explanation of how the information contained within the bulk fixed crowdsource data was gathered.
- Value may be null if the methodology value is “Knowledge of Infrastructure”.
Full name of the contact associated with the bulk crowdsource data.
- If methodology value is “Information Collected from Individual Consumers,” then this value is not collected via this form but will be collected in the upload file.
Email address of the contact associated with the bulk crowdsource data.
- Value must match valid email address form if not null, e.g.: email@example.com.
Contact Phone Number
Phone number of the contact associated with the bulk crowdsource data.
- Value is optional and may be null.
- If entered, value must match valid US phone number format: 000-000-0000.