diff --git a/handbook/survey/newrig.html b/handbook/survey/newrig.html index 7c5581bf9..2a4349490 100644 --- a/handbook/survey/newrig.html +++ b/handbook/survey/newrig.html @@ -79,11 +79,14 @@ ensure that all bolts can be found again and any deviations and natural belays r
  • making them findable/appear in cave descriptions,
  • (optionally) making prettier versions for important caves which have complex rigging. -

    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 "Merry Go Round" pitches in the Swings and Roundabouts area in 204. +

    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 "Merry Go Round" pitches in the Swings and Roundabouts area +in 204. -Creating a new cave in the online system is how you create the inline HTML. It is the next step in this Survey Handbook sequence of pages.
    [To Do - improve documentatiton for how to add in image files in cave descriptions] +Creating a new cave in the online system is how you create the inline HTML. It is the next step in this +Survey Handbook sequence of pages.
    [To Do - improve documentation for how to add in image files in cave descriptions] -

    You should produce a separate rigging guide file for each connected set of pitches which will live in
    +

    You should produce a separate rigging guide file for each connected set of pitches which will initially live in
    expofiles/rigging_topos/ e.g. see
    expofiles/rigging_topos/264/entrance_topo_2016.pdf
    but also (to demonstrate that something is always better than nothing):
    @@ -93,10 +96,37 @@ ensure that all bolts can be found again and any deviations and natural belays r

    If you are using a drawing package then produce the file in SVG format. Inkscape is what most cavers use as it's free and stable. This will make it possible to edit and update your topo in future. -

    Discussions on Expo Slack after the 2019 expo resulting in us consolidating rigging topo files into expofiles/rigging_topos/ 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 expofiles/rigging_topos/. +

    Uploading the topo files

    +

    When you first produce a topo, don't upload it to the server. Copy it to the right folder on the expo laptop 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 expo laptop to the server and then move the copy on the +expo laptop to e.g. expofiles/rigging_topos/2022/copied-to-server/ + +

    If you draw up the topo after expo is over, then email them to a nerd who will upload them into the right place. + +

    If you have your own machine configured as a expo basic laptop then you can use +Filezilla to upload the topo files directly to the server. + +

    This may be a change from how you used to do it

    +

    Discussions on Expo Slack after the 2019 expo resulting in us consolidating rigging topo files into +expofiles/rigging_topos/ 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 expofiles/rigging_topos/. + +

    Eventually when the full cave description is written up, selected topos will be moved to the +:expoweb: verson-controlled repository +where they will be linked in to the HTML files for the cave descriptions, e.g. +:expoweb:/topos/204/kiwi.svg.

    [ 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.] +

    Final editing of cave descriptions

    +

    If you look in detail at the description of Steinbrückenhöhle 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 :expoweb:/1623/204/rigging/kiwi.png, +whereas the master copy of this rigging diagram is the vector file at +:expoweb:/topos/204/kiwi.svg. We needed both because web browsers +used not to be able to display SVG files embedded in HTML. +

    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.


    Back to the previous page in this sequence Drawing up your survey.