expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-02-08 08:10:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Surveying instructions updates

Browse Source
This commit is contained in:
Philip Sargent
2022-12-10 16:09:19 +00:00
parent e31194648b
commit e5a23ca291
6 changed files with 31 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
handbook/survey/datamgt.html Normal file
View File

@@ -0,0 +1,57 @@
<html>
<head>
<title>CUCC Expo Handbook - Data Management</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook - Data Management</h2>
<h1>Why cavers need effective data management</h1>
<div style="text-align:left">
<!-- Comment
Justified text is hard to read:
https://designshack.net/articles/mobile/the-importance-of-designing-for-readability/
https://designforhackers.com/blog/justify-text-html-css/
-->
<p>
Cave exploration is more data-intensive than any other sport. The only way to "win" at this
sport is to bring back large quantities of interesting survey, and possibly photos or scientific
data. Aside from the data collection requirements of the game itself, setting up a game (an
expedition) of cave exploration often involves collection of personal information ranging from
dates available to medical information to the desire to purchase an expedition t-shirt.
<p>
<img class="onright" src ="../i/qm-image.jpg" />
If an expedition will only happen once, low-tech methods are usually adequate to record
information. Any events that need to be recorded can go in a logbook. Survey notes must be
turned into finished cave sketches, without undue concern for the future expansion of those sketches.
<h2>Recurring expeditions</h2>
<p>
However, many caving expeditions are recurring, and managing their data is a more challenging
task. For example, let us discuss annual expeditions.
<ul>
<li>Every year, for each cave explored, a list
of <a href="/cave/qms/1623-290">unfinished underground leads</a> (which we call "<a href="qmentry.html">Question Marks</a>" or "QMs") must be maintained to
record what has and has not been investigated. Each QM must have a unique id, and information
stored about it must be easily accessible to future explorers of the same area.
<li>Similarly, on
the surface, a "<a href="../essentials.html">prospecting map</a>" showing which entrances have been investigated needs to be
produced and updated at least after every expedition, if not more frequently. We call this "essentials.gpx" because it stops people getting lost.
</ul>
<p>When we have hundreds of explored shafts, and thousands of potential holes on the plateau, it is absolutely essential that we record holes we have already looked at.
</div>
<p><em>From "<a href="/expofiles/documents/troggle/troggle_paper.pdf" download>Troggle:
a novel system for cave exploration information management</a>", by Aaron Curtis (2006) and
updated as "<a href="/expofiles/documents/troggle/troggle2020.pdf" download>Troggle:
a revised system for cave data management</a>" in 2020.</em>
<hr />
</body>
</html>