Skip Navigation

Federal Communications Commission

English Display Options

by: Wireline Competition Bureau

October 1, 2012 - 05:00 PM

Please provide comments to the issue below as part of the 2012 WCB cost model virtual workshop for inclusion in the record. Comments are moderated for conformity to the workshop’s guidelines.


Hybrid Cost Proxy Model: When adopting the HCPM, the Commission concluded that it should use geocode data to the extent available for determining customer locations. The Commission later affirmed this conclusion, but found that "no source of actual geocode data has yet been made adequately accessible for public review." The Commission expected that a source of accurate and verifiable actual geocode data would be identified in the future for use in calculating federal support.

In the absence of such data, the Commission used road network information as the basis for locating within a census block boundary customers whose precise locations were unknown. This approach entails associating customer locations with roads and excluding some road types or road segments (e.g., interstate highways, bridges, and on- and off-ramps) that are unlikely to be associated with customer locations. The Commission used an algorithm proposed by PNR Associates to distribute locations uniformly on road segments (based on Topologically Integrated Geographic Encoding and Referencing (TIGER) data). The PNR Associates' National Access Line Model is used to estimate the number of customer locations within census blocks and wire centers. The PNR Associates model's information sources include: survey information; the Local Exchange Routing Guide (LERG) database; Business Location Research (BLR) wire center boundaries; Dun & Bradstreet's business database; Metromail's residential database; Claritas's demographic database; and U.S. Census Bureau estimates.

CQBAT: The CQBAT model estimates the number of customer locations using multiple sources. These include obtaining the number of residential locations from commercial data (GeoLytics) and obtaining the number and distribution of business locations from commercial data (GeoResults). CQBAT also determines the type (SIC code) and size of businesses (used to estimate the bandwidth required at each location) from the US BLS Economic Census at the ZIP-code level, using the commercial data to distribute ZIP-level counts to census blocks. The model distributes locations randomly along roads, excluding some road types and road segments (e.g., interstate highways, bridges, and on- and off-ramps). CQBAT's approach to placing customer locations randomly along roads appears to be consistent with current best practice and represents an improvement relative to the HCPM. This distribution has the effect of putting more customer locations in areas with higher road density—i.e., more homes near a town grid and fewer along open rural roads. This approach is similar to the approach used in the Commission's Broadband Assessment Model, used during the National Broadband Plan, and to the approach used in the National Broadband Map (to estimate coverage in blocks greater than two square miles).

Questions for Comment

  1. Is there any reason to deviate from CQBAT's approach? Are there any improvements to this approach that would be beneficial to incorporate?
  2. An alternative approach is to determine customer locations by only using commercial data from GeoResults that provides actual and estimated customer locations. Does this approach offer any significant advantage over CQBAT's method?


Not seeing comment form in IE 8? Turn off IE compatibility mode to see comments.
Updated: February 22, 2013 - 03:06 PM
blog comments powered by Disqus

You are leaving the FCC website

You are about to leave the FCC website and visit a third-party, non-governmental website that the FCC does not maintain or control. The FCC does not endorse any product or service, and is not responsible for, nor can it guarantee the validity or timeliness of the content on the page you are about to visit. Additionally, the privacy policies of this third-party page may differ from those of the FCC.