Module 3: Control, Reconnaissance, and Field Survey

Module 3: Control, Reconnaissance, and Field Survey

$Learning Objectives$

Identify the reference system and control requirements before collecting property-boundary observations.
Plan reconnaissance that searches for monuments, occupation, access constraints, obstructions, and field hazards.
Select GNSS, total-station, traverse, or integrated methods based on site conditions and verification needs.
Collect redundant observations that allow independent checks rather than relying on a single instrument solution.
Maintain field notes, photographs, station information, and monument records that support later boundary analysis.

$Survey Control$

Survey control is the network or set of verified reference points and coordinate information used to establish position, orientation, and consistency for subsequent survey observations.

$Reconnaissance$

Reconnaissance is the deliberate pre-observation inspection of the site to locate likely boundary evidence, assess control and instrument conditions, identify access and hazards, and refine the field observation plan.

$Reference System Before Coordinates$

DENR Administrative Order No. 2007-29 uses the Philippine Reference System of 1992 (PRS92) as the reference framework for land surveys under that regulation. NAMRIA continues to identify PRS92 as the country's standard reference system for surveying and mapping, while its current PAGeNet real-time service exposes multiple reference frames, including PGD2020 and WGS84 variants.

Therefore, never infer the project frame merely from the fact that GNSS corrections came from PAGeNet. Before using supplied or observed coordinates, confirm the reference frame, projection or zone where applicable, coordinate convention and units, source of control, correction product, epoch or realization information when relevant, and any transformation/localization applied for the intended survey work.

A coordinate pair without its reference context is incomplete survey information.

$PRS92 and PAGeNet Handling Without Coordinate Drift$

PRS92 provides the national land-survey reference framework used by the cited DENR regulation, while PAGeNet supplies continuously operating GNSS reference-station services. PAGeNet's current real-time service can deliver corrections in more than one reference frame, including PGD2020 and WGS84 variants. Neither the network name nor a fixed RTK status makes an imported or observed coordinate self-explanatory.

For every coordinate dataset or GNSS control solution used in the project, retain the available metadata that defines its meaning, including:

stated reference system/datum and projection or zone when applicable;
coordinate order, units, and whether values are grid, ground, or transformed;
control point or reference-station identity and source;
correction service, reference frame/product, and observation mode used for GNSS work;
antenna/instrument setup information material to the observation;
transformation parameters or localization used between coordinate frames;
date and source of the coordinate record.

A coordinate transformation or localization should be treated as a documented survey operation, not an invisible CAD shift used only to make two datasets appear to coincide.

$Reference-Frame Verification Procedure$

STEP-BY-STEP

Identify the source frame. Determine what datum/reference system, projection or zone, units, and coordinate convention the supplied values use.
Identify the control realization. Record the monument, control source, PAGeNet/CORS reference, or other basis from which project position is derived.
Test known relationships. Compare independent control, baseline geometry, record bearings/distances, and parcel shape before using coordinates for stakeout.
Resolve transformations explicitly. If a transformation or localization is needed, preserve its parameters, source points, residuals, and intended area of use.
Verify after transformation. Check independent points or record relationships not used to create the transformation.
Label the deliverables. State the coordinate reference information needed for another competent surveyor to interpret the published values.

Field Method Selection

Select and verify a field method based on reference/control quality, visibility, obstruction, and whether one method can reliably cover the required observations. Start only after the reference framework and field conditions are understood. Combine GNSS with total-station/traverse work only when each method suits its assigned observations. If GNSS is unsuitable, exclude it; hold and revise the station/control plan when total-station coverage is insufficient.

$Control Assurance$

Do not assume a point is suitable control because it has coordinates painted on a marker or listed in an old file. Verify:

point identity and physical condition;
source and reference system;
agreement with independent known or checked control;
orientation or baseline consistency;
observation quality and repeatability;
transformation parameters when different coordinate systems are involved;
whether the control geometry is adequate for the parcel and required accuracy.

