expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-27 01:32:03 +00:00
Code Issues Packages Projects Releases Wiki Activity
6164db9c11
expoweb/handbook/survey/qmentry.html

128 lines
6.6 KiB
HTML
Raw Normal View History

QMs in svx files
2020-01-03 02:56:23 +00:00
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
Wallt docm re Upload Form
2022-03-19 22:10:27 +00:00
<title>Handbook - survex - QMs</title>
QMs in svx files
2020-01-03 02:56:23 +00:00
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook - New Cave - QMs</h2>
Making the survey processing pipeline consistent and documented
2020-03-01 17:46:05 +00:00
<h1>Adding QMs (Question Marks)</h1>
QMs in svx files
2020-01-03 02:56:23 +00:00
<h2>QM data and cave descriptions</h2>
<p>
Docs on QM code status, troggle redesign
2020-05-14 22:28:13 +01:00
This document describes how to include Question Marks (QMs) and cave descriptions in .svx files.
QMs in svx files
2020-01-03 02:56:23 +00:00
<p>There
are dedicated fields in the template.svx file for this purpose, but there has been laxness recently on filling them in.
It seems to be an unknown resource among too many expo-goers despite the manifold benefits.
<h3>Why do we want to do this?</h3>
<p>
We need to store Question Marks (QMs) and cave description data in an easy-to-use format for setting objectives and
planning trips.
<p>When planning an expo, it is necessary to work out where leads are in each cave before
arriving in Austria to make effective use of time and equipment. The most readily
accessible place for such information is in .svx files, because this is more efficient
compared to including QMs only in survey drawings in Tunnel or writing a cave
description then putting it on the expo website.
<p>Svx files are a very stable place to store the data long-
weird characters replaced by UTF-8
2022-03-31 00:22:05 +01:00
term: there is no need to rely on a ‘master file' of any kind, which can be problematic if not everyone
QMs in svx files
2020-01-03 02:56:23 +00:00
on expo has the same level of computer literacy, and requires just basic text entry to create and update
the data after a trip.
weird characters replaced by UTF-8
2022-03-31 00:22:05 +01:00
<h3>How it's done:</h3>
QMs in svx files
2020-01-03 02:56:23 +00:00
<p>
weird characters replaced by UTF-8
2022-03-31 00:22:05 +01:00
So, you've got your .svx file started (if entering new data), or located and opened (if updating a
QMs in svx files
2020-01-03 02:56:23 +00:00
previously surveyed bit of cave after checking out some QMs again), and it looks a bit like this (visual
format will change depending on your preferred text editor):
<p>
<img src="wob-svx-edit-pic.jpg" width=900>
<p>
weird characters replaced by UTF-8
2022-03-31 00:22:05 +01:00
If you don't understand what is in front of you here, then you need to read the <a href="newcave.html#survexformat">survey handbook guide on svx files</a> which will lead you to the survex documentation, or ask
QMs in svx files
2020-01-03 02:56:23 +00:00
someone about basic entry of survey leg and station data into the .svx file format.
<p>
Near to the end of the text in the file, you will see a section that looks like this:
<p>
<img src="wob-svx-edit-pic2.jpg" width=900>
<p>
This is where the action is! You literally just follow the instructions in the file to create QM and cave
description data, replacing the template text with your own as you would with the cave passage data.
<p style="margin:4%">
<em>Technical Note:</em> The syntax for a QM includes a leading semi-colon. So it is syntactically a "comment" so far as the survex software is concerned. But we have other software and scripts in the Expo online system which inderstand just fine that these are QMs.
<p>
Here is an example from the last bit of bipedalpassage.svx in 264. Note that each QM description is all on one line.
<pre><code>;-----------
;Question Mark List ;(leave commented-out)
<em>;Serial number grade(A/B/C/X) nearest-station resolution-station description</em>
;QM1 A bipedalpassage.1 - Very good. 50m+ (?) deep pit below start of 13 bolt bipedal traverse - rather slanted, large ongoing rift glimpsed below. very good.
;QM2 A bipedalpassage.3 - Very good. 50m+ (?) deep pit below end of 13 bolt bipedal traverse. best approched via station 4 (?) and looks ok to rig. May connect to first deep pit.
;QM3 C bipedalpassage.1 - Poor c lead, across thin rock bridge over abyss (!) leads to blind aven, but small tube for thin person on left.
;QM4 A bipedalpassage.10 - Good. Ongoing big phreatic passage forms pitch dropped in Bipedal Passage4 by Ben, then continued by Mike and Elain on Aug 6th.
;QM5 C bipedalpassage.9 - Speculative - climb up needs short 5-10m rope - could be tube in roof.
;QM6 C bipedalpassage.31 - Very good location where main phreatic passages and enlarges - but far side of chamber choked. One part of choke was not accessed as needs 2m climb up to poke nose in it. A good free climber could do this or needs one bolt to be sure no way on. Very strong draft in choke! Interesting southerly trend at margin of known system
</code></pre>
Docs on QM code status, troggle redesign
2020-05-14 22:28:13 +01:00
<p>
The format for question mark lists is <br>
<ul>
QM refresh 3 perl scripts
2021-12-30 14:56:05 +00:00
<li>QM identifier, <li><a href="qm.html">Quality Grade</a>, <li>Area indicator, <li>description of QM.
Docs on QM code status, troggle redesign
2020-05-14 22:28:13 +01:00
</ul>
missed marking some stuff as obsolete
2020-05-14 22:53:22 +01:00
<p>The QM numbers themselves used to be in the format <br>
Docs on QM code status, troggle redesign
2020-05-14 22:28:13 +01:00
<ul>
QM refresh 3 perl scripts
2021-12-30 14:56:05 +00:00
<li><a href="qm.html">Discoverer identifier</a>, <li>Year of discovery, <li>Cave identifier, <li>serial number.
Docs on QM code status, troggle redesign
2020-05-14 22:28:13 +01:00
</ul>
Wallt docm re Upload Form
2022-03-19 22:10:27 +00:00
but today, with the QMs inside the survex files, the identifiers are QM1, QM2 etc.
moe QM bits
2021-12-30 16:20:45 +00:00
<p>This format is <a href="qm.html">documented in the original QM conventions</a> page.
Docs on QM code status, troggle redesign
2020-05-14 22:28:13 +01:00
Wallt docm re Upload Form
2022-03-19 22:10:27 +00:00
<style>figure {font-weight: bold; font-size: small; font-family: sans-serif;font-variant-caps: small-caps;}</style>
<div class="onright">
<figure>
<a href="cavedescription.html">
<img src="../t/svx-cave-descript.jpg"></a>
<figcaption style="font-variant-caps: small-caps;">
<em>Cave description in survex file (click for more)</em>
</figcaption>
</figure>
</div>
<h4>Cave Descriptions</h4>
<p>The description of the passage is written in the same way as you write QMs, but as free text without
formatting. See the single line at the bottom of the figure below and
in more detail on the <a href="cavedescription.html">Cave Description"</a> handbook page.
<h4 id="example">Full QMs example</h4>
QMs in svx files
2020-01-03 02:56:23 +00:00
<p>
Wallt docm re Upload Form
2022-03-19 22:10:27 +00:00
The example below demonstrates correct and effective use of the QM list referring back to earlier elements in the svx file.
Cave descriptions are done in a similar way, see the <a href="cavedescription.html">Cave Description"</a> handbook page.
QMs in svx files
2020-01-03 02:56:23 +00:00
<p>
<img src="wob-svx-edit-pic3.jpg" width=900>
<p>
If these data are not entered along with the rest of the survey data, it is as if you decided not to enter
some of the actual passage data you surveyed: information is being lost and someone will have to
trawl back through all the survey data at a later time to keep it up-to-date, a very tedious task which
is a very inefficient use of time.
weird characters replaced by UTF-8
2022-03-31 00:22:05 +01:00
<p>Also if the person reading it hasn't been to the bit of cave (which is, like, <em>the whole point</em>, then the data has a higher chance of being incorrect. It is not always easy to interpret Tunnel or Therion
QMs in svx files
2020-01-03 02:56:23 +00:00
drawings correctly with this sort of thing.
Docs on QM code status, troggle redesign
2020-05-14 22:28:13 +01:00
<h3>Programming note</h3>
<p>Better handling of historic QMs is a current, occasionally active, area of
development in our online systems. The current status is <a href="../troggle/scriptsqms.html">documented here</a>.
QMs in svx files
2020-01-03 02:56:23 +00:00
<h3>Conclusion</h3>
<p>Survey data recorded in .svx files is incomplete if there is no QM List data and
cave description data!
<hr />
Wallt docm re Upload Form
2022-03-19 22:10:27 +00:00
<p>Return to "<a href="newsurvex.html">Survey handbook - survex format</a>".</p>
QMs in svx files
2020-01-03 02:56:23 +00:00
</body>
</html>
Reference in New Issue Copy Permalink