
A number of low-cost devices, including unmanned aircraft systems (UASs), smartphones and tablets, and external GNSS antennas, are adequate for conducting utility inspections. Most UAS applications used for inspections involve the use of small rotary platforms. Real-time kinematic (RTK) support is desirable but not essential if ground control points (GCPs) are used in the field. Recent smartphones and tablets have the capability to receive data from multiple GNSS constellations.
External GNSS antennas of interest here are devices and companion services that offer centimeter-level positional accuracy at lower costs than traditional GNSS equipment. A typical business model is one in which the cost of the GNSS antenna is low (say $500 to $5,000). The receiver provides a positional accuracy between 60 cm (2 ft) and 1.5 m (5 ft) in autonomous mode, but when connected to an RTK correction subscription service, the positional accuracy improves up to 1–3 cm horizontally and 1–10 cm vertically. RTK subscription rates range from $4,000 per year to $400 per month or $100 per day. Depending on the brand and model, GNSS receivers can connect to public RTK networks for free, but in other cases, users first must pay an unlocking or access fee to the GNSS vendor.
Mobile device data collection apps of interest are apps that enable users to complete activities such as the following:
Documenting offsets between planned and actual locations is critical for deciding whether to accept an installation as is or to require removal and reinstallation, and for preparing accurate, reliable as-built plans. Examples of relevant utility inspection activities include the following:
The following five basic data collection cases apply to one or more of the utility inspection activities listed above:
This case involves the inspector occupying one or more project SCPs to make sure the coordinate system parameters used for the data collection are consistent with those used for project survey
control (Figure 4). This is one of the first activities to complete at the job site. This case also provides an opportunity to verify the positional accuracy of the GNSS antenna by using the SCP coordinates the project surveyor has provided. The data collection procedure is as follows:
This use case involves having a georeferenced digital representation of the plans on the mobile device and using the stakeout tool of the data collection app to find the point feature and verify whether its location is within a prespecified tolerance (Figure 5). If the user does not have the design plans but has the planned coordinates of the point feature of interest, the stakeout tool can still be used to verify the location of the point feature.
If the location is within the required tolerance, the data collection procedure is as follows:
If the location is outside the required tolerance, the data collection procedure is as follows:
In certain cases, it is not possible to occupy the center of the point feature, but documenting a point around the perimeter is feasible. For example, for utility poles, it is common to document the point at the base of the pole that is closest to the highway. Using the pole diameter, it is then possible to calculate the coordinates of the center of the base of the pole.
This case involves having a georeferenced digital representation of the plans on the mobile device and using the line stakeout tool of the data collection app to find the line feature and verify whether its location is within a prespecified tolerance (Figure 6).
If the line feature is within the required tolerance, the data collection procedure is as follows:
If the line feature is outside the required tolerance, the data collection procedure is as follows:
The ASCE 75-22 consensus standard includes guidance regarding desired spacing between consecutive measurements for the purpose of developing as-built plans.
This case involves having a georeferenced digital representation of the plans on the mobile device and using the stakeout tool of the data collection app to find the corners of the polygon feature and verify whether its location is within a prespecified tolerance (Figure 7).
If the polygon feature is within the required tolerance, the data collection procedure is as follows:
If the polygon feature is outside the required tolerance, the data collection procedure is as follows:
This use case involves using a device such as a UAS or a smartphone to capture multiple images around the area of interest and processing the images using photogrammetry software (Figure 8). It may be possible to augment this capability by using LiDAR to generate point clouds and fuse the data with the results from the photogrammetric process. The result is a georeferenced 3D model of the feature of interest (and, by extension, the area surrounding the utility feature) that meets project datum requirements.
When using GCPs, the data collection procedure is as follows:
When using RTK, the data collection procedure is as follows:
In some cases, georeferencing is not a critical requirement, but other features in the scene (e.g., sidewalk edges, building facades, or edge of pavement) can be used to provide context and enable a quick assessment. The data collection procedure is as follows: