Closures don't match map, oh no. What to do?
Well, change the text in the closure, of course.
I remember the DOS based COGO programs that were first used for closures printed out on long sheets of connected dot matrix printer paper. You could not change the text for the printing output and that was on purpose.
Closures don't match map, oh no.
-
Scott
- Posts: 261
- Joined: Mon Oct 11, 2004 11:52 am
- Location: Modesto, CA
Closures don't match map, oh no.
Last edited by Scott on Tue Jun 30, 2026 8:07 am, edited 4 times in total.
Scott DeLaMare
LS 8078
LS 8078
-
wingding
- Posts: 81
- Joined: Sun May 10, 2015 9:04 am
Re: Closures don't match map, oh no.
don't forget the 0.004' nudge to get 2 decimal distance closures that match.
-
steffan
- Posts: 269
- Joined: Wed Oct 10, 2007 2:44 pm
- Location: N CA
Re: Closures don't match map, oh no.
With GNSS survey methods being so prevalent I’m curious how many surveyors submit mapping that purposely contains misclosure due to convergence of the meridians with a basis of bearing of true north observed at all points of the survey?
Some years back the BLM, in cooperation with a university, developed a program called Cadastral Measurement Management (CMM) that produced true geodetic bearings for all boundaries resulting in anticipated misclosures.
I personally prefer this method rather than holding only one boundary as a basis of bearing or reporting as grid. Especially for larger surveys and where GNSS observations are predominantly utilized.
Some years back the BLM, in cooperation with a university, developed a program called Cadastral Measurement Management (CMM) that produced true geodetic bearings for all boundaries resulting in anticipated misclosures.
I personally prefer this method rather than holding only one boundary as a basis of bearing or reporting as grid. Especially for larger surveys and where GNSS observations are predominantly utilized.