Challenge Resolution Information for Bulk Fabric Challengers

Once bulk Fabric challenges have been reviewed, processed, and resolved, the challenge results will be provided in the BDC system for challenge filers as downloadable CSV files. The CSV files include a response code field, indicating how each challenge included in that batch of results was addressed. Further information about the response codes, including detailed descriptions about each code, can be found at Fabric Challenge Response Codes.

Results of challenges that are accepted will be posted around the time an updated Fabric version is released to Fabric licensees, typically every June and December, and those results will be incorporated into that next version of the Fabric dataset.

Results reflecting a Fabric challenge that has been rejected may be provided earlier in the process, before the next version of the Fabric is released. Parties can refile a challenge if they wish using a different challenge type or submitting other information in their file upload.

See How to Submit a Successful Bulk Fabric Challenge and the correct challenge types to use when submitting a challenge.

The table below explains the fields in the Fabric challenge results 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

jane.broadband@fcc.gov

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.

  • Note: this may be null for some challenge types.

address_primary

String

45 L St NE

The address of the location challenged as part of the challenge submission.

  • Note: this may be null for challenge type or if the bsl_lacks_address_flag = 1.

city

String

Washington

The city of the location challenged as part of the challenge submission.

  • Note: this may be null for some challenge types.

state

String {2}

DC

The state of the location challenged as part of the challenge submission.

  • Note: this may be null for some challenge types.

zip_code

String {5}

20002

The ZIP code of the location challenged as part of the challenge submission.

  • Note: this may be null for some challenge types.

zip_code_suffix

String {4}

 

Four-digit USPS ZIP+4 code suffix, if applicable, filed as part of the challenge submission.

  • Note: this may be null for some challenge types.

unit_count

Integer

5

The number of units files as part of the challenge submission.

  • Note: this may be null for some challenge types.

building_type_code

Enumerated String {1}

B

The building type code filed as part of the challenge submission.

  • Note: this may be null for some challenge types.

non_bsl_code

String {1}

C

The building type code indicating a non-BSL filed as part of the challenge submission. - -

  • Note: this may be null for some challenge types.

bsl_lacks_address_flag

Boolean integer

1

Indicator that a BSL lacks an address, filed as part of the challenge submission.

  • Note: this may be null for some challenge types.

latitude

Decimal (10.7)

38.903693

The latitude of a challenge, filed as part of the challenge submission.

  • Note: this may be null for some challenge types.

longitude

Decimal (10.7)

-77.009682

The longitude of a challenge, filed as part of the challenge submission.

  • Note: this may be null for some challenge types.

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

Description of 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.

  • Note: this may be null for some challenge types or for challenges that are not accepted .

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 Fabric Challenge Response Codes.

response_description_code_desc

String

Challenge Accepted

A description of the response_description_code value, explained in the Fabric Challenge Response Codes

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.

Further information, including detailed descriptions about each code, can be found in the Fabric Challenge Response Codes.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

Video Resources
Key Reference Documents
BDC User Guide and Data Specifications
Form 477 Resources
Get Help