Traverse DeskGet COGO
Direction and distance

Catch a packed DMS bearing before it moves a corner

A field-book entry of 12.3045 can mean two different angles. Work through the endpoint difference and a reliable import check.

Worked example12.3045 packed → 12°30′45″ → 12.5125°
On this pageDecode both readings explicitlyPredict the horizontal effectRun a reversible parsing testTest the formatting at its weakest points

A bearing column contains the number 12.3045. One program reads it as twelve point three zero four five degrees. The field-book convention used in this example means 12°30′45″. Both inputs are numerically valid and both point into the same quadrant. At 200 m they put a corner roughly 0.73 m apart.

Decode both readings explicitly

For packed degrees, minutes and seconds, treat the digits after the point as two digits of minutes followed by two digits of seconds. This interpretation requires a documented format. Here 30 minutes and 45 seconds become 30/60 + 45/3600 degrees. Add the whole 12 degrees and obtain 12.5125°.

For decimal degrees the full fraction is already a fraction of one degree. Multiply 0.3045 by 60 to get 18.27 minutes. The remaining 0.27 minute is 16.2 seconds. The decimal entry therefore describes 12°18′16.2″. The difference between the two directions is 0.2080°, or 12′28.8″. Nothing about the number alone identifies which convention the observer used.

Predict the horizontal effect

Consider two 200 m rays from the same origin, one using each direction. The endpoint separation is the chord across the small included angle. Use 2 × 200 × sin(0.208° / 2), giving about 0.726 m. As a quick estimate, convert 0.208° to radians and multiply by 200. The result agrees to the nearest millimetre. Doubling the length doubles the separation.

That is the change from one affected absolute bearing. If an entire imported list uses the wrong convention, individual changes vary with each row’s minutes and seconds. They may reinforce or cancel around a circuit. Treating the final misclosure as a single constant angular offset can hide the original input problem.

Run a reversible parsing test

Enter this synthetic four-course control loop in Traverse Desk. Each row specifies its quadrant, angle fields and horizontal distance. The distances alternate between 200 and 80 metres. Keeping the rectangle small enough to check by hand helps distinguish a parsing error from a problem in the rest of a job.

N 12-30-45 E, 200
S 77-29-15 E, 80
S 12-30-45 W, 200
N 77-29-15 W, 80

The opposite courses cancel. Now change just the first line to N 12.3045 E, 200. The meter-based result shows a gap of about 0.726 m. Restore the first line using N 12.5125 E, 200. The loop closes again. The input reference explains the accepted separated forms. Use an explicit separator when transferring sexagesimal angles.

Test the formatting at its weakest points

Choose at least one test row with nonzero seconds and one with minutes less than ten. A packed value such as 5.0304 needs both leading zeros in the fractional fields to mean 5°03′04″. A spreadsheet that displays fewer digits can lose a trailing zero that a fixed-width parser expects. Preserve the original text beside any conversion result.

Inspect minutes and seconds for values at or above 60. Those values cannot describe ordinary DMS fields and can expose a wrong hypothesis about the format. Valid-looking values below 60 still require provenance. A mixture of decimal and packed values can pass a purely numeric range test.

For the handoff, label the column with the representation, direction convention and unit. Include one original entry beside its expanded DMS and decimal-degree equivalents. That single equivalence gives the recipient a reliable check even if their import dialog uses different terminology.

Include the precision of the source when reporting the test. An entry rounded to four decimal degrees has a display interval of 0.0001°, or 0.36 arcseconds. Four places in packed DMS represent whole seconds when the fields use two digits each. Equal numbers of printed digits can therefore express different angular resolutions as well as different directions.

References

Check traverses offline with COGO