Layer: FCC Official BSL BDC Service BEAD Deduplicated View (ID: 0)

Name: FCC Official BSL BDC Service BEAD Deduplicated View

Display Field: bdc_brand_name

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV>Details:Coordinate System – WGS84 (WKID: 4326)Update Frequency – Data is updated as frequently as new data is made available to the New Mexico Office of Broadband Access and Expansion. At minimum, the data will be updated as new BSL/NoBSL Fabric and BDC Service Provider information is published.This dataset is hosted in an OBAE-hosted SQL Server, published via a local ArcGIS Enterprise Instance, that is shared with ArcGIS Online via an ArcGIS Enterprise “Collaboration”Data Custodian: Kevin Hoffman (<A href="mailto:kevin.hoffman.contractor@doit.nm.gov" STYLE="text-decoration:underline;">kevin.hoffman.contractor@doit.nm.gov</A>)Access Use Constraints: Data is not intended for editing; updates to this dataset will be made internally by OBAE staff.Data is intended for specific users and not the general public. OBAE staff will grant permissions to users/groups as needed. Methodology:FCC BSL/NoBSL data is downloaded in CSV format. The CSVs are merged into a single table and converted to spatial data using the latitude/longitude values within. Each row in this merged table represents a single BSL/NoBSL location.BDC Provider Service Availability data is downloaded one technology type at a time in CSV format. Each entry in the BDC Provider Service Availability dataset corresponds to a single BSL or NoBSL location (joined using the location_id attribute). These individual tables are then merged into a single table. To determine the best-available technology at a given location (as there may be multiple technology types available at a single location), each BDC entry was ranked based on the technology type:<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Copper Wire, rank of 1</LI><LI>Licensed Terrestrial Fixed Wireless, rank of 2</LI><LI>Licensed-by-Rule Terrestrial Fixed Wireless, rank of 2</LI><LI>Coaxial Cable / HFC, rank of 3</LI><LI>Optical Carrier Fiber to Premises, rank of 4</LI></UL>BDC technology service availability is also ranked as Served/Underserved/Unserved based on the following criteria (<A href="https://broadbandusa.ntia.doc.gov/sites/default/files/2022-09/BEAD-Frequently-Asked-Questions-%28FAQs%29_Version-2.0.pdf" STYLE="text-decoration:underline;">https://broadbandusa.ntia.doc.gov/sites/default/files/2022-09/BEAD-Frequently-Asked-Questions-%28FAQs%29_Version-2.0.pdf</A>, also available <A href="https://nm-community.maps.arcgis.com/home/item.html?id=5f47e138e8194bb1aa1562f9886315ed" STYLE="text-decoration:underline;">here</A>):<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Unserved locations either have no access to broadband service or lack access to "(i) a speed of not less than 25 Mbps for downloads; and (ii) a speed of not less than 3 Mbps for uploads"</LI><LI>Underserved locations lack access to "(i) a speed of not less than 100 Mbps for downloads; and (ii) a speed of not less than 20 Mbps for uploads"</LI><LI>Served locations have access to speeds exceeding these thresholds (100Mbps Download/20Mbps Upload)</LI></UL>Once these rankings are tagged to rows in the merged BDC Technology table, the records are loaded into a database and a database-view is created to discern the best-available technology at a given location based [first] on the service availability (Served, Underserved, Unserved). This is the composition of that database-view:SELECT * FROM ( SELECT a.frn, a.provider_id, a.brand_name, a.location_id, a.technology, a.max_advertised_download_speed, a.max_advertised_upload_speed, a.low_latency, a.business_residential_code, a.id_for_rank, a.service_level, a.tech_level, rank() OVER ( PARTITION BY a.location_id ORDER BY a.service_level DESC, a.tech_level DESC, a.max_advertised_download_speed DESC, a.max_advertised_upload_speed DESC, a.id_for_rank ASC ) AS rank FROM <BDC_TECH_TABLE_MERGED> a ) b WHERE b.rank = 1;Using this database-view, the best-available technology data for a given location is joined to the BSL/NoBSL fabric based on a shared location_id.NTIA/FCC location challenge adjudications correspond to the BSL/NoBSL FCC Fabrics of 6/30/20222 and 12/31/2022. Challenges were submitted to FCC/NTIA on 12/23/2022 and 3/16/2023, respectively. If there were multiple responses that corresponded to a single Location ID, the most relevant response was included in this dataset. The most relevant response was then joined to the BSL/NoBSL and BDC Technology information.For BSL locations that do not have corresponding BDC Technology information:<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>If the BSL was in the previous fabric release, and there is still no BDC match (under normal circumstances, providers will have 6 months to provide this data in time for the next BSL/NoBSL fabric release), it is assumed the provider has had a chance to claim service for this point, but did not. Therefore, we deem these points “Unserved”.</LI><LI>If the BSL was not in the previous fabric release, we consider the location new (meaning providers have not had a chance to claim service), we do a spatial inference using FCC Hex shapes. Anything outside those hexes would be deemed “Unserved”.</LI></UL>For NoBSL locations that do not have corresponding BDC Technology information:<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>No spatial-inferences or assumptions are made of the data. Because many bsl_flag=false (aka NoBSL) locations will not subscribe to Mass Market internet, locations without matching BDC Technology data are labeled with an availability_status of “Enterprise (Non-BSL)”</LI></UL>Spatial Inference process Description:Service availability status was set via a modified Nearest Neighbor type analysis. A summary analysis of service availability per H3 hexagon (iterated at the hex 9 - hex 6 levels) was used to impute estimated service levels to locations without a BDC Technology match.For those BSLs with a BDC Technology match, Each hexagon in the state was assigned a number of Served/Underserved/Unserved BSLs within it by service type using the ArcGIS Pro “Summarize Within” tool.Once the mean service level was determined for a given hex polygon, that value could be spatially joined to the challenge points as estimated service levels. For example, if a hexagon had 100 BSLs in it, and 80 of these were Served, 12 were Underserved, and 8 were unserved, the mean service level (as an integer value) would be 2.72, the majority would be 3, and the challenge BSL point would be assigned an availability status of "Served". Means were rounded to the nearest integer. Because many 'New BSLs' did not intersect with smaller hexagons containing valid BSLs, hexagon levels were iterated through until the hex6 level to capture wider areas of interest. Where challenge points did not intersect such hexagons, they were assigned an availability_status of "Unserved" because they are estimated to be too far from any existing service claims.Attributes:Attribute fields with a preface of “bsl_” come from the FCC Broadband Serviceable Fabric <A href="https://help.bdc.fcc.gov/hc/en-us/articles/5375384069659-What-is-the-Location-Fabric-" STYLE="text-decoration:underline;">What is the Location Fabric? – BDC Help Center (fcc.gov)</A>. The acronym “BSL” stands for “Broadband Serviceable Location”. The data dictionary for the dataset is accessible <A href="https://nm-community.maps.arcgis.com/home/item.html?id=ba906272c5ba4c66a53e57439d48e6cc" STYLE="text-decoration:underline;">here</A>.Attribute fields with a preface of “bdc_” come from the Broadband Data Collection Provider Availability dataset download available here - <A href="https://broadbandmap.fcc.gov/data-download/nationwide-data" STYLE="text-decoration:underline;">https://broadbandmap.fcc.gov/data-download/nationwide-data</A>Attribute fields with a preface of “fccresponse_” come from the FCC/NTIA Location Challenge adjudications that correspond to the BSL/NoBSL FCC Fabrics of 6/30/20222 and 12/31/2022. location_id - BSL Fabric Schema - Unique ID for the Fabric location. bsl_address_primary - BSL Fabric Schema - Postal addressbsl_city - BSL Fabric Schema - Postal address city namebsl_state - BSL Fabric Schema - 2 digit state abbreviationbsl_zip - BSL Fabric Schema - 5 digit zip codebsl_zip_suffix - BSL Fabric Schema - 4 digit zip+4 suffixbsl_unit_count - BSL Fabric Schema - An estimate of the number of residential, nonresidential units within the location. In the case of Community Anchor Institutions and Group Quarters, there is an indication of the presence of CAI or Group Quarters structure.bsl_flag - BSL Fabric Schema - an indication of whether the Fabric Record is a BSL (1 - TRUE or Not 0 - FALSE)bsl_building_type_code - BSL Fabric Schema - Indicates if the record is considered residential (R), nonresidential (B) mixed (X), Group Quarters (G), Community Anchor Institution (C), Enterprise (E) or Other (O)bsl_land_use_code - BSL Fabric Schema - A modeled land use designation estimated from assembled county assessor information (see domain)bsl_address_confidence_code - BSL Fabric Schema - A code indicating the confidence in the association of the textual address with the BSL.bsl_county_geoid - BSL Fabric Schema - 5 digit TIGER 2020 identifier for countybsl_block_geoid - BSL Fabric Schema - 15 digit 2020 Census FIPS code for census blockbsl_latitude - BSL Fabric Schema - Latitude of locationbsl_longitude - BSL Fabric Schema - Longitude of locationbsl_h3index_hex9 - BSL Fabric Schema - A reference to the H3 hex cell I.D., level 9bsl_h3index_hex8 - BSL Fabric Schema - A reference to the H3 hex cell I.D., level 8bsl_h3index_hex7 - BSL Fabric Schema - A reference to the H3 hex cell I.D., level 7bsl_h3index_hex6 - BSL Fabric Schema - A reference to the H3 hex cell I.D., level 6bsl_fabric_version - Indicates the latest version of the BSL Fabric in which the point is represented. Generally, 12312022_ver1bsl_in_previous_fabric- date release of FCC Fabricbdc_frn – 10-digit FCC Registration Number (FRN) of the entity that submitted the databdc_provider_id – Unique identifier for the fixed service providerbdc_brand_name – Name of the entity or service advertised or offered to consumersbdc_technology_code – Code for the technology used for the deployed servicebdc_technology – Text description of technologybdc_max_advertised_down_speed – Maximum advertised download speed offered at the location in MBPSbdc_max_advertised_upload_speed – Maximum advertised upload speed associated with the maximum advertised download speed offered at the location in MBPSbdc_low_latency – Boolean integer flag indicating whether or not the offered service is low latency, defined as having round-trip latency of less than or equal to 100 MS based on the 95th percentile of measurements (0 – False, 1 – True)bdc_business_residential_code – Enumerated character identifying whether the service at the location is offered only to business customers, or to both business and residential customers. Value is one of the following codes (B – business-only location, R – residential-only location, X – business and residential locationfccresponse_ref_id - Unique identifier for the bulk Fabric challenge data submission for pointfccresponse_file_status – Indicator of whether the submitted challenge file was accepted by the FCC/NTIAfccresponse_file_record_status – Indicator of the record file status with FCC/NTIAfccresponse_date_received - Date the location challenge submission was receivedfccresponse_fabric_vintage - As-of date associated with the Fabric that has been challenged. This information is part of the filed challengefccresponse_category_code - The challenge type included as part of the challenge submissionfccresponse_response_code – The NTIA/FCC Response Codefccresponse_status_desc – Text description of fccresponse_response_codefccresponse_location_id - Unique identifier for the challenged locationfccresponse_description_code - A code indicating the reason for the adjudication of each individual challengefccresponse_desc_code_desc - A description of the response_description_code valuefccresponse_description - Free text field for conveying additional information, if applicableavailability_code – number value that corresponds to availability_status. 1 = Unserved, 2 = Underserved, 3 = Servedavailability_status_source - Indicator of the source for availability status. availability_status – Broadband service availability, based on thresholds defined by the FCC<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Unserved locations either have no access to broadband service or lack access to "(i) a speed of not less than 25 Mbps for downloads; and (ii) a speed of not less than 3 Mbps for uploads"</LI><LI>Underserved locations lack access to "(i) a speed of not less than 100 Mbps for downloads; and (ii) a speed of not less than 20 Mbps for uploads"</LI><LI>Served locations have access to speeds exceeding these thresholds (100Mbps Download/20Mbps Upload)</LI></UL></DIV></DIV></DIV>

Service Item Id: c87cd5f03bfc4c70acf27ade2456631d

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

Drawing Info:

Renderer:

Unique Value Renderer:

Field 1:

Field 2:

Field 3:

Field Delimiter:

Default Symbol:

N/A

Default Label:

UniqueValueInfos:

Value: Unserved
Label: Unserved
Description: N/A
Symbol:
Value: Underserved
Label: Underserved
Description: N/A
Symbol:
Value: Served
Label: Served
Description: N/A
Symbol:

Transparency:

Labeling Info:

Advanced Query Capabilities:

HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

bsl_flag ( type: esriFieldTypeString, alias: BSL Flag, length: 1073741822 )
bsl_fabric_version ( type: esriFieldTypeString, alias: BSL Fabric Version, length: 255 )
bdc_brand_name ( type: esriFieldTypeString, alias: BDC Brand Name, length: 1073741822 )
bdc_technology ( type: esriFieldTypeString, alias: BDC Technology, length: 255 )
bead_service_status ( type: esriFieldTypeString, alias: BEAD Service Status, length: 50 )
deduplication_status ( type: esriFieldTypeString, alias: Deduplication Status, length: 50 )
OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )

Supported Operations: Query Query Attachments Query Analytic Generate Renderer Return Updates

Iteminfo Thumbnail Metadata