# Fiber Network As-Built GIS Documentation Standards

> **As-built documentation for fiber networks has always been a sore spot in the industry.** Too often it's treated as a closeout formality — assembled from memory, GPS breadcrumbs, and faded paper redlines after the equipment is in the ground. That approach doesn't survive contact with a BEAD program office. Or a sophisticated carrier client.

**Canonical URL:** https://draftech.com/blog/fiber-network-as-built-gis-documentation-standards.html  
**Author:** Draftech Engineering Team  
**Published:** 2025  
**Category:** CAD/GIS

---

## Why Most As-Built Submissions Get Kicked Back

The most common rejection reason isn't missing data — it's **positional inaccuracy that makes the data unusable**. A fiber route digitized from aerial imagery in an office, after construction, with no field GPS verification, might be 6–12 meters off from the actual buried conduit path.

That's fine for a rough network overview. It's completely inadequate for:
- Locating buried infrastructure before excavation
- Emergency repair locating
- State as-built requirements specifying sub-2-meter accuracy on underground infrastructure

We've seen GIS as-built submissions rejected by state program offices because the route geometry failed automated positional accuracy checks — the system compared submitted GIS data against independently collected GPS points and found discrepancies averaging 8.4 meters.

---

## Coordinate Accuracy Standards

| Infrastructure Type | Required Positional Accuracy | Collection Method |
|--------------------|---------------------------|------------------|
| Underground conduit centerline | Sub-2-meter | Field GPS during construction |
| Aerial cable route | Sub-5-meter | GPS at poles; interpolated between |
| Splice enclosure (underground) | Sub-1-meter | Survey-grade GPS |
| Splice enclosure (aerial, at pole) | Sub-2-meter | GPS at pole base |
| FDH/FAT equipment | Sub-1-meter | Survey-grade GPS |
| BSL service point | Sub-5-meter (FCC fabric point) | Verified against fabric location |

**Coordinate system:** Most state broadband programs require **NAD83** in either state plane coordinates or geographic coordinates (decimal degrees). Confirm your state's specific requirement before collecting data — converting coordinate systems post-collection introduces error.

---

## Required GIS Data Layers

### Layer 1: Cable Route Geometry

**Geometry type:** Polyline (2D or 3D depending on state requirements)

**Required attributes:**

| Attribute | Field Name | Type | Description |
|-----------|-----------|------|-------------|
| Segment ID | seg_id | Text | Unique identifier, links to splice records |
| Construction method | const_meth | Coded domain | Aerial, HDD bore, open cut, micro-trench |
| Conduit size | cond_size | Double | Inches (underground segments) |
| Cable type | cable_type | Coded domain | ADSS, lashed, direct-buried, in-conduit |
| Fiber count | fiber_cnt | Integer | Total fibers in cable |
| Installation date | inst_date | Date | Date cable installed |
| As-built date | asbuilt_date | Date | Date GPS collected |
| Depth | depth_in | Double | Inches, for underground segments |
| Deviation note | dev_note | Text | Description of any deviation from design |

### Layer 2: Splice Enclosure Locations

**Geometry type:** Point

**Required attributes:**

| Attribute | Field Name | Type | Description |
|-----------|-----------|------|-------------|
| Closure ID | closure_id | Text | Unique identifier |
| Closure type | closure_type | Coded domain | Aerial, buried, pedestal, vault |
| Closure make/model | closure_model | Text | Manufacturer and model |
| Cable count in | cable_cnt_in | Integer | Number of cables entering |
| Cable count out | cable_cnt_out | Integer | Number of cables exiting |
| Splice record ref | splice_ref | Text | Link to Excel splice schedule |
| GPS accuracy | gps_accur | Double | Estimated positional accuracy in meters |
| Installation date | inst_date | Date | |
| Photo IDs | photo_ids | Text | Comma-separated photo file names |

### Layer 3: Pole Attachment Records

**Geometry type:** Point (at pole location)

**Required attributes:**