Where GNSS corrections are used, understand the correction source and preserve enough observation metadata to reproduce the setup.

$Horizontal Check-Point Residual$

A horizontal check-point residual is the difference between an independently observed horizontal position and the accepted reference coordinates for the same known point; its magnitude summarizes the planimetric separation between them.

Horizontal Check-Point Residual

Compute the planimetric difference between an observed check point and its accepted reference coordinates.

\begin{aligned} \Delta E &= E_{\text{obs}}-E_{\text{ref}}, \\ \Delta N &= N_{\text{obs}}-N_{\text{ref}}, \\ r_h &= \sqrt{(\Delta E)^2+(\Delta N)^2} \end{aligned}

Variables

Symbol	Description	Unit
$\Delta E$	Observed minus reference easting	m
$\Delta N$	Observed minus reference northing	m
$r_h$	Horizontal residual magnitude	m

$Independent Control-Check Acceptance Procedure$

STEP-BY-STEP

Identify the criterion first. Determine the current regulation, project specification, or survey instruction that defines the required check and acceptance limit for the method and purpose.
Confirm coordinate comparability. Verify that the observed and reference coordinates use the same reference frame, projection, coordinate order, and units, or document and validate any required transformation.
Observe independent check points. Use known points not used to establish the setup or transformation whenever the task allows; retain the raw observations and setup metadata.
Compute each residual. Calculate $\Delta E$ , $\Delta N$ , and $r_h$ separately for every required check point.
Apply the stated criterion. Proceed only when all required checks meet the applicable limit. If no applicable criterion is known, or any check fails, hold boundary staking, investigate, and seek direction from the responsible Geodetic Engineer or competent authority.
Preserve the audit trail. Keep failed as well as repeated observations, along with the correction, reoccupation, and acceptance decision.

$Acceptance Limits Must Be Project- and Method-Specific$

Do not invent one universal RTK, GNSS, or traverse tolerance. Use the applicable current regulation and project requirements. A fixed solution or a small residual by itself does not establish that a survey meets the required accuracy.

Independent Control-Check Acceptance

Use the current regulation, project specification, or survey instruction for this method and purpose; do not assume a universal tolerance. Compare like-for-like coordinates or document and validate any transformation. Where the task allows, check points independent of the setup and transformation. Compute ΔE, ΔN, and the horizontal residual for every required point, retain failed and repeated observations, and hold staking until the check basis is verified and the stated criterion is met or the responsible Geodetic Engineer or competent authority directs the next step.

Survey Control Assurance Stack

A coordinate becomes useful control only when its identity, reference frame, observation quality, and independent checks are credible.

The control stack progresses from identity to independent verification; weakness at a lower layer undermines later property-corner coordinates.

Point identity and condition

Reference system and source

Independent positional check

Orientation / baseline consistency

Documented observation quality

$Reconnaissance Is an Evidence Search$

Before setting up instruments, walk the parcel and surrounding area where access is authorized. Look for:

existing corner monuments and witness/reference marks;
adjoining monuments that may support common-line analysis;
fences, walls, buildings, roads, ditches, waterways, and occupation lines;
disturbed ground, recent construction, or signs a monument may have been moved;
sky visibility, multipath risks, and GNSS obstructions;
line-of-sight opportunities for total-station work;
stable instrument stations and safe crew positions;
access limitations, vegetation, traffic, animals, utilities, or other hazards.

Record what was searched even when nothing is found.

Reconnaissance-to-Observation Sequence

Search first, then choose stations and observations around the evidence actually present.

Reconnaissance converts the office prediction into a field search and observation plan.

Walk and orient the site

Search expected corner areas

Inspect occupation and obstructions

Select control / stations

Finalize observation plan

$GNSS/RTK Use$

GNSS is powerful when satellite visibility, correction quality, control, and multipath conditions are suitable. Good practice includes:

