diff --git a/handbook/survey/qmentry.html b/handbook/survey/qmentry.html index aa0e80171..88013f2ab 100644 --- a/handbook/survey/qmentry.html +++ b/handbook/survey/qmentry.html @@ -138,29 +138,28 @@ real content replaces template text):
;[ QM2 B surveyname.5 - description of QM ] ;TICKed off QMs -; in the past, if another survey existed, the resolution-station -; field was filled in, e.g. +; if another later survey exists, the resolution-station +; field is filled in, e.g. ;[ QM2 B surveyname.5 anothersurvey.7 description of QM and description of progress ] -; or we can use the trial format -;Serial number TICK date resolution description -;[QM2 TICK 2022-07-20 This is an example ticked QM] +; or if there is no survey, but the QM is dead tehn repeat the original survey station: +;[ QM2 B surveyname.5 surveyname.5 description of QM resolution DATE and description of results ] -Since 2015 we have had no generally-agreed, well-documented or widely-practiced way of recording whether a QM has been ticked-off or not. +
In 2015 we had had no generally-agreed, well-documented or widely-practiced way of recording whether a QM has been ticked-off or not. -
In the past, this was done by +
We now do this by
In 2022 we had a proposal to add an extra line to the original survex file, now that survex files can be edited +
If the new QM is explored but is not worth surveying (e.g. a snow-filled drop which in a later year is seen to be just a pile of snow), then edit the original survex file to repeat the same survey satstion as the "resolution station" and put a comment with the date this was done and a reference to the logbook entry or wallet. + +
Better handling of historic QMs is a current, occasionally active, area of