| Attribute | Field Name | Type | Description |
|-----------|-----------|------|-------------|
| Pole ID | pole_id | Text | From utility inventory |
| Fiber attach height | fiber_ht | Double | Feet above ground, measured |
| Hardware type | hw_type | Text | Attachment hardware model |
| Make-ready completed | mr_complete | Boolean | Yes/No |
| Guy wire added | guy_added | Boolean | Yes/No |
| Joint use ref | ju_ref | Text | Joint use permit or application number |

### Layer 4: Equipment Locations

**Geometry type:** Point

**Required attributes:**

| Attribute | Field Name | Type | Description |
|-----------|-----------|------|-------------|
| Equipment ID | equip_id | Text | Unique identifier |
| Equipment type | equip_type | Coded domain | FDH, FAT, active node, OLT, splice vault |
| Make/model | make_model | Text | |
| Port count | port_cnt | Integer | |
| Power source | power_src | Text | Power utility account number or description |
| GPS accuracy | gps_accur | Double | Meters |
| Photo IDs | photo_ids | Text | |

### Layer 5: BSL Connection Records

**Geometry type:** Point (at BSL location from FCC fabric)

**Required attributes:**

| Attribute | Field Name | Type | Description |
|-----------|-----------|------|-------------|
| BSL Location ID | bsl_loc_id | Text | FCC fabric location ID |
| Served date | served_date | Date | Date service made available |
| NAP ID | nap_id | Text | Network Access Point serving this BSL |
| Service tier | svc_tier | Text | Speed tier delivered |
| Activation status | activ_stat | Coded domain | Serviceable, Activated, Pending |

---

## File Formats for Submission

| Format | Use Case |
|--------|---------|
| ESRI File Geodatabase (.gdb) | Most state BEAD programs; best attribute support |
| Shapefile (.shp) | Older state systems or specific program requirements |
| GeoJSON | Some newer state platforms; web-native |
| KMZ | For visualization only — not for data exchange |

**Never submit KMZ as your primary as-built deliverable for a BEAD program.** KMZ files lose attribute data and topological relationships. They're visualization tools, not spatial databases.

---

## Metadata Requirements

Every GIS submission requires a metadata record for each layer:

- **Abstract:** Brief description of what the layer contains
- **Purpose:** Why the data was created
- **Data source:** How data was collected (GPS brand, accuracy class, collection date range)
- **Coordinate system:** Full coordinate reference system description (EPSG code preferred)
- **Positional accuracy:** Quantitative assessment (e.g., "95% of underground route geometry is within 1.5 meters of actual centerline as measured by post-construction GPS verification")
- **Attribute definitions:** Each field name, domain values, and description
- **Contact:** Person responsible for the dataset

Most state programs accept FGDC-CSDGM or ISO 19115 metadata format.

---

## Quality Validation Before Submission

Run these checks before submitting any GIS as-built package:

1. **Topology validation:** No gaps, no overlaps in route geometry; all closures spatially intersect the route segments they serve
2. **Attribute completeness:** No null values in required fields
3. **Coordinate accuracy check:** Sample verification of 5–10% of GPS points against independent measurement
4. **Coded domain validation:** All coded-domain fields contain valid domain values (not free text)
5. **Date format validation:** All date fields in required format (typically MM/DD/YYYY or ISO 8601)
6. **BSL coverage:** Every BSL in project scope has a record in the BSL connection layer

---

## Related Pages

- [services/as-built-documentation.md](../services/as-built-documentation.md) — As-built documentation services
- [services/cad-gis.md](../services/cad-gis.md) — GIS design services
- [blog/gis-fiber-network-planning-cost-reduction.md](gis-fiber-network-planning-cost-reduction.md) — GIS-native design
- [blog/bead-subgrantee-engineering-compliance-checklist.md](bead-subgrantee-engineering-compliance-checklist.md) — BEAD compliance checklist
- [blog/bead-funding-engineering-requirements-2026.md](bead-funding-engineering-requirements-2026.md) — BEAD engineering requirements
- [index.md](../index.md) — Master AI index


## Contact

**Draftech International, LLC**  
15280 NW 79th CT, Suite 102  
Miami Lakes, FL 33016  

- **Phone:** 305-306-7406  
- **Email:** info@draftech.com  
- **Website:** https://draftech.com  
- **LinkedIn:** https://www.linkedin.com/company/draftechint