North Dakota Exchange Boundaries

SDE Feature Class

Tags
boundaries, exchange, telco, communication, utilitiesCommunication, carriers

Description

Exchange boundary information was requested from all North Dakota Incumbent Local Exchange Carriers (ILECs). Thirty-two ILECs submitted data for 302 exchanges in North Dakota.


Summary

The North Dakota Public Service Commission collected boundary data including all applicable attribute information as outlined by the FCC on behalf of the incumbent Local Exchange Carriers operating in the state. 

Credits

Information Technology Department, Public Service Commission, State of North Dakota

Use limitations

The State of North Dakota has compiled this data according to conventional cartographic standards, using what is thought to be the most reliable information available. This data is intended to make results of research available at the earliest possible date, but is not intended to constitute final or formal publication. The State of North Dakota makes every effort to provide virus-free files but does not guarantee uncorrupted files. The State of North Dakota does not guarantee this data to be free from errors, inaccuracies, or viruses, and disclaims any responsibility or liability for interpretations or decisions based on this data.

Scale Range

Metadata 

Topics and Keywords 

Themes or categories of the resource  boundaries, utilitiesCommunication


*Content type  Downloadable Data

Citation 

Title North Dakota Exchange Boundaries
Creation date 2013-05-24 00:00:00


Presentation formats* digital map


Citation Contacts 

Responsible party
Individual's name Travis Durick
Organization's name Information Technology Department, State of North Dakota
Contact's position Broadband Technology Manager
Contact's role  point of contact


Contact information
Phone
Voice 701-328-1125

Address
Type
e-mail addresstdurick@nd.gov



Resource Details 

Dataset languages* English (UNITED STATES)
Dataset character set  utf8 - 8 bit UCS Transfer Format


Spatial representation type* vector


Supplemental information
The North Dakota Public Service Commission collected boundary data including all applicable attribute information as outlined by the FCC on behalf of the incumbent Local Exchange Carriers operating in the state. 

*Processing environment Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.3.1.4959


Credits
Information Technology Department, Public Service Commission, State of North Dakota


Extents 

Extent
Geographic extent
Bounding rectangle
Extent type  Extent used for searching
*West longitude -104.050040
*East longitude -96.554411
*North latitude 49.000692
*South latitude 45.935072
*Extent contains the resource Yes

Extent in the item's coordinate system
*West longitude -104.050040
*East longitude -96.554411
*South latitude 45.935072
*North latitude 49.000692
*Extent contains the resource Yes

Resource Points of Contact 

Point of contact
Individual's name Travis Durick
Organization's name Information Technology Department, State of North Dakota
Contact's position Broadband Technology Manager
Contact's role  point of contact


Contact information
Phone
Voice 701-328-1125

Address
Type
e-mail addresstdurick@nd.gov



Resource Constraints 

Constraints
Limitations of use

The State of North Dakota has compiled this data according to conventional cartographic standards, using what is thought to be the most reliable information available. This data is intended to make results of research available at the earliest possible date, but is not intended to constitute final or formal publication. The State of North Dakota makes every effort to provide virus-free files but does not guarantee uncorrupted files. The State of North Dakota does not guarantee this data to be free from errors, inaccuracies, or viruses, and disclaims any responsibility or liability for interpretations or decisions based on this data.


Spatial Reference 

ArcGIS coordinate system
*Type Geographic
*Geographic coordinate reference GCS_North_American_1983
*Coordinate reference details
Geographic coordinate system
Well-known identifier 4269
X origin -399.99999999883602
Y origin -399.99999999883602
XY scale 858993458
Z origin 0
Z scale 1
M origin 0
M scale 1
XY tolerance 9.3132257591652096e-009
Z tolerance 1.3038516062831299e-005
M tolerance 1.9999999999999998e-005
High precision true
Left longitude -180
Latest well-known identifier 4269
Well-known text GEOGCS["GCS_North_American_1983", DATUM["D_North_American_1983", SPHEROID["GRS_1980", 6378137.0, 298.257222101]], PRIMEM["Greenwich", 0.0], UNIT["Degree", 0.0174532925199433], AUTHORITY["EPSG", 4269]]

