Terrain comparison
and earthwork survey control.
A KM29+500 desktop pilot, the mathematics behind the comparison, and a proposed day-zero survey framework for ATAT.
Technical review · 17 October 2026 · Proposed workflow v1Explore two terrain comparisons, review how they were calculated, and see the control needed for future surveys.
01 / ComparisonCan we compare drone surveys with historical data we know little about?
We can compare their geometry. Using the differences as earthwork quantities also requires verified dates, survey control and height references.
No survey-grade accuracy has been established for this comparison. The differences show apparent terrain change. They may combine actual earthwork, reference offsets and differences in surface quality; their individual contributions have not yet been established.
Useful for: general progress communication, investor updates and directing technical review.
Insufficient for: establishing survey accuracy, certifying cut/fill, payment approval or replacing an independent volumetric audit.
It can flag areas to investigate. Using the results as earthwork quantities requires reconciled references, verified control and surfaces, agreed boundaries and an uncertainty assessment. The map’s appearance does not establish accuracy.
KM29+500 · Historical terrain and drone models
Compare the initial and progress surfaces, then the August and October drone models. Colors show elevation; both views use the same scale.
What does the historical pair tell us?
The two historical surfaces give apparent cut of 159,399.1 m³, apparent fill of 31.2 m³ and net change of −159,368.0 m³ on the 0.5 m grid. Negative net change means net lowering. Maximum sampled lowering is about 16.41 m.
The small positive volume is an apparent residual, not proof of actual placed fill. The figures are exploratory in-place terrain differences, not trucked quantities, compacted quantities, design quantities or payment certification.
What is needed before using drone-based quantities?
We have not reproduced an agreed ATAT quantity, validated either historical survey against independent field control, transformed the drone DTMs into Planas, or computed accepted drone volumes.
Different survey dates include real earthwork. A June-to-October surface difference cannot be interpreted as same-date survey error.
Source files and reference systems
| Surface / provenance | Geometry / resolution | Reference / interpretation |
|---|---|---|
Initial terrain · TN_INICIAL_CORTE_29+500.xml | 556 vertices; 1,059 face records. 1,019 active / 40 excluded. | Survey date unconfirmed. Declared EPSG:32614 retained; actual horizontal and height references unverified. |
Recorded progress · 260624_SUPERFICIE_AVANCE_CORTE_29+500.xml | 775 vertices; 1,473 face records. 1,443 active / 30 excluded. | June 24 appears in the filename; confirm acquisition date and accepted survey issue. |
| 33Visual · August 7 · KM28–30 | Numeric GeoTIFF DTM; native cells ≈7.68 cm. | EPSG:6369. Source reference confirmed by 33Visual: ITRF2008, epoch 2010.0, UTM 14N. Export has no explicit vertical CRS. |
| 33Visual · October 7 · KM27+500–30+500 | Numeric GeoTIFF DTM; native cells ≈7.01 cm. | Same declared horizontal CRS. Both drone exports cover the historical progress footprint in the initial numeric-XY sampling check. |
KM22–27 · Drone 2024 vs. drone 2026
October is higher across much of the shared area. How much is earthwork, and how much comes from the surveys’ height references?
Loading satellite context…
Satellite imagery is a location reference, not imagery from either survey date. Uncolored areas have no model data.
Compare an elevation profile
Cyan: June 2024 · dashed ochre: October 2026.
What explains the difference?
Earthwork, different height references, or both may contribute. We need unchanged ground and the survey records to separate them. No height correction has been applied.
These surveys are more than two years apart. They do not test repeatability over unchanged terrain.
Calculation and results
We sampled both DTMs onto matching 1 m and 0.5 m grids and subtracted June from October, using only valid shared cells. Original heights were retained.
| Grid | Shared area (m²) | Median Δz (m) | Mean Δz (m) |
|---|---|---|---|
| 1.0 m | 343,049.00 | +6.223 | +4.633 |
| 0.5 m | 342,972.25 | +6.220 | +4.634 |
Changing grid size barely changes the result. This checks numerical sensitivity; it does not establish field accuracy.
Bilinear resampling; no model registration, vertical transformation or bias correction. Map overlays are rendered at approximately 2 m; point inspection and profiles use the 8 m preview. Sources: EPSG:6369; vertical CRS unspecified. Basemap placement does not verify survey positioning.
Preliminary volume integration
The totals below include all shared valid terrain. Height references and the measurement boundary remain unconfirmed, so these are not accepted earthwork or payment quantities.
| Grid | Apparent lowering (m³) | Apparent raising (m³) | Net (m³) |
|---|---|---|---|
| 1.0 m | 355,551 | 1,944,986 | +1,589,435 |
| 0.5 m | 355,752 | 1,944,982 | +1,589,230 |
Terrain views
These terrain previews are embedded in this HTML and work without internet. The satellite basemap requires a connection.
North up. Both dates share the same height scale; differences saturate at ±25 m.
Can repeat drone flights support recurring volumetric audits?
Yes, provided each survey is checked against stable control and the uncertainty is suitable for the quantity being assessed. A repeat-flight test over unchanged ground establishes repeatability under the tested conditions; later surveys measure change against an accepted baseline.
1. Test repeatability without earthwork between flights
Select a representative area with stable ground, slopes and surfaces comparable to the production survey. Fly it independently at least twice within a short period, with no excavation, placement or other surface change between acquisitions. Retain the same verified control network, horizontal and height references, and independent checkpoints; document conditions for each flight.
Process each flight separately using a documented, consistent workflow. Check each DTM against reserved surveyed checkpoints before comparing the DTMs on the same valid-ground mask and measurement boundary. Do not use those checkpoints to adjust the models or force the surfaces to coincide.
ΔVrepeat = Σ(Δzᵢ × aᵢ)
With unchanged ground, the expected physical volume change is zero. Report the mean elevation difference, RMSE of the surface differences, difference map, and apparent cut, fill and net volume. A near-zero net can conceal opposing errors. These repeat-survey statistics describe agreement between flights; checkpoint residuals assess their agreement with independent survey control.
2. Apply the validated workflow to successive work periods
After accepting the baseline and test results, repeat acquisition and checkpoint verification for every reporting period. Calculate period-to-period and cumulative cut/fill within agreed boundaries, retaining source files, control observations, processing settings, exclusions, revisions and approvals. Recheck the method when equipment, control, terrain conditions or processing changes.
3. Judge whether the measured change is meaningful
Set acceptance criteria before the test, based on the intended engineering or commercial use. Evaluate volume uncertainty, including systematic bias and spatially correlated surface errors; do not treat all grid cells as independent or convert checkpoint RMSE directly into a volume tolerance. Changes comparable to the assessed uncertainty require further review.
The deliverable would combine side-by-side terrain views, an elevation-difference map, stable-ground profiles, independent checkpoint statistics and a cut/fill table for each period. This would demonstrate the method with measured evidence, without implying identical accuracy for every future mission. Technical background: USGS: repeat UAS topographic surveying; USGS: uncertainty in topographic change.
02 / MethodComparing historical and current surveys
A useful comparison needs compatible survey references and a clear definition of what is being measured. The checks below separate real earthwork from differences introduced by the surveys.
1. Dates, purpose and source records
Identify when each surface was surveyed, who produced it and which revision was accepted. Retain original LandXML/TIN or elevation rasters, survey reports, breaklines and exclusions; obtain field observations and processing records where available. Distinguish measured terrain from design surfaces. A filename alone does not establish a survey date.
2. Horizontal and height references
Document the datum/reference-frame realization, coordinate epoch, projection or local grid, axes and units for each survey. Confirm whether heights are ellipsoidal, orthometric or project elevations, including the geoid model, vertical datum, benchmarks and antenna-height convention. A matching EPSG code does not establish matching height references.
3. Common control and unchanged ground
Recover and verify surviving monuments and benchmarks. Survey common marks in the relevant systems and reserve independent points for validation. Unchanged ground may help diagnose offsets only after its stability is established. New measurements can check surviving evidence; they cannot independently verify ground that has already been excavated.
4. Transformation and local calibration
Establish whether a transformation is needed. A seven-parameter Helmert can relate 3D coordinate frames using three translations, three rotations and one scale factor. UTM-to-Planas localization may instead require a documented local-grid calibration and a separate height adjustment. Obtain the actual method, parameters, direction, units, rotation convention, reference epochs, residuals and valid corridor sections; verify them on points withheld from fitting. Do not substitute a terrain-wide median offset for this evidence.
5. Comparable ground surfaces
Compare ground with ground: review vegetation, structures, ground classification, breaklines, gaps and interpolated areas in both datasets. Preserve the original TIN geometry and exclusions. After reconciling references, use a documented common grid and valid-data mask; retain source resolution and resampling details. Agreement after resampling does not establish accuracy.
6. Measurement boundary and quantity definition
Agree the chainage limits, measurement polygon, excluded areas and cut/fill convention. Separate actual change between dates from disagreement between surveys. Define whether quantities are in-place, loose or compacted; apply only documented conversion factors. Shared data coverage is not automatically the contractual earthwork boundary.
7. Validation and uncertainty
Check transformed coordinates and terrain elevations against independent survey control. Report residuals, systematic offsets and spatial patterns, with control-survey uncertainty. Assess volume sensitivity to height bias, surface uncertainty and boundaries, including spatial correlation where relevant. Set tolerances for the intended use. Where historic control is missing, state what can be inferred and leave unsupported accuracy claims unassigned.
8. Reproducible calculation and review
Retain source versions, the transformation pipeline, validation results, masks, cell sizes and calculation settings. Deliver difference maps, profiles, separate cut/fill/net totals and an uncertainty statement for joint survey review. Record unresolved historical limitations. Establish a controlled new baseline for future monitoring without treating it as a reconstruction of the original terrain.
Current examples: original elevations retained; reference reconciliation and independent field validation remain pending. Numerical differences are available, but accepted historical-to-drone earthwork quantities have not been established.
Processing record for the examples shown
Preserve the evidence
Retain the source LandXML, DTM exports and original metadata. Record file identity, surface name, survey date, CRS, vertical reference, calibration section and approved revision. Work on derived copies.
Reconstruct the original TINs
Interpret LandXML point coordinates as northing, easting and elevation; store as E, N, Z. Use each original face’s connectivity. Omit faces flagged i="1"; do not create a new Delaunay triangulation or bridge excluded gaps.
Rasterize active triangles
Interpolate each active triangular facet using barycentric coordinates on a 0.5 × 0.5 m grid. Preserve NoData outside valid facets. This creates a numeric surface, not a color image.
Compare shared valid coverage
The historical grids have coincident 0.5 m cell centers. Use their intersection of valid cells; do not substitute zero for missing terrain. No resampling was needed for the original historical subtraction. No client-approved measurement polygon is assumed.
Integrate cut, fill and net
Subtract initial elevation from progress elevation, separate negative and positive differences, and sum difference × planimetric cell area. Keep cut and fill separate; net alone can conceal simultaneous excavation and placement.
Add drone terrain for review
Crop the August and October DTMs near the pilot without changing native heights, resolution or CRS. The viewer places all surfaces on a common numeric-XY preview grid. No section calibration, geoid correction or vertical shift has been applied.
Test numerical sensitivity
Re-interpolate the same active source triangles in Float64 at 1.0, 0.5 and 0.25 m. Compare grid-based quantities. This tests sampling effects, not field accuracy, datum validity or historical survey completeness.
Confirm survey references and quantity criteria
Verify common control and height references; agree the calculation polygon and exclusion areas; confirm dates and earthwork definition. Then compare with ATAT’s approved quantity and calculation method. Only after those gates should the drone surface replace or supplement historical progress terrain.
03 / MathematicsCalculation methods and coordinate transformations
TIN interpolation · used
The λ values are barycentric weights from the point’s XY position inside the original triangle. Non-negative weights keep interpolation within the facet. The triangle’s original boundary and exclusions are retained.
Elevation difference · used
Only cells valid in both surfaces enter the mask M. Δz < 0 indicates apparent cut; Δz > 0 indicates apparent fill. NoData is excluded, not treated as zero elevation.
Volume integration · used
Vfill = ΣM max(Δzᵢ,0)a
Vnet = Vfill − Vcut
This is plan-area integration of a raster DEM of difference. It approximates TIN-to-TIN volume; it is not an exact facet-overlay calculation. Swell, shrinkage, bulking and compaction factors are separate engineering inputs. A DTM is a 2.5D surface: it cannot resolve overhangs, vertical faces or ground beneath bridge decks from one elevation per XY. Photogrammetry does not measure ground hidden by vegetation; flag unsupported interpolation and supplement with ground survey where needed.
Local grid calibration · not yet applied
N′ = tN + s(E sinθ + N cosθ)
A candidate 2D similarity transformation uses translations, rotation and scale. Use centered coordinates for stable estimation; solve from verified common marks, weight observations appropriately and validate on withheld marks. ATAT’s section-specific calibration and boundary treatment must be verified; this formula is not an accepted corridor-wide conversion.
Seven-parameter transformation · method to be confirmed
X₁ and X₂ are 3D Cartesian coordinate vectors; T contains three translations, R combines three rotations, and s is the scale difference in ppm. Geodetic frame transformations normally use geocentric coordinates, with the required coordinate conversions and projections before and after. Rotation convention, units and epochs must be documented; time-dependent changes may require a rate model. This operation alone does not establish orthometric heights or define ATAT’s local-grid calibration. It has not been applied in these examples. PROJ · Helmert
Height reference · not yet reconciled
h is ellipsoidal height, H is orthometric height and N is geoid undulation. Identify the actual geoid/vertical datum or a documented project benchmark adjustment. Do not apply an arbitrary constant derived from changing construction terrain.
Independent accuracy testing · proposed
bz = Σez,i/n; RMSEz,fit = √(Σez,i²/n)
RMSEH,fit = √(RMSEE,fit² + RMSEN,fit²)
Calculate on independent checkpoints, not adjusted GCPs. Report bias, dispersion, extrema and spatial patterns. Raw checkpoint-fit RMSE is not automatically the final ASPRS product accuracy: checkpoint survey uncertainty must also be included under the adopted standard’s reporting procedure. [S1–S3]
04 / AccuracyHow accurate are these results?
Using a finer calculation grid changes the historical cut volume by only about 0.3 m³. That tells us the grid size has little effect on this result. We still need to check how well the source surveys match the ground and whether they use compatible coordinates and elevations. Until then, we cannot put a reliable error range on the volume or claim accuracy within ±5 cm or ±1%.
How much detail do the models contain?
The drone DTMs have cells about 7–8 cm wide. We calculated the historical volumes on a 50 cm grid and use a coarser, roughly 5 m grid for the viewer. Cell size describes the spacing of the data; it does not tell us how close the elevations are to the actual ground.
Does a finer grid change the volume?
For these historical surfaces, changing from 50 cm to 25 cm cells changes the cut volume by about 0.30 m³, out of roughly 159,400 m³. The calculation is consistent at these grid sizes. The source surveys could still contain errors.
How closely do the surveys match the ground?
We do not yet know for this comparison. We need to confirm the historical coordinate and elevation references and compare the surfaces with independently surveyed checkpoints.
Would another flight give the same result?
That needs to be tested with separate flights over ground that has not changed. We also need to assess how surface errors affect the total volume. Nearby cells can share the same error, so adding more cells does not necessarily improve accuracy.
What changes when we use a finer grid?
| Cell size | Shared area | Apparent cut | Apparent fill |
|---|---|---|---|
| 1 m | 21,862.00 m² | 159,400.36 m³ | 29.23 m³ |
| 0.5 m | 21,861.00 m² | 159,399.13 m³ | 31.16 m³ |
| 0.25 m | 21,855.19 m² | 159,398.83 m³ | 31.16 m³ |
We recalculated the original historical triangles at three grid sizes. The area changes slightly because each grid samples the surface edges differently. Similar totals show that grid size has little effect here; they do not verify the source surveys or establish an approved measurement boundary. [C1]
What if one surface is consistently too high?
+1,093 m³A uniform height offset changes the volume by area × offset. Across 21,861 m², even a small offset matters. This calculator illustrates the effect; it is not an error measured in these surveys.
How small a height change could we detect?
13.9 cmσΔz = √(σ₁² + σ₂² − 2Cov₁₂). For zero covariance and unbiased, approximately normal errors, an illustrative two-sided threshold is 1.96σΔz. With σ₁ = σ₂ = 5 cm, that is about 13.9 cm. This generic propagation example is not a measured ATAT threshold and does not include all horizontal/slope, interpolation, registration or vegetation effects. ASPRS Edition 2 reports positional classes in RMSE, not this 95% threshold. [S3]
05 / StakeholdersWho uses this information—and why?
Different decisions need different levels of accuracy. Agree the requirements before the survey.
| Audience | What it helps them do | What must be verified |
|---|---|---|
| Contractors and supervision | Track excavation, fill and work fronts. | Survey control, checkpoints and approved quantity calculations. |
| Budgeting and finance | Forecast costs and reconcile quantities. | Volume uncertainty suited to the decision; approved measurements for payment. |
| Authorities and auditors | Review work limits and compliance. | Evidence and tolerances required by the applicable permit or specification. |
| Shareholders and investors | Understand progress through maps, imagery and 3D views. | Correct dates and locations; validated sources for reported figures. |
| Engineering and asset teams | Check terrain, design interfaces and asset condition. | Task-specific tolerances; specialist monitoring where needed. |
Use one verified dataset, with reports tailored to each audience.
Technical requirements
Contractors and construction supervision
Survey-controlled geometry, independent checkpoints and an agreed measurement boundary and method. Payment quantities require accepted surfaces and stated volumetric uncertainty; a progress image alone does not substantiate a payable volume.
Estimating, cost control and finance
Match the quantity uncertainty to the financial exposure and decision. Preliminary forecasts can use clearly identified estimates; certified quantities and payment applications require the agreed measurement and approval procedure.
Government oversight, environmental compliance and audit
Follow the accuracy, timing, coverage and evidence requirements of the applicable permit, specification or authority. There is no universal “government compliance” tolerance. Photography and photogrammetry support the evidence package; some requirements also need field measurements or specialist inspection.
Shareholders, boards and investor relations
For visual reporting, prioritize correct dates, locations, representative coverage and clear annotations. Any stated percentage complete, volume or cost must be traceable to an appropriately validated source, with material limitations disclosed. A rendering is not evidence of geometric accuracy.
Engineering and asset management
Specify tolerances for the engineering decision and use a suitable measurement method. Small movements or structural performance may require dedicated geodetic, geotechnical or structural monitoring beyond the general corridor survey.
06 / Day zeroDay-zero baseline survey and permanent control
“Day zero” means an agreed monitoring baseline at the time it is surveyed. It is not a reconstruction of original natural ground. Establish the baseline, freeze its approved issue, and compare later epochs to it using the same verified reference framework.
A / Reference framework
33Visual continues ITRF2008, epoch 2010.0 / UTM 14N with RTK. ATAT topography verifies the actual project grid, section localizations, benchmark elevations and vertical datum. Preserve both source and project coordinates; document every operation.
B / Stable primary control
Recover and inspect mojoneras, monuments and concrete nails. Use redundant survey observations, independent setups, measured antenna heights and documented GNSS correction sources. Check closures and network adjustment; use total-station traverses and differential leveling where required. Monument count follows the network design, not the aerial target count.
C / Visible GCPs
Establish durable, high-contrast ground control targets tied to stable primary control. Survey each target center and its surface elevation. Use GCPs in bundle adjustment / aerial triangulation. Distribute across both corridor margins, block ends and elevation ranges; avoid a single near-collinear strip.
D / Independent checkpoints
Reserve separate surveyed points from localization, bundle adjustment, surface fitting and post hoc bias correction. Locate them to test the block between control locations. Use well-defined points for XY and suitable smooth, open ground for vertical checks, away from abrupt breaks; assess breaklines separately.
E / Accepted baseline
Acquire imagery with suitable geometry and overlap; preserve raw GNSS/RINEX, capture logs and processing settings. Classify ground, edit artifacts, preserve terrain breaklines and map occluded or interpolated areas. Test checkpoints and a no-change repeat block. Issue the baseline only after acceptance.
F / Repeated monitoring
Re-observe control stability, retain the same reference and versioned baseline, and use independently checked targets each epoch. Compare only common reliable ground inside approved polygons. Record actual intervention dates, ground changes, exclusions and uncertainty before releasing quantities.
ASPRS accuracy assessment
Thirty independent checkpoints is the standard starting sample for horizontal and non-vegetated vertical accuracy assessment of a defined small assessment dataset. A single set can serve both tests only where each point meets both requirements. Vegetated terrain requires its own appropriate assessment. A reduced sample must be identified and reported as such. [S1–S3]
Checkpoint survey accuracy must be at least twice as good as the required product accuracy in the assessed component. For an illustrative 5 cm product RMSE target, that implies checkpoint survey uncertainty no worse than 2.5 cm in the corresponding component—not an assumed RTK FIX quality. Define the target and demonstrate the survey uncertainty first. [S2]
ASPRS does not prescribe the following corridor GCP counts. They are an initial 33Visual engineering proposal to be tested. The pilot may need more targets for terrain, occlusion, independent sub-blocks or calibration transitions. RICS emphasizes independent verification, distribution and survey control of materially higher accuracy. [S4]
| Purpose | GCPs | Independent checkpoints | Reporting / decision |
|---|---|---|---|
| Day-zero validation pilot · ≈3 km block | Start with 8 | At least 30 for the defined assessment dataset | Test RTK-only and GCP-supported solutions against the same reserved checks. Select a configuration based on measured results, not a preselected minimum. |
| Routine weekly block · ≈2.5–3.1 km | Initial proposal: 6–8 | Initial proposal: 10–12 | Limited-sample operational QA. Do not label it a full 30-checkpoint assessment. More points if geometry or risk requires. |
| Formal testing of each mission | As validated by block geometry | 30 or more per dataset / applicable test | Meet distribution, independence, survey accuracy and reporting requirements. A day-zero assessment does not certify every later mission. |
Placement rule: bracket each block at its ends, spread control on both sides and at different elevations, add checks at calibration transitions and overlaps, and sample the interior between controls. For an 8-GCP pilot, a starting pattern is two near each end plus four interior targets. Accessibility and image visibility determine the final arrangement; no universal spacing is prescribed.
07 / Mission planningProposed control and checkpoint layout
This proposed layout covers four October 14–16 mission blocks at KM36–48, with 30 GCPs and 46 routine checkpoints. The map illustrates possible target distribution for field review. These locations have not been surveyed and are separate from the KM29+500 historical comparison. A formal accuracy-assessment pilot requires its own expanded set of independent checkpoints.
| Mission | GCP | CP | Calibration |
|---|---|---|---|
| KM36+300–KM39+000 | 8 | 12 | CAL 6 → CAL 7 |
| KM39+500–KM42+000 | 6 | 10 | CAL 7; transition near northern end requires confirmation |
| KM42+400–KM45+500 | 8 | 12 | CAL 8 → CAL 9; confirm chainage mapping |
| KM45+500–KM48+500 | 8 | 12 | CAL 9 — Zacapexco |
Satellite basemap: Mapbox. Planning coordinates and target register remain available without the basemap. Map labels use the selected language; point IDs and mission chainages remain unchanged.
Proposed target register · 76 locations
| Target | Mission | Role | Latitude | Longitude | Approx. route distance |
|---|---|---|---|---|---|
| KM36+300-KM39+000-GCP01 | KM36+300-KM39+000 | GCP | 19.59738700 | -99.41446709 | 72 m |
| KM36+300-KM39+000-GCP02 | KM36+300-KM39+000 | GCP | 19.59684439 | -99.41447126 | 72 m |
| KM36+300-KM39+000-GCP03 | KM36+300-KM39+000 | GCP | 19.60542897 | -99.43771787 | 2795 m |
| KM36+300-KM39+000-GCP04 | KM36+300-KM39+000 | GCP | 19.60503990 | -99.43811669 | 2795 m |
| KM36+300-KM39+000-GCP05 | KM36+300-KM39+000 | GCP | 19.59791629 | -99.41969037 | 631 m |
| KM36+300-KM39+000-GCP06 | KM36+300-KM39+000 | GCP | 19.59843765 | -99.42464754 | 1147 m |
| KM36+300-KM39+000-GCP07 | KM36+300-KM39+000 | GCP | 19.60215537 | -99.42860514 | 1720 m |
| KM36+300-KM39+000-GCP08 | KM36+300-KM39+000 | GCP | 19.60233964 | -99.43357716 | 2236 m |
| KM36+300-KM39+000-CP01 | KM36+300-KM39+000 | Checkpoint | 19.59694249 | -99.41492618 | 119 m |
| KM36+300-KM39+000-CP02 | KM36+300-KM39+000 | Checkpoint | 19.59738666 | -99.41718843 | 358 m |
| KM36+300-KM39+000-CP03 | KM36+300-KM39+000 | Checkpoint | 19.59741491 | -99.41947810 | 597 m |
| KM36+300-KM39+000-CP04 | KM36+300-KM39+000 | Checkpoint | 19.59821338 | -99.42163847 | 836 m |
| KM36+300-KM39+000-CP05 | KM36+300-KM39+000 | Checkpoint | 19.59824226 | -99.42398818 | 1075 m |
| KM36+300-KM39+000-CP06 | KM36+300-KM39+000 | Checkpoint | 19.59981926 | -99.42555648 | 1314 m |
| KM36+300-KM39+000-CP07 | KM36+300-KM39+000 | Checkpoint | 19.60110418 | -99.42735890 | 1553 m |
| KM36+300-KM39+000-CP08 | KM36+300-KM39+000 | Checkpoint | 19.60222158 | -99.42932223 | 1792 m |
| KM36+300-KM39+000-CP09 | KM36+300-KM39+000 | Checkpoint | 19.60217677 | -99.43162818 | 2031 m |
| KM36+300-KM39+000-CP10 | KM36+300-KM39+000 | Checkpoint | 19.60282477 | -99.43382794 | 2270 m |
| KM36+300-KM39+000-CP11 | KM36+300-KM39+000 | Checkpoint | 19.60333115 | -99.43604146 | 2509 m |
| KM36+300-KM39+000-CP12 | KM36+300-KM39+000 | Checkpoint | 19.60505964 | -99.43746093 | 2748 m |
| KM39+500-KM42+000-GCP01 | KM39+500-KM42+000 | GCP | 19.60935093 | -99.44204384 | 62 m |
| KM39+500-KM42+000-GCP02 | KM39+500-KM42+000 | GCP | 19.60899398 | -99.44240911 | 62 m |
| KM39+500-KM42+000-GCP03 | KM39+500-KM42+000 | GCP | 19.62107901 | -99.46072123 | 2433 m |
| KM39+500-KM42+000-GCP04 | KM39+500-KM42+000 | GCP | 19.62074380 | -99.46110875 | 2433 m |
| KM39+500-KM42+000-GCP05 | KM39+500-KM42+000 | GCP | 19.61425548 | -99.44781601 | 873 m |
| KM39+500-KM42+000-GCP06 | KM39+500-KM42+000 | GCP | 19.61711170 | -99.45433261 | 1622 m |
| KM39+500-KM42+000-CP01 | KM39+500-KM42+000 | Checkpoint | 19.60976372 | -99.44311366 | 175 m |
| KM39+500-KM42+000-CP02 | KM39+500-KM42+000 | Checkpoint | 19.61156516 | -99.44458702 | 424 m |
| KM39+500-KM42+000-CP03 | KM39+500-KM42+000 | Checkpoint | 19.61282058 | -99.44658437 | 674 m |
| KM39+500-KM42+000-CP04 | KM39+500-KM42+000 | Checkpoint | 19.61522547 | -99.44946967 | 1073 m |
| KM39+500-KM42+000-CP05 | KM39+500-KM42+000 | Checkpoint | 19.61575672 | -99.45132272 | 1273 m |
| KM39+500-KM42+000-CP06 | KM39+500-KM42+000 | Checkpoint | 19.61686857 | -99.45286026 | 1472 m |
| KM39+500-KM42+000-CP07 | KM39+500-KM42+000 | Checkpoint | 19.61802064 | -99.45597671 | 1822 m |
| KM39+500-KM42+000-CP08 | KM39+500-KM42+000 | Checkpoint | 19.61908719 | -99.45755345 | 2021 m |
| KM39+500-KM42+000-CP09 | KM39+500-KM42+000 | Checkpoint | 19.61963341 | -99.45938781 | 2221 m |
| KM39+500-KM42+000-CP10 | KM39+500-KM42+000 | Checkpoint | 19.62063607 | -99.46041313 | 2371 m |
| KM42+400-KM45+500-GCP01 | KM42+400-KM45+500 | GCP | 19.62529503 | -99.46161342 | 65 m |
| KM42+400-KM45+500-GCP02 | KM42+400-KM45+500 | GCP | 19.62537565 | -99.46217930 | 65 m |
| KM42+400-KM45+500-GCP03 | KM42+400-KM45+500 | GCP | 19.64540582 | -99.46567073 | 2536 m |
| KM42+400-KM45+500-GCP04 | KM42+400-KM45+500 | GCP | 19.64541773 | -99.46624290 | 2536 m |
| KM42+400-KM45+500-GCP05 | KM42+400-KM45+500 | GCP | 19.62975632 | -99.46263305 | 572 m |
| KM42+400-KM45+500-GCP06 | KM42+400-KM45+500 | GCP | 19.63370766 | -99.46278962 | 1041 m |
| KM42+400-KM45+500-GCP07 | KM42+400-KM45+500 | GCP | 19.63803042 | -99.46149947 | 1561 m |
| KM42+400-KM45+500-GCP08 | KM42+400-KM45+500 | GCP | 19.64134734 | -99.46405883 | 2029 m |
| KM42+400-KM45+500-CP01 | KM42+400-KM45+500 | Checkpoint | 19.62574930 | -99.46201884 | 108 m |
| KM42+400-KM45+500-CP02 | KM42+400-KM45+500 | Checkpoint | 19.62772601 | -99.46164264 | 325 m |
| KM42+400-KM45+500-CP03 | KM42+400-KM45+500 | Checkpoint | 19.62930731 | -99.46292017 | 542 m |
| KM42+400-KM45+500-CP04 | KM42+400-KM45+500 | Checkpoint | 19.63126604 | -99.46321670 | 759 m |
| KM42+400-KM45+500-CP05 | KM42+400-KM45+500 | Checkpoint | 19.63316505 | -99.46304905 | 976 m |
| KM42+400-KM45+500-CP06 | KM42+400-KM45+500 | Checkpoint | 19.63462281 | -99.46161935 | 1192 m |
| KM42+400-KM45+500-CP07 | KM42+400-KM45+500 | Checkpoint | 19.63659656 | -99.46171557 | 1409 m |
| KM42+400-KM45+500-CP08 | KM42+400-KM45+500 | Checkpoint | 19.63863485 | -99.46182857 | 1626 m |
| KM42+400-KM45+500-CP09 | KM42+400-KM45+500 | Checkpoint | 19.64015499 | -99.46281731 | 1843 m |
| KM42+400-KM45+500-CP10 | KM42+400-KM45+500 | Checkpoint | 19.64185307 | -99.46390976 | 2059 m |
| KM42+400-KM45+500-CP11 | KM42+400-KM45+500 | Checkpoint | 19.64306660 | -99.46557561 | 2276 m |
| KM42+400-KM45+500-CP12 | KM42+400-KM45+500 | Checkpoint | 19.64501589 | -99.46577995 | 2493 m |
| KM45+500-KM48+500-GCP01 | KM45+500-KM48+500 | GCP | 19.65060434 | -99.46348951 | 76 m |
| KM45+500-KM48+500-GCP02 | KM45+500-KM48+500 | GCP | 19.65050855 | -99.46405284 | 76 m |
| KM45+500-KM48+500-GCP03 | KM45+500-KM48+500 | GCP | 19.66123225 | -99.48193334 | 2963 m |
| KM45+500-KM48+500-GCP04 | KM45+500-KM48+500 | GCP | 19.66107889 | -99.48248236 | 2963 m |
| KM45+500-KM48+500-GCP05 | KM45+500-KM48+500 | GCP | 19.65350830 | -99.46790063 | 669 m |
| KM45+500-KM48+500-GCP06 | KM45+500-KM48+500 | GCP | 19.65127690 | -99.47254827 | 1216 m |
| KM45+500-KM48+500-GCP07 | KM45+500-KM48+500 | GCP | 19.65281748 | -99.47779796 | 1824 m |
| KM45+500-KM48+500-GCP08 | KM45+500-KM48+500 | GCP | 19.65583254 | -99.48213307 | 2371 m |
| KM45+500-KM48+500-CP01 | KM45+500-KM48+500 | Checkpoint | 19.65094700 | -99.46406288 | 127 m |
| KM45+500-KM48+500-CP02 | KM45+500-KM48+500 | Checkpoint | 19.65293762 | -99.46520145 | 380 m |
| KM45+500-KM48+500-CP03 | KM45+500-KM48+500 | Checkpoint | 19.65326738 | -99.46737834 | 633 m |
| KM45+500-KM48+500-CP04 | KM45+500-KM48+500 | Checkpoint | 19.65270547 | -99.46975238 | 886 m |
| KM45+500-KM48+500-CP05 | KM45+500-KM48+500 | Checkpoint | 19.65159872 | -99.47190008 | 1140 m |
| KM45+500-KM48+500-CP06 | KM45+500-KM48+500 | Checkpoint | 19.65138554 | -99.47433559 | 1393 m |
| KM45+500-KM48+500-CP07 | KM45+500-KM48+500 | Checkpoint | 19.65152302 | -99.47665913 | 1646 m |
| KM45+500-KM48+500-CP08 | KM45+500-KM48+500 | Checkpoint | 19.65316098 | -99.47843364 | 1900 m |
| KM45+500-KM48+500-CP09 | KM45+500-KM48+500 | Checkpoint | 19.65427728 | -99.48057586 | 2153 m |
| KM45+500-KM48+500-CP10 | KM45+500-KM48+500 | Checkpoint | 19.65618844 | -99.48168985 | 2406 m |
| KM45+500-KM48+500-CP11 | KM45+500-KM48+500 | Checkpoint | 19.65846810 | -99.48208667 | 2659 m |
| KM45+500-KM48+500-CP12 | KM45+500-KM48+500 | Checkpoint | 19.66076597 | -99.48189285 | 2913 m |
08 / AcceptanceSurvey acceptance and volume review
Identify the responsible parties and document completion of each review item. These checkboxes are an on-screen review aid, not survey acceptance, a shared database or a signed approval.
Required survey documentation
Coordinate and monument register; raw and adjusted survey observations; localization/vertical-reference record; GCP and checkpoint lists with surveyed uncertainties; baseline and epoch DTMs/TINs plus ground-classified point cloud where available; orthomosaic; breaklines and exclusion polygons; per-checkpoint residuals and accuracy statement; difference surface and cut/fill/net by agreed polygon; uncertainty notes; processing manifest and approved issue history.
Technical glossary · EN / ES
| English | Español |
|---|---|
| Survey control monument | Monumento de control / mojonera |
| Ground control point (GCP) | Punto de apoyo fotogramétrico / control terrestre |
| Independent checkpoint | Punto de comprobación independiente |
| Baseline / epoch | Línea base / época de levantamiento |
| Datum / coordinate epoch | Datum / época de coordenadas |
| Digital terrain model (DTM) | Modelo digital del terreno (MDT) |
| Digital surface model (DSM) | Modelo digital de superficie (MDS) |
| Triangulated irregular network (TIN) | Red irregular de triángulos (TIN) |
| Breakline | Línea de quiebre |
| Cut / fill / net | Corte / relleno / neto |
| In-place / loose / compacted volume | Volumen en banco / suelto / compactado |
| Accuracy / precision / repeatability | Exactitud / precisión / repetibilidad |
| Bias / uncertainty / RMSE | Sesgo / incertidumbre / raíz del error cuadrático medio |
09 / SourcesTechnical references and calculation record
Standards inform the proposed assessment, not certification of this pilot. Number and distribution of GCPs, permanent control design, day-zero gates and illustrative uncertainty examples are engineering recommendations for joint review.
- [S1] ASPRS · Positional Accuracy Standards, Edition 2, Version 2 (2024): official standards directory and download.
- [S2] ASPRS technical overview / PE&RS May 2025: checkpoint quality, uncertainty and reduced-sample reporting.
- [S3] USGS · Adoption of the 2024 ASPRS accuracy standard: RMSE reporting and updated assessment framework.
- [S4] RICS · Earth observation and aerial surveys, 6th edition: §§3.4–3.5, ground control and independent verification.
- [C1] This project · LandXML conversion, full-resolution historical subtraction and independent 1.0 / 0.5 / 0.25 m sensitivity calculation; no field accuracy test performed.
Source review: 17 October 2026. ASPRS/RICS are professional references; adoption does not substitute ATAT’s contractual acceptance requirements.
