From 4cac523ada679fcc9cc91828d75c5ca41d404f0d Mon Sep 17 00:00:00 2001 From: "Philip Sargent (muscogee)" Date: Sun, 1 Mar 2020 17:46:05 +0000 Subject: [PATCH] Making the survey processing pipeline consistent and documented --- handbook/{ => computing}/exposerver.html | 0 handbook/{ => computing}/getsurvex.html | 0 handbook/{ => survey}/caveentry.html | 0 handbook/survey/drawup.htm | 110 ++++++++++++++++++----- handbook/survey/index.htm | 13 ++- handbook/survey/newrig.html | 44 +++++++++ handbook/survey/newsurvex.html | 92 +++++++------------ handbook/survey/newwallet.html | 7 +- handbook/survey/qmentry.html | 8 +- 9 files changed, 177 insertions(+), 97 deletions(-) rename handbook/{ => computing}/exposerver.html (100%) rename handbook/{ => computing}/getsurvex.html (100%) rename handbook/{ => survey}/caveentry.html (100%) create mode 100644 handbook/survey/newrig.html diff --git a/handbook/exposerver.html b/handbook/computing/exposerver.html similarity index 100% rename from handbook/exposerver.html rename to handbook/computing/exposerver.html diff --git a/handbook/getsurvex.html b/handbook/computing/getsurvex.html similarity index 100% rename from handbook/getsurvex.html rename to handbook/computing/getsurvex.html diff --git a/handbook/caveentry.html b/handbook/survey/caveentry.html similarity index 100% rename from handbook/caveentry.html rename to handbook/survey/caveentry.html diff --git a/handbook/survey/drawup.htm b/handbook/survey/drawup.htm index c9fc401ee..7566a450c 100644 --- a/handbook/survey/drawup.htm +++ b/handbook/survey/drawup.htm @@ -4,21 +4,99 @@ - -

CUCC Expo Surveying Handbook

+

CUCC Expedition Handbook - New Survex file

Drawing up your survey

+

Great, I have discovered a new cave...

+

