2018-08-14 15:39:24 +01:00
<!DOCTYPE html>
2004-04-22 21:11:29 +01:00
< html >
2001-08-15 19:29:27 +01:00
< head >
2020-01-08 21:18:21 +00:00
< meta http-equiv = "Content-Type" content = "text/html; charset=utf-8" / >
2004-04-22 21:11:29 +01:00
< title > CUCC Expo Surveying Handbook: Entering data< / title >
2004-04-21 10:35:34 +01:00
< link rel = "stylesheet" type = "text/css" href = "../../css/main2.css" / >
2001-08-15 19:29:27 +01:00
< / head >
< body >
2018-08-08 13:17:03 +01:00
< h2 id = "tophead" > CUCC Expo Surveying Handbook< / h2 >
2018-08-10 13:08:59 +01:00
< h1 > From muddy book to survex plot< / h1 >
2018-08-08 13:17:03 +01:00
2018-08-10 13:08:59 +01:00
< div class = "onright" >
2004-04-23 08:58:27 +01:00
< a href = "../../piclinks/typing.htm" > < img src = "../../tinypix/typing.jpg"
width="176" height="115" alt="" />< / a >
2018-08-10 13:08:59 +01:00
< p class = "caption" > Tony Rooke entering data (1991)< / p > < / div >
2018-08-08 13:17:03 +01:00
2001-08-15 19:29:27 +01:00
< p > Survex has its own documentation for the format of the data, though the
template file and a look at someone else's data will quickly make this
2018-08-10 13:08:59 +01:00
fairly clear.
< p > Survex has some very flexible data entry options, so there
2001-08-15 19:29:27 +01:00
are a few extra guidelines to try to get some consistency in the way
2004-04-22 21:11:29 +01:00
everyone uses it within this project.< / p >
2001-08-15 19:29:27 +01:00
2018-08-10 13:08:59 +01:00
< p > Survex (including the graphical software 'aven') is already installed
on the expo laptop. These instructions assume that you are using the expo laptop.
< h3 > Where to put your data< / h3 >
< p > Where to put your data: < b > If in doubt, ask!< / b > . These instructions assume
that you are typing it in on the < em > expo laptop< / em > . (You can do it fom your own
2020-01-08 21:18:21 +00:00
laptop if you have been initiated into the deep magic of the ":loser:" repository
2018-08-10 13:08:59 +01:00
of the distributed version control system - see the
2020-04-26 23:27:38 +01:00
< a href = "../computing/repos.html" > list of repositories< / a > .
2018-08-10 13:08:59 +01:00
< ul > < li > If it is a surface
2020-01-08 21:18:21 +00:00
survey, it goes in the :loser:/surface" directory;
2018-08-10 13:08:59 +01:00
< li > if it is a file of fixed points
2020-01-08 21:18:21 +00:00
(like GPS fixes, or map coordinates), it goes in the ":loser:/fixedpts" directory;
2018-08-10 13:08:59 +01:00
< li > if
2020-01-08 21:18:21 +00:00
it is a new cave on the near-plateau, put it in a new directory under ":loser:/caves-1623".
2018-08-10 13:08:59 +01:00
< li > Underground data for Steinbrü ckenhö hle goes in one of the
2020-01-08 21:18:21 +00:00
subdirectories under :loser:/caves-1623/204/; it may well be clear which one from what it
2018-08-10 13:08:59 +01:00
links to, but if not, ask.< / p >
< / li >
< / ul >
< h3 > Use a template< / h3 >
2020-01-08 21:18:21 +00:00
< p > The beginner should start from the existing template file :loser:/template/template.svx
as this has lines to remind you to add various details - make sure you
2018-08-10 13:08:59 +01:00
don't leave any blanks! Copy < em > and rename this< / em > to where you want to put your data
< em > before< / em > editing it. Too many people have overwritten the
template in the past, try not to do this yourself.
2020-01-08 21:18:21 +00:00
< p > Working by editing a .svx file from another bit of the same cave may seem like a short cut but whoever edited it may have deleted some of the helpful and useful hints that are in the template.svx file - so don't do this please, until you really know what you are doing.
2018-08-10 13:08:59 +01:00
2020-01-08 21:18:21 +00:00
< h3 > < a id = "filenames" > Filename and data-entry conventions in svx files< / a > < / h3 >
2018-08-10 13:08:59 +01:00
< ul >
< li > Use Unix line endings (i.e. \n not \r\n).
< li > Use UTF-8 character encoding.
2022-12-22 15:10:14 +00:00
< li > NO UMLAUTS. Use < em > & uml;< / em > for u-umlaut and < em > & oml;< / em > for o-umlaut in text. But don't use these
in filenames.
2018-08-10 13:08:59 +01:00
< li > Cave numbers are written without any leading zeros at all (in filenames,
survey names, or anything else!).
2020-01-08 21:18:21 +00:00
< li > Entrances have station names such as < b > p204b< / b > . In the event of the tag
2018-08-10 13:08:59 +01:00
location being different from the entrance location, the tag point
2020-01-08 21:18:21 +00:00
should be named with a "t" instead, e.g. < b > t204b< / b > .
2018-08-10 13:08:59 +01:00
< li > No full stop (.) characters in station names.
2022-12-22 15:10:14 +00:00
< li > All filenames to be in lower case. Capital letters in filenames can still (in 2022)
cause hassle when moving between Linux and Windows. (This includes suffix letters for cave entrances: it is "87a" NOT "87A".)
2001-08-15 19:29:27 +01:00
2004-04-22 21:11:29 +01:00
<!-- I think we can dispense with this now - DL
2001-08-15 19:29:27 +01:00
< li > Filenames: Because Survex is used on different sorts of computer, it is
best to use filenames which won't get changed when the files are moved
between systems. On a PC this means using xxxxxxxx.SVX, where "xxxxxxxx" is a
name of letters, numbers and maybe the underscore character, with a maximum
length of eight. On an Acorn machine, the equivalent filename is
"xxxxxxxx/SVX", and should have a filetype of "Text". Note that this must be
kept in an image filing system such as SparkFS (.ZIP), X-files or DOSFS
(which is most logical) to avoid truncation. I know Windows lets you have
long meaningful names, but these tend to get lost on DOS floppies, or when
moved to other machines. For directories (=folders), use a maximum of eight
2004-04-22 21:11:29 +01:00
characters with no extension.-->
2018-08-10 13:08:59 +01:00
< li > No filenames starting with "-" or "!".
2022-12-22 15:10:14 +00:00
< li > No colons in filenames.
2018-08-10 13:08:59 +01:00
< li > Caves with a provisional number consisting of a year and a serial number
2022-12-22 15:10:14 +00:00
should be < em > hyphenated< / em > , thus 2018-ad-01 not with underscore 2018< b > _< / b > 01 or any of the various other
2018-08-10 13:08:59 +01:00
variants.
< / ul >
2004-04-22 21:11:29 +01:00
2018-08-10 13:08:59 +01:00
< h3 > The name of your survey< / h3 >
What to call your survey: all your data should be inside a begin/end pair
2004-04-22 21:11:29 +01:00
with a meaningful name. This need not be the same name as the file, but as a
general rule it should be so unless there is a really good reason not to. On
the other hand, if you have made two or three trips to the same cave,
it can be a good idea to nest surveys in one file:
< pre > < i > File 2050-01.svx< / i >
*begin 2050-01
*export pt1.1 pt2.5 [...]
*begin pt1
< i > [survey data from first trip]< / i >
*end pt1
*begin pt2
< i > [survey data from second trip]< / i >
*end pt2
*end 2050-01
< / pre >
2018-08-10 13:08:59 +01:00
or you can create several .svx files.
2020-01-08 21:18:21 +00:00
Creating several .svx files seems to be current practice as it
simplifies the manual process of knitting several different people's trips together (though the online wallet system can only record one of these at the moment).
2001-08-15 19:29:27 +01:00
2004-04-22 21:11:29 +01:00
< p > There is no restriction on the length of these names, but as they can be
2018-08-10 13:08:59 +01:00
displayed in aven, tunnel and other such programs, it helps not to have
anything too elaborate. Older versions of survex required each prefix to be
2004-04-22 21:11:29 +01:00
unique in its first eight characters, and this is not a bad guideline to
follow.< / p > < / li >
2020-01-08 21:18:21 +00:00
< h3 id = "stationanmes" > Station names< / h3 >
2018-08-10 13:08:59 +01:00
< p > Every station should have a number < em > within your survey< / em > even if it
2004-04-22 21:11:29 +01:00
is an existing station to which you have connected. Any survey stations which
you think can reliably be found again should be listed at the start of your
survey file. This includes the name (within your survey) of any existing points
you linked into. I have used lines like < tt > ;*export mysurvey.pt1.0 ; 2nd bolt at
head of new pitch< / tt > – this may or may not catch on as a standard.< / li >
2001-08-15 19:29:27 +01:00
< / ul >
< p > At this stage, you have done enough to get a centre line for drawing up.
2004-04-22 21:11:29 +01:00
If you aren't completely confident about the structure of the Austria data, or
2018-08-10 13:08:59 +01:00
the survex syntax of < tt > *equate< / tt > and < tt > *export< / tt > which can be rather
2004-04-22 21:11:29 +01:00
cryptic for the uninitiated, it may be best not to try to link your survey to
everything else so skip the next bit and read on < a href = "#concrete" > from
here< / a > .< / p >
2001-08-15 19:29:27 +01:00
2020-01-08 21:18:21 +00:00
< h3 id = "plumbing" > Plumbing your survey into the rest of the cave< / h3 >
2001-08-15 19:29:27 +01:00
< p > However, if you need to see your survey in relation to the rest of the
2004-04-22 21:11:29 +01:00
dataset:< / p >
2001-08-15 19:29:27 +01:00
< ul >
2004-04-22 21:11:29 +01:00
< li > Don't put any *equate directives to other surveys into your file (or any
survey legs which quote station names from other survey files). Instead, go to
2020-03-05 23:23:41 +00:00
the file which *includes the other files in the same area. < br / > < br / >
2018-08-10 13:08:59 +01:00
For example, if you
have created a file trivial.svx in the caves-1623/204/deepsouth directory, go to the
2004-04-22 21:11:29 +01:00
file deepsouth/deepsouth.svx, where you will find *include lines for each of
the files, together with the *equate lines to connect them together. Add an
include for your file, and *equate lines for each of your survey stations which
is the same as one in another survey. If your survey connects to points in
surveys in files in more than one directory then the *equates should go in the
2018-08-10 13:08:59 +01:00
/204/204.svx file, but at this stage it is probably worth enlisting the help of
2020-03-05 23:23:41 +00:00
someone who knows the structure of the data inside-out! < br / > < br / >
2018-08-10 13:08:59 +01:00
< li > You should now find that if you run survex on one of the master files
2023-01-30 22:27:46 +00:00
(
< a href = "/survexfile/1623-and-1626-no-schoenberg-hs" > 1623-and-1626-no-schoenberg-hs.svx< / a > ,
< a href = "/survexfile/204" > 204.svx< / a > ,
< a href = "/survexfile/smk-system" > smk-system.svx< / a >
, etc.) which includes the area of
2001-08-15 19:29:27 +01:00
your new survey, it is linked in and will show up when you use the resultant
2023-01-30 22:27:46 +00:00
.3d file in aven. < / li >
2001-08-15 19:29:27 +01:00
< / ul >
2018-08-10 13:08:59 +01:00
< p > Now you have been typing this on the expo laptop, and before you let someone
else use the laptop you need to find a nerd to do the deep magic to add your
2020-04-26 23:27:38 +01:00
file to the version control < a href = "../computing/repos.html" > repository< / a > "loser". Watching the nerd do this is
2018-08-10 13:08:59 +01:00
usually your first initiation into learning how to do it yourself.
< h3 id = "concrete" > Example svx file< / h3 >
< p > To make that all a bit more concrete, here is a
2004-04-22 21:11:29 +01:00
fictitious example of a survey off Swings & Roundabouts in 204. Let's say
that you went to explore a lead from the QM list numbered 2002-99, that the
nearest survey station was listed as 204.allswings.swings5.2 and you found it
successfully, and numbered it within your own survey as station 0. Then you
2018-08-14 15:44:28 +01:00
might create the following file: (note we don't use umlauts)< / p >
2004-04-22 21:11:29 +01:00
<!-- Stolen, with apologies to Martin and Lucia, from
caves/204/swings/ermintrude.svx. -->
2020-01-08 21:18:21 +00:00
< pre > < code > < i > File wibble.svx< / i >
2004-04-22 21:11:29 +01:00
*begin wibble
; Locn: Totes Gebirge, Austria - Loser/Augst-Eck Plateau (kataster group 1623)
2018-08-14 15:44:28 +01:00
; Cave: Steinbruckenhohle
2004-04-22 21:11:29 +01:00
*title "Wibbled by Goesser"
*date 2004.08.32 ;date the survey was done
*team Insts John Doe
2023-07-09 12:11:34 +01:00
*team Notes Amalthea Jones
*team Tape Amalthea Jonese
2004-04-22 21:11:29 +01:00
; ref.: 2004 #999 ; the #number is on the clear pocket containing the original notes.
2001-08-15 19:29:27 +01:00
; ====== stations refindable to link to other surveys: ======
2004-04-22 21:11:29 +01:00
*export 0 ; list all exported survey points.
2001-08-15 19:29:27 +01:00
2004-04-22 21:11:29 +01:00
*calibrate tape 0 ; +ve if tape was too short, -ve if too long
;calibration data 148,+23,147,+23.5,148,+23,329,-23,328,-23.5,328.5,-23
2001-08-15 19:29:27 +01:00
2004-04-22 21:11:29 +01:00
;from to tape compass clino ; remarks
1 p5 5.48 181 -27
< i > [and the rest of your survey data]< / i >
6 5 5.66 - DOWN
2001-08-15 19:29:27 +01:00
2004-04-22 21:11:29 +01:00
;stn L R U D Desc
;1 0.7 0.4 0.3 0.5 RP top of boulder
< i > [and the rest of the station details]< / i >
2020-01-08 21:18:21 +00:00
*end wibble< / code >
2001-08-15 19:29:27 +01:00
< / pre >
2020-01-08 21:18:21 +00:00
< p > That lot would be typed by copying :loser:/template/template.svx to
:loser:/caves-1623/204/swings/wibble.svx and then filling in the blanks and adding your
2004-04-22 21:11:29 +01:00
data. If you are linking to the rest of the survey then in the file
2020-01-08 21:18:21 +00:00
:loser:/caves-1623/204/swings/allswings.svx add the lines:< / p >
2001-08-15 19:29:27 +01:00
2020-01-08 21:18:21 +00:00
< pre > < code > *include wibble
2004-04-22 21:11:29 +01:00
*equate wibble.0 swings5.2
2020-01-08 21:18:21 +00:00
< / code > < / pre >
< h3 id = "split" > Split surface and underground files< / h3 >
2001-08-15 19:29:27 +01:00
2004-04-22 21:11:29 +01:00
< p > Remember not to put surface data and underground data in the same file,
2001-08-15 19:29:27 +01:00
even if they are part of one continuous survey. You need to create two
files, with a defined station for the entrance, and a suitable equate in
2004-04-22 21:11:29 +01:00
the file which includes both surface stuff and underground stuff.< / p >
<!-- Did whoever surveyed bogenhoehle read this? -->
2001-08-15 19:29:27 +01:00
2023-07-09 12:11:34 +01:00
< h3 id = "roles" > *Team options< / h3 >
< p > We have used a varied and peculiar range of roles in our survex files over the years. e.g.
< pre > < code > *team nail_varnish_bitch Amalthea Jones
< / code > < / pre >
< p > The list of approved roles (as of July 2023) is: < br >
< code > bitch|bodger|bolt|bolter|bolting|book|clino|comp|
compass|consultant|disto|distox|distox2|dog|
dogsbody|drawing|drill|gps|helper|inst|instr|
instrument|monkey|nagging|nail|nail_polish|
nail_polish_bitch|nail_polish_monkey|nail_varnish|
nail_varnish_bitch|note|paint|photo|pic|point|
polish|powerdrill|rig|rigger|rigging|sketch|
slacker|something|tape|topodroid|unknown|
useless|varnish|waiting_patiently< / code >
2020-01-08 21:18:21 +00:00
< h3 id = "postprocess" > Postprocessing and Update< / h3 >
2001-08-15 19:29:27 +01:00
< p > Once you have your data typed in and checked, it must be run through the
2004-04-22 21:11:29 +01:00
survey software (which on expo will be < a
2018-08-10 13:08:59 +01:00
href="http://www.survex.com/">survex< / a > ) and a centre line printed, both for
2004-04-22 21:11:29 +01:00
plan and for extended elevation. Measure the print out to check that it really
has printed at the scale you wanted (typically 1:500), as this has sometimes
caused problems in the past.< / p >
2020-01-08 21:18:21 +00:00
< p > Return to "< a href = "newcave.html#survexformat" > Survey handbook - survex format< / a > ".< / p >
2004-04-22 21:11:29 +01:00
2023-07-09 12:11:34 +01:00
< hr / > < / body >
2001-08-15 19:29:27 +01:00
< / html >
