move detail - online edit of handbook/survey/newsurvex.html

This commit is contained in:
Expo on server 2023-10-16 23:59:43 +01:00
parent 955e6c6f19
commit aabc822d7d

View File

@ -244,30 +244,7 @@ telling them to use the online form.]
<h3><a id="location">Entering the Entrance location data</a></h3>
<p>The location of the cave is, eventually, stored in a survex file, just <em>not the same survex file</em>.
<p><b>If you are doing this for the first time</b>, don't bother with this *fix stuff. Just type the latitude &amp; logitude numbers into the <a href="ententry.html">New Entrance form</a> and someone else will do the *fix stuff.
<p>
The survex location uses a *fix statement and it looks like this:
<code>
*cs LONG-LAT<br>
*fix p2023-js-02 reference 13.80841 47.69055 1745<br>
*entrance p2023-js-02
</code>
<p>If you are doing this for the first time, <em>do</em> put it in the same survex file. A nerd will move it to the right place later.
<div style="margin-left: 3em; margin-right: 4em"><em>The 'right place' is in the <var>fixedpts</var> part of the <var>:loser:</var> repository, but is very different depending on whether the cave is in the 1623 or the 1626 area - for historic reasons
</em> </div>
<p>And in your main survex file you will need to make the connection between the survey points in the cave and the external location. This would be something like this (not real data), where survey station "1" is the tag at the entrance of the cave, and outside the begin/end section it is called "2023-js-02.1"
<code>
*equate p2023-js-02 2023-js-02.1<br />
<br />
*begin 2023-js-01<br />
*export 1<br />
...<br />
*data normal from to length bearing gradient ignoreall<br />
1 2 4.46 099.3 -54<br />
...<br />
*end 2023-js-01<br />
</code>
<p>There is a lot more to say about how to record the best GPS data, and how to link GPS with survey points
<h3><a id="tickingoff">Entering the cave description in the survex file</a></h3>