If you have not come to this page from the sequence starting at Starting a New Cave" then go and read that first. + +

  • This page outlines the next step of the process. Each part of it is documented separately. + + +

    Process

    +

    +

    Drawing up your survey

    The original notes and sketches will be filed in a clearly marked -wallet - see "Creating a new cave" +wallet - see "Starting a new wallet" - don't take them out until you are ready to scan them, and put them away again as soon as you have finished. They may never be referred to again, but ultimately they are the most valuable record of your survey and are kept for reference if there is ever a problem.

    -

    After typing in all the data in +

    After typing in all the data in survex format , run - -aven (the GUI interface to survex) and print out a centre-line plan. + +aven (the GUI interface to survex) and print out a centre-line plan. + +

    OK if this is your first time doing this, you need to go through the +"How to use survex" training procedure. + +

    Running survex to create a centre-line

    +

    to be documented + + + +

    Transcribing and re-scanning your sketches

    +

    to be documented See drawing up the sketches. +

    The files of your scanned and re-scanned sketches should be stored in the same folder +as the scanned notes, i.e. (for wallet #19) you would put them in: + +/home/expo/expofiles/surveyscans/2018/2018#19/ + + +

    Using tunnel or therion for final survey production

    +

    to be documented +

    + +

    Tunnel only produces plan surveys, but they are very pretty. + +

    The tunnel (or therion) files should NOT stored in the same folder as the scanned notes. They should +be uploaded to the version control repository drawings, + + + +

    Guidebook description and final rigging guide

    + +

    This is the last thing to do - typically after all exploration has been finished for the summer. +The rigging guide sections will have been written into the logbook, and the passage descriptions will +have been written into the survex files, with more lyrical descriptions written into the logbook for each trip. +

    to be documented + +

    Write a passage descriptions by copying and extending the descriptions +given in all the component .svx files. +

    This should be detailed enough to be +followed by someone in the cave who hasn't been there before, and should +include all passage names, lengths of pitches and climbs, compass directions +when this makes left/right/ahead clearer. If your passage is a connection +it is worth while writing descriptions from both directions. + +

    In +written descriptions, underline passage names the first time they are +mentioned, or when they are "defined".

    + +

    +You will type this description, and pass it on to someone more nerdy who +will file it in the right place. This will involve "creating a new cave" using the troggle system. +

    to be documented + + +

    Complementing the passage description in vertical bits is a Rigging +Guide. This is usually easiest to do as a sketch, but include notes to +ensure that all bolts can be found again and any deviations and natural belays recognised. + + +

    to be completed + + + +

    OLD BIT

    Take the printed centre lines and redraw the survey round it, working from the original sketches as if this was to be the final published survey. You @@ -76,23 +154,9 @@ experience: it's now late April 2004, and the 204 survey is only just approaching completion. This shows how easy it is for these things to go wrong. The chief problems were a change of software and the fact that the Expo printer broke down last summer, so a number of surveys never got drawn up. --> -

    -
    • -
  • 2013 Training Course a slide-pack of a surveying course using Steinbruckhohle as the example
    • -
  • How to create a survex file
    • +
  • More resources on surveying
    • -
  • Older methods: -
  • GPS for Surveying: Coordinate Systems and how to convert between them
    • +
  • More obscure methods: +
  • GPS for Surveying: Austrian Coordinate Systems and how to convert between them
    • diff --git a/handbook/survey/newrig.html b/handbook/survey/newrig.html new file mode 100644 index 000000000..c0656aedf --- /dev/null +++ b/handbook/survey/newrig.html @@ -0,0 +1,44 @@ + + +CUCC Expo Surveying Handbook: Drawing Up + + + +

    CUCC Expedition Handbook - New rigging guide

    +

    New rigging guide

    + +

    Great, I have discovered a new cave...

    +

    If you have not come to this page from the sequence starting at Starting a New Cave" then go and read that first. + +

  • This page outlines the next step of the process. Each part of it is documented separately. + + +

    Process

    +

    + +

    Interim rigging guide

    +The logbook is the place where we record the rigging of caves as we discover them. + +When a cave is derigged, a good way of getting the rope lengths for your rigging guide is to leave the knots in ropes removed so they can be measured, but these days our caves are a bit deep and complicated for this to be feasible. Although a good survey and details of the belays can be used to estimate the length of rope needed, this is no substitute for measuring how much rope it actually took to rig. + +

    Final rigging guide

    + +

    Complementing the passage description in vertical bits is a Rigging +Guide. This is usually easiest to do as a sketch, but include notes to +ensure that all bolts can be found again and any deviations and natural belays recognised. +

    +You will already have an "Interim rigging guide" in the logbook entries of the trips, and also sketches on waterproof paper +which were made underground which were stored in the survey wallet and scanned to produce "notes-XXX.jpg" files in the online survey wallet for your trip. For small caves the logbook entry may be all you need. +

    Collect together your notes for the rigging guide now, including all the pitch lengths. It is a good idea to copy these notes now and put them in the plastic survey wallet or to photograph them and put the files in the online survey wallets. The next step can take some time so get the rigging data in order now. +

    You will enter the final rigging guide as part of the cave description when you edit the HTML pages for the online cave documentation. This is done using the "New Cave" online form.. + + + +

    +

    Back to the previous page in this sequence Drawing up your survey". +
    Now go the the next page in this sequence Filling in the "New Cave" form. +

    + + diff --git a/handbook/survey/newsurvex.html b/handbook/survey/newsurvex.html index 6eaf18b12..a7ab60d66 100644 --- a/handbook/survey/newsurvex.html +++ b/handbook/survey/newsurvex.html @@ -58,68 +58,42 @@ loser "caves-1623/264/mongolrally.svx". We are assuming that normal users have n worked with an distributed version control system at this point which is why we are only telling them to use the expo laptop.] -

    Ticking off QMs

    -

    To be written.

    - -

    Running survex to create a centre-line

    -

    to be documented - - - -

    Transcribing and re-scanning your sketches

    -

    to be documented See drawing up the sketches. -

    The files of your scanned and re-scanned sketches should be stored in the same folder -as the scanned notes, i.e. (for wallet #19) you would put them in: - -/home/expo/expofiles/surveyscans/2018/2018#19/ - - -

    Using tunnel or therion for final survey production

    -

    to be documented -

    - -

    Tunnel only produces plan surveys, but they are very pretty. - -

    The tunnel (or therion) files should NOT stored in the same folder as the scanned notes. They should -be uploaded to the version control repository drawings, - - - -

    Guidebook description and final rigging guide

    - -

    This is the last thing to do - typically after all exploration has been finished for the summer. -The rigging guide sections will have been written into the logbook, and the passage descriptions will -have been written into the survex files, with more lyrical descriptions written into the logbook for each trip. -

    to be documented - -

    Write a passage descriptions by copying and extending the descriptions -given in all the component .svx files. -

    This should be detailed enough to be -followed by someone in the cave who hasn't been there before, and should -include all passage names, lengths of pitches and climbs, compass directions -when this makes left/right/ahead clearer. If your passage is a connection -it is worth while writing descriptions from both directions. - -

    In -written descriptions, underline passage names the first time they are -mentioned, or when they are "defined".

    - +

    Entering the QM data

    -You will type this description, and pass it on to someone more nerdy who -will file it in the right place. This will involve "creating a new cave" using the troggle system. -

    to be documented + QMs are the unexplored leads, they are Question Marks because we don't + know where they go to. There is a specific format for recording them in survex files. +

    +

    + Read this separate description about + entering the QM data into a survex file. +

    +

    Entering the cave description in the survex file

    +

    The last part of the survex file is a description of the passage surveyed. Remember + that this is intended to be read by people + who have not been to that bit of the cave themselves + +;------------
    +;Cave description ;(leave commented-out)
    +; See 2017 description for details of GSH up to the 'p50'. +Briefly, on the way to couldashouldawoulda a 22 m entrance crawl from the +surface leads to a climb down and a junction. Left leads to easy c +rawling passage for a short distance, then another junction where +traversing over a shallow hole and down a stooping-height sandy +passage to a sharp left turn and a sandy, easy 'squeeze' leading to a +straighforward p10. +     +[from couldashouldawoulda_to_bathdodgersbypass.svx] +

    +

    + Note that the description is often written as one long line. Use the word-wrap capability in your editor + to make it easier for yourself. +

    -

    Complementing the passage description in vertical bits is a Rigging -Guide. This is usually easiest to do as a sketch, but include notes to -ensure that all bolts can be found again and any deviations and natural belays recognised. - - -

    to be completed +

    +

    Back to the previous page in this sequence + Creating a new survey wallet. +
    Now go the the next page in this sequence Drawing up your survey. diff --git a/handbook/survey/newwallet.html b/handbook/survey/newwallet.html index 09e7b6fff..77f7df06c 100644 --- a/handbook/survey/newwallet.html +++ b/handbook/survey/newwallet.html @@ -131,9 +131,12 @@ ensure that it is copied from the expo laptop to the expo server.

    If you are not in the potato hut then email all the .topo files to a friendly nerd (not necessarily on expo) who will upload them in the right place. +

    +

    Back to the previous page in this sequence + Creating a new cave in the online system. +
    Now go the the next page in this sequence Starting a new survex file". -

    Now go the the next page in this sequence Starting a new survex file". - +

    diff --git a/handbook/survey/qmentry.html b/handbook/survey/qmentry.html index 7c2347006..4ead8f5ac 100644 --- a/handbook/survey/qmentry.html +++ b/handbook/survey/qmentry.html @@ -7,7 +7,7 @@

    CUCC Expedition Handbook - New Cave - QMs

    -

    Adding QMs (Question Marks) and Cave Descriptions

    +

    Adding QMs (Question Marks)

    QM data and cave descriptions

    @@ -83,13 +83,9 @@ drawings correctly with this sort of thing.

    Conclusion

    Survey data recorded in .svx files is incomplete if there is no QM List data and cave description data! -

    Return to "Survey handbook - survex format".

    +

    Return to "Survey handbook - survex format".

    -