Reference system identifier
*Value 4269
*Codespace EPSG
*Version 8.6.2


Spatial Data Properties 

Vector
*Level of topology for this dataset  geometry only


Geometric objects
Feature class name NDHUB.TelecomExchangeBoundaries
*Object type  composite
*Object count 302



ArcGIS Feature Class Properties
Feature class name NDHUB.TelecomExchangeBoundaries
*Feature type Simple
*Geometry type Polygon
*Has topology FALSE
*Feature count 302
*Spatial index TRUE
*Linear referencing FALSE



Lineage 

Lineage statement
The North Dakota Public Service Commission collected boundary data including all applicable attribute information as outlined by the FCC on behalf of the Incumbent Local Exchange Carriers (ILECs) operating in the state.  Exchange boundary information was requested from all North Dakota ILECs. Thirty-two ILECs submitted data for 302 exchanges in North Dakota.  

Process step
Description
The workflow and methods used include the following.

Existing exchange boundary information was requested of all North Dakota ILECs in the following order of preference by data type: GIS shapefile or feature class, AutoCAD drawing, digital map, or scanned image of a paper map(s).  Upon receipt each ILEC submitted dataset was converted to a common format (Esri feature class) and projected coordinate system (NAD83 North Dakota South State Plane Coordinate System Feet (FIPS 3302)).  Following the initial data conversion two separate but simultaneous processes occurred with each ILEC dataset; the first involved the adjustment of internal exchange lines to a set of common base layers, the second process entailed the resolution of discrepancies between shared ILEC study area boundaries.  

In order to comply with the FCC request that study area boundaries and exchanges conform to a scale of 1:24,000, the collected exchange boundary lines were adjusted to one of the following data sources (listed in the order of priority and precedence): 1) North Dakota State Boundary via US Census Bureau – All exchanges existing within the state were clipped or adjusted to this layer regardless of overlap into an adjoining state; 2) Bureau of Land Management (BLM) Cadastral National Spatial Data Infrastructure (CadNSDI) Quarter-Quarter Sections – This layer was the primary layer for the exchange boundary line adjustment.  In areas where the CadNSDI was not complete (eastern portion of North Dakota) the BLM alternative sources of the PLSS (where BLM is the data steward or the data is from a BLM trusted source) were used. Wherever the CadNSDI did not exist and sections were the smallest alternative PLSS features available, quarter-quarter sections were mathematically derived, measured equally in a section from the section corner mid-point; 3) County lines – Exchange boundaries were only adjusted to this layer when they were coincident with or followed water features that the ILECS indicated as boundary lines for an Exchange; 4) National Hydrography Dataset (NHD) Flowlines - Exchange boundaries were adjusted to follow this layer when ILECS indicated they were boundary lines.

A preliminary review of the exchange boundary lines indicated that the vast majority of the data followed a version of the public land survey system (PLSS).  Therefore the first step in the adjustment process was to snap all of the exchange boundary lines to the CadNSDI quarter-quarter section lines.  This process was completed using the Esri ArcGIS Snap tool with a tolerance of 700 feet (approximately half of the distance between a typical quarter-quarter section). A systematic review of the adjusted data was conducted to ensure that all lines followed the appropriate quarter-quarter section.  Areas where the exchange boundaries followed water features were snapped to county lines or NHD flowlines where county lines were not present.  Diagonal lines that traversed more than a quarter-quarter section were left intact only snapping the end points of the line to the CadNSDI.

In order to integrate all of the exchanges from 32 individual ILECs into a seamless state-wide dataset, over 70 web-enabled conference calls were conducted between provider pairs (a pair defined as two ILECs who share a portion of a common study area boundary) to collaboratively review maps and resolve and document  boundary overlaps, void areas, or disputes along common study area boundaries.  Following the initial data conversion outlined above, shared ILEC study area boundaries were identified and review maps were generated including reference layers (CadNSDI and water features) at a scale of 1:63,360.  Approximately 670 review maps were returned to contiguous ILECs and the PSC. When necessary additional web-enabled conference calls were conducted between each ILEC pair to resolve and correct boundary overlaps, void areas, or disputes using the same authoritative base layers and precedence rules described above.

