expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-01-18 17:02:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

QMs docm update

Browse Source
This commit is contained in:
Philip Sargent 2022-07-05 20:41:04 +03:00
parent 463c861409
commit b80f6d2e64
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
handbook/troggle/scriptsqms.html
View File

@ -41,6 +41,8 @@ each cave system. A perl script turned that into an HTML file for the website. B
<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> and produces reports by cave and individually, e.g. see <a href="/cave/qms/1623-161">the 161 QMs</a>
(slow page), which is <em>old</em> compared with the hand-edited <a href="/1623/161/qmtodo.htm">1623-161</a> page which was derived from it.
<li><strong>troggle and QMs in survex files</strong> - Since Sam wrote this in 2020 we have had the recent QMs in troggle but the report
to display them was not written. This has now (July 2022) been fixed. Note that this means some duplication for 1623-161 and a few others.
<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>The elderly Prospecting Guide</strong> - Used to cover some of the same sorts of information as needed by someone wanting to
chase QMs. It was a troggle-generated document at <a href="/prospecting_guide/">expo.survex.com/prospecting_guide/</a>.
@ -52,7 +54,13 @@ integrate these QMs into the same reports as those parsed from the CSV files.
<p>QMs all use <a href="../survey/qm.html">the same QM description conventions</a>.
<h4 id="qms.py">troggle/parsers/qms.py</a></h4>
<p>Troggle currently reports QMs for only three historic caves and ignores all the QMs inside survex files.
<p>Troggle currently reports QMs for only three historic caves and also imports all the QMs inside survex files.
Thus a recent cave such as 1623-264 (Balkh&ouml;hle)will only show QMs imported from the survex files:
<ul>
<li>/cave/qms/&lt;caveslug&gt; e.g. <a href="/cave/qms/1623-264/">/cave/qms/1623-264/</a> works (slow page)
<li>/cave/&lt;caveslug&gt;-&lt;year&gt;&lt;qm_id&gt; e.g. <a href="/cave/qms/1623-264/2019-2B">/cave/qms/1623-264/2019-2B</a> broken (multiple hits)
</ul>
<p>The bug in the individual QMs is probably in the importing process.
<p>The parser <em>troggle/parsers/qms.py</em> currently imports the <var>qm.csv</var> files used by
the 2004 perl script tablize-qms.pl (see below) into troggle using a mixture of csv and html parsers:
<code><pre>parseCaveQMs(cave='stein',inputFile=r"1623/204/qm.csv")