expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-22 07:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add link to prospecting guide in QMs documn.

Browse Source
This commit is contained in:
Philip Sargent 2020-07-21 02:50:36 +01:00
parent d495e0f0d9
commit 44cb2b2ca6
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.gitignore vendored
View File

@ -470,3 +470,4 @@ years/1997/log.htm.cache
years/1998/log.htm.cache
syntax: regexp
years/2006/logbook.html.cache
scripts/make-folklist.py.bak

6
handbook/troggle/scriptsqms.html
View File

@ -32,12 +32,14 @@ tl;dr - use <em>svx2qm.py</em>. Look at the output at:<br>
<img class="onright" src ="qm-image.jpg" />
<p>You will be familiar with <a href="../survey/qmentry.html">documenting newly found QMs</a> in the survex file when you type it in. But QMs are only useful if they can be easily scanned by people planning the next pushing trip. That's what we are discussing here.
<p>There are four ways we have used to manage QMs:
<p>There are four (and a half) ways we have used to manage QMs:
<ol>
<li><strong>Perl script</strong> - Historically QMs were not in the survex file but typed up in a separate list <var>qms.csv</var> for each cave system. A perl script turned that into an HTML file for the website. But there appear to be 3 different formats for this.
<li><strong>Perl + troggle</strong> - One of troggle's input parsers "QM parser" is specifically designed to import the three HTML files produced from <var>qms.csv</var> but doesn't do anything with that data (yet).
<li><strong>Python script</strong> - Phil Withnall's 2019 script <em>svx2qm.py</em> scans all the QMs in a single survex file. See below for how to run it on all survex files.
<li><strong>New troggle</strong> - Sam's recent addition to troggle's "survex parser" makes it recognise and store QMs when it parses the survex files.
<li><strong>The elderly Prospecting Guide</strong> - covers some of the same sort sof information as needed by someone wanting to
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>.
@ -127,7 +129,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 thge 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 tis 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 rudimentary, 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>