The  agreed upon shared study area boundaries were digitized from the maps marked up in the web-enabled conference calls in Esri ArcGIS, snapping to the authoritative source layers.  Following multiple quality assurance checks, agreed upon study area boundaries were integrated with the ILECs adjusted internal exchange lines.  Polygons of the new exchanges were generated and attributed with the required information once all of the shared study area boundaries were completed.  With all provider data mapped to a common set of base layers and study area boundaries agreed upon with neighboring ILECs, the polygons were checked for topology errors (no gaps and no overlaps) and corrected when necessary. Minor topology rule violations caused by the authoritative source layer adjustment process were resolved, and the topology check repeated.

Final review maps of the 302 exchanges in the state were created and sent to the individual ILECs for their review.  A statement of certification was requested from a designated individual for each ILEC using language from the FCC order.  Final methodology documentation, metadata and feature level metadata for any remaining unresolved discrepancies was prepared. All FCC required attributes, shapefiles and csv files were prepared for review and certification by the North Dakota Public Service Commission for the FCC submission.

Following the collaborative web-enabled conference calls no study areas included overlaps between contiguous ILECs.  The only void area in the state is in T134N R106W, and portions of T134N R105W and T133N R106W, approximately 48 square miles on the Montana/North Dakota border.   Midstate Communications Inc., Consolidated Telcom, and Mid-Rivers Telephone Cooperative, Inc.confirmed via email that no ILEC wanted to claim this void area.  There are no structures, roads or subscribers in this area and it is remote, generally inaccessible public land.

Coincident with the exchange boundary mapping, spreadsheets were emailed to each ILEC to collect attribute information to populate the shapefile database and the associated comma delimited csv file.  Follow up calls and emails were made with ILECs when incomplete results or known discrepancies were found in the spreadsheets.  The results were recorded in a common database.  There was widespread confusion on the question of which Exchanges were considered “frozen” and subject to 54.305.  After consultation via phone and email with representatives at the FCC, we compared data returned by ILECs with two spreadsheets provided by the FCC at http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/usf12r11.zip.   After further communication with each ILEC listed in the spreadsheets as having a study area likely having one or more frozen exchanges, our procedure was to include FROZEN = “N” in the shapefile database for all exchanges, with the following exceptions:  1) When an ILEC acquired an exchange, and they were listed on either of two spreadsheets provided by the FCC indicating they most likely had a study area with an acquisition that was frozen and the ILEC confirmed which exchanges were frozen; or 2) When an ILEC submitted a FROZEN = “Y” and confirmed after we double checked and explained the contents of these spreadsheets and the FCC clarification.  

Those ILECS who indicated to us that they have an acquired exchange that may have been frozen at some point in the past, but they are not aware that it was “frozen” in the context of 54.305, are included in the following list (the majority of these were acquisitions from US West in the 1980s):

SAC, Exchange, ILEC Name
381607, Consolidated Telcom, Bowman
381607, Consolidated Telcom, Hettinger
381607, Consolidated Telcom, Killdeer
381607, Consolidated Telcom, Mott
381607, Consolidated Telcom, New England
381615, Griggs County Telephone Co, Finley
381622, Griggs County Telephone Co, Sheldon
381632, Reservation Telephone Cooperative, Garrison
381632, Reservation Telephone Cooperative, Kenmare
381632, Reservation Telephone Cooperative, Max
381637, West River Telecommunications Cooperative, Elgin
381637, West River Telecommunications Cooperative, Hebron





Distribution 

Distribution format
*Name SDE Feature Class


Transfer options
*Transfer size 3.008


Fields 

Details for object NDHUB.TelecomExchangeBoundaries 
*Type Feature Class
*Row count 302


Field OBJECTID
 
*Alias OBJECTID
*Data type OID
*Width 4
*Precision 10
*Scale 0
*Field description
Internal feature number.

