Once bulk Fabric challenges have been processed and resolved, challenge filers will be able to download a CSV file from the BDC system indicating how each challenge was addressed. Challenges that were accepted have been incorporated into the next version of the Fabric dataset.
The table below explains the fields in that data download.
Field |
Data Type |
Example |
Description / Notes |
submission |
String |
4e11b315-751a-4050-b51e-dd85c37d0861 |
Unique identifier for the bulk Fabric challenge data submission |
id |
Integer |
9991001 |
Unique identifier for the challenge |
file_status |
String |
Accepted |
Status of the submission in a (bulk challenge) |
file_record_status |
String |
Withdrawn |
Status of the individual challenge |
date_received |
Date |
2022-10-17 |
Date the submission was received |
fabric_vintage |
Date |
2022-06-30 |
As-of date associated with the Fabric that has been challenged. This information is part of the filed challenge |
contact_name |
String |
Jane Broadband |
The contact name included as part of the challenge submission |
contact_email |
String |
The contact email included as part of the challenge submission |
|
contact_phone |
String |
888-225-5322 |
The contact phone number included as part of the challenge submission |
category_code |
Integer |
3 |
The challenge type included as part of the challenge submission |
location_id |
Integer |
1357135307 |
The ID of the location challenged as part of the challenge submission.
|
address_primary |
String |
45 L St NE |
The address of the location challenged as part of the challenge submission.
|
city |
String |
Washington |
The city of the location challenged as part of the challenge submission.
|
state |
String {2} |
DC |
The state of the location challenged as part of the challenge submission.
|
zip_code |
String {5} |
20002 |
The ZIP code of the location challenged as part of the challenge submission.
|
zip_code_suffix |
String {4} |
|
Four-digit USPS ZIP+4 code suffix, if applicable, filed as part of the challenge submission.
|
unit_count |
Integer |
5 |
The number of units files as part of the challenge submission.
|
building_type_code |
Enumerated String {1} |
B |
The building type code filed as part of the challenge submission.
|
non_bsl_code |
String {1} |
C |
The building type code indicating a non-BSL filed as part of the challenge submission. - -
|
bsl_lacks_address_flag |
Boolean integer |
1 |
Indicator that a BSL lacks an address, filed as part of the challenge submission.
|
latitude |
Decimal (10.7) |
38.903693 |
The latitude of a challenge, filed as part of the challenge submission.
|
longitude |
Decimal (10.7) |
-77.009682 |
The longitude of a challenge, filed as part of the challenge submission.
|
response_code |
Integer |
1 |
The disposition of each individual challenge. Value will be one of the following codes: 0 – Pending 1 – Accepted 2 – Rejected (insufficient evidence) 3 – Rejected (invalid challenge) |
status_desc |
String |
Accepted |
The disposition of each individual challenge. Value will be one of the following codes: Pending Accepted Rejected (insufficient evidence) Rejected (invalid challenge) Withdrawn [if the filer has withdrawn the submission] |
location_id_response |
Integer |
1357135307
|
The Fabric ID of a successful type 1 challenge to be included in the next version of the Fabric.
|
response_description_code |
Float |
1.0 |
A code indicating the reason for the adjudication of each individual challenge. Value will be one of the codes listed in the table below. |
response_description_code_desc |
String |
Challenge Accepted |
A description of the response_description_code value, explained in the table below. If a challenge was not accepted, then it was not incorporated in the next version of the Fabric for the reason provided. |
response_description |
String |
|
Free text field for conveying additional information, if applicable. |
response_description_code |
response_description_code_desc |
Resolution Codes for Category 1 Challenges (Missing Broadband Serviceable Location) |
1.0 |
The FCC has accepted the challenge. |
1.1 |
The address provided for the challenge is a duplicate. |
1.2 |
The address provided for the challenge could not be validated. |
1.3 |
The geographic coordinates for the challenge intersect with the footprint of an existing BSL. |
1.4 |
The challenge impermissibly attempts to add another BSL within an "entity”boundary. |
1.5 |
The challenge failed following manual review. |
1.6 |
The challenge duplicated a previously accepted challenge. |
1.7 |
The challenge attempted to add another BSL to a single-location parcel inconsistent with the FCC definition of a BSL. |
1.8 |
The geographic coordinates provided with the challenge are not valid. |
1.9 |
The challenge duplicates key fields from another challenge. |
1.11 |
The challenge duplicates key fields from another challenge. |
1.12 |
The challenge failed following manual review. |
1.21 |
The challenge was withdrawn. |
1.22 |
The challenge was rejected per staff adjudication. |
1.23 |
The challenge was overtaken by new data as reflected in updated Fabric. |
Resolution Codes for Category 2 Challenges (Incorrect Primary Address) |
2.0 |
The FCC has accepted the challenge. |
2.1 |
The address provided for the challenge is a duplicate of an address included in the Fabric data. |
2.2 |
The address provided for the challenge could not be validated. |
2.5 |
The challenge failed following manual review. |
2.6 |
The challenge duplicated a previously accepted challenge. |
2.21 |
The challenge was withdrawn. |
2.22 |
The challenge was rejected per staff adjudication. |
2.23 |
The challenge was overtaken by new data as reflected in updated Fabric. |
Resolution Codes for Category 3 Challenges (Incorrect Unit Count) |
3.0 |
The FCC has accepted the challenge. |
3.1 |
The challenge impermissibly attempted to change the unit count for a non-BSL or location within an “entity”boundary. |
3.2 |
The unit count provided for the challenged location exceeds expectations. |
3.3 |
The FCC has accepted the challenge but capped the unit count increase at “5.” |
3.5 |
The challenge failed following manual review. |
3.6 |
The challenge duplicated a previously accepted challenge. |
3.21 |
The challenge was withdrawn. |
3.22 |
The challenge was rejected per staff adjudication. |
3.23 |
The challenge was overtaken by new data as reflected in updated Fabric. |
Resolution Codes for Category 4 Challenges (Incorrect Building Type Code) |
4.0 |
The FCC has accepted the challenge. |
4.1 |
The challenge impermissibly attempted to change the building type code for a location within an “entity”boundary. |
4.5 |
The challenge failed following manual review. |
4.6 |
The challenge duplicated a previously accepted challenge. |
4.21 |
The challenge was withdrawn. |
4.22 |
The challenge was rejected per staff adjudication. |
4.23 |
The challenge was overtaken by new data as reflected in updated Fabric. |
Resolution Codes for Category 5 Challenges (Location Not Within Footprint of the Correct Building) |
5.0 |
The FCC has accepted the challenge. |
5.1 |
The challenge impermissibly attempted to change the geographic coordinates for a location within an “entity”boundary. |
5.2 |
The challenge impermissibly attempted to move the challenged location outside of the parcel boundaries for the Fabric record. |
5.3 |
The challenge impermissibly attempted to move the challenged location to an existing Fabric record. |
5.5 |
The challenge failed following manual review. |
5.6 |
The challenge duplicated a previously accepted challenge. |
5.21 |
The challenge was withdrawn. |
5.22 |
The challenge was rejected per staff adjudication. |
5.23 |
The challenge was overtaken by new data as reflected in updated Fabric. |
Resolution Codes for Category6 Challenges (Location Is Not Broadband Serviceable) |
6.0 |
The FCC has accepted the challenge. |
6.1 |
The challenge impermissibly attempted to updates the status of a location within an “entity”boundary. |
6.5 |
The challenge failed following manual review. |
6.6 |
The challenge duplicated a previously accepted challenge. |
6.7 |
The challenge failed following manual review. |
6.21 |
The challenge was withdrawn. |
6.22 |
The challenge was rejected per staff adjudication. |
6.23 |
The challenge was overtaken by new data as reflected in updated Fabric. |
Resolution Codes for Category7 Challenges (Add Supplemental Address) |
7.0 |
The FCC has accepted the challenge. |
7.1 |
The address provided for the challenge is a duplicate of an address included in the Fabric data. |
7.2 |
The address provided for the challenge could not be validated. |
7.5 |
The challenge failed following manual review. |
7.6 |
The challenge duplicated a previously accepted challenge. |
7.21 |
The challenge was withdrawn. |
7.22 |
The challenge was rejected per staff adjudication. |
7.23 |
The challenge was overtaken by new data as reflected in updated Fabric. |