What you will learn
- What a monument record contains, and why history matters
- How control points differ from boundary markers in the database
- How recovery notes help the next crew find a marker faster
- How search by location, identifier, and job works
- What happens when a marker is disturbed, destroyed, or reset
What the project is
Survey monuments are physical markers in the ground: control points with known coordinates, and boundary markers set during surveys. Their value lies in being found again. A crew that can pull up a marker's last recovery note, its condition, and its coordinates saves a search that might otherwise take an hour or a return visit.
The database is the firm's memory for markers. Each record holds an identifier, coordinates, marker type, the job that set or found it, recovery notes, photos, and a status history. Over years, that history becomes one of the firm's most useful assets, because markers outlast individual jobs and individual staff.
Core features
Search by map and by identifier is the core: a crew on site should find nearby markers on a map, and the office should find a marker from an old plan reference. Recovery notes are the most valuable field, because they record access details, nearby landmarks, and the marker's condition in plain language. Status history tracks found, disturbed, destroyed, and reset events, so nobody relies on a marker that no longer exists.
- Map and identifier search for control points and boundary markers
- Recovery notes with access details, landmarks, and condition
- Status history: found, disturbed, destroyed, reset
- Photos of the marker and its surroundings
- Links to the jobs and plans that reference each marker
- Coordinate history showing every adjustment and its source
How it is built
Start by importing what the firm already holds: control point lists, old job files, and plan references. That import is the hard part, because marker identifiers are often inconsistent across decades of jobs. A matching pass, with human review of uncertain matches, is worth more than a fast automated import that merges the wrong markers.
- Gather existing control lists, job files, and plan references.
- Agree on an identifier scheme and match old records to it, with human review.
- Build the record store with search, map view, and status history.
- Add mobile access so crews can check and update records on site.
- Add quality checks for duplicate markers and coordinate outliers.
Technology considerations
Coordinates need their reference system stored with them, because the same marker can carry coordinates in different systems over its life, and mixing them silently creates errors. The database should record the system, the adjustment, and the date for every coordinate set, and show the current best value separately from the history.
Mobile access on site is where the database earns its keep, so the record view must be readable outdoors and updates must sync offline. A crew that cannot check a marker from the site will not use the system, and the history will stop growing.
Challenges to plan for
Identifier drift is the chronic problem. The same marker may appear under a plan number, a job number, and a control list number, and linking those without merging distinct markers takes care. Duplicate detection helps, but the final call on uncertain matches should stay with a surveyor.
- One marker recorded under several identifiers across old jobs
- Destroyed markers that remain in lists and waste crew time
- Coordinate sets in different reference systems for the same marker
- Recovery notes that are too vague to help the next crew
Who it is for, and its limits
This database fits survey firms with a long operating history and many repeat areas, government survey offices maintaining control networks, and engineering firms that rely on control points across projects.
It does not certify a marker. A record says what was found and when; the surveyor on the current job still verifies the marker before relying on it, and a disturbed or destroyed marker must be treated as such. Costs and timelines vary with record count and import condition, so confirm with a quote before budgeting.
Frequently asked questions
What is the difference between a control point and a boundary marker?
A control point carries known coordinates used as a survey reference. A boundary marker marks a property corner or line. The database holds both, but their use and verification differ.
Why does marker history matter?
Because markers are found, disturbed, and reset over decades. Knowing the last recovery, condition, and coordinate adjustment tells a crew whether to trust a marker or verify it first.
What happens when a marker is destroyed?
Its status is set to destroyed, with the date and evidence, so crews stop searching for it. The record is kept, not deleted, because old plans may still reference it.
Can crews update records from the field?
Yes, and they should. A recovery note written on site, with a photo, is far more useful than one reconstructed in the office days later.
How are duplicate marker records handled?
Duplicate detection flags likely matches for surveyor review. Merging is a professional judgment, not an automatic step, because merging the wrong markers corrupts the record.