*Description source
ESRI

*Description of values
Sequential unique whole numbers that are automatically generated.





Field Shape
 
*Alias SHAPE
*Data type Geometry
*Width 4
*Precision 0
*Scale 0
*Field description
Feature geometry.

*Description source
ESRI

*Description of values
Coordinates defining the features.





Field Id
 
*Alias ID
*Data type Integer
*Width 4
*Precision 9
*Scale 0
Field description
A virtual column created by ArcGIS to guarantee that each record has at least one unique value.



Field OCN
 
*Alias OCN
*Data type String
*Width 4
*Precision 0
*Scale 0
Field description
The four digit NECA Operating Company Number associated with the polygon.



Field CO_NAME
 
*Alias CO_NAME
*Data type String
*Width 254
*Precision 0
*Scale 0
Field description
The company name associated with the polygon. The preferred format for this field is Title Case.



Field EXCHANGE
 
*Alias EXCHANGE
*Data type String
*Width 254
*Precision 0
*Scale 0
Field description
The exchange name associated with the polygon. The preferred format for this field is Title Case. If submitting wire center boundaries, or if the polygon represents the study area boundary only, this field may be left blank.



Field WIRECENTER
 
*Alias WIRECENTER
*Data type String
*Width 8
*Precision 0
*Scale 0
Field description
The eight character CLLI code associated with the polygon. If submitting exchange boundaries, or if the polygon represents the study area boundary only, this field may be left blank.



Field SAC
 
*Alias SAC
*Data type String
*Width 6
*Precision 0
*Scale 0
Field description
The six digit Study Area Code associated with the polygon.



Field STATE
 
*Alias STATE
*Data type String
*Width 2
*Precision 0
*Scale 0
Field description
The two character USPS state abbreviation for the state corresponding to the Study Area Code associated with the polygon.



Field FROZEN
 
*Alias FROZEN
*Data type String
*Width 1
*Precision 0
*Scale 0
Field description
A single character relating to the status of frozen support for the company associated with the polygon. Acceptable values are "Y" (Yes), or "N" (No). If the polygon represents the study area boundary only this field may be left blank.



Field BOUND_TYPE
 
*Alias BOUND_TYPE
*Data type String
*Width 2
*Precision 0
*Scale 0
Field description
A two character identifier for the type of boundary represented by the polygon. Acceptable values are "SA" (Study Area), "EX" (Exchange), or "WC" (Wire Center).



Field Shape_Leng
 
*Alias SHAPE_LENG
*Data type Double
*Width 8
*Precision 38
*Scale 8




Field SHAPE.AREA
 
*Alias SHAPE.AREA
*Data type Double
*Width 0
*Precision 0
*Scale 0




Field SHAPE.LEN
 
*Alias SHAPE.LEN
*Data type Double
*Width 0
*Precision 0
*Scale 0






Metadata Details 

*Metadata language English (UNITED STATES)
Metadata character set  utf8 - 8 bit UCS Transfer Format


Scope of the data described by the metadata* dataset
Scope name* dataset


*Last update 2016-04-05


ArcGIS metadata properties
Metadata format ArcGIS 1.0
Metadata style FGDC CSDGM Metadata
Standard or profile used to edit metadata FGDC


Created in ArcGIS for the item 2013-05-24 09:46:20
Last modified in ArcGIS for the item 2016-04-05 08:34:51


Automatic updates
Have been performed Yes
Last update 2016-04-05 08:34:51

Item location history
Item copied or moved 2013-05-24 09:46:20
From Z:\Broadband\BBND\Exchange_Boundary\Shapefiles\sab_template
To \\tawonga\data\Broadband\BBND\Exchange_Boundary\FinalDeliverables\sab_template


Metadata Contacts 

Metadata contact
Individual's name Fred Gifford
Organization's name Tetratech, Inc.
Contact's position Broadband Mapping Contract Project Manager
Contact's role  point of contact


Contact information
Phone
Voice 406-431-1490

Address
Type
e-mail addressFred.gifford@tetratech.com