mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-22 23:31:56 +00:00
152 lines
8.8 KiB
HTML
152 lines
8.8 KiB
HTML
|
<html>
|
||
|
|
<head>
|
||
|
|
<title>CUCC Expo Surveying Handbook: LRUDs</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
|
||
|
|
<h2 id="tophead">CUCC Expo Surveying Handbook - LRUDs</h2>
|
||
|
|
|
||
|
|
<h1>Enhanced LRUD Recording</h1>
|
||
|
|
<P>
|
||
|
|
<I>Andy Atkinson</I>
|
||
|
|
<P>
|
||
|
|
<I>A number of survey software packages now let you
|
||
|
|
include LRUD (Left Right Up Down) passage dimensions in some form
|
||
|
|
or other and will produce a plot using this information. All of
|
||
|
|
these, with the exception of Toporobot, are simplistic in their
|
||
|
|
approach, and if you have seen the output you will recognise the
|
||
|
|
rather odd-looking characteristic shapes that occur. There are
|
||
|
|
good reasons why this is so. The conventions that surveyors use
|
||
|
|
when recording the data, such as 'in the direction of the survey',
|
||
|
|
and 'across the passage' are not very easily defined in computing
|
||
|
|
terms. Also the fact that LRUDs are typically taken at stations,
|
||
|
|
and stations are often at junctions causes problems as junctions
|
||
|
|
tend to be atypical, rather than typical, of the passage. There
|
||
|
|
are a whole host of other things like what to do when a value
|
||
|
|
is not given, a question mark is entered, and at the ends of passages.
|
||
|
|
If zero is assumed at an omitted reading then a pinch-point occurs
|
||
|
|
in the walls at that station - not really the desired effect.</I>
|
||
|
|
<P>
|
||
|
|
<I>We have been examining the details of this process
|
||
|
|
with a view to implementing something in Survex, and generationg
|
||
|
|
a proper 3D model of the complex Kaninchenhohle. It quickly became
|
||
|
|
clear that as well as the programming difficulties there were
|
||
|
|
significant problems in terms of the data that was actually collected.
|
||
|
|
Obviously a set of 4 numbers conveys much less information than
|
||
|
|
a sketch. Unfortunately a sketch is inherently 2-dimensional,
|
||
|
|
and thus is not very helpful when trying to construct a 3D model.
|
||
|
|
So the question becomes - what is the least information that needs
|
||
|
|
to be recorded in order to construct a useful 3D model? Obviously
|
||
|
|
the answer depends on what you want to use the finished model
|
||
|
|
for, and the usual constraints on surveying manpower, time &
|
||
|
|
conditions.</I>
|
||
|
|
<P>
|
||
|
|
<I>Andy Atkinson took a look at the specific area
|
||
|
|
of improving the information contained in the LRUD data without
|
||
|
|
dramatically increasing the time it took to record, or the complexity
|
||
|
|
beyond the point which surveyors would stand (where relatively
|
||
|
|
inexperienced Cambridge Cavers in Austria's horrible caves have
|
||
|
|
a particularly low tolerance of such things). Obviously improvements
|
||
|
|
of this nature are no use if surveyors think they are too much
|
||
|
|
extra work. Here he presents his second iteration of the idea
|
||
|
|
for comment.</I>
|
||
|
|
<P>
|
||
|
|
<I>The computing aspects of LRUD interpretation and
|
||
|
|
the broader issues of wall modelling need articles of their own
|
||
|
|
to explore. These will be in future issues.<BR>
|
||
|
|
</I>
|
||
|
|
<P>
|
||
|
|
The suggested format is an extension of the now standard
|
||
|
|
LRUD, with a 5th column -'E' for Extension - which is used in
|
||
|
|
some cases. One obvious improvement is a notation for allowing
|
||
|
|
more than one value to be given in the same direction. This particularly
|
||
|
|
useful in traversable rift where you really want to indicate the
|
||
|
|
distance to both the actual and apparent floors, or sometimes
|
||
|
|
in a wide bedding where only the centre part is person-sized.
|
||
|
|
There are many possibly notations, all prone to confusion, or
|
||
|
|
not completely general.
|
||
|
|
<UL>
|
||
|
|
<LI>Two values separated by a slash is obvious except
|
||
|
|
that many people (CUCC included) use slash instead of the decimal
|
||
|
|
point, so that would be confusing.
|
||
|
|
<LI>A secondary reading below the first may use an
|
||
|
|
extra line or be cramped, and which is which?.
|
||
|
|
<LI>A comma-separated pair is plausible, but the
|
||
|
|
French use commas for decimal points.
|
||
|
|
<LI>Or you could use another letter: e.g. F3, in
|
||
|
|
the E or comment columns, meaning Floor., but Americans use Floor
|
||
|
|
instead of Down.
|
||
|
|
<LI>R for rift is likely to be confused with R for
|
||
|
|
right if put in the comment column.
|
||
|
|
<LI>A for Alternate is the best I can think of. Obviously
|
||
|
|
you could just pick any letter, but we have been careful thoughout
|
||
|
|
to use easy-to-remember abbreviations so something completely
|
||
|
|
arbitrary is not a good idea.
|
||
|
|
</UL>
|
||
|
|
|
||
|
|
<TABLE BORDERCOLOR=#808080 BORDER=1>
|
||
|
|
<TR><TD BGCOLOR=#FFFF00 WIDTH=83><CENTER><B>Bit of Cave</B></CENTER>
|
||
|
|
</TD><TD BGCOLOR=#FFFF00 WIDTH=36><CENTER><B>L</B></CENTER>
|
||
|
|
</TD><TD BGCOLOR=#FFFF00 WIDTH=38><CENTER><B>R</B></CENTER>
|
||
|
|
</TD><TD BGCOLOR=#FFFF00 WIDTH=38><CENTER><B>U</B></CENTER>
|
||
|
|
</TD><TD BGCOLOR=#FFFF00 WIDTH=38><CENTER><B>D</B></CENTER>
|
||
|
|
</TD><TD BGCOLOR=#FFFF00 WIDTH=27><CENTER><B>E</B></CENTER>
|
||
|
|
</TD><TD BGCOLOR=#FFFF00 WIDTH=100><CENTER><B>Comment</B></CENTER>
|
||
|
|
</TD><TD BGCOLOR=#FFFF00 WIDTH=298><CENTER><B>Explanation</B></CENTER>
|
||
|
|
</TD></TR>
|
||
|
|
<TR><TD WIDTH=83>
|
||
|
|
<CENTER><IMG src="../i/img00060.gif"></CENTER></TD><TD WIDTH=36><CENTER>n</CENTER>
|
||
|
|
</TD><TD WIDTH=38><CENTER>~n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
|
||
|
|
<TD WIDTH=27><P></TD><TD WIDTH=100></TD><TD WIDTH=298>L & R are defined as the bisector of the legs. For the last station they are perpendicular to the last leg. ~ is used to indicate estimated distances (very useful to know which numbers may be suspect when drawing up)
|
||
|
|
</TD></TR>
|
||
|
|
<TR><TD WIDTH=83>
|
||
|
|
<CENTER><IMG src="../i/img00061.gif"></CENTER></TD><TD WIDTH=36><CENTER>(n)</CENTER>
|
||
|
|
</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
|
||
|
|
<TD WIDTH=27><P></TD><TD WIDTH=100>(220)</TD><TD WIDTH=298>Where L or R in standard direction is unhelpful, irrelevant or meaningless another direction is given. The approximate bearing is given in the comments field.
|
||
|
|
</TD></TR>
|
||
|
|
<TR><TD WIDTH=83><P></TD><TD><CENTER>Pn<P>Pn<P></CENTER></TD><TD
|
||
|
|
WIDTH=38><CENTER>Pn<P>P(n)<P></CENTER></TD>
|
||
|
|
<TD WIDTH=38><CENTER>Pn<P>P(n)<P></CENTER></TD><TD
|
||
|
|
WIDTH=38><CENTER>Pn<P>P(n)<P></CENTER></TD><TD
|
||
|
|
WIDTH=27><P></TD><TD WIDTH=100><P>(NE)(160)(260)
|
||
|
|
</TD><TD WIDTH=298>For pitches give NSEW instead of LRUD.<BR>Where NSEW is not appropriate (e.g. axes of elliptical shaft lie in another orientation) then use bracket notation to give bearings</TD></TR>
|
||
|
|
<TR><TD WIDTH=83>
|
||
|
|
<CENTER><IMG src="../i/img00062.gif"></CENTER></TD><TD WIDTH=36><CENTER>Jn</CENTER>
|
||
|
|
</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
|
||
|
|
<TD WIDTH=27><P></TD><TD WIDTH=100><P></TD><TD WIDTH=298>At a Junction the value that would otherwise disappear down the joining passage is given as where the wall would have been if the joining passage was not there.
|
||
|
|
</TD></TR>
|
||
|
|
<TR><TD WIDTH=83>
|
||
|
|
<CENTER><IMG src="../i/img00063.gif"></CENTER></TD><TD WIDTH=36><CENTER>Jn</CENTER>
|
||
|
|
</TD><TD WIDTH=38><CENTER>Jn</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
|
||
|
|
<TD WIDTH=27><CENTER>n</CENTER></TD><TD WIDTH=100><P></TD><TD WIDTH=298>When a survey ends at a junction the L & R values for the surveyed passage as if it continued are given. Also given is the 'Extension'. The distance that the survey leg would need to be continued to meet the wall.
|
||
|
|
</TD></TR>
|
||
|
|
<TR><TD WIDTH=83>
|
||
|
|
<CENTER><IMG src="../i/img00064.gif"></CENTER></TD><TD WIDTH=36><CENTER>n</CENTER>
|
||
|
|
</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>Jn</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
|
||
|
|
<TD WIDTH=27><CENTER>n</CENTER></TD><TD WIDTH=100><P></TD><TD WIDTH=298>At a point where a passage meets a pitch The extension is given to the far wall and the roof or floor (roof in the example) is given using the Junction notation.
|
||
|
|
</TD></TR>
|
||
|
|
<TR><TD WIDTH=83>
|
||
|
|
<CENTER><IMG src="../i/img00065.gif"></CENTER></TD><TD WIDTH=36><CENTER>C</CENTER>
|
||
|
|
</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
|
||
|
|
<TD WIDTH=27><P></TD><TD WIDTH=100><P></TD><TD WIDTH=298>For a perimeter survey use C (for Chamber) in either the L (anticlockwise survey) or R (clockwise) column. Readings are on bisectors of legs
|
||
|
|
</TD></TR>
|
||
|
|
<TR><TD WIDTH=83><CENTER><IMG src="../i/img00066.gif"><P><Pre> </Pre><IMG src="../i/img00067.gif"></CENTER></TD><TD
|
||
|
|
WIDTH=36><CENTER>C<P>C<P><Pre> </Pre>Cn<P></CENTER></TD><TD WIDTH=38><CENTER>C<P>C<P><Pre> </Pre>Cn<P></CENTER></TD><TD WIDTH=38><CENTER>n<P>n<P><Pre> </Pre>n<P></CENTER>
|
||
|
|
</TD><TD WIDTH=38><CENTER>n<P>n<P><Pre> </Pre>n<P></CENTER></TD><TD WIDTH=27><CENTER>C<P>n<P><Pre> </Pre>n<P></CENTER></TD><TD
|
||
|
|
WIDTH=100><P></TD>
|
||
|
|
<TD WIDTH=298>For a radial survey the centre point is given like this<BR>Then
|
||
|
|
the other give the Extension value to the wall, as well as U & D<P>In more complex areas L & R values can also be given if they are significant
|
||
|
|
</TD></TR>
|
||
|
|
<TR><TD WIDTH=83>
|
||
|
|
<CENTER><IMG src="../i/img00068.gif"></CENTER></TD><TD WIDTH=36><CENTER>n</CENTER>
|
||
|
|
</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>Jn</CENTER></TD><TD WIDTH=38><CENTER>Jn</CENTER></TD>
|
||
|
|
<TD WIDTH=27><CENTER>Jn</CENTER></TD><TD WIDTH=100><P></TD><TD WIDTH=298>For more complicated bits of the cave the notations given can be combined to fit the need
|
||
|
|
</TD></TR>
|
||
|
|
</TABLE>
|
||
|
|
|
||
|
|
<hr />
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|