expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-25 08:41:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rigging guide topo uploads

Browse Source
This commit is contained in:
Philip Sargent 2022-03-13 22:00:55 +00:00
parent 0feb58a639
commit 6c3353a6f1
1 changed files with 34 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
handbook/survey/newrig.html
View File

@ -79,11 +79,14 @@ ensure that all bolts can be found again and any deviations and natural belays r
<li>making them findable/appear in cave descriptions,
<li>(optionally) making prettier versions for important caves which have complex rigging.
</ul>
<p>The simple and nicest-looking way to make them findable is to add them to the HTML inline in cave descriptions. For a finished example see the rigging topo for the "<a href="/1623/204/swings.html">Merry Go Round</a>" pitches in the Swings and Roundabouts area in 204.
<p>The simple and nicest-looking way to make them findable is to add them to the HTML inline in cave descriptions. For a finished
example see the rigging topo for the "<a href="/1623/204/swings.html">Merry Go Round</a>" pitches in the Swings and Roundabouts area
in 204.
<a href="caveentry.html">Creating a new cave in the online system</a> is how you create the inline HTML. It is the next step in this Survey Handbook sequence of pages. <br><em>[To Do - improve documentatiton for how to add in image files in cave descriptions]</em>
<a href="caveentry.html">Creating a new cave in the online system</a> is how you create the inline HTML. It is the next step in this
Survey Handbook sequence of pages. <br><em>[To Do - improve documentation for how to add in image files in cave descriptions]</em>
<p>You should produce a separate rigging guide file for each connected set of pitches which will live in<br>
<p>You should produce a separate rigging guide file for each connected set of pitches which will initially live in<br>
<var>expofiles/rigging_topos/</var> e.g. see <br>
<a href="/expofiles/rigging_topos/264/entrance_topo_2016.pdf">expofiles/rigging_topos/264/entrance_topo_2016.pdf</a><br>
but also (to demonstrate that something is always better than nothing):<br>
@ -93,10 +96,37 @@ ensure that all bolts can be found again and any deviations and natural belays r
<p>If you are using a drawing package then produce the file in SVG format.
<a href="https://www.theregister.com/2020/04/14/16_years_inkscape_v1/">Inkscape</a> is what most cavers use as it's free and stable. This will make it possible to edit and update your topo in future.
<p>Discussions on Expo Slack after the 2019 expo resulting in us consolidating rigging topo files into <var>expofiles/rigging_topos/</var> when previously they had had a number of different homes. So if you remember putting them somewhere else int he past, don't do that now. Put them in <var>expofiles/rigging_topos/</var>.
<h3>Uploading the topo files</h3>
<p>When you first produce a topo, don't upload it to the server. Copy it to the right folder on the <var>expo laptop</var> in the potato hut and
tell a nerd on expo that it is there. Or, if you are confident with Filezilla, copy it from the <var>expo laptop</var> to the server and then move the copy on the
<var>expo laptop</var> to e.g. <var>expofiles/rigging_topos/2022/copied-to-server/</var>
<p>If you draw up the topo after expo is over, then email them to a nerd who will upload them into the right place.
<p>If you have your own machine configured as a <a href="../computing/basiclaptop.html#basic">expo basic laptop</a> then you can use
<a href="../computing/fzconfig.html">Filezilla</a> to upload the topo files directly to the server.
<h3>This may be a change from how you used to do it</h3>
<p>Discussions on Expo Slack after the 2019 expo resulting in us consolidating rigging topo files into
<var>expofiles/rigging_topos/</var> when previously they had had a number of different homes. So if you remember putting them
somewhere else in the past, don't do that now. Put them in <var>expofiles/rigging_topos/</var>.
<p>Eventually when the full cave description is written up, selected topos will be moved to the
<var>:expoweb:</var> verson-controlled repository
where they will be linked in to the HTML files for the cave descriptions, e.g.
<a href="/topos/204/kiwi.svg"><var>:expoweb:/topos/204/kiwi.svg</var></a>.
<p>[ We could dream up some fancy scheme for indexing the rigging for every pitch in the system and add that
into troggle but frankly we don't think it's worth the effort.]
<h3>Final editing of cave descriptions</h3>
<p>If you look in detail at the description of <a href="/1623/204/204.html">Steinbrückenhöhle</a> you will see rigging topos
inline as pixel images (not vector files) in the passage descriptions. These are stored with the passage HTML files, e.g.
in <a href="/1623/204/rigging/kiwi.png"><var>:expoweb:</var>/1623/204/rigging/kiwi.png</a>,
whereas the master copy of this rigging diagram is the vector file at
<a href="/topos/204/kiwi.svg"><var>:expoweb:</var>/topos/204/kiwi.svg</a>. We needed both because web browsers
used not to be able to display SVG files embedded in HTML.
<p>If you use a vector file format which is not SVG you may still need to do
this vector-to-pixel conversion when you write up the cave description. But we always keep the original vector file.
<hr />
<p>Back to the previous page in this sequence <a href="drawup.htm">Drawing up your survey</a>.