Accurate field data is what separates a clean construction job from a money pit. Our crews collect the ground-truth information your engineers need — strand mapping, GPS pole surveys, underground assessment, and full photo documentation — across 22 states.
Fiber optic field survey services provide the verified ground-truth data that construction engineering depends on: pole attachment heights, span lengths, underground conduit locations, and route constraints that satellite imagery cannot detect. Skipping survey or using low-quality data routinely causes unbudgeted make-ready work, construction stoppages, and change orders that cost 10–20 times the original survey cost.
I've said this to clients more times than I can count: the cheapest mistake you can make is skimping on field survey. The second-most-expensive mistake is not doing one at all.
Here's what actually happens when you design off aerial imagery and county GIS records without ground-truth verification. Your route goes through a corridor where Google Maps shows clear span — but in the field there's a 34.7-foot clearance issue at a secondary road crossing that nobody flagged. Construction hits that crossing, the inspector shuts it down, and now you're looking at a pole replacement plus a rearrangement order plus three weeks of delay while the utility company processes paperwork. That's not a hypothetical. We cleaned up exactly that situation on a deployment in central Georgia in 2023 — a corridor where the desktop analysis looked clean but 6 of 41 poles had attachment conflicts that required make-ready work nobody had budgeted for.
Field survey is insurance. Not the kind you hope you never need — the kind that pays back 10-to-1 when the alternative is a blown construction schedule.
The real cost math: A thorough field survey on a 10-mile aerial route runs somewhere between $8,000–$14,000 depending on pole density and terrain. A single unbudgeted pole replacement — which one missed attachment conflict can trigger — costs $3,500–$7,000 before you factor in delay. You don't need many surprises to justify the survey budget.
Our OSP field survey services cover every data layer that downstream engineering depends on: pole inventory, attachment census, mid-span measurements, underground assessment, route walkout documentation, and site photography. The data feeds directly into our CAD/GIS design workflow and our pole loading analysis, so nothing gets lost in translation between the field and the design office.
For more on why field data quality determines construction outcomes, our team wrote a detailed breakdown — field survey data accuracy for fiber construction — that covers common collection errors and how to avoid them.
Full aerial route survey: pole ID, GPS coordinates, attachment heights measured to the inch, mid-span clearances, guy wire locations, and pole condition flags. This is the foundation of make-ready engineering. We don't estimate — we measure.
Every pole gets a GPS coordinate, owner ID, species and class where visible, height verification, and a photo log. Our crews use Fulcrum to capture structured data in the field — no loose field notes that get interpreted differently back at the desk.
Existing conduit trace, manhole / handhole inventory, conduit fill analysis, and bore path assessment. Where records don't match reality — and they often don't — we flag discrepancies and mark for locating services before design commits to a route.
Pre-design route walkout documenting physical constraints: tree canopy conflicts, road crossing types, easement access issues, terrain grade changes, and any site conditions that affect route selection. Catches design-killers before engineering starts.
Wetland proximity, flood zone crossings, agricultural land notes, and right-of-way access constraints. This feeds directly into permit packages and helps the environmental compliance team avoid NEPA surprises mid-construction.
Physical address confirmation for BEAD and FTTH deployment planning — verifying structure locations, unit counts at MDU properties, and serviceable address boundaries. Critical for accurate subsidy claims and take-rate projections.
Our fiber field survey data collection methodology uses structured digital capture in Fulcrum and Katapult — enforcing required fields at the pole level before records submit. Attachment heights, GPS coordinates, pole condition, and photos are all linked to a single pole record. QA/QC runs in the field daily, not as a post-processing step, catching GPS outliers and missing attributes before crews leave the corridor.
The problem with field survey isn't usually the surveyors — it's the process. No standardized data schema. Hand-written notes that get typed up differently by whoever's back at the office. Photos stored in someone's phone with no association to a specific pole. GPS points recorded on one coordinate system and imported into a GIS using another.
We've built our collection process around structured data from the first click. Every field crew works in Fulcrum with a configured app template that enforces required fields before a pole record can be submitted. Pole number, GPS point (auto-captured), attachment count, measured attachment heights, condition rating, photos — all linked to the same record. If a required field is blank, the record doesn't close. That's not a policy. That's a technical constraint built into the form.
For projects feeding directly into pole loading analysis, we collect in Katapult — which produces a data format that O-Calc Pro and SPIDA Calc can ingest directly. That eliminates a re-entry step that, in our experience, is where a lot of data errors get introduced. Attachment heights that were measured correctly in the field get mistyped at the desk. That's a 0.5-foot error on an attachment that was already at a borderline clearance, and suddenly a pole that passed loading analysis fails in the field because the modeled height was wrong.
We've seen that exact failure mode cause schedule delays of 3–6 weeks on mid-size deployments. It's preventable. Katapult-to-load-calc direct import is how you prevent it.
Our QA process isn't a post-processing step — it's built into daily collection. Each crew lead reviews the day's submissions before leaving the field area. GPS outliers (points more than 30 meters from the nearest road centerline without a logged reason) get flagged and re-verified same day. Photo counts get spot-checked against pole counts. Attachment heights get compared against previous surveys of the same corridor if one exists.
Back at the office, a QC engineer runs automated validation scripts against each submission batch: duplicate pole IDs, coordinate system mismatches, missing mandatory fields, and attribute value ranges outside expected parameters. Anything that fails gets kicked back to the crew lead with a specific correction request — not a vague "please review."
One thing I'll push back on: Clients sometimes ask if we can do "drive-by" surveys using vehicle-mounted cameras as a cost-saving measure. For route feasibility and rough address counts? Sure, that's defensible. For construction-ready strand mapping and aerial plant assessment? No. You can't measure attachment heights from a car window, and mid-span clearances require being at the pole. Cut this corner and you'll pay for it in make-ready rework. We'd rather tell you that now than after the design is done.
When field survey data feeds into our FTTH design process, we require verified attachment data — no estimates, no assumptions from prior similar projects. Every project is different. Central Florida palm trees create different clearance patterns than Pacific Northwest Douglas firs, and both are different from the aging hardwood canopy you'll find along creek corridors in Tennessee.
We're not religious about any single tool. What matters is that the data comes back accurate, structured, and in a format the engineers can actually use.
Our field crews carry GNSS-enabled survey tablets with real-time correction capability where network coverage allows. Sub-meter accuracy is achievable in open conditions. In dense urban areas or under heavy canopy, we use post-processing correction and flag reduced-accuracy points in the dataset metadata — so the design team knows which coordinates to treat with extra scrutiny.
Fulcrum and Katapult are our primary platforms — both for different use cases. Fulcrum handles general inventory, photo capture, and multi-layer data collection. Katapult is purpose-built for joint use and pole loading data, and its integration with downstream engineering tools makes it the right call for those workflows.
Attachment heights are measured physically — either by tape where accessible or by calibrated height poles at the base of the structure. Laser rangefinders get used for mid-span measurements on longer spans. We don't estimate heights from visual inspection. A 2-foot error in attachment height can swing a loading calc from pass to fail, especially on older poles operating near their capacity limits.
For underground depth verification on bore routes with no reliable record, we coordinate ground-penetrating radar with certified locating contractors. Rare, but sometimes necessary — especially on routes crossing through older municipal areas where the utility records are whatever the crew foreman wrote on a paper map in 1987.
On LiDAR: Mobile and aerial LiDAR can supplement field survey on large projects where crew deployment is constrained by timeline. LiDAR captures structure heights and clearance zones at scale but doesn't replace physical attachment census — you still need eyes on the pole to identify attachment owners and measure to the actual bolt. We treat LiDAR as a first-pass tool, not a substitute for boots on the ground.
We start with your project files — route shapefiles, design extents, or a simple KMZ. We calculate pole density estimates from aerial imagery, segment the route into crew workzones, and build a collection schedule with daily production targets. On a 50-mile rural aerial project, this takes 1–2 days. We don't pad the timeline to look thorough.
We configure the Fulcrum app to your project's data schema before crews leave the office. Required fields, attribute picklists, photo requirements per structure type — all set up to match your deliverable format or ours. Crews get a pre-field briefing on any project-specific conventions (e.g., how to handle utility-owned streetlights, or how to flag disputed pole ownership).
Crews work the route in segments, submitting records daily. Fulcrum's cloud sync means data is visible to the project manager in near-real-time — no waiting for crews to return with USB drives. Production rates, geographic coverage, and open flags are monitored daily.
Each evening, a QC engineer reviews that day's submissions. GPS outliers, missing photos, height values outside normal ranges, and duplicate pole IDs all get flagged automatically. Corrections go back to the crew lead the same night — field crews resolve them the following morning while they're still in the area. No backtracking across the state two weeks later.
Cleaned data gets processed into your delivery format: Esri geodatabase, shapefile, KMZ, CSV, or a Katapult-compatible export. Pole records, attachment records, photo links, and condition flags are all relationally linked so the design team can pull the full pole record from a map click without hunting through a spreadsheet.
Delivered with a data dictionary, QC summary report (total poles surveyed, flags resolved, flags remaining with explanation), and a coverage map confirming full route completion. If anything needs re-survey after design review, we track it and return. That's part of the job, not an extra charge.
Fiber optic field survey deliverables include GPS-attributed pole inventories, attachment height records, span measurement tables, mid-span clearance data, underground conduit assessments, and geotagged photo documentation — all exported in ArcGIS-compatible geodatabase, Shapefile, KMZ, CSV, and Katapult formats. Deliverables are QC'd and formatted to feed directly into pole loading analysis and CAD/GIS construction package design.
Every deliverable is GIS-ready and formatted for direct ingestion into your engineering workflow. No reformatting, no manual re-entry.
Shapefile or geodatabase with pole GPS coordinates, owner, species, height class, condition rating, and all attachment attributes. Fully attributed and ready for ArcGIS or QGIS import.
Per-pole attachment list with measured heights, attachment owner, cable type, and clearance flags. Formatted for direct import into O-Calc Pro or SPIDA Calc.
Geotagged photos for every pole — minimum 2 per structure (full pole face + attachment closeup). Photos are linked to pole records in the GIS database, not stored as a loose image folder.
Measured clearances at road crossings, secondary crossings, and other regulated span types. Includes NESC violation flags and recommended make-ready actions at non-compliant spans.
Manhole and handhole locations, conduit type and fill data, access condition, and bore path constraints. Includes survey-grade GPS coordinates and dimensional notes.
Coverage map, production statistics, open flags with disposition, re-survey notes, and data completeness certification. Required for BEAD engineering submittals and some utility company permit packages.
We also write about why field data quality directly affects construction outcomes — see our article on field survey data accuracy in fiber construction for specifics on the error types that cause the most downstream damage. And if you're seeing survey data inconsistencies show up as FTTH design errors, our guide on common FTTH HLD design mistakes addresses several that originate in bad field input.
Strand mapping is the process of physically walking or driving an aerial route and recording the existing messenger wire (strand) on each pole — including pole ID, GPS coordinates, attachment height, mid-span clearances, and pole condition. That data becomes the foundation for make-ready engineering and FTTH route design. Without it, you're designing on assumptions. Assumptions become change orders.
Survey-grade GPS units typically achieve sub-meter accuracy (0.3–0.5 meters) under open sky conditions. In dense urban canyons or heavy canopy areas, accuracy degrades to 1–3 meters without differential correction. Our crews use GNSS-enabled devices with real-time correction where available, and flag anomalies for desktop verification. We don't report positions we can't verify.
A standard OSP field survey includes: pole inventory (GPS location, species, height class, owner, condition), attachment census (all attachments measured to the inch), mid-span clearance measurements, guy wire and anchor documentation, underground marker flags, photo logs for every pole, and any environmental or access constraints noted in the field. Deliverables are GIS-ready data exports, not just a spreadsheet.
A desktop survey uses satellite imagery, county GIS records, and utility data to plan a route from a computer. It's fast and inexpensive but misses ground-level reality: pole condition, actual attachment heights, mid-span sags, access issues, and environmental conflicts. A field survey catches all of that. For construction-ready design, field data is non-negotiable — desktop analysis is only appropriate for early-stage feasibility.
In rural or suburban environments with good road access, an experienced crew averages 60–90 poles per day using Fulcrum and a calibrated GPS unit. In urban environments, dense tree canopy, or high-traffic corridors, that drops to 35–55 poles per day. We size crews to project timelines — not the other way around.
We coordinate with 811 (Call Before You Dig) for underground marking on bore and trench routes. For complex multi-utility corridors, we work with certified private locating firms. Ground-penetrating radar is available on projects where buried plant depth verification is critical — for example, when existing conduit records are absent or suspect.
If you're planning a fiber deployment and need ground-truth survey data that your engineers can actually build from, reach out. We've run field survey operations on projects ranging from 3-mile rural spurs to 200-mile BEAD corridors — the process scales. Send us your project extents and we'll turn around a scope and schedule within 48 hours.
Talk to Our Survey TeamOr email directly: info@draftech.com | Join our field team