diff --git a/handbook/troggle/scriptsqms.html b/handbook/troggle/scriptsqms.html index 09a813547..c1471a66b 100644 --- a/handbook/troggle/scriptsqms.html +++ b/handbook/troggle/scriptsqms.html @@ -24,9 +24,9 @@ var { # to match but inline

CUCC Expedition Handbook

QMs and leads

-tl;dr - use svx2qm.py. Look at the output at:
-qms2019.txt
-qms2019.csv
+tl;dr - use the troggle reports for each cave, e.g.
+QMs for Fischgesicht +

QMs - the fourfold path

@@ -35,18 +35,22 @@ QMs are only useful if they can be easily scanned by people planning the next pu

There are half a dozen ways we have used to manage QMs:

    +
  1. troggle and QMs in survex files - Since Sam wrote a QM svx parser in 2020 we have had the recent QMs in troggle but the report +to display them was not written until July 2022. Note that this means some duplication for 1623-161 and a few others where the same QM is +in both the survex file and the CSV file - see below. + +
  2. troggle + perl era CSV - One of troggle's input parsers imports the +three + qms.csv files and produces reports by cave and individually, e.g. see the 161 QMs +(slow page), which is old compared with the hand-edited 1623-161 page which was derived from it.
  3. Hand-edited lists of QMS - only exist for 1623-161 Kaninchenhöhle
  4. Perl script - Historically QMs were not in the survex file but typed up in a separate list qms.csv 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. Not currently used. +each cave system. A perl script turned that into an HTML file for the website. +But there are 3 different formats for this. The perl script is not used, but the same three CSV files (caves 161, 204 and 234) +are imported into troggle during initial data load (see above). -
  5. Perl + troggle - One of troggle's input parsers "QM parser" is specifically designed to import the three HTML files -produced from qms.csv and produces reports by cave and individually, e.g. see the 161 QMs -(slow page), which is old compared with the hand-edited 1623-161 page which was derived from it. - -
  6. troggle and QMs in survex files - 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.
  7. Python script - Phil Withnall's 2019 script svx2qm.py scans all the QMs in a single survex file. See below for how to run it on all survex files. @@ -60,7 +64,7 @@ It has been retired because the mapping software packages it used were terminall

    QMs all use the same QM description conventions.

    troggle/parsers/qms.py

    -

    Troggle currently reports QMs for only three historic caves and also imports all the QMs inside survex files. +

    Troggle currently reports QMs separately collated for three historic caves and also imports all the QMs inside survex files. Thus a recent cave such as 1623-264 (Balkhöhle) will only show QMs imported from the survex files:

    • /cave/qms/<caveslug> e.g. /cave/qms/1623-264/ works (slow page) @@ -167,8 +171,7 @@ This will work on all survex *.svx files even those which have not yet been run

      troggle/parsers/survex.py

      Troggle troggle/parsers/survex.py currently parses and stores all the QMs it finds in survex files. The tables where the data -is put are listed in the current data model including structure for ticking them off. These QMs are stored in -the database. But the webpage which displays this data is currently broken, e.g. /getQMs/1623-204. +is put are listed in the current data model including structure for ticking them off.

      troggle archeology