LiDAR and Orthoimagery Reuse for a Solar-Site Base Map
A 60-acre solar project in the Hudson Valley needs a planimetric base map at 1 in = 100 ft and 1-ft contours. The client supplies a 2021 six-inch-GSD leaf-off orthophoto and a 2020 LiDAR point cloud at 2 points/m2 with a vendor-reported RMSEz of 0.15 ft. Your independent 18 checkpoints on open ground yield a mean vertical bias of +0.22 ft and an RMSEz of 0.31 ft; six checkpoints under shrub/scrub are outside 0.5 ft. The LiDAR was flown leaf-on. The site has about 12 ft of grade change and mapped wetlands. An existing USGS 10-m DEM is also offered. The client wants to avoid a new field survey and asks you to certify the existing data as adequate for construction layout.
1. Evaluate whether the supplied LiDAR and orthoimagery are adequate for the requested 1-ft contours and construction base map.
Read the worked answer
They are not adequate as supplied. The orthophoto can support planimetric features if its horizontal accuracy is independently checked, but it does not provide reliable bare-earth elevations under vegetation. The LiDAR vendor's reported RMSEz of 0.15 ft is not supported by your checkpoints: the +0.22-ft mean bias and 0.31-ft RMSEz exceed a reasonable budget for 1-ft contours, and the shrub/scrub errors above 0.5 ft show classification or vegetation-penetration problems. Leaf-on acquisition is a serious concern because returns may come from canopy rather than ground. A 1-ft contour interval generally calls for much better vertical control than a dataset with 0.31-ft RMSEz and a known bias. The USGS 10-m DEM is coarser and cannot rescue the project. Recommend either a new leaf-off LiDAR/acquisition with ground control and independent checkpoints, or a field survey of breaklines and spot elevations sufficient for the design. Do not certify the existing data for construction layout.
2. What datum, classification, and deliverable issues must be resolved before any map is produced?
Read the worked answer
First confirm the horizontal and vertical datums of each source. The orthophoto may be in a State Plane or UTM projection, while the LiDAR may be in ellipsoid heights or a different geoid model; mixing them without transformation will create systematic shifts. Check the LiDAR classification: ground points under shrub/scrub and along wetland edges must be separated from vegetation, and the leaf-on condition means the ground class may be sparse or wrong. Resolve the +0.22-ft bias by comparing to control and decide whether a corrector surface is defensible; do not simply shift the data without documenting it. For deliverables, specify the contour interval, horizontal accuracy, vertical accuracy, wetland boundary source, and a metadata statement. If the client wants certification, explain that certification must be based on your own quality control, not the vendor's claims. A limited field check can support a map of existing conditions, but construction layout requires design-grade control and monumented points.
3. How would you explain the risk to a client who wants to save the cost of a new survey?
Read the worked answer
Frame the risk in project terms, not in technical jargon. The existing data may be useful for screening, wetland delineation review, or preliminary layout, but it is not reliable enough for final grading, drainage design, or construction staking. A 1-ft contour map built from data with a 0.31-ft RMSEz and a +0.22-ft bias can misplace drainage flow, undercut a racking foundation, or create conflicts with wetland limits. The cost of rework, permit delay, or redesign usually exceeds the cost of a proper field survey. Offer a phased scope: use the existing orthophoto for planning, then perform field survey and control for the construction base. Put the limitations in writing and avoid a blanket certification. If the client still elects to use the existing data, document that decision, limit the intended use, and require an independent check before construction layout.