mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2025-12-08 14:54:28 +00:00
154 lines
6.7 KiB
HTML
154 lines
6.7 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>CUCC Expedition Handbook: Cave entry field</title>
|
|
<link rel="stylesheet" type="text/css" href="/css/main2.css" />
|
|
</head>
|
|
<body>
|
|
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
|
|
|
<h1>Entrance entry page fields</h1>
|
|
<p>There are a lot of fields on the 'new/edit cave' page and the 'new/edit entrance' page and
|
|
some of them are a quite mysterious. This page explains what they mean. The same fields appear in each entrance_data/ xml file.</p>
|
|
<p>
|
|
Instructions on how to enter the data for new
|
|
caves and entrances, and especially how to add images/surveys so that they appear properly,
|
|
is to be found on the sequence of pages <a href="caveentry.html">starting here</a>. For entrance data, you will use the online form New Entrance whcih is a link on the cave escription page, e.g. look at the page for cave 1623-172 : <a href="/1623/172.htm">172</a> and scroll down until you see the link text "New Entrance".
|
|
</p>
|
|
|
|
|
|
<h3>Only two field are essential for Entrances</h3>
|
|
<p>There are only two essential fields which must be there before the Submit button will work:
|
|
|
|
<ul>
|
|
<li><b>Marking</b> e.g. Tag or Paint
|
|
<li><b>Findability</b> e.g. Lost or Coordinates
|
|
</ul>
|
|
<p>See below for explanations.
|
|
|
|
<h3>Names of identifiers and files</h3>
|
|
<p>Always use <b>lower case</b> in names of caves, despite what you might see in historical data.
|
|
<p>So a new cave would be 2023-zz-01 and its entrances would be 2023-zz-01a, 2023-zz-01b and 2023-zz-01c.
|
|
<p>This is to prevent confusion between Windows and Linux machines, and unintentional deletion of data.
|
|
|
|
<h2>List of New Entrance/Entrance_data fields</h2>
|
|
<dl>
|
|
<dt>letter</dt>
|
|
<dd>Nothing, if the cave has only one entrance, otherwise a lower case letter 'a', 'b', 'c' etc. for the different entrances.</dd>
|
|
</dl>
|
|
|
|
|
|
<dt>entrance_description</dt>
|
|
<dd>the description of the entrance itself goes here (the description of the approach to the entrance is further down). <em>HTML freeform field.</em></dd>
|
|
|
|
|
|
<dl>
|
|
<dt>explorers</dt>
|
|
<dd>Names of the actual people or just e.g. 'EXPO 1978'. <em>HTML freeform field.</em></dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>location</dt>
|
|
<dd>Context in the frame of other local features. <em>HTML freeform field.</em></dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>last visit date</dt>
|
|
<dd>ISO format date, e.g. 2025-07-25, the date that the last person looked at the entrance from the surface</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>non_public</dt>
|
|
<dd>'False' or 'True'. True if the cave should only be visible to logged-in users. Caves
|
|
are normally public, so enter 'False' unless you know otherwise.</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>Findability</dt>
|
|
<dd>Dropdown: values are Coordinates, Lost, Refinable, and To Be Confirmed </dd>
|
|
</dl> <dl>
|
|
<dt>marking</dt>
|
|
<dd>A dropdown: Paint, Tag, Unmarked etc.</dd>
|
|
</dl>
|
|
|
|
<dl>
|
|
<dt>approach</dt>
|
|
<dd>How to get to and to find the entrance</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>underground_description</dt>
|
|
<dd>the description of the entrance passage or pitch. <em>HTML freeform field.</em></dd>
|
|
</dl>
|
|
|
|
|
|
<dl>
|
|
<dt>photos</dt>
|
|
<dd>Use the [image] button next to the field on the form to upload and insert images/photos into the form. It can be used on most of hte fields but we put them all here by convention. This will re-size the photo for putting into the cave description and create a thumbnail for inserting into the text. </dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>marking text</dt>
|
|
<dd>A text field: what colour paint? Where was the aluminium tag place?? The actual text on an aluminium tag, e.g. "CUCC 1623 201" <em>HTML freeform field.</em></dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>how to find it</dt>
|
|
<dd>Historic. Seems to duplicate "Approach".</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>other comments</dt>
|
|
<dd>Notes about the process of uploading or editing the data</dd>
|
|
</dl>
|
|
|
|
<dl>
|
|
<dt>tag_station</dt>
|
|
<dd>a survey station id. It has to be in a format similar to this: "1623.p204e" (for the 'e' entrance to cave 1623-204). This is where the aluminium ID tag is bolted at the entrance.</dd>
|
|
</dl>
|
|
<dl>
|
|
|
|
<dl>
|
|
<dl>
|
|
<dt>other_station</dt>
|
|
<dd>a survey station id. It has to be in a format similar to this: "1623.p204e" (for the 'e' entrance to cave 1623-204). Typically used for the GPS survey station, which has a better view of the sky than the entrance tag.</dd>
|
|
</dl>
|
|
|
|
|
|
|
|
<dl>
|
|
<dt>latitude</dt>
|
|
<dd>Decimal degrees of longitude in WGS84 datum, e.g. 47.694779 (North is assumed).To be entered when entrance is first found so that someone can find it again. Will be overwritten in due course by proper survey data which will be enforced to be consistent with the UTM position.</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>longitude</dt>
|
|
<dd>Decimal degrees of longitude in WGS84 datum, e.g. 13.816002 (East is assumed). To be entered when entrance is first found so that someone can find it again. This will be deleted here when a proper tag station or other station is created</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>Altitude (metres)</dt>
|
|
<dd>In old caves this will have been calculated in UTM coordinates. Enter your GPS value here (WGS84). Yes, altitudes are slightly different. This will be overwritten in due course by an altitude derived from the location and the lidar dataset.</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>bearings</dt>
|
|
<dd>Obsolete: Read-only. For locating the entrance by bearings to well-known peaks - archaic.</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>identified login</dt>
|
|
<dd>'Not editable. This is a visual indicator of whether you have logged in as a real person or logged in as e.g. 'expo'</dd>
|
|
</dl>
|
|
<dl>
|
|
<dt>who_are_you</dt>
|
|
<dd>Your name: the name of the person editing this information, who may not be an explorer or even
|
|
have ever visited the cave. This is only used in the version control history of the edits (new in 2025). e.g. <var>"Anathema Device <anathema@hut.expo>"</var></dd>
|
|
</dl>
|
|
|
|
<h4>Alternative data entry using a file</h4>
|
|
<p>
|
|
There are template files for you to fill-in when creating new caves and entrance in the online system. You will need to be on a machine which has
|
|
<a href="../computing/keyexchange.html">keys installed</a> and you will need to know how to use git.
|
|
<p>Download them:
|
|
<ul>
|
|
<li><a download href="../../templates/cave_data.html">cave_data template</a>
|
|
<li><a download href="../../templates/entrance_data.html">entrance_data template</a>
|
|
</ul>
|
|
<p>
|
|
These are actually XML files, not HTML files, using special tags which are used by the online system to create the webpages in combination with numerical survey data. Instructions are within each file.
|
|
</p>
|
|
<hr />
|
|
<p>Back to <a href="caveentry.html">Cave data entry</a>
|
|
<hr /></body>
|
|
<html>
|