expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-09 07:14:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

QM refresh 3 perl scripts

Browse Source
This commit is contained in:
Philip Sargent
2021-12-30 14:56:05 +00:00
parent 40d307ba4c
commit ef5e5e9509
12 changed files with 782 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/survey/newsurvex.html
View File

@@ -95,7 +95,7 @@ scan it again and then use that scanned image to digitise passage layout into tu
worked with an distributed version control system at this point which is why we are only
telling them to use the <em>expo laptop</em>.]
<h3><a id="tickingoff">Entering the QM data</a></h3>
<h3><a id="tickqm">Entering the QM data</a></h3>
<p>
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.

88
handbook/survey/qm.html Normal file
View File

@@ -0,0 +1,88 @@
<!DOCTYPE html">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" type="text/css" href="/css/main2.css" />
<title>CUCC Austria Expeditions: QM list conventions</title>
</head>
<body>
<h1>Question Mark list conventions</h1>
<p>This page is somewhat outdated. For the current 21st century QM methods,
where we store QMs in the survex files, see
<ul>
<li><a href="qmentry.html">QM data and cave descriptions</a>
<li><a href="newsurvex.html#tickqm">Entering the QM data</a>
<li>Only if really keen: <a href="../troggle/scriptsqms.html">QMs - the fourfold path</a>
</ul>
<p>The format for question mark lists is QM identifier, Quality Grade, Area
indicator, decription of QM. The QM numbers themselves are in the format
Discoverer identifier, Year of discovery, Cave identifier, serial number.
<p>[Archaic: If
you look at the html, you will find that the nearest survey station (without
its "&lt;cavenumber&gt;." prefix) is included in an html comment for almost all
leads.]</p>
<p>In general, an unpushed QM will have a link from its QM number in the
cave description file to the list (generated by a perl script), and a link from the list to the relevant point in the
description. If there is no link, it means that I can't yet work out where the
QM is in the description, or the description doesn't yet exist :-).</p>
<h2>Discoverer identifiers</h2>
<dl>
<dt>A</dt>
<dd>ARGE</dd>
<dt>B</dt>
<dd>Groupe Sp&eacute;l&eacute;o de Clerval - Baume les Dames </dd>
<dt>C</dt>
<dd>Cambridge University Caving Club</dd>
</dl>
<h2>Quality grades</h2>
<dl>
<dt>A</dt>
<dd>A fine QM - git down there and look. </dd>
<dt>B</dt>
<dd>Not so promising, or requiring some effort (eg. a climb) </dd>
<dt>C</dt>
<dd>Pretty cruddy, or good but very hard to get to.</dd>
<dt>D</dt>
<dd>A dig- only possible to continue if loose rocks or soil are removed.</dd>
<dt>V</dt>
<dd>An aven which might be climbable, but not adequately assessed</dd>
<dt>X</dt>
<dd>A high, wet or unsafe-looking aven unlikely to be climbed</dd>
<dt>?</dt>
<dd>No-one writing this list actually knows!</dd>
</dl>
<p>Note that the quality grades are assigned by the explorers at the time, and
that subsequent discoveries may mean that the grade is optimistic, since the
lead may now drop into passage which wasn't then explored. Also, different
explorers have different ideas, or different waist sizes - one man's "A-lead"
may be another's "C-lead" :-(</p>
<hr />
<ul id="links">
<li>Back to <a href="https://camcaving.uk/">CUCC Home page</a></li>
<li>Back to <a href="index.htm">Expedition Intro page</a></li>
<li><b>Main Indices:</b>
<ul>
<li><a href="infodx.htm"><b>Index</b> to Expo</a> information pages</li>
<li><a href="areas.htm">Description of CUCC's area</a> and split to subareas</li>
<li>Full <a href="indxal.htm">Index to cave descriptions</a> in area 1623</li>
<li>List of (links to) <a href="pubs.htm">published reports and logbooks</a></li>
</ul></li>
<li><b>Pictures:</b>
<ul>
<li><a href="gall0.htm">Text only Index</a></li>
<li><a href="gallery/0.htm">Index pages (with thumbnails)</a></li>
</ul></li>
<li>Table of <a href="folk/index.htm"><b>members</b> of CUCC expeditions</a> 1976-present</li>
</ul>
</body>
</html>

