From 3f9bf27a04ff51ba237b241572e7237c52eb5664 Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Tue, 5 Jul 2022 22:49:16 +0300 Subject: [PATCH] QM docm update --- handbook/troggle/scriptsqms.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/handbook/troggle/scriptsqms.html b/handbook/troggle/scriptsqms.html index 157403000..9efa663d7 100644 --- a/handbook/troggle/scriptsqms.html +++ b/handbook/troggle/scriptsqms.html @@ -33,7 +33,7 @@ tl;dr - use svx2qm.py. Look at the output at:

You will be familiar with documenting newly found QMs 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. -

There are four (roughly) ways we have used to manage QMs: +

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

  1. Hand-edited lists of QMS - only exist for 1623-161 Kaninchenhöhle
  2. Perl script - Historically QMs were not in the survex file but typed up in a separate list qms.csv for @@ -49,18 +49,18 @@ chase QMs. It was a troggle-generated document at It has been retired because the mapping software packages it used were terminally outdated.
-

The plan is to write new parsers to extract the QM information from the survex files and to -integrate these QMs into the same reports as those parsed from the CSV files. +

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. -Thus a recent cave such as 1623-264 (Balkhöhle)will only show QMs imported from the survex files: +Thus a recent cave such as 1623-264 (Balkhöhle) will only show QMs imported from the survex files:

-

The bug in the individual QMs is probably in the importing process. +

There is an open issue in that although we use the name of the 'block' in the survex file to disambiguate QMs in the same cave and from +the same year, it is still possible for blocks to be named non-uniquely. This would crash the system as two QMs would have the same URL.

The parser troggle/parsers/qms.py currently imports the qm.csv files used by the 2004 perl script tablize-qms.pl (see below) into troggle using a mixture of csv and html parsers: 

parseCaveQMs(cave='stein',inputFile=r"1623/204/qm.csv")