Case Study 4

Beware of straight-line HDD as-built data in your GIS platform

Reduct_Steel_Pipe_Vector_Image

– HDPE
– Ø 40mm (1.5”) ID

Reduct_Ruler_Vector_Image

– Length : 432m (1,417’)
– Depth : 15m (45’)

Reduct as-build HDD mapping false GIS information case

A telecom utility was requested to provide duct depth information to the waterway authorities ahead of a planned deepening of the canal that the duct crosses. The utility owner realized that for this particular HDD crossing the data stored in their GIS platform was unreliable, so they commissioned a gyro survey.

The mapping result proved this to be a wise decision because the actual location of the duct infrastructure was significantly different. In fact, the segment contained an HDD and subsequently a trenched segment back to the public road.

Reduct case study as-build and depth profile

Although this is an extreme case, all too often as-built data stored in GIS platforms is  as-planned/as-permitted data, or in case both of those are not available, a straight line between the nearest known manholes. At first sight straight lines may appear plausible for HDD segments, but in reality, and with 20+ years of data to prove it, they hardly ever are!

Resources

Discover
DR-2

Start typing and press Enter to search

Shopping Cart