checking solution status and quality indicators;
repeating occupations or using independent check points;
avoiding blind acceptance of one fixed solution;
documenting antenna height and setup;
testing against known control;
recognizing canopy, structures, walls, vehicles, and electromagnetic or reflective environments that can degrade observations;
using total-station observations when line-of-sight methods provide a stronger solution.

GNSS should support boundary evidence analysis, not replace it.

$Total Station and Traverse Use$

Total stations are useful for controlled angular and distance observations, especially where GNSS visibility is poor. A robust setup includes:

accurate centering and leveling;
verified station identity and coordinates;
checked backsight/orientation;
redundant angular or distance observations as appropriate;
closure to known/check control where possible;
documented prism constants, heights, and instrument settings;
independent check shots to critical points.

An integrated GNSS-plus-total-station survey is often stronger than forcing one method into every site condition.

GNSS-Favorable Versus Total-Station-Favorable Conditions

Instrument choice should follow geometry and site conditions rather than habit.

The comparison shows when each method is naturally strong and when integration is preferable.

GNSS / RTK Favors

Open sky
Reliable correction/control
Efficient distributed control
Longer intervisibility not required

Total Station / Traverse Favors

Urban/canopy obstruction
Precise local line-of-sight
Corners near walls or structures
Integrated traverse/check geometry

$Field Evidence Documentation$

For every corner search or observed feature, record enough information that another surveyor can understand what happened:

corner/feature identifier;
found/not-found status;
monument type, markings, dimensions, condition, and apparent disturbance;
measured coordinates or ties;
station and observation method;
photographs with useful context;
reference/witness measurements;
nearby occupation features;
date, crew, instrument, and relevant environmental conditions;
remarks explaining ambiguity or limitations.

Avoid notes such as “corner OK” without the evidence supporting that statement.

Field Evidence Capture Grid

Each boundary observation should connect identity, condition, measurement, and contextual documentation.

The evidence grid separates the object itself from the measurement and documentation needed to evaluate it later.

Corner / feature identity

Monument condition

Coordinates and ties

Observation method

Photographs / sketch

Occupation and remarks

$Redundancy and Independent Checks$

A property survey should contain observations that can expose mistakes. Examples include:

reoccupying a critical GNSS point;
checking a rover solution against known control;
closing a traverse;
observing a corner from more than one setup;
measuring a known distance or common line independently;
inverse-checking measured coordinates against direct field measurements;
comparing field geometry with the approved record before leaving site.

Redundancy is not waste; it is evidence that the observation can survive review.

$A Fixed GNSS Solution Is Not a Boundary Decision$

A technically good coordinate observation answers where the receiver was. Boundary determination still requires the surveyor to reconcile the observation with the approved record, control, monuments, adjoining evidence, and the purpose of the survey.

Key Takeaways

Verify the coordinate reference and control before trusting parcel coordinates.
Reconnaissance is a structured search for boundary evidence and survey constraints.
Choose GNSS, total station, or integrated methods based on field conditions and checkability.
Redundant observations are essential for detecting blunders and supporting professional review.
Field notes, photographs, monument descriptions, and raw observations form part of the defensible survey record.

$References$

DENR Administrative Order No. 2007-29 — Revised Regulations on Land Surveys — Department of Environment and Natural Resources.
NAMRIA Projects — Philippine Reference System of 1992 — National Mapping and Resource Information Authority.
PAGeNet Frequently Asked Questions — NAMRIA Philippine Active Geodetic Network.
PAGeNet Services and Fees — Current Reference Frames and RTK Products — NAMRIA Philippine Active Geodetic Network.
Republic Act No. 8560 — Philippine Geodetic Engineering Act of 1998 — Lawphil / Congress of the Philippines.

Previous TopicModule 2: Titles, Technical Descriptions, and Record Research - Worked Examples

Quiz Me

Next TopicModule 3: Control, Reconnaissance, and Field Survey - Worked Examples

Prev Next

Quiz Me