26 October 2026
Boundary beacon vs gazette line: why they don't always match

Every ranger who's walked a line with a GPS unit has hit this at some point: the beacon says one thing, the gazette map says another, and somewhere in between is a cassava patch that's either inside the park or outside it depending on which line you trust.
What a boundary beacon is
A boundary beacon (sometimes called a boundary pillar, corner beacon, or just "the marker") is the physical object placed in the ground to show where a surveyed line runs. Concrete pillar, painted rock, metal pipe set in cement, whatever the survey department used at the time. It's meant to be the ground truth version of a line that otherwise only exists as coordinates and bearings in a document.
The gazette notice is the legal version. It's the instrument that establishes the protected area, usually with a schedule of beacon numbers, bearings, and distances, or a plotted map attached as a schedule. In theory the gazette describes the beacons and the beacons mark the gazette. In practice those two things drift apart, sometimes by a few meters, sometimes by a few hundred.
Why the two don't line up
A few reasons, and usually it's more than one at once:
The original survey was never that precise. A lot of gazettement happened decades ago using chain-and-compass or early theodolite surveys, sometimes on a local datum that was never properly tied into a national grid. The bearings and distances in the schedule were good enough for the paperwork at the time. They were not good enough to put a line within a meter on the ground today.
Beacons move, get destroyed, or were never maintained. Concrete pillars sink, get buried under silt, get knocked over by vehicles or elephants, or get deliberately shifted by someone who wants their field on the park side of the line to fall outside it instead. A missing beacon often gets "re-established" years later from memory or from the nearest surviving neighbor, which introduces its own error.
Re-plotting onto modern coordinate systems introduces drift. When an old gazette schedule gets digitized and converted from the original datum to WGS84 for a GIS layer, small projection and transformation errors creep in. On a map that looks fine. On the ground, at the edge of a 50-meter-wide contested strip, that drift decides whether a plot is a violation or not.
The gazette map and the gazette text sometimes disagree with each other. It happens more often than anyone likes to admit: the attached map and the written schedule of bearings were drawn up by different people at different times, and nobody reconciled them before publication.
None of this is an argument for ignoring beacons. It's the reason most authorities treat the beacon as the primary legal evidence of the line and the GIS boundary as a working approximation that needs field verification wherever a dispute shows up. If you're drafting a boundary dispute report or pushing back on an encroachment claim, the beacon position (or a properly surveyed re-establishment of it) usually carries more legal weight than a polygon pulled from an old shapefile.
What this means for patrol and monitoring work
Your GIS boundary, the one used for monitoring and for flagging new activity inside the line, is only as good as the survey it came from. If that boundary sits 30 meters off from where the beacons sit on the ground, you'll get false positives on one side (flagging land that's legally outside the park) and missed activity on the other (clearing that's inside the real line but outside your digitized one).
Knowing where your line actually sits is a separate problem from catching new clearing, roads, or cultivation once that line is settled. Encroachment Alerting runs your digitized boundary against a monthly satellite pass and flags where something's changed inside it, so patrol time goes to the spots that moved, not the whole perimeter. It won't fix a bad survey, but it will tell you exactly where to send someone to check a beacon against what's growing in the ground around it.
If your boundary layer is solid and you just want to know where it's being tested this month, that's the gap this is built for.