Data alignment
LiDAR, imagery, field records and client pole identifiers are aligned in a consistent coordinate and attribute environment.
Utility pole data prepared for faster engineering review.
Pole profiles, attachment inventories, CAD drawings and structured SPIDAcalc-ready records from LiDAR, imagery and field data.
Prepare observed pole and attachment records in your agreed template. Flag missing field attributes and test sample import before describing an exchange file as SPIDAcalc-ready.
Request a pilot ↗︎BEST FIT
A focused production service.
- Utility GIS and engineering support teams
- Pole-profile production programs
- Make-ready data preparation workflows
DELIVERABLES
What arrives.
Final scope follows your project specification and accepted calibration sample.
01
Pole profile and elevation drawings
✓02
Pole, attachment and equipment inventories
✓03
SPIDAcalc-ready data preparation
✓04
Make-ready base information
✓05
Span, clearance and wire-height schedules
✓06
SHP, CSV, DWG and client-template outputs
✓PRODUCTION WORKFLOW
Controlled from input to acceptance.
Each stage has an explicit output, responsible reviewer and defined check.
Pole interpretation
Poles, attachments, equipment, wires, spans and visible clearance conditions are captured against the approved rules.
Profile production
Pole profiles, CAD geometry and structured records are prepared in the client template and required exchange format.
Technical QA
Identifiers, units, elevations, attachment order, required fields and cross-file consistency are reviewed before delivery.
FORMATS TO CONFIRM IN PILOTSPIDAcalc-ready dataDWGDXFSHPCSVXLSXPDF
SPECIFICATIONS TO AGREEClient utility standardEngineer-supplied project criteriaClient CAD templateEngineering review workflow
INPUTS AND ACCEPTANCE
Define a handoff your team can verify.
Provide pole IDs, LiDAR and imagery dates, field records, the engineer's attribute definitions, units and an accepted import template for the target SPIDAcalc version.
- Reconcile pole IDs, span connections, units and drawing references
- Separate measured, supplied, inferred and unknown attributes
- Have the receiving team test a pilot import and review unresolved fields
SCOPE LIMITSource capture represents observed conditions at that time. Material properties, structural condition, loading assumptions and design clearances require qualified engineering and field evidence; do not infer them from point clouds.DELIVERY EVIDENCEAgree the output inventory, source references, validation results and exception log. Set review deadlines and correction responsibilities in the written scope.
COMMON QUESTIONS
Before a pilot.
Does Altivue Geospatial perform the final pole-loading analysis?+
Altivue Geospatial prepares pole records, profiles and proposed exchange inputs. Final structural analysis, design decisions and professional responsibility remain with the client’s appropriately qualified engineer. Compatibility is confirmed through sample import into the agreed software version.
Can you work from LiDAR and field collection together?+
Yes. A pilot confirms identifiers, units, attachment rules, visible-versus-field attributes and how conflicts between sources are resolved.
Can outputs match our existing templates?+
Yes. We calibrate against your CAD layers, pole profile, attribute table, SHP schema, CSV columns and accepted example before scaling.
CALIBRATE BEFORE YOU SCALE
Define the source, output and review boundary.
Share a representative area, the working template and the acceptance conditions your team will use.