4
handbook/survey/qmentry.html
View File

@@ -71,11 +71,11 @@ Here is an example from the last bit of bipedalpassage.svx in 264. Note that eac
<p>
The format for question mark lists is <br>
<ul>
<li>QM identifier, <li><a href="../../qm.html">Quality Grade</a>, <li>Area indicator, <li>description of QM.
<li>QM identifier, <li><a href="qm.html">Quality Grade</a>, <li>Area indicator, <li>description of QM.
</ul>
<p>The QM numbers themselves used to be in the format <br>
<ul>
<li><a href="../../qm.html">Discoverer identifier</a>, <li>Year of discovery, <li>Cave identifier, <li>serial number.
<li><a href="qm.html">Discoverer identifier</a>, <li>Year of discovery, <li>Cave identifier, <li>serial number.
</ul>
but today, with the QMs inside the survex files, the identifiers are just QM1, QM2 etc.
<p>This format is <a href="../../qm.html">documented in the original QM conventions</a> page (which now needs revising).

6
handbook/troggle/scriptsqms.html
View File

@@ -42,7 +42,7 @@ tl;dr - use <em>svx2qm.py</em>. Look at the output at:<br>
chase QMs. It is a troggle-generated document at <a href="/prospecting_guide/">expo.survex.com/prospecting_guide/</a>. It is so old that "top camp" in the guide refers to the col camp and not the Stonebridge bivvy. Some updates were done in 2007.
</ol>
<p>QMs all use <a href="../../qm.html">the same QM description conventions</a>.
<p>QMs all use <a href="../survey/qm.html">the same QM description conventions</a>.
<h4 id="QM_helper">js/QM_helper.js</h4>
<p>A relic.
@@ -55,7 +55,7 @@ Django Admin control panel for manipulating QMs. It is not live as media/js/ is
<p>This is a perl script dating from November 2004.
<p>it takes a <em>hand-edited</em> CSV file name as the program's argument and generates an HTML page listing all the QMs.
<p><a href="../../1623/258/tablize-qms.pl" download>Copies of it</a> live in the three cave file folders in <em>:expoweb:/1623/</em>, in <em>258/, 234/</em>, and <em> 204/</em> . These generated html files are live pages in the cave descriptions: <br />
<p><a href="../../1623/258/tablize-qms.pl" download>Varient copies of it</a> (they are all slightly different) live in the three cave file folders in <em>:expoweb:/1623/</em>, in <em>258/, 234/</em>, and <em> 204/</em> . These generated html files are live pages in the cave descriptions: <br />
<a href="../../1623/258/qm.html">/1623/258/qm.html</a><br />
<a href="../../1623/234/qm.html">/1623/234/qm.html</a><br />
<a href="../../1623/204/qm.html">/1623/204/qm.html</a><br />
@@ -136,7 +136,7 @@ This will work on all survex *.svx files even those which have not yet been run
<h4>troggle/parsers/survex.py</a></h4>
<p>The QMs inside the survex files are parsed by troggle along with all the other information
inside survex files and stored in the database. But the webpages which display this data are rudimentary, e.g. <a href="/getQMs/1623-204">/getQMs/1623-204</a> or <a href="/cave/qms/1623-204">/cave/qms/1623-204</a>.
inside survex files and stored in the database. But the webpages which display this data are very rudimentary and currently useless, e.g. <a href="/getQMs/1623-204">/getQMs/1623-204</a> or <a href="/cave/qms/1623-204">/cave/qms/1623-204</a>.
Looking through urls.py and core/view_caves.py we see a lot of code for providing new QM numbers, producing lists of QMs for a given cave and for downloading QM.csv files generated by the database. But none of it appears to be working today (14 May 2020), see below.
<h4 id="samqms">Sam's parser additions</a></h4>