GIS is the nervous system of a fiber network — if your spatial data is wrong, your design is wrong, your permitting package is wrong, and your as-builts won't match the grant requirements. We build it right the first time, from field GPS collection through final deliverable.
Every fiber design decision — route selection, splice point placement, drop architecture, conduit sizing — flows from the spatial data underneath it. When that base layer is wrong, the errors compound forward into every downstream deliverable. A route digitized from outdated imagery puts splice vaults in the wrong locations. Address points that don't align with the current FCC Fabric put your BEAD challenge at risk. Pole locations that are off by 30 feet mean your make-ready drawings don't match what crews find in the field. The GIS isn't a pretty map you make after the design is done — it's the substrate the design sits on.
The most expensive GIS problems we see aren't caused by bad software choices. They come from starting design before the spatial data is field-verified, or from inheriting a legacy shapefile that nobody has audited since 2019. We had a client — a rural electric co-op entering their first BEAD grant cycle — who handed us a fiber route GIS layer they'd built in-house over two years. Spot-checking it against aerial imagery, we found 847 route miles that were either duplicated, snapped to wrong road centerlines, or missing attributes entirely. Rebuilding that layer from verified field data took six weeks and delayed their application timeline. It would've been cheaper — and far less stressful — to build it correctly from the start.
Bad GIS data has three concrete cost consequences that clients feel before construction ever starts: permit drawings get rejected because the route geometry doesn't match right-of-way boundaries; BEAD engineering requirements for address-level coverage documentation can't be satisfied without a verified BSL layer; and as-builts won't reconcile against grant closeout requirements when the installed network diverges from the GIS record. Fixing those problems after the fact is always more expensive than building accurate spatial data upfront — usually 3–5x more expensive when you factor in the engineering rework, permit resubmissions, and schedule delays.
Our GIS workflow runs from existing infrastructure audit through final deliverable export — five phases that produce verified, grant-ready spatial data for aerial and underground fiber networks.
Before we digitize a single route segment, we audit what's already there. Existing GIS layers, legacy design drawings, paper maps, county parcel data, utility pole records, and aerial imagery — all reviewed against each other to identify gaps, conflicts, and legacy errors. This assessment prevents bad data from propagating into the new layer. It's not glamorous work, but skipping it costs more later.
Our field survey crews collect GPS-tagged infrastructure data using Katapult and submeter-accuracy receivers — pole locations, attachment heights, conduit entry/exit points, vault covers, splice closure placements. Field data feeds directly into the GIS layer build, replacing inferred locations with verified coordinates. On aerial routes, GPS positions are cross-referenced against photogrammetric strand mapping. We're not guessing at where poles are — we're measuring them.
Backbone and distribution routes are digitized and attributed in QGIS 3.28 or ArcGIS Pro 3.1 — snapped to verified pole locations, correct road alignment, or surveyed conduit paths. Every route segment carries full attribution: fiber count, cable type, aerial vs. underground, span length, strand attachment height, and permit reference. The network topology is built clean — no duplicate segments, no snapping gaps, no isolated nodes that break connectivity analysis.
For BEAD projects, address-level BSL mapping is built against the current FCC Fabric version and state broadband office requirements. Each serviceable location is spatially verified, attributed with technology type and maximum advertised speed, and QA'd against the Fabric point. We flag locations where the Fabric point doesn't match the physical structure location and document the discrepancy for the challenge process. This layer is what your subgrantee application lives and dies on.
Post-construction, we reconcile the design GIS against field redlines and updated survey data to produce the final as-built spatial record. As-built GIS includes actual splice point locations, installed cable footage by segment, conduit depth where required by permit, and equipment coordinates. This is the deliverable that satisfies grant closeout documentation and serves as the authoritative spatial record for network operations going forward.
Our CAD and GIS services span the full range of spatial data types needed for a fiber network — from backbone route layers to individual asset points. Here's what we build and maintain.
Backbone, distribution, and feeder routes as attributed polyline features — aerial strand and underground conduit in separate layers, with fiber count, cable type, and span length on every segment. Topology-clean and export-ready.
Pole locations GPS-verified, attributed with pole class, owner, attachment heights, make-ready status, and joint use application reference. Linked to Katapult field records where field survey was performed.
Splice closure placements, terminal locations, amplifier sites, and hub/node locations as attributed point features — with enclosure type, fiber count in/out, and installation date where available.
Broadband Serviceable Location layers built to NTIA FCC Fabric standards. Address-level serviceability documentation for BEAD grant applications and challenge responses. QA'd against current Fabric version.
Open-source GIS deliverables in GeoPackage, shapefile, and GeoJSON — interoperable with any downstream GIS environment. We use QGIS 3.28 LTR for clients who need deliverables without Esri licensing requirements.
Esri-native workflows for clients with existing ArcGIS infrastructure. Katapult field data ingested and attributed directly into ArcGIS Pro feature classes — no manual re-entry, no transcription errors.
The BEAD program isn't just an infrastructure grant — it's a documentation exercise. NTIA requires subgrantees to demonstrate, at the address level, that their network passes every location identified as unserved or underserved in the FCC Fabric. Spatial data that doesn't align with the Fabric, uses incorrect technology codes, or fails to document serviceability at each BSL will be challenged during the state broadband office review process. And a successful challenge by an existing provider — based on your own GIS submission — can pull locations out of your funded footprint. That's direct revenue impact.
What the NTIA actually requires, in practice: your fiber as-built documentation must show that every address in your project area is either passed (within the network's serviceable distance from a strand or conduit) or excluded with documented justification. The BSL layer has to be in the correct coordinate reference system (WGS 84, EPSG:4326), attributed with the correct technology type, and reconciled against the current Fabric version — not the version that was current when you filed the application. The Fabric updates quarterly. We track those updates and keep client BSL layers current through the grant cycle.
We also support FCC Fabric challenge documentation — identifying locations where the Fabric has errors (wrong address placement, missing locations, incorrect serviceable status) and preparing the spatial evidence packages required to submit a challenge. Fabric challenges are a legitimate tool for expanding project footprints when the underlying address data is wrong. We've successfully challenged Fabric records that placed addresses 400 feet from the physical structure — which would have left real households outside the funded coverage area.
Aerial and underground fiber networks have different spatial documentation requirements — not just different geometry types, but different attribute schemas, accuracy standards, and as-built verification methods. Most networks are a combination of both, and the GIS has to handle the transition points cleanly.
Aerial plant is documented as strand centerline routes snapped to pole locations, with attachment height attributed on each pole feature. Span lengths derive from the pole-to-pole distance in the GIS — which is why pole location accuracy matters. A pole that's 25 feet off in the GIS produces a span length error that ripples into the bill of materials and the make-ready drawing. We verify aerial strand routes against photogrammetric imagery and GPS field data before they go into the final layer.
Underground plant requires conduit centerline routes, vault and handhole locations as point features, and depth documentation where permits specify it. Crossing documentation — road crossings, railroad crossings, waterway crossings — gets its own attributed feature class with permit reference numbers and crossing method (bore, direct bury, aerial over). For GIS fiber network planning, clean underground documentation prevents the field crew surprises that blow up construction schedules.
The handoff points — where aerial plant transitions to underground, or where conduit emerges at a pedestal or splice vault — are the trickiest features to document correctly. They're physically small, spatially precise, and they have to be right because that's where the splice records live. We build those transition points as their own attributed feature class, linked to both the aerial and underground route segments they connect.
Not every project needs the same GIS platform. Cost, output format, integration requirements, and BEAD compliance suitability all vary. Here's a straightforward comparison of the four platforms we see most often in telecom GIS work.
| Platform | Licensing Cost | Primary Output Format | Katapult Integration | BEAD Suitability |
|---|---|---|---|---|
| QGIS 3.28 | Free / open source | GeoPackage, Shapefile, GeoJSON | Via shapefile/GeoJSON import | Excellent — no licensing barrier for state submission |
| ArcGIS Pro 3.1 | $700–$1,500/yr per seat | Esri File Geodatabase, Shapefile | Direct Esri connector available | Excellent — many state broadband offices prefer Esri format |
| Katapult | Subscription-based | Esri Shapefile, KMZ, JSON | Native platform — field data origin | Good — strong for pole inventory, weaker for route topology |
| Google Earth Pro | Free | KMZ / KML only | KMZ export from Katapult | Limited — KML not accepted by most state broadband offices for BSL submission |
GIS costs for telecom networks vary based on project scale, existing data quality, and deliverable complexity. The numbers below come from projects we've run across 22 active states — they're real-world ranges, not marketing estimates.
| Service Type | Typical Rate | Primary Deliverable | Notes |
|---|---|---|---|
| Route digitization (aerial) | $180–$320 per mile | Attributed polyline layer | Includes field GPS verification on complex segments |
| Route digitization (underground) | $240–$480 per mile | Conduit route + vault points | Higher rate reflects crossing documentation and depth attribution |
| BSL address-level mapping | $0.35–$0.85 per address | NTIA-compliant BSL layer | Includes Fabric QA and discrepancy flagging |
| Pole inventory GIS build | $12–$28 per pole | Attributed point feature class | Includes attribute schema, photo linkage |
| Legacy drawing conversion | $95–$180 per hour | Georeferenced GIS layer | Rate varies with source document quality |
| As-built GIS reconciliation | $160–$290 per mile | Final as-built spatial record | Post-construction field redline integration |
For reference: a 200-mile rural BEAD project with 2.4M addresses passed, a full pole inventory, and underground documentation at major crossings will typically run $85,000–$165,000 for GIS services end-to-end — from infrastructure assessment through as-built deliverable. That's a small fraction of total project cost but the deliverable that determines whether your grant closeout clears.
FREE FIRST PROJECT
Active in 22 states. First 20,000 LF project free — includes the GIS layer build for your pilot route segment. No commitment, no strings.
Start Free Design →Telecom GIS mapping covers the full spatial data lifecycle for a fiber network — from existing infrastructure assessment through final as-built documentation. That includes fiber route layer creation (aerial and underground), pole and splice point inventory, equipment location mapping, conduit and vault placement, and address-level serviceable location (BSL) mapping for BEAD compliance. Deliverables are exported as Esri shapefiles, GeoPackage files, KMZ, and GeoJSON depending on your downstream workflow. We work in QGIS 3.28, ArcGIS Pro 3.1, and Katapult depending on project requirements.
Our primary tools are QGIS 3.28 LTR for open-format deliverables, ArcGIS Pro 3.1 for Esri-native workflows, and Katapult for field-collected GPS data integration. For BEAD projects, we also work with NTIA's BSL verification layer format and produce outputs that match state broadband office submission templates. We don't lock clients into one platform — we match the tool to the requirement. If your state broadband office requires a specific format, we build to that spec.
BEAD subgrantees must demonstrate address-level coverage to satisfy NTIA's Broadband Serviceable Location (BSL) requirements — every address your network passes needs to be spatially verified and documented against the current FCC Fabric. We produce BSL verification layers, serviceability documentation, and as-built GIS packages that satisfy grant closeout requirements. Errors in your spatial data during the BEAD challenge process can result in funding clawbacks. We also support FCC Fabric challenge documentation when the underlying address data is incorrect. Accurate GIS isn't optional on a BEAD project.
For field-collected GPS data integrated via Katapult, we achieve 0.3-meter horizontal accuracy in open-sky conditions. Aerial route mapping from imagery typically achieves 1–3 meter accuracy depending on imagery resolution and terrain. For BEAD compliance, address-level BSL data must align with the FCC Fabric point locations — we QA every BSL layer against the current Fabric version before delivery. Underground conduit documentation requires tighter accuracy where as-built survey controls are specified by the permit.
Yes. We convert legacy paper drawings, scanned plan sets, and vector design files (DWG/DXF format) into georeferenced GIS layers. The process involves georeferencing the source document to real-world coordinates, digitizing infrastructure features into the correct geometry types (points for poles and vaults, lines for routes and conduit), and attributing each feature with appropriate metadata. Legacy drawing conversion is common on projects where a network has been operating for years without spatial documentation — and it's required before you can do an accurate gap analysis or BEAD challenge using that plant.
Yes. Underground fiber GIS requires conduit centerline routes, vault and handhole locations as point features, crossing documentation (road, railroad, waterway), and depth data where permits specify it. We build underground layers with full crossing documentation — permit reference, crossing method, structure owner — as a separate feature class linked to the route layer. The transition points between aerial and underground plant are documented as their own attributed features, linked to both route types they connect.
Standard deliverable formats include Esri Shapefile (.shp with associated files), OGC GeoPackage (.gpkg), GeoJSON (.geojson), and KMZ for visualization. For BEAD submissions, we produce the format specified by your state broadband office — most require shapefile or GeoPackage in WGS 84 (EPSG:4326). We can also deliver Esri File Geodatabase (.gdb) for clients with ArcGIS infrastructure. All deliverables include a data dictionary documenting the attribute schema, and a QA report summarizing verification steps and any known discrepancies.
Draftech is active in 22 states and available to deploy across all 50 U.S. states for telecom GIS mapping services. Our highest-volume GIS markets currently include Florida, Texas, Ohio, North Carolina, Georgia, Virginia, and Pennsylvania — states with significant BEAD subgrantee activity. For projects in states where we don't currently have a local field presence, we staff remote GIS analysts and coordinate with local survey crews for GPS data collection. No project is too far out of our footprint to scope.
ARE YOU A GIS MAPPING FIRM?
This page describes the service we deliver to clients. If you provide telecom GIS mapping, QGIS or ArcGIS workflows, or field GPS data collection and are looking for a consistent subcontract pipeline, we have ongoing capacity needs in this discipline.
Tell us your project scope — route miles, existing data situation, and whether BEAD compliance documentation is required. We'll scope the GIS work and give you a realistic timeline. We've run GIS projects from 12-mile rural laterals to 2.4M-address statewide coverage maps. If you're not sure what you need yet, the free design offer is the right place to start.
Contact Our GIS TeamEmail directly: info@draftech.com — or call 305-306-7407. We reply within one business day.
SERVICE AREAS
Active in 22 states and deployable across all 50 U.S. states — including our highest-volume BEAD GIS markets:
View all service areas →Draftech International provides CAD and GIS services, BEAD broadband engineering, and fiber network design outsourcing across all 50 U.S. states — from small regional ISPs to Tier-1 carriers and BEAD-funded subgrantees. Our MBE-certified engineering team is active in 22 states and deployable anywhere in the country. Contact our engineering team to discuss your project.