Draft
UIS Cave and Karst Field Definitions

This version generated on 5-Sep-1998

Caution: The material below is under preparation and has not yet been released for discussion. Its details are being changed.

These are the draft cave and karst field definitions under discussion, as referred to in the Cave Data Exchange Proposal of the Informatics Commission (UISIC) of the International Union of Speleology. It is part of UISIC's project to facilitate data exchange between different cave/karst databases. When the definitions have been finalised in English, they will be translated to other languages.

This document will be updated as discussion via the CaveData Internet mailing list proceeds.

The definitions below are arranged in Field ID (FID) order. The FID and field name are shown first, followed by the other details. See also the Notes at the end for the meanings of the various codes.

Finding a field in this list may be difficult unless you already know its FID, or what text to search for. Normally access to the definitions is made from the Field List document, which has arranged the fields firstly into the entities they belong to, then into subject headings within those entities. However if you know the FID, you can go straight to the field by adding #fid to the URL in your browser window and pressing <Return>.

[ Field List ] [ Field value codes ] [ Updates ] [ UISIC ] [ UIS ]


1 : Karst feature type
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
For those karst features which are not caves, this field denotes
what type of karst feature they are. It is mutually exclusive with
8[Cave type].

2 : Submersion
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The degree of submersion of THIS entrance. Blank if the
entrance is never submerged.

3 : Flow presence
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Describes how active THIS entrance is.
Comment:
(1) An entrance is classified as 'dry' only when it is NEVER active.
(2) Sea caves should not be classified as 'active' unless they
contain a flowing stream, permanent or intermittent. If water in
them is from the sea they should be described under 2[Submersion].

4 : Flow direction
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Describes the flow direction if THIS entrance is active, otherwise
it is blank.
Comment:
(1) An "inflow-outflow" is an entrance where sometimes the stream flow
is inwards, and at other times outwards. It is not used to describe a
through-cave with an inflow at one end and an outflow at the other:
such a cave is two items, an inflow and an outflow.
(2) An inundated sea cave does not normally qualify as an inflow-
outflow because the term refers to stream flow.

5 : Internal flow
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Describes the flow conditions inside a cave, if they differ from
the flow conditions at THIS entrance, otherwise left blank.
Example:
This field would be completed where a dry entrance led to an internal
stream, or where an intermittently active entrance led to a
permanent stream. A perennially active entrance would not have this
field completed unless its stream was joining another independent
stream inside the cave.

6 : Internal water
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Describes the internal standing water conditions in a cave if they
differ from the water conditions at THIS entrance, otherwise left
blank.

7 : Rock type
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
Describes the type(s) of rock in which the cave or karst feature is
formed.
Usage:
If this is a further entrance to a cave and its rock type is
different from the rest of the cave, then record the respective
rock type against this entrance also.

8 : Cave type
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
Describes the cave type(s), but left blank if 1[Karst feature type]
has a value.
Comment:
One of either 8[Cave type] or 1[Karst feature type] must be completed
for an item to be recorded.

9 : Quantity of entrances
Entity: CA
Data type: I       Max length:   3.       Coding: U       Single/Multi-valued: S

Definition:
The total quantity of entrances to the cave, whether they are
numbered or not, and including this one.
Comment: Normally completed only for the main record for the cave and
if there is more than one entrance.

10 : Entrance type
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Identifies whether this entrance is a vertical pothole-type entrance
or not, ignoring any inconsequential effects due to collapse in the
immediate entrance area.

11 : Development
Entity: CA
Data type: A       Max length:   3.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
Key words related to the development of the cave or karst feature,
and sequenced so that a reasonably readable statement of development
is the result.
Comment:
This is not intended to replace a description of the cave or karst
feature, but to provide a finite number of terms for development
searches. Of course the result is also a kind of description.
Usage:
(1) The same word can be used more than once.
(2) A "through-cave" should be noted using this field.
(3) A suggested method is to scan the list of available terms a few
times to become more familiar with it,
assess the significant aspects of the cave's development,
construct a brief statement, write the code numbers against each
word, and when OK, transfer the code numbers into the computer in
the correct sequence.

12 : Decoration
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The degree of decoration or secondary deposits (speleothems) in the
cave.

13 : Minimum temperature
Entity: CA
Data type: N       Max length:   5.1      Coding: U       Single/Multi-valued: S

Definition:
The minimum air temperature known to exist in the cave, expressed in
degrees Celsius (but omitting the degrees symbol).
Comment: This field is obviously too simplified to serve as an
adequate scientific statement of a cave's minimum temperature. Its
purpose is to give an approximate guide and allow preliminary
comparison/searching/sorting on the basis of temperature.

14 : Maximum temperature
Entity: CA
Data type: N       Max length:   5.1      Coding: U       Single/Multi-valued: S

Definition:
The maximum air temperature known to exist in the cave, expressed in
degrees Celcius (but omitting the degrees symbol).
Comment: See comment in 13[Minimum temperature].

15 : Minimum humidity
Entity: CA
Data type: N       Max length:   6.1      Coding: U       Single/Multi-valued: S

Definition:
The minimum humidity percent humidity known to exist in the cave.
Comment: This field is obviously too simplified to serve as an
adequate scientific statement of a cave's humidity. Its purpose is
to give an approximate guide and allow preliminary
comparison/searching/sorting on the basis of humidity.

16 : Maximum humidity
Entity: CA
Data type: N       Max length:   6.1      Coding: U       Single/Multi-valued: S

Definition:
The maximum percent humidity known to exist in the cave.
Comment: See comment under 15[Minimum humidity].

17 : Moisture level
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
A guide as to how wet or dry the cave is as a whole.
Usage:
If substantial areas of the cave depart from this average, then
choose "wide moisture range".

18 : State in cave number
Entity: CA
Data type: A       Max length:   2.       Coding: L       Single/Multi-valued: S

Definition:
The component of a cave or karst feature number which identifies the
country's State in which the cave is considered to be located.
Usage:
(1) In some cases a cave may straddle a State border. It is a matter
for local policy to decide which State the cave is considered to be
in, and whether any further entrances are considered to be in the
same State or in their actual State, for cave number purposes. The
53[Comments] field can also be used to indicate their actual State.
The cave's or entrances' locational fields would of course show their
actual position.
(2) State code is filled indirectly via the Lookup on 303[Area lookup]
(3) The local codes for a country's States can be set
in 286[State code], 287[State name], and 354[State abbreviation].

19 : Area in cave number
Entity: CA
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: S

Definition:
The component of the cave or karst feature number which identifies
the area or region where the cave is located, and is unique within
its parent State code.
Comment:
In deciding new area codes, it is best to avoid using the letters I
and O as they can become confused with the adjacent numerical serial
number component, and also with any numeric State code.
Usage: Area codes are auto-filled via lookup on 303[Area lookup].

20 : Penetrability
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Whether this entrance is penetrable or not, including entry by diving.

21 : Latitude - coarse
Entity: CA
Data type: N       Max length:   8.4      Coding: U       Single/Multi-valued: S

Definition:
The latitude given not closer than the precision specified in
294[Coarse - geogr. precision] in order not to reveal the exact
location. Expressed as +/- degrees.decimal degrees. Positive if north
of or on the Equator, negative if south of the Equator.
Comment:
(1) Expression as a real number instead of deg:min simplifies
location-based searches, and geo-coding in GIS systems.
(2) Because grid references are discontinuous at grid-zone
boundaries, lat/longs are needed to allow wide-area searches. They
also allow finding the location using an ordinary atlas.
(3) This field is available for where coarse latitude is not being
auto-derived from the exact latitude in 245[Position - latitude].
(4) Max text length: sign(1)+whole(2)+sep(1)+dec(4)=total 8, scale 4.

22 : Longitude - coarse
Entity: CA
Data type: N       Max length:   9.4      Coding: U       Single/Multi-valued: S

Definition:
The longitude given not closer than the precision specified in
294[Coarse - geogr. precision], in order not to reveal the exact
location. Expressed as +/- degrees.decimal degrees. Positive
if east of Greenwich or on the Prime Meridian, or negative
if west of Greenwich or on the 180-degree meridian.
Comment:
(1) See comments in field 21[Latitude - coarse].
(2) Max text length: sign(1)+whole(3)+sep(1)+dec(4)=total 9, scale 4.

23 : Map sheet name - coarse
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The official name of the map or mapsheet used for giving a coarse
grid reference for the cave or karst feature.
Comment:
(1) The map series to which this mapsheet belongs is given in
412[Coarse - map series] normally in the Site Parameters table.
(2) Coarse locations are OK for publication or distribution studies,
but not good enough to find the cave.

24 : Topo 100K sheet name
Entity: CA
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Replaced by 414[Map or sheet name], normally found in the grid
references table.

25 : Gr.ref qualifier - coarse
Entity: CA
Data type: A       Max length:   4.       Coding: L       Single/Multi-valued: S

Definition:
A value used in order to distinguish between similar grid references
on the one mapsheet when giving the coarse grid reference for a cave.
Comment: The description of this grid reference qualifier is given
in 413[Coarse - gr.ref qualifier], normally found in the site
parameters table.

26 : Grid reference - coarse
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: S

Definition:
The approximate grid reference for this cave, given only to the
coarse precision agreed as being suitable for publication, yet
still reasonable for local distribution analyses. Expressed using the
method described on the respective mapsheet, but omitting digits to
achieve the required coarse precision.
Comment:
(1) The precision used is defined in
295[Coarse - gr.ref precision] in the site parameters table.
(2) Accurate grid refs can be recorded in 241[Grid ref - easting] etc.

27 : Nearest locality
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The name of the village, locality or named geographical feature
nearest to the cave or karst feature.
Usage: Normally required only when lat/long and grid references are
not available.

28 : Entrance altitude
Entity: CA
Data type: N       Max length:   7.1      Coding: U       Single/Multi-valued: S

Definition:
The approximate altitude of this entrance of the cave to a precision
suitable for publication. The altitude units are set in
446[Coarse - altitude units], normally found in the site parameters
table.

29 : Degree explored
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The degree to which this cave or karst feature has been explored.
Usage: Where data is being stored per entrance as well as for the
cave, this field should be completed only for the cave.

30 : Discoverer type
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The type of event now being recorded about the original discovery
or recording of this cave or karst feature.
Example: It could be when the cave was first found, explored, or
recorded.
Usage:
(1) This entry is mandatory if the discovery name or date fields
are filled in.
(2) These discovery fields are multi-valued, therefore the various
discovery and first exploration and recording events can all be
recorded if known.
(3) The discovery of later extensions can be recorded in field
35[Extension discovery].

31 : Discoverer name
Entity: CA
Data type: A       Max length:  45.       Coding: U       Single/Multi-valued: M

Definition:
The name of the person(s) and/or organisation(s) who were involved
in this original event for the cave or karst feature. The preferred
formats are surname then initials for people, or initials without
full stops for organisations.
Comment:
Ideally the value for this field would be shown on the screen
simply by a link to 478[Person ID] or 380[Organisation ID] in the
person or org databases, via links on the discovery fields
for Person ID or Organisation ID. A 'names'
field would then not be needed in the 'caves discovery' table at all.
An actual field is needed in the caves-discovery table only when
the database software does not allow such a link to the People or
Organisations databases.
Usage:
Normally you would need to enter a value here only if:
- the information was not autofilled by your lookup on Person or
Organisation ID.
- the person or organisation details were not available in a Person
or Organisation database at this site.

32 : Discoverer day
Entity: CA
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: M

Definition:
The day of the month of the respective discovery event, in the range
1-31.
Usage: If unknown, leave blank.

33 : Discoverer month
Entity: CA
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: M

Definition:
The month number of the respective discovery event, in the range 1-12.
Usage: If unknown, leave blank.

34 : Discoverer year
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: M

Definition:
The year, in full, of the respective discovery event.
Usage: If unknown, leave blank.

35 : Extension discovery
Entity: CA
Data type: A       Max length:  52.       Coding: U       Single/Multi-valued: M

Definition:
Brief information about the discovery of a later extension to a cave,
including extension name, discoverer name(s), and date.
Examples:
(1) Starburst Chamber: TCC, 26 Jan 1958.
(2) Kelly's passage: Kelly J C & Downs X A, 13 June 1987.
Usage: For multiple extensions, these are best entered in date order,
earliest first. (Edit the value sequence numbers to alter the order.)

36 : Discoverer date
Entity: CA
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: M

Definition:
The full date of the respective discovery event, in database date
format.
Usage: Normally used only where a date-format field is wanted. Note
that this field can accept only fully specified dates.

37 : Genus name
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: M

Definition:
The genus name of a biological specimen found in the cave.
Usage:
(1) The accuracy of the genus identification should be indicated
in 509[Genus confidence level].
(2) A Genus value can be entered only via a lookup table. This
ensures that only valid and correctly spelt species can be entered,
which aids later searching. To achieve this,
the lookup table on this 37[Genus name] field allows
loading of both the genus and the species values, with no separate
lookup table for 38[Species name], except for allowing special
species notations (See 38[Species name] help).
(3) If your site also has a Specimen database as part of this system,
then Genus/species can be automatically filled in via a lookup on the
nearby 364[Specimen ID] field.
(4) If a wanted Genus/species is
missing from the Genus lookup table, please contact your database
administrator to have it added.

38 : Species name
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: M

Definition:
The species name of a biological specimen found in a cave.
Usage:
(1) The accuracy of the species identification should be
indicated in the 510[Species confidence level] field.
(2) If the Genus is known but the species is not, or, if it is a new
species, then the correct notation can be entered by loading the
Genus field with any species having the correct Genus in the Genus
lookup table, then using the lookup table on this 38[Species name]
field to overwrite the species with the correct notation.
(3) If a wanted species is not in the Genus/species lookup table,
please contact your database administrator to have it added.

39 : Species ref - surname
Entity: CA
Data type: A       Max length:  45.       Coding: U       Single/Multi-valued: M

Definition:
The surname(s) and initials of the author(s) of a reference
describing the occurrence. Otherwise,
the surname and initials of the person identifying the species
occurrence in the cave, or the name of the person whose
collection is holding it.
The format for an author should be: "surname, initials".
Example: Brown, D.E. and McDougal, M.A.
Usage:
This field would normally only need to be filled in if the value could
not be auto-filled via a lookup on the relevant Article ID in
263[Species ref - article ID], or on a specimen via 364[Specimen ID].

40 : Species significance
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
Any special significance which this species occurrence in the
cave or karst feature may have. Expressed as a coded value.
Usage:
This field would normally only need to be filled in if the value
was not shown or auto-filled via a link to the relevant
Specimen ID in 364[Specimen ID].

41 : Cave use
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The present use (if any) being made of the cave, or of this entrance
if a multi-entrance cave.
Comment: "wild tourist cave" in the value means a cave which is
more or less in its wild state without added construction work for
tourists, but is known to and accessible to the general public, as
opposed to cavers, via some form of entry management or control.

42 : Owner type
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The owner category for this particular entrance.
Comment:
(1) A multi-entrance cave could have several owner categories.
(2) Ownership of normal public reserves should be stated as
"govt owned" - the phrase "community owned" means joint possession
and control by the community, and generally applies to tribal
ownership.

43 : Damage
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The types of damage present in the cave.

44 : Management classifier
Entity: CA
Data type: A       Max length:   8.       Coding: L       Single/Multi-valued: S

Definition:
The state-agreed initials or abbreviation for the organisation who
has allocated the management classification to the cave.
Usage:
(1) Left blank if not formally classified.
(2) Mandatory if 45[Management category] is completed.
(3) If this field is completed, then 45[Management category] should
also be completed.

45 : Management category
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The formal category into which the cave or karst feature has been
placed by the management authority.
Usage:
(1) If a cave has more than one classification, or different parts
of it are classified differently, then choose "multi-category" and
give details in 53[Comments].
(2) If this field is completed, then 44[Management classifier] should
also be completed.

46 : Protection methods
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The situation or measures which assist in the protection of the cave
or karst feature.

47 : Controller
Entity: CA
Data type: A       Max length:   8.       Coding: L       Single/Multi-valued: S

Definition:
The state-agreed initials of the controlling organisation.
Comment: Normally omitted if controlled by a private owner or manager.
Usage: If no per-trip permission is required, enter "nobody" (See
pre-text, "entry permission from".)

48 : Importances
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
Aspects for which this cave or karst feature is important, including
the type(s) of any specific studies made in the cave.
Usage: If studies have been performed, include them in the References
database and cross-reference to them via cave field 270[Article ID].

49 : Surface use
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The present surface use(s) of the land in which this cave entrance or
karst feature is located.

50 : Difficulties
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
Unusual equipment, skills or activities which are unavoidable in a
normal visit or reasonable exploration of the cave, rather than when
pushing the cave to its limits.

51 : Prospects
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
Indications which point to the likelihood of further extensions to
the known cave being possible.

52 : Hazards
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
Dangers which could be encountered in some parts of the cave or
karst feature.

53 : Comments
Entity: CA
Data type: A       Max length:  62.       Coding: U       Single/Multi-valued: M

Definition:
Comments lines about a cave or karst feature.
Usage:
(1) This field should be used only when a suitable more specific field
is not available because (1) the comments cannot easily be displayed
in various languages, and (2) its information is difficult to make
use of in analyses and searches.
(2) One valid use of Comments is for qualifying an entry in another
field or for specifying a field value choice which was not available.
(3) Each field value is one line of the overall comments.
(4) Use semicolons (;) between separate comments.

54 : Percent mapped
Entity: CA
Data type: I       Max length:   4.0      Coding: U       Single/Multi-valued: S

Definition:
The approximate percentage of the known extent of the cave which
has been mapped.
Usage: Do not include the % symbol.

55 : Map source - org code
Entity: CA
Data type: A       Max length:   3.       Coding: U       Single/Multi-valued: M

Definition:
The standard 3-letter organisation code for the organisation
which produced the map which is being referenced for the cave or
karst feature.
Comment: See Comment in field 264[Map sequence number].
Usage:
You would normally need to enter this value only when:
- the information was not auto-filled by the lookup on 265[Map ID], or
- the map details were not available in a map database on the site.

56 : Length
Entity: CA
Data type: N       Max length:  10.1      Coding: U       Single/Multi-valued: S

Definition:
The aggregate length of the cave or karst feature in metres.
Usage:
(1) The method used should be indicated in 57[Length method].
(2) Dimensions which are better described as horizontal extent can
be entered in 67[Extent length] and 68[Extent width].
(3) When caves join, or when there is more than one numbered
entrance, the total length should be recorded only in the nominated
"cave" record, not in any entrance records.

57 : Length method
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The method used in arriving at the stated length of a cave or karst
feature.
Usage: This field should always be used when 56[Length] is completed,
but not if it is empty.

58 : Length accuracy
Entity: CA
Data type: N       Max length:  10.2      Coding: U       Single/Multi-valued: S

Definition:
The accuracy of the stated length of a cave or karst feature, stated
in +/- metres.
Example: If the length is between 510 and 520 metres, then the length
should be given as 515 and the value of this field as 5, i.e.
515m +/-5m.

59 : Extent below entrance
Entity: CA
Data type: N       Max length:   8.2      Coding: U       Single/Multi-valued: S

Definition:
The vertical distance the cave extends below the lowest point of the
entrance, in metres.
Usage:
(1) If only the overall vertical range is known, or if this is a
karst feature, use 511[Vertical range] instead of this field.
(2) If the entrance is in a karst feature, such as a doline, the
entrance is taken to be where the cave leaves the profile of the
karst feature.
(3) If this field is completed, then 61[Vertical method] should be
completed, and also 62[Vertical accuracy] if possible.
(4) Any underwater depth, if known, should be included. The depth to
the watertable can be shown in 53[Comments], e.g. "wtable -50m;"
(5) When caves join, or when there is more than one numbered
entrance, this field should be completed in the nominated "cave"
record, and left blank in any entrance records.

60 : Extent above entrance
Entity: CA
Data type: N       Max length:   8.2      Coding: U       Single/Multi-valued: S

Definition:
The vertical distance the cave extends above the lowest point of the
entrance, in metres.
Usage: See notes in 59[Extent below entrance].

61 : Vertical method
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The method used in arriving at the stated vertical dimensions of
the cave or karst feature.
Usage: This field should always be completed if any of the vertical
dimension fields have been completed, but not otherwise.

62 : Vertical accuracy
Entity: CA
Data type: N       Max length:   7.2      Coding: U       Single/Multi-valued: S

Definition:
The accuracy of the stated vertical dimensions of the cave or karst
feature, stated in +/- metres.
Example: If the vertical range was calculated or estimated to be
between 70 and 80 metres, then the vertical range should be stated
as 75 and this field as 5, i.e. 75m +/-5m.

63 : Length of largest chamber
Entity: CA
Data type: N       Max length:   8.2      Coding: U       Single/Multi-valued: S

Definition:
The length of the largest chamber in a cave, in metres.
Usage: Normally completed only for a chamber of notable size.

64 : Width of largest chamber
Entity: CA
Data type: N       Max length:   8.2      Coding: U       Single/Multi-valued: S

Definition:
The width of the largest chamber in a cave, in metres.
Usage: Normally completed only for a chamber of notable size.

65 : Height of largest chamber
Entity: CA
Data type: N       Max length:   8.2      Coding: U       Single/Multi-valued: S

Definition:
The height of the largest chamber in a cave, in metres.
Usage: Normally completed only for a chamber of notable size.

66 : Pitches
Entity: CA
Data type: N       Max length:   7.1      Coding: U       Single/Multi-valued: M

Definition:
All pitch lengths (not rope or ladder lengths) in a cave, in metres,
and listed nominally in sequence from upper to lower level.

67 : Extent length
Entity: CA
Data type: N       Max length:   8.1      Coding: U       Single/Multi-valued: S

Definition:
The maximum overall horizontal extent of a cave or karst feature, in
metres, i.e. the straight-line horizontal distance between its
furthermost ends.
Comment: When combined with 68[Extent width] it forms the length of
the smallest horizontal rectangle which would just encompass the cave
or karst feature.

68 : Extent width
Entity: CA
Data type: N       Max length:   8.1      Coding: U       Single/Multi-valued: S

Definition:
The maximum overall horizontal width of a cave or karst feature, in
metres, the width being measured in a direction at right angles to
the dimension recorded in 67[Extent length].
Comment: See comment in 67[Extent length].

69 : Other names
Entity: CA
Data type: A       Max length:  52.       Coding: U       Single/Multi-valued: M

Definition:
Further names which a cave or karst feature has or has had beyond
its current name as given in 70[Principal name], and expressed in
the local language.
Usage: See usage notes in 70[Principal name].

70 : Principal name
Entity: CA
Data type: A       Max length:  52.       Coding: U       Single/Multi-valued: S

Definition:
The current formal agreed name for a cave or karst feature, expressed
in the local language.
Usage:
(1) When choosing new names, be mindful of any local naming
guidelines which may be in effect.
(2) Where a new name is awaiting ratification, enclose it in round
brackets.
(3) Because this recorded name is likely to be propagated, take
special care to record it with the correct spelling and form.
(4) If you want the word "cave" or the like to appear in the name,
include it in the field.

71 : Ref - surnames
Entity: CA
Data type: A       Max length:  45.       Coding: U       Single/Multi-valued: M

Definition:
The surname and initials of the author(s) of a reference which is
relevant to the cave or karst feature, expressed as
"surname, initials".
Examples: "Smith, A.B., Brown, Y.L. & White, X.A.", "Smith, A.B.",
"White, X.A. et al".
Usage:
(1) Normally only needs to be filled in when the author surname(s)
cannot be auto-filled via a lookup on 270[Article ID].
(2) If the article does not yet exist in the Articles tables, enter
the surname(s) manually.
(3) If more than three authors, just enter the first author and
initials, plus "et al".

72 : Contents
Entity: CA
Data type: A       Max length:   3.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
What the cave contains.
Comment:
The purpose of this field is to be the 'plain language guide' to
what is in the cave by summarising any entries in scientific
fields such as 37[Genus name], and listing any other items which do
not have a formal classification system.
Usage:
(1) If any 'scientific' field has a contents entry, include an entry
in this field also, so that this field summarises ALL contents.
(2) If a required entry in not available in the picklist, enter it
in 53[Comments] instead.
(3) In the case of sensitive items, consider including them in the
database but flagging their security level in 467[Data security level]
or suppressing this field from printing via 75[Cave list exclusion
FID].

73 : Value sequence
Entity: SY
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: M

Definition:
The sequence number of one record among several which represent the
values of a multi-valued field, and forming part of each such record's
key.
Example:
Three  records describing three different items representing the
contents of a cave would have "Value sequences" of 1, 2, & 3 resp.
Comments:
The purpose of this field is (1) to make the key of each multi-valued
record unique, and (2) to set the sequence in which the multi-valued
records are stored and displayed.

74 : Cross-reference serial
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: M

Definition:
The serial number component of the number of other connected caves,
entrances or other karst features.
Usage:
(1) Usage will depend to some extent on how cave and karst feature
numbers have been used, for example, whether further entrances to
a cave have their own number. See the Australian 'Local help'
for examples of one method.

75 : Cave list exclusion FID
Entity: CA
Data type: I       Max length:   6.0      Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The FID of a field for this cave which is to be excluded from the
output for a Cave List.
Comment:
(1) This would normally be because the field has the same value for
all caves in the area, and the value can therefore better be covered
for Cave List purposes in the overall Area Description. Examples
could be 7[Rock type] or 42[Owner type].
(2) However where the issue is security, see 467[Data security level].

Usage:
Enter the FID of each field for this cave which does have data in
it but whose data is not to be printed out in a Cave List.

The technique is to record this common or almost common data instead
in the Region/Area entity, so that it can appear in the area notes
preceding the cave details, and then not print it in the individual
cave details. Any caves which are an exception to the norm for the
area can omit suppression of that particular field so that their
different data does get printed in the individual listings.

However, note that this common data DOES still need to be
entered into every cave's data. This is so that each cave's data is
complete in itself, and the cave will respond correctly to a
search looking for those characteristics.

Fields which are usually candidates for suppression are:
7, 21, 22, 23, 414, 25, 26, 27, 28, 42, 49, 46, 47, 78, 13-16,
71/270, 76/431.
Fields which normally should not be suppressed are:
18, 19, 77, 1, 69/70, 74, 9, 10/20/3/4/5/6, 11, 56, 57/58, 59/60/511,
61/62, 63/64/65, 66, 67/68, 52, 50, 29, 51.

This field should normally be re-assessed at each update.

76 : Latest update by
Entity: CA
Data type: A       Max length:  40.       Coding: U       Single/Multi-valued: S

Definition:
The first name, surname, and organisation of the person who most
recently provided the update data for the database for this cave or
karst feature, together with the date they supplied the information,
as opposed to the date the original information was generated.
Usage:
(1) The entry should refer only to this latest update, because the
system keeps track of previous updates.
(2) It is good practice when supplying particular updates to
review other data for the cave to see if it is still correct.
Comments:
(1) This field would normally only be available for users to enter
a value if the database system was not using the fields available
for capturing information about each update batch.
(2) Normally this field would be read-only information.
(3) A better alternative to this field is to use 431[Latest update
ID], which derives from 421-424, which allow separate fields for
Update ID, person, org, and date.
(4) For the supplier of the original information itself, see
470[Data supplier - person ID] and/or 471[Data supplier - org ID] in
the Data Quality fields.

77 : Serial in cave number
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: S

Definition:
The component of the Cave Number, within the given area code,
which identifies the cave. Normally numeric. Does not repeat within
that area code. Right-justified if numeric.
Usage:
(1) Do not include any karst feature letter suffix in the field.

78 : Entrance marking
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The type of identification marked on this particular entrance or
karst feature.
Usage:
(1) If the mark is not the cave or entrance number, but some
other identifying mark from say a surface survey or surface
exploration, choose from codes 12-18, i.e. 'identifier' rather than
cave/entrance number.
(2) If more than one type of marking is present, choose the best.

79 : Report title
Entity: RP
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The title given to a trip report or equivalent,
published or unpublished. If the author gave no title, a nominal
descriptive one may be given by the Records Keeper.

80 : Area name
Entity: RE
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The agreed name of a karst area or region.

81 : Area code
Entity: RE
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: S

Definition:
An alphabetic code of up to 3 letters to designate a karst area or
region. Normally issued by State Speleo organisation.
Comment:
This is where the code is defined rather than used.

82 : Standard short field ID
Entity: AT
Data type: I       Max length:   5.0      Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The standard international identification number for a standard
cave/karst data field. Always an integer. Issued only from the UIS
master field database.
Comments:
(1) Unlike normal data entities, standard field keys do not need
to include country and organisation codes
because they are generated only by a single master database.
(2) Non-standard fields from other databases use keys which use
principles similar to 227[Cave ID].
(3) If standard field keys are stored in the same database as
non-standard fields, then they should be prefixed by AAUIS and their
standard ID zero-filled to a width of 5 digits, e.g.
in a foreign database, Field 34 should be stored as Field AAUIS00034.

83 : Local field ID
Entity: AT
Data type: A       Max length:  10.       Coding: L       Single/Multi-valued: S

Definition:
The record ID used locally by an organisation for the definition
of a field they use.

84 : Local status of UIS field
Entity: AT
Data type: I       Max length:   1.0      Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
For a field which has been issued by UIS, this is the local status
regardless of the UIS status.

85 : Table where value set
Entity: AT
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: S

Definition:
The name of the database table where the value of the respective
field is set, as opposed to used.

86 : Master table filename
Entity: EN
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: S

Definition:
The filename of the master database table for an entity.
Example:
For the Cave entity, the master table filename in the UISIC system
is CA0000.

87 : Field length when text
Entity: AT
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: S

Definition:
The maximum number of character positions needed to contain any
possible value which the field may have when its value is expressed
using text characters.
Example:
A numeric field which has a range +/-10,000 and up to two decimal
places, would need 9 character positions to ensure all values
could be accomodated: (sign(1) + whole number digits(5) + decimal
separator(1) + decimal digits(2) = total(9)).
A date field may require a field length of 10 for text
representation: (day digits(2) + day/month separator(1) + month
digits(2) + month/year separator(1) + year digits(4) = total(10)).
Comment:
This field is needed when non-text fields are converted to text
representation for transfer between databases.

88 : Field scale
Entity: AT
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: S

Definition:
The number of decimal places which a particular numeric field
requires.

89 : Field position when fixed
Entity: AT
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: S

Definition:
The character position for the start of a particular field when
its table has been exported to fixed-length text format.
Comment:
(1) This would normally be in preparation for construction of
a text-based Karst Data Interchange (KDI) file.
(2) This value will vary according to the database design being used
at the specific source site.

90 : Field seq when delimited
Entity: AT
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: S

Definition:
The sequence position (1st, 2nd, 3rd, etc) of a particular field
when its table has been exported to delimited text format.
Comment:
As for 89[Field position when fixed].
Example:
If it is the third field, then the value would be '3'.

91 : Length type
Entity: AT
Data type: I       Max length:   1.0      Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Whether the field is of nominally 'long' or 'short' type. Long-type
is where the value in
the field could be quite long, spanning one or more lines,
and may contain delimiting characters such as commas, quotes, etc.
Short-type is where the length is quite short and limited, and does
not contain any delimiting characters.
Comment:
The main purpose for this field is to help with writing and reading
Karst Data Interchange files.
Usage:
If there is any doubt whether the field may contain delimiting
characters such as commas, quotes, etc, choose 'long' type.

92 : Data type
Entity: AT
Data type: I       Max length:   1.0      Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Not yet ready.

93 : Coding type
Entity: AT
Data type: I       Max length:   1.0      Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The type of coding, if any, used as values for the field. The
values for this field are numeric codes.

94 : SSC ID seq
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The sequence number assigned to the SSC ID for this field in order to
put the field in a convenient sequence when fields are listed by
SSC ID. Can be changed at will to rearrange order of field listing.

95 : Single or multi-valued
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

96 : UIS status of UIS field
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
For a field definition issued by UIS, this is the UIS status of the
definition.

97 : Transfer to Level 1 OK
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

98 : Transfer to Level 2 OK
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

99 : Transfer to Level 3 OK
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

100 : Local field designation
Entity: AT
Data type: A       Max length:  12.       Coding:         Single/Multi-valued: S

Definition:
The local identification for a field on the current data-entry form.
Example: ASF's local designation for Field 10 (Entrance type) is 8.1
Comment: The user is able to define the equivalence between this
current local designation and the standard ID of the field.
This allows a range of custom data-entry forms
with their fields conveniently identified for quick data entry, yet
still calling up the correct standard field.

101 : Local field code
Entity: AT
Data type: A       Max length:  12.       Coding:         Single/Multi-valued: S

Definition:
Any permanent identification used by an organisation for a field
definition other than its database Record ID.

102 : Field name - full
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

103 : Field name - short
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

104 : Pre-data text (singular)
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

105 : Post-data text (singular)
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

106 : Between-data text
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

107 : Field definition seq
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

108 : Field definition line
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

109 : Field help text seq
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

110 : Field help text line
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

111 : Field value code
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
This field holds allowable codes which can be entered in a data field.
Normally UIS standard codes.
A closed range of uncoded actual values (e.g. map sheet names)
should not be entered: instead, they should be included in a lookup
table.

112 : Field value translation
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

113 : Field value defn seq
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

114 : Field value defn line
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

115 : Table usage seq
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

116 : Field also in table
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Another table which this field appears in, apart from the table where
its value is set (Field 85).

117 : Value set or used here?
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Whether this instance of the field is for setting/defining its value,
or for using a value already set elsewhere. This would be the case
where the instance was a 'foreign key', for example. Normally a field
would be set in only one place (Field 85), so that this field here
should normally be set to 'used'.

118 : Primary/secondary key?
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

119 : A foreign key of key ID
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
This is the Field ID of the key field which this field is a foreign
key of.

120 : Local lookup table name
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The name of the lookup table, if any, for this field. May vary from
site to site.

121 : Value numeric range MAX
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The maximum numeric value allowed for this field at this site.

122 : Value numeric range MIN
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The minimum numeric value allowed for this field at this site.

123 : Field value local code
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The equivalent local code, if any, for a UIS-coded field value. For
example, the UIS system always uses numeric codes for coded field
values, but local codes for the field might be alphabetic, e.g. letter
codes for a State or a geologic formation.

124 : Organisation ID
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The internal record ID of an organisation which uses the current
field.

125 : System field used in
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

126 : Date org started field
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

127 : Field usage comment seq
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

128 : Field usage comment line
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

129 : Date org started fld val
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

130 : Fldval usage comment seq
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

131 : Fldval usage comment line
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

132 : Entity ID
Entity: EN
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The identifier and database key for an Entity. It consists always of
a unique pair of letters, chosen to represent as closely as possible
and in as many languages as possible, the name of the entity, while
remaining a unique pair.

133 : Local short entity name
Entity: EN
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
This is the version of the entity name to be used locally, and in the
local language.

134 : Numeric width in keys
Entity: EN
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The quantity of characters forming the zero-filled, fixed-width,
numeric part of the Record ID for instances of this entity.
Example: For the Cave Record ID "AUASF00035" created by ASF in
Australia, the fixed numeric width is "5".
Comment: The numeric part is right-justified and zero-filled so
that the alphanumeric keys will sort in numeric order.

135 : SSC ID
Entity: SU
Data type: A       Max length:   8.       Coding:         Single/Multi-valued:

Definition:
The ID code assigned to a subject in the Speleological Subject
Classification (SSC) System. It can be up to 8 digits long, each
successive digit representing a subdivision of the subject
represented by the previous digit. Its data type is
alphabetic so that it will stay left-justified for proper sorting.

136 : SSC parent ID
Entity: SU
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

137 : SSC grandparent ID
Entity: SU
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

138 : SSC designation
Entity: SU
Data type: A       Max length:  15.       Coding: U       Single/Multi-valued: S

Definition:
Not yet ready.

139 : SSC attention needed?
Entity: SU
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

140 : SSC status
Entity: SU
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

141 : SSC ID
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

142 : Entity ID of field owner
Entity: AT
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Not yet ready.

143 : Subject comment sequence
Entity: SU
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

144 : Subject comment line
Entity: SU
Data type: A       Max length:  70.       Coding: U       Single/Multi-valued: M

Definition:
Not yet ready.

145 : Subject name - English
Entity: SU
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

146 : Subject descrip - English
Entity: SU
Data type: A       Max length: 210.       Coding: U       Single/Multi-valued: S

Definition:
Not yet ready.

147 : Subject instr - English
Entity: SU
Data type: A       Max length: 140.       Coding: U       Single/Multi-valued: S

Definition:
Not yet ready.

148 : Subject name - French
Entity: SU
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

149 : Subject descrip - French
Entity: SU
Data type: A       Max length: 210.       Coding: U       Single/Multi-valued: S

Definition:
Not yet ready.

150 : Subject instr - French
Entity: SU
Data type: A       Max length: 140.       Coding: U       Single/Multi-valued: S

Definition:
Not yet ready.

151 : Entity name - English
Entity: EN
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

152 : Entity name - French
Entity: EN
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

153 : Entity name - German
Entity: EN
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

154 : UIS status UIS code
Entity: SY
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The code for the UIS status of a field or value definition issued
by UIS.

155 : UIS status UIS text
Entity: SY
Data type: A       Max length:    .       Coding: U       Single/Multi-valued: S

Definition:
The English text for the UIS status of a field or value definition
issued by UIS.

156 : Site country code
Entity: SY
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: S

Definition:
The country in which this database site is located.
Usage:
This field can be set only by the Central Database Administrator.

157 : Site organisation code
Entity: SY
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: S

Definition:
The standard three-letter code for the organisation operating this
database site.
Comment:
(1) See also 178[Organisation code], 182[Database org code].
Usage:
This field can be set only by the Regional Database Administrator.

158 : Site default language
Entity: SY
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: S

Definition:
The spoken language normally used by this database site, expressed
as an ISO 2-letter language code, normally in lower case.

159 : Pre-data text (plural)
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The plural version of text which precedes data values in a text
listing.

160 : Post-data text (plural)
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The plural version of text which follows data values in a text listing

161 : Data-entry prompt
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The prompt to be inserted on the form for this field during data entry

162 : Field value help seq
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The sequence number of a line of help text for a field value.

163 : Field value help line
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
A line of local help text for a field value.

164 : Person adding new field
Entity: AT
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The record ID of a person adding a new field.

165 : Person's organisation
Entity: AT
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: S

Definition:
The record ID of the organisation the person represents who is
proposing the new field.

166 : Date of adding new field
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The date when a person added a proposed new field to the database.

167 : Local status of new field
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The status of local existing usage of a new field proposed by a user.

168 : Person adding new value
Entity: AT
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The temporary record ID of a person who is proposing a new coded field
value for consideration by UISIC.

169 : Person's organisation
Entity: AT
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: S

Definition:
The temporary record ID of the organisation which the person is
representing who is proposing a new coded field value.

170 : Date of adding new value
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Date when person added proposed new coded field value to database.

171 : Local status of new value
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The status of local existing usage of a new coded field value
proposed by a user.

172 : Person ID - temporary
Entity: PE
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The database temporary Record ID for a person. Similar principles
to Field 177 for Organisation temporary IDs.
Comment: Typically used where there is a need to record the name
of a person against other data before the name of that person has
been formally included in the Person Database.

173 : Surname - temporary
Entity: PE
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
Surname or family name of person being temporarily registered.

174 : Given name - temporary
Entity: PE
Data type: A       Max length:  20.       Coding: U       Single/Multi-valued: S

Definition:
Given name of a person being temporarily registered.

175 : Title - temporary
Entity: PE
Data type: A       Max length:  20.       Coding: U       Single/Multi-valued: S

Definition:
Title of person being temporarily registered, e.g. Dr, Mr. Ms., etc.

176 : Person address - temp
Entity: PE
Data type: A       Max length: 200.       Coding: U       Single/Multi-valued: S

Definition:
The postal address of a person being temporarily registered. This
is a temporary field for the whole address - later it will be split
into separate fields in the UIS 'Person' database.

177 : Org ID - temporary
Entity: OR
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: S

Definition:
A database temporary Record ID for an organisation. Constructed
using same principles as Field 227 Cave ID, but using the 3-letter
Organisation Code of the site where it is being entered, as opposed
to the code for the organisation being described.
Comments:
(1) Typically used where a person is entering their organisation's
name into a database in response to a question, but is not the
organisation operating the site database currently being used.
(2) The code for the organisation may not be known, hence the
code for the current site is used to identify the record in the
interim.
(3) This ID and the associated organisation details are stored in
a separate table to the site's main Organisation Tables.
(4) Eventually the organisation will be allocated a permanent formal
ID and its temporary record deleted.

178 : Organisation code
Entity: OR
Data type: A       Max length:   3.       Coding: U       Single/Multi-valued: S

Definition:
A 3-letter code, unique within a country, to designate an
organisation within that country, and formally issued by the
country's speleological community.
Comment:
(1) There is no requirement for the code to reflect the name or
initials of the organisation, however it is obviously beneficial
if, where possible, it relates to the name or initials
of the organisation in that country's language. However because of
the many organisations in a country, it may not always be possible to
allocate the ideal code for any particular organisation.
(2) This code can be used anywhere a short or fixed-length
identifier is needed to uniquely specify an organisation.
Example:
The database internal keys to identify each cave entry need to
permanently distinguish the site which initially created the entry.
The Organisation Code is therefore used in the prefix in this key,
i.e. the prefix is Country Code + Organisation Code. So the prefix
used by the Australian Speleological Federation (Org Code = "ASF")
is AU + ASF = AUASF. The rest of the ID is a serial number from a
series unique to this prefix.
(3) The 3-letter Organisation Code is the human-usable identification
for an organisation, whereas 380[Organisation ID] is the
computer-oriented internal record ID for the organisation in the
database system.
Usage:
(1) A new Organisation Code can be issued only by the country's
formally appointed person. Send the details of the new organisation
so that they can be entered into the master Org database and a new
code issued.

179 : Org name - temporary
Entity: OR
Data type: A       Max length:  60.       Coding: U       Single/Multi-valued: S

Definition:
Temporary storage for the name of an organisation, expressed in its
national language.
Comment: Typically used when gathering data from a passing user.

180 : Org address - temporary
Entity: OR
Data type: A       Max length: 200.       Coding: U       Single/Multi-valued: S

Definition:
Temporary storage for the complete address of an organisation,
excluding the name but including the country.
Comment: Used when obtaining data from a passing user, not from the
site of data entry.

181 : Org coverage - temporary
Entity: OR
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Temporary storage for the geographical coverage of an organisation,
expressed as a numeric code.
Examples: Codes for International, National, Regional or Local.
Comment: Typically used when gathering data from a passing user.

182 : Database org code
Entity: SY
Data type: A       Max length:   3.       Coding: U       Single/Multi-valued: S

Definition:
The standard 3-letter code for the organisation controlling
the standards and design for the database being used at this site.
Comment:
See also 178[Organisation code].
Usage:
This field can be set only by the Central Database Administrator.

183 : Form seq
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The sequence number of a form which this field appears on.

184 : Detail form tablename
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The tablename of the detail form for this instance of the field.

185 : Detail form form number
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The form number of the detail table for this instance of the field.

186 : Page number of form
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The page number of the form for this instance of the field.

187 : Local status of UIS value
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
For a field value issued by UIS, this is the local status, regardless
of its UIS status.

188 : UIS status of UIS value
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
For a field value issued by UIS, this is the UIS status.

189 : Flag if field modified
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
This flag becomes set if the field definition has been altered by a
user since it was issued by UIS.

190 : Flag if value modified
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
This flag becomes set if this field value has been modified by a user
since it was issued by UIS.

191 : Local status UIS code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The code to indicate the local status of a field or value definition
which has been issued by UIS, regardless of the UIS status of that
definition.

192 : Local status UIS text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The English text to indicate the local status of a field or value
definition which has been issued by UIS, regardless of the UIS status
of that definition.

193 : Local status new code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The code to indicate the local status of a new field or value
definition proposed to UIS.

194 : Local status new text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The English text to indicate the local status of a new field or value
definition proposed to UIS.

195 : Map ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The unique database key for a map record. Same principles as Cave ID.

196 : Map scope - country code
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The country where the subject of the map is located, expressed as
its standard 2-letter country code.

197 : Map scope - state code
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The state in which the subject of the map is located, expressed as
the standard code for the state.

198 : Map scope - area code
Entity: PL
Data type: A       Max length:   5.       Coding:         Single/Multi-valued:

Definition:
If required, the code for the main area or region covered by the map.
Comments:
(1) In the case of a cave map, this would be the cave area code.
(2) If the map covers more than one region, further regions can be
added via Field 409.

199 : Map cave serial number
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The cave serial number part of a cave map number. Right-justified
to cause this alpha-numeric value to sort into numeric order.

200 : Map source - org code
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The standard 3-letter code for the organisation which produced the
map.

201 : Map sequence number
Entity: PL
Data type: A       Max length:   5.       Coding: U       Single/Multi-valued: S

Definition:
The map sequence number used by the organisation which issued the
map number.
Comment: This may or may not be the same as the organisation which
produced the map, e.g. a caving club numbering a government cave map.
The map producer can be recorded in 200[Map source - org code].

202 : Map or sheet name
Entity: PL
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The name of the map, or, if a map series, then the name of the sheet.
If there is no name, then a brief description.
Comment: In the case of a cave map which shows only the silhouetted
relationship between caves, then an entry such as 'Relates 21, 22 and
27' would be appropriate.

203 : Map & survey grade org
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The code for the organisation whose survey grading system has been
used to grade the survey and map.

204 : Map & survey grade value
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The quality level for the survey and map chosen from a particular
grading scheme.

205 : Map scale
Entity: PL
Data type: N       Max length:    .       Coding: U       Single/Multi-valued: S

Definition:
The scale of the map using the system "1:scale", but omitting the
"1:" from the entered data, e.g. for 1:200 enter only the 200.
If the map is not to scale, enter 0 (zero). If unknown, leave empty.

206 : Map views shown
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Codes to indicate what types of views the map presents from among
plan (P), long sections (L), and cross-sections (X).
Examples: PLX = shows plan, long section, and cross-sections.
PX  = shows plan and cross-sections only.

207 : Map survey year
Entity: PL
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: S

Definition:
The year (in full) in which the survey was done.

208 : Map surveyor ID
Entity: PL
Data type: I       Max length:    .       Coding:         Single/Multi-valued: S

Definition:
The internal ID of the person principally responsible for the
surveying for the map.

209 : Map source if no ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The name of the map source if it has a "source code" of GEN, the
code for covering miscellaneous sources who do not have a
specific code.

210 : Map controller if no ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Who currently controls the original of the map, if the original
source no longer does so, and if the controller does not have
a record ID on this database site.

211 : Map host area map ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The internal Record ID of the area map on which this cave map
exists, if the cave map exists only on the area map and the area
map cannot be identified from the cave map number.
Comment: A cave area map is here defined as a map showing the inter-
relationship of two or more caves, as well as the normal definition
of depicting a cave area.

212 : Map restricted Y/N
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Whether or not there is some restriction on access to the map.

213 : Map microfilmed Y/N
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Whether or not the map has been microfilmed.

214 : Map sheet size
Entity: PL
Data type: A       Max length:  25.       Coding:         Single/Multi-valued: S

Definition:
The size of the map sheet, expressed either as a standard size, or
by stating its overall dimensions. Where the map consists of several
sheets, state the size of an individual sheet.
Examples:  A4
1000mmH x 700mmV
2 x 3 ft.

215 : Map biblio updater ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The internal Record ID of the person who most recently supplied
updates for this map bibliographic information.

216 : Map biblio updater org ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The internal Record ID of the organisation which most recently
supplied updates for this map bibliographic information.
Comment: Normally this would be the organisation to which the updating
person belonged.

217 : Map biblio updater year
Entity: PL
Data type: A       Max length:   4.       Coding:         Single/Multi-valued: S

Definition:
The year (in full) in which the map bibliographic information was
most recently updated.

218 : Map comment
Entity: PL
Data type: A       Max length:  70.       Coding: U       Single/Multi-valued: M

Definition:
A line of comment about the map.

219 : Map publication - no ID
Entity: PL
Data type: A       Max length:  70.       Coding: U       Single/Multi-valued: S

Definition:
The publication details, in the case where the map has been
published but no Article ID is yet available.

220 : Country in cave number
Entity: CA
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: S

Definition:
The component in the cave number which identifies the country in
which the cave is located, expressed as a standard two-letter ISO
country code.
Usage: This country code is filled indirectly via the lookup on
303[Area lookup].

221 : Master table if updating
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Table used when the value for this field is being updated. If it
is a single-valued field, then it will probably be updated directly
in place in its normal table. But if it is multi-valued, then it
may be done in a temporary table before being copied to its
permanent table. NB: Is this still so???

222 : Form number when updating
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The form number of the form used with the table used for updating
this field. (See also Field 221).

223 : Area designation
Entity: RE
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The combination of country, state, and area codes which uniquely
identifies an area. Generally used as a single-value-lookup for
an area, e.g. AU3B for Buchan (B) area in Victoria (3) in Australia
(AU).
Comment:
It is not generally feasible to use a lookup on area alone, because
the one area code may be repeated in different States.

224 : Area country
Entity: RE
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The country in which a defined cave or karst area is located.

225 : Area state
Entity: RE
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The State in which a defined cave or karst area is located.

226 : Area ID
Entity: RE
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The unique database key for a defined Cave or Karst Area record.
Same principles as Cave ID.

227 : Cave ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The unique database key for a cave record. It consists of the
concatenation of the ISO 2-letter country code of the creating
organisation, their 3-letter organisation code, and a right-justified
integer serial number, zero-filled to the standard width for the
entity as given in Field 134[Numeric width in keys].
Example: 35th cave for ASF in Australia: AU+ASF+00035 ==> AUASF00035
The numeric width for caves is 5 digits, hence 35 ==> 00035
Comments: (1) This ID is normally used only within a database system.
(2) It is originally generated by the site creating the original
record, and is retained regardless of where the record is subsequently
copied to, in order to maintain the correct links between relational
tables.
(3) It is not the same as the "International Cave Number", which is
the published national cave number, prefixed with the 2-letter
country code.

228 : Owner - person ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The unique record ID of the owner of the cave or karst feature, if
it is a person as opposed to an organisation.
Usage:
(1) If it is an organisation rather than a person, use Field
417[Owner - organisation ID] instead.
(2) If there are no record IDs available, enter the name of the person
or organisation in Field 418[Owner - name].

229 : Local government area
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The name of the municipality or local-government area in which
the cave or karst feature is located.
Comment:
This is the area based on administration or government, typically by
a local council, as opposed to the area name based on land
definition as found in the cadastre.
Example:  "Surfcoast Shire"

230 : Update status
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The degree to which the database is up to date for this cave or
karst feature, as opposed to the amount of data stored. Numeric coded
using the codes of generic field 512[Entity update status].

231 : Previous country
Entity: CA
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: M

Definition:
The country code in any previous cave number which this cave may have
had. The country code is the 2-letter code according to international
standard ISO-3166. See also 220[Country in cave number].
Usage: This field is filled indirectly via the lookup on
304[Previous area lookup].

232 : Previous state
Entity: CA
Data type: A       Max length:   2.       Coding: L       Single/Multi-valued: M

Definition:
The State code in any previous cave number which this cave may have
had. See also 18[State in cave number].
Usage: This field is filled indirectly via the lookup on
304[Previous area lookup].

233 : Previous area
Entity: CA
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: M

Definition:
The area code in any previous cave number which this cave may have
had. See also 19[Area in cave number].
Usage: This field is filled indirectly via the lookup on
304[Previous area lookup].

234 : Previous serial
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: M

Definition:
The serial number in any previous cave number which this cave may
have had. See also 77[Serial in cave number].

235 : Cross-reference country
Entity: CA
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: M

Definition:
The country component in the number of any cave or karst feature
which is associated with this cave or karst feature.
See also 220[Country in cave number] re country.
See also 74[Cross-reference serial] re cross-referencing issues.
Usage:
This country code is filled indirecly via the lookup on
305[Cross-reference lookup].

236 : Cross-reference state
Entity: CA
Data type: A       Max length:   2.       Coding: L       Single/Multi-valued: M

Definition:
The State code in the number of any cave or karst feature associated
with this cave or karst feature.
Usage:
This field is filled indirectly via the lookup on
305[Cross-reference lookup].
See also 18[State in cave number] re state code issues.
See also 74[Cross-reference serial] re cross-reference issues.

237 : Cross-reference area
Entity: CA
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: M

Definition:
The area code in the number of any cave or karst feature associated
with this cave or karst feature.
Usage:
This field is filled indirectly via the lookup on
305[Cross-reference lookup].
See also 19[Area in cave number] re area code issues.
See also 74[Cross-reference serial] re cross-reference issues.

238 : Map scale
Entity: CA
Data type: N       Max length:   8.0      Coding: U       Single/Multi-valued: M

Definition:
The scale of the map sheet used for giving the current grid reference
of the cave, omitting the leading "1:".
Example: 25000.
Comment: Its field properties are the same as those for 205[Map
scale] for that sheet.
Usage:
(1) Normally auto-supplied when you use the lookup on the Map ID,
411[Grid ref - map ID].
(2) This field needs to be actually filled in only when the map is
not already in the site's map table, or the information is not
otherwise automatically available via a lookup on the Map ID.

239 : Map number
Entity: CA
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: M

Definition:
The official map number of the map used for giving the current
grid reference of the cave or karst feature.
Example: 4324
Comment:
To qualify the grid reference, the Map Number can be used in place of
the normal Grid Zone Designation and 100km-square pair of letters.
Usage:
(1) Normally auto-supplied when you use the lookup on the Map ID,
411[Grid ref - map ID] on this screen.
(2) This field needs to be actually filled in only when the map is
not already in the site's map table, or the information is not
otherwise automatically available via a lookup on the Map ID.

240 : Grid ref - map edition
Entity: CA
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: M

Definition:
The edition identification for the map which has been used
for the current grid reference for the cave or karst feature.

241 : Grid ref - easting
Entity: CA
Data type: N       Max length:   6.0      Coding: U       Single/Multi-valued: M

Definition:
The easting part of a grid reference for a cave or karst feature,
as shown on a particular map, and expressed in the manner described
on that map.
Comment: The purpose of this field is to locate the item on the
associated mapsheet, not to give its actual physical position. The
actual position can be given using 249[Position - easting].
Usage: The associated mapsheet used should be given using 411[Grid
ref - map ID], or if the map description is not yet in the site's
database, using 239[Map number] and 414[Map or sheet name], on the
grid ref screen.
Max text length: sign(0)+whole(6)+sep(0)+dec(0) = total 6, scale 0

242 : Grid ref - northing
Entity: CA
Data type: N       Max length:   6.0      Coding: U       Single/Multi-valued: M

Definition:
The northing part of a grid reference for a cave or karst feature,
as shown on a particular map, and expressed in the manner described
on that map.
Comment: The purpose of this field is to locate the item on the
associated mapsheet, not to give its actual physical position. The
actual position can be given using 250[Position - northing].
Usage: As for Easting, 241[Grid ref - easting].
Max text length: sign(0)+whole(6)+sep(0)+dec(0) = total 6, scale 0.

243 : Grid ref - units
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The length units in which the grid reference for a cave or karst
feature have been given, which should be the same as those of
the associated topographic map used, but expressed as a UIS coded
value.

244 : Grid ref - precision used
Entity: CA
Data type: N       Max length:   7.0      Coding: U       Single/Multi-valued: M

Definition:
The +/- precision used in the grid reference values given in the
"grid reference" fields, 241[Grid ref - easting] and 242[Grid ref -
northing], for the cave or karst feature,
and expressed in the same length units as that grid reference.
Example: If the map units are metres, and the grid reference has
been specified to the nearest +/- 1 km, then the precision
would be given as "1000".
Comment: The precision is how closely (number of significant digits)
the grid ref has been expressed, not necessarily how accurate (true)
its value is. Its accuracy can be given in field 302[Grid ref -
accuracy used].
Max text length: sign(0)+whole(7)+sep(0)+dec(0) = total 7, scale 0.

245 : Position - latitude
Entity: CA
Data type: N       Max length:  11.7      Coding: U       Single/Multi-valued: S

Definition:
The exact latitude of this cave entrance or karst feature, expressed
as +/- degrees and decimal degrees. The sign is +ve if
north of or on the Equator, or -ve if south of the Equator.
Comment: Expression as a real number, rather than as degress, minutes,
and seconds, simplifies location-based searches, and the geo-coding
of the position in GIS systems.
Example: -38.38274
Usage: The Geodetic Datum on which the latitude is based can be
given in 288[Geodetic Datum used].
Max text length: sign(1)+whole(2)+sep(1)+dec(7) = total 11, scale 7.

246 : Position - longitude
Entity: CA
Data type: N       Max length:  12.7      Coding: U       Single/Multi-valued: S

Definition:
The exact longitude of this cave entrance or karst feature, expressed
as +/- degrees and decimal degrees. The sign is +ve if
east of Greenwich or on the Prime Meridian, or -ve if west of
Greenwich or on the 180th meridian.
Comment: Expression as a real number, rather than as degrees, minutes,
and seconds, simplifies
location-based searches, and the geo-coding of the position in
GIS systems.
Example: 143.38543
Usage: The Geodetic Datum on which the longitude has been based
can be given in 288[Geodetic Datum used].
Max text length: sign(1)+whole(3)+sep(1)+dec(7) = total 12, scale 7.

247 : Position - grid zone
Entity: CA
Data type: A       Max length:   3.       Coding: U       Single/Multi-valued: S

Definition:
The Universal Transverse Mercator Grid Zone in which the
cave or karst feature lies.
Example: "55" for Grid Zone 55.
Comment:
(1) The Grid Zone is required in order to qualify full co-ordinate
eastings and northings.
(2) Sometimes the north-south Grid Zone letter
is also included (giving a Grid Zone Designation of e.g. 55H), but
this letter is not actually needed when full co-ordinates are given.
(3) Sometimes a map sheet number is given instead of a Grid Zone
in order to make a set of co-ordinates unique within a country,
e.g. using 248[Position - sheet number].

248 : Position - sheet number
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: S

Definition:
The map sheet number used in order to qualify a set of eastings and
northings, instead of using a Grid Zone Designation for this purpose.
Comment: However, Grid Zones are more internationally useful for
this purpose.
Example: In Australia, the 4-figure sheet number for the relevant
1:100 000 sheet is commonly used to make a set of grid co-ordinates
unique within the country.

249 : Position - easting
Entity: CA
Data type: N       Max length:  10.3      Coding: U       Single/Multi-valued: S

Definition:
The full easting co-ordinate value for the actual ground position
of this cave entrance or karst feature.
Comment: This is an actual ground position as opposed to a position
shown on a particular mapsheet, e.g. in 241[Grid ref - easting].
Example: 497346.623 (for an easting of 497,346.623 metres).
Usage: The units for the co-ordinate value should be as specified
in 251[Position - grid ref units].
Max text length: sign(0)+whole(6)+sep(1)+dec(3) = total 10, scale 3.

250 : Position - northing
Entity: CA
Data type: N       Max length:  12.3      Coding: U       Single/Multi-valued: S

Definition:
The full northing co-ordinate value for the actual ground position
of this cave entrance or karst feature.
Comment: This is an actual ground position as opposed to a position
shown on a particular mapsheet, e.g. in 242[Grid ref - northing].
Example: 6852369.432 (for a northing of 6,852,369.432 metres).
Usage: The units for the co-ordinate value should be as specified
in field 251[Position - grid ref units].
Max text length: sign(0)+whole(8)+sep(1)+dec(3) = total 12, scale 3.

251 : Position - grid ref units
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The length units in which the full easting and northing positional
co-ordinates have been given, expressed as a coded value.

252 : Position - gref precision
Entity: CA
Data type: N       Max length:  10.3      Coding: U       Single/Multi-valued: S

Definition:
The +/- precision of the stated full easting and northing positional
co-ordinates, expressed in the same length units as the co-ordinates.
Example: An easting stated as 497 300 metres could have a precision
of 100, 10 or 1 metre. The actual value needs to be stated.
Comment: The precision says nothing about the accuracy of the
stated position. Its accuracy should be stated in 300[Position - gref
accuracy].
Max text length: sign(0)+whole(6)+sep(1)+dec(3) = total 10, scale 3.

253 : Fourth-smallest land unit
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The official name of the cadastral land unit in which this cave or
karst feature is located, this land unit being the 4th smallest in
the cadastral hierarchy.
Example: In the hierarchy from smallest
to largest of : allotment, section, parish, county, and state,
this field would contain the name of the "county" where the cave was
located, e.g. Tambo, for the County of Tambo.
Comments: (1) The names of the various land unit types forming the
hierarchy, e.g. County here, are defined in the Site Parameters using
the multi-valued field, 293[Land unit name].
(2) These land units are distinct from "local government" or
municipal subdivisions, such as shires or cities.

254 : Third-smallest land unit
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The official name of the cadastral land unit within which this cave
or karst feature is located, this unit being the 3rd smallest in the
cadastral hierarchy.
Example: In the hierarchy from smallest
to largest of: allotment, section, parish, county, and state,
this field would contain the name of the "parish" where the cave
was located. For example, "Buchan" for the Parish of Buchan
within the County of Tambo.
Comment: These land units are distinct from "local government" or
municipal subdivisions, such as shires or cities.

255 : Second-smallest land unit
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The official name of the 2nd-smallest cadastral land unit within
which this cave or karst feature is located.
Example:
In the cadastral hierarchy from smallest to largest of: allotment,
section, parish, county, and state, this field would contain the
name or designation of the "section" where the cave was located. For
example, "F" for Section F within the Parish of Buchan.
Comment:
(1) The names forming the land unit hierarchy, e.g. "section"
in this example, are defined in the database site parameters using
Field 293[Land unit names].
(2) These cadastral land units are distinct from "local government"
or municipal subdivisions, such as shires, or cities.

256 : Smallest land unit
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The designation of the smallest separately identifiable cadastral
land parcel in which this cave entrance or karst feature is located.
See also 255[Second-smallest land unit].
Example: "21a" for Crown Allotment 21a.

257 : Directions to find cave
Entity: CA
Data type: A       Max length:  62.       Coding: U       Single/Multi-valued: M

Definition:
One line of the directions on how to get to the cave entrance or karst
feature. As many lines as necessary may be used.
Usage:
Normally a narrative of how to find the cave, starting from an
a readily found point. The cave's locational co-ordinates should be
recorded elsewhere.

258 : Access status
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The situation regarding any restrictions on access to the cave.

259 : Other cave IDs
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: M

Definition:
Any database internal record IDs this cave has had in
other database sytems.
Example: If data for this cave had also been generated in VSA's
database in Australia, then one of its "Other cave IDs" in this
database here might be "AUVSA00516".
Usage:
This is normally a read-only field for informational purposes only.
It would normally be completed only by the central database
administrator.

260 : Species ref - year
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: M

Definition:
The publication year in full for a reference or identification of
a species occurrence in the cave or karst feature.
Example: 1964
Usage: See Usage note in 39[Species ref - surname].

261 : Species ref - year suffix
Entity: CA
Data type: A       Max length:   1.       Coding: U       Single/Multi-valued: M

Definition:
The year suffix for a reference for a species occurrence in the cave
where it is necessary to distinguish between references which have
the same author(s) and year.
Comment: This is normally necessary only when producing a particular
reference list, and it may vary per reference list.
Example: "a" or "b" in the case 1964a and 1964b for the same author(s)
Usage: See usage note in 39[Species ref - surname].

262 : Species ref - comment
Entity: CA
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: M

Definition:
A comment related to a reference or an identification of a species
occurrence in the cave or karst feature.
Usage: See Usage comment in 40[Species significance].

263 : Species ref - article ID
Entity: CA
Data type: A       Max length:  11.       Coding: U       Single/Multi-valued: M

Definition:
The internal Article ID in the Articles database for a reference for
a species occurrence in the cave.
Usage: If an Articles database is part of the system, this field
would be auto-filled by a lookup on the Articles database. This
lookup might also auto-fill other nearby Species Ref fields.

264 : Map sequence number
Entity: CA
Data type: A       Max length:   5.       Coding: U       Single/Multi-valued: M

Definition:
The serial number part of a cave map number, that map having
been referenced for this cave or karst feature.
Example: For a map number of Australian cave 3B-16 equal to
AU3B16.VSA245, this field would be "245", the map serial number.
Comment:
(1) This cave database field reflects the value of field
201[Map sequence number] in the map database.
(2) Ideally the value for this field would be shown on the screen
simply by a link to 201[Map sequence number] in the map database, via
the Map ID field on this screen. A [Map sequence number] field
would then not be needed in this "Widest map" table in the cave
database. An actual field is needed in the cave database only when the
database software does not allow such a linkage to the map database.
(3) The field should be right-justified to aid sorting - it is an
alpha field rather than numeric in order that letters can also be
included if desired.
Usage:
Normally you would need to enter a value here only if:
- the information was not autofilled by your lookup on the Map ID, or
- the map details were not available in a map database at this site.

265 : Map ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: M

Definition:
The database internal record ID of a map which has been
referenced as giving an
extensive coverage of this cave or karst feature, even though it
may not be the most accurate map available of the cave.
Usage: If the details of the map have not yet been entered into
the map tables, then no ID will be available for lookup, so instead,
enter the map's details in the other fields nearby. Similarly if
there is no map database on this site.

266 : Ref - year of publication
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: M

Definition:
The publication year in full for a reference which has been cited
for this cave or karst feature.
Example: 1987
Usage: See usage notes 1 & 2 in 71[Ref - surnames].

267 : Ref - suffix to year
Entity: CA
Data type: A       Max length:   1.       Coding: U       Single/Multi-valued: M

Definition:
The year suffix for a reference cited for this cave or karst feature
where it is necessary to distinguish between references which have
the same author and year.
Comment: This is normally necessary only when producing a particular
reference list, and it may vary per reference list. Normally its
value is not known until the reference list has been completed.
Example: "a" or "b" in the case 1964a and 1964b for the same authors.
Usage: See usage notes 1 & 2 in 71[Ref - surnames].

268 : Ref - subjects
Entity: CA
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: M

Definition:
The subject(s) addressed in a reference cited for this cave or
karst feature, expressed as key words separated by commas.
Comment: The purpose is to give some quick guidance as to the
relevance of the article.
Examples: (1) "bones". (2) "habitation, artifacts".

269 : Ref - relevant page range
Entity: CA
Data type: A       Max length:  20.       Coding: U       Single/Multi-valued: M

Definition:
The relevant page number range in a reference cited for this
cave or karst feature.
Examples: (1) "112-7". (2) "27, 30-4, 120".

270 : Article ID
Entity: CA
Data type: A       Max length:  11.       Coding: U       Single/Multi-valued: M

Definition:
The database internal record ID in the Articles database for a
reference cited for this cave or karst feature. Blank if
the article is not yet in the Articles database but
the details are available for the cave database entry.
Usage:
This field would normally be auto-filled by a lookup on
the Articles database, which might at the same time auto-fill
other cave references fields on the screen.

271 : Map number
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The official number allocated to a map, or to a map sheet in a series.

272 : Map subsheet name
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The sheet name in the case where a single map is spread over
several sheets. If the subsheet has no name, then enter a short
distinguishing description.
Comment: Do not use this field for the sheet name in a map series:
instead, use Field 202 and the Map Series table.

273 : Map update year
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The year in which the map was last updated, expressed in full.

274 : Map scope - N latitude
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The latitude of the northern main boundary of the map sheet.
Format: +/- degrees.decimal degrees, e.g. -38.5
Comment: Any small extensions are handled separately.

275 : Map scope - S latitude
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The latitude of the southern main boundary of the map sheet.
Format: +/- degrees.decimal degrees, e.g. -39.5
Comment: Any small extensions are handled separately.

276 : Map scope - E longitude
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The longitude of the eastern main boundary of the map sheet.
Format: +/- degrees.decimal degrees, e.g. 144.75
Comment: Any small extensions are handled separately.

277 : Map scope - W longitude
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The longitude of the western main boundary of the map sheet.
Format: +/- degrees.decimal degrees, e.g. 144.25
Comment: Any small extensions are handled separately.

278 : Map series code
Entity: PS
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The official number or code for a Map Series.

279 : Map series name
Entity: PS
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The official name of a Map Series.

280 : Map series length units
Entity: PS
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The length units used on a map series, expressed as a coded value.

281 : Genus name
Entity: SP
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The officially recognised Genus name of a biological specimen.

282 : Species name
Entity: SP
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The officially recognised Species name of a biological specimen.

283 : Org initials - temporary
Entity: OR
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: S

Definition:
Temporary storage for the officially recognised initials for an
organisation.
Comment: Typically used when gathering data from a passing user.

284 : Country code ISO-3166
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The "Alpha-2" two-letter country code according to ISO Standard 3166.
Comment: Codes which ISO has designated for user allocation are
AA, QM-QZ, XA-XZ, and ZZ. It is therefore proposed to use AA for
"International", and XA-XZ for country regional groupings, e.g.
XA = Australasia.

285 : Country name
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The country name, sometimes abbreviated, based on ISO Standard 3166,
which corresponds to an Alpha-2 Country Code.

286 : State code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The local code for a State within a country. For example, "7" for
Tasmania within Australia, or "TX" for Texas within USA.

287 : State name
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The name of a State within a country, in the local language.

288 : Geodetic Datum used
Entity: SY
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The official name of the Geodetic Datum upon which actual location
values for latitude, longitude and co-ordinates are based.
Example:
"Australian Geodetic Datum" in Australia.
Usage:
(1) Depending on the table structure being used at your database
site, this field might appear once for the whole site, or else for
each location entered.
(2) This field can be set only by the Regional Database Administrator.

289 : Map Grid used
Entity: SY
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The official name of the Map Grid upon which the actual location
co-ordinates are based, as opposed to the map grid co-ordinates
given using any specific mapsheet.
Example:
"Australian Map Grid" in Australia.
Usage:
(1) Depending on the table structure being used at your database site,
this field might appear once for the whole site, or else for each
location entered.
(2) This field can be set only by the Regional Database Administrator.

290 : Table scroll arrows Y/N
Entity: SY
Data type: L       Max length:   1.       Coding: U       Single/Multi-valued: S

Definition:
The default value for whether the database site wants the arrows
which indicate the scrolling situation for the detail tables on
a multi-table screen to be available or not.
Comment:
(1) Leaving them off allows better performance on a low-powered PC.
(2) This value can be overridden for the duration of a particular
session.
Example:
1 = Yes, 0 = No.

291 : Code translations Y/N
Entity: SY
Data type: L       Max length:   1.       Coding: U       Single/Multi-valued: S

Definition:
The default value for whether the database site wants to have field
value codes translated into the selected language on the screen
during operation.
Comment:
(1) Leaving them off will improve performance on a low-powered PC.
(2) This value can be overridden during any particular session.
Example:
1 = Yes, 0 = No.

292 : Government level name
Entity: SY
Data type: A       Max length:  15.       Coding: U       Single/Multi-valued: M

Definition:
The name of one of the levels of government in the country.
Comment:
(1) The levels should be stored in order of size with the largest
first and the smallest last.
Example:
In Australia there are two levels below "country" - the first is
"State", and the second is "Local Government Area", i.e. municipality.
Usage:
This field can be set only by the Central Database Administrator.

293 : Land unit name
Entity: SY
Data type: A       Max length:  15.       Coding: U       Single/Multi-valued: M

Definition:
The name of one of the series of land units used within the
country to subdivide land.
Comment:
These should be stored in order of size with the largest first and
the smallest last.
Example:
In the State of Victoria in Australia, land is divided first by
"State", then by "County", "Parish", "Section", "Crown allotment",
"LP" (lot on plan), "Lot".
Usage:
This field can be set only by the Regional Database Administrator.

294 : Coarse - geogr. precision
Entity: SY
Data type: N       Max length:   8.4      Coding: U       Single/Multi-valued: S

Definition:
The precision to which the coarse geographic co-ordinates,
21[Latitude - coarse] and 22[Longitude - coarse], can be given,
expressed in degrees.decimal degrees.
Comment:
(1) Having coarse co-ordinates available allows publication of
an approximate location to enable spatial searches and reports
without revealing the exact location. This field chooses the coarse
precision which is suitable for coarse lat/longs in this country.
Example:
In Australia the precision used is 0.0833 degrees (5 minutes).
Max text length:
sign(1)+whole(2)+sep(1)+dec(4) = total 8, scale 4.
Usage:
This field can be set only by the Central Database Administrator.

295 : Coarse - gr.ref precision
Entity: SY
Data type: N       Max length:  10.3      Coding: U       Single/Multi-valued: S

Definition:
The precision to which the coarse grid references, 26[Grid reference
- coarse], can be given, using the same units as the grid references.
Comment:
Having coarse co-ordinates available allows publication of an
approximate location to enable spatial searches and reports without
revealing the exact location. This field chooses the coarse
precision which is suitable for coarse grid refs in this country.
Example:
In Australia coarse grid references are given to a precision of
10 000 metres (10km).
Max text length:
sign(0)+whole(6)+sep(1)+dec(3) = total 10, scale 3.
Usage:
This field can be set only by the Central Database Administrator.

296 : Coarse - grid ref units
Entity: SY
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The length units in which the coarse grid references are given,
expressed as a coded value.
Usage:
This field can be set only by the Central Database Administrator.

297 : Length category
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The broad length grouping to which the cave belongs.
Comment:
Benefits of this field include (1) often enabling a cave to be length-
classified before the actual length is known, (2) reducing length
updating load in national/central databases where the latest actual
length is stored with the local club.

298 : Length units
Entity: SY
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
A generic coded field which can be used for translating the coded
values used by any field containing codes which specify the units
of length used.
Usage:
UIS fields related to length measurement will already specify the
unit to be used, i.e. the units are always fixed for a particular
field, so this field is not needed. However, where a field is
describing lengths set outside our control, e.g. the grid units used
on a government-produced topographic map, then the field's length
units are not pre-determined and so a further field is needed to
specify the length units used. Having length units fixed for a
particular field greatly simplifies data transfers; a further
possibility would be separate fields for different units (not
recommended!).

299 : Length units abbreviation
Entity: SY
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
A generic coded field which can be used for translating the codes
used by any length unit field into abbreviations for the length units.

300 : Position - gref accuracy
Entity: CA
Data type: N       Max length:  10.3      Coding: U       Single/Multi-valued: S

Definition:
The +/- accuracy of the stated full easting and northing positional
co-ordinates, expressed in the same length units as the co-ordinates.
Example: An easting stated as 497 300 metres could have an accuracy
ranging from + or - hundreds of metres down to + or - 1 metre. The
accuracy needs to be stated.
Comment: The accuracy says nothing about the precision with which
the value has been stated. Its precision should be stated in
252[Position - gref precision].
Max text length: sign(0)+whole(6)+sep(1)+dec(3) = total 10, scale 3.

301 : Field is not suppressible
Entity: AT
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Flag to show that this field cannot be included among those which
are to be suppressed from a cave listing. (Many fields can be
suppressed from a listing because they have the same value for
every cave in an area, and can instead be covered in the area
part of the listing. They must still be stored in the database
however to enable searches on their value.)

302 : Grid ref - accuracy used
Entity: CA
Data type: N       Max length:   7.0      Coding: U       Single/Multi-valued: M

Definition:
The +/- accuracy of the grid reference values given for the cave
or karst feature in the "grid ref" fields, 241[Grid ref - easting]
and 242[Grid ref - northing], and expressed in the same length
units as that grid reference.
Example: If the map units are metres, and the accuracy of the given
grid reference is +/- 50m, then enter the accuracy as "50".
Comment: The accuracy is how close the given value is to the true
value, not how precisely (number of significant digits) it has
been expressed. The precision can be given in 244[Grid ref -
precision used].
Max text length: sign(0)+whole(7)+sep(0)+dec(0) = total 7, scale 0.

303 : Area lookup
Entity: CA
Data type: A       Max length:   7.       Coding: L       Single/Multi-valued: S

Definition:
An auxiliary field to aid using a lookup table for a cave area.
To make it unique it concatenates country+state+area codes.
See also 223[Area designation], which is the lookup for this field.

304 : Previous area lookup
Entity: CA
Data type: A       Max length:   7.       Coding: L       Single/Multi-valued: M

Definition:
An auxiliary field to aid the use of an area code lookup for
'previous cave numbers'. To make it unique it concatenates
country+state+area codes.
See also 223[Area designation], which is the lookup for this field.

305 : Cross-reference lookup
Entity: CA
Data type: A       Max length:   7.       Coding: L       Single/Multi-valued: M

Definition:
An auxiliary field to aid the use of an area lookup table on
Cross-references. To make it unique it concatenates
country+state+area codes.
See also 223[Area designation], which is the lookup for this field.

306 : Auxmaster name
Entity: SY
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: S

Definition:
The name of an auxmaster table. Enables each auxmaster table to be
kept up to date with its respective entity ID. This field will
appear in the auxmaster table for each entity, e.g. for caves, will
appear in CA0000x0.

307 : Article ID
Entity: AR
Data type: A       Max length:  11.       Coding: U       Single/Multi-valued: S

Definition:
The unique database key for an Article record. Same principles as
Cave ID.

308 : Ref - year of publication
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The year, in full, that a reference was published.
Comment: There needs to be allowance for where the reference is not
yet published, e.g. "In Press" or "Personal Communication".

309 : Ref - suffix to year
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

310 : Book author or editor
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

311 : Ref - name of publication
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The name of the publication in which the reference appears.

312 : Ref - volume number
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

313 : Ref - issue number
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

314 : Book publisher and city
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

315 : Page range or quantity
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

316 : Bibliography present?
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

317 : Quantity of maps
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

318 : Quantity of plates
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

319 : Country where published
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

320 : ISSN or ISBN
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

321 : State supplying this ref
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

322 : Type of publication
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

323 : Local abstract year
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

324 : Local abstract category
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

325 : Local abstract reference
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

326 : BBS year
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

327 : BBS sequence number
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

328 : SSC code
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

329 : Flag if surname overflow
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

330 : Author sequence
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

331 : Author surname
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

332 : Author initials
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

333 : Article comment
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

334 : Compacted surnames
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

335 : Ref - name of article
Entity: AR
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Not yet ready.

336 : Local abstracts name
Entity: SY
Data type: A       Max length: 132.       Coding: U       Single/Multi-valued: S

Definition:
The name of the bibliographic abstracts publication which has been
referred to in the "local abstracts" fields in the References table.
Usage:
This field can be set only by the Regional Database Coordinator.

337 : Local abstracts initials
Entity: SY
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The initials or abbreviation of the bibliographic abstracts
publication which has been referred to in the "local abstracts"
fields in the References table.
Example:
"ASA" for "Australian Speleo Abstracts".
Usage:
The field can be set only by the Regional Database Administrator.

338 : AT coding-type code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
A range of available code numbers for indicating the coding-type
of a field. For example, whether it is uncoded, has a standard code,
or has a local code.

339 : AT coding-type text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The text corresponding to an 'AT coding-type code'.

340 : Field length-type code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The range of integer codes available to indicate a field's length
type for data interchange purposes, e.g. whether it is a long or a
short field.

341 : Field length-type text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The text corresponding to a 'Field length-type code'.

342 : Key status code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
A range of integer codes to indicate whether a field is a primary
or secondary key.

343 : Key status text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The text corresponding to a 'key status code'.

344 : AT cardinality code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
A range of integer codes to indicate whether a field is single-
valued or multi-valued.

345 : AT cardinality text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The text corresponding to an 'AT cardinality code'.

346 : Value set code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
A range of available integer codes to indicate whether a field is
set or whether it is used in a particular table.

347 : Value set text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The text corresponding to a 'value set code'.

348 : AT data-type code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
A range of available integer codes to indicate the data-type of
a field. For example, numeric, integer, alphanumeric, etc., types.

349 : AT data-type text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The text corresponding to an 'AT data-type code'.

350 : Language code ISO-639
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The range of available codes from the ISO-639 international
standard to indicate the language being used. These codes are
two-letter lower-case codes.

351 : Language text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The text corresponding to a 'Language code ISO-639'.

352 : SSC update-status code
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
A range of available integer codes to indicate the update status
of an SSC category.

353 : SSC update-status text
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The text corresponding to an 'SSC update-status code'.

354 : State abbreviation
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The common abbreviation (as opposed to the code) for a State in a
country.

355 : Ref - name of article
Entity: CA
Data type: A       Max length: 132.       Coding: U       Single/Multi-valued: M

Definition:
The article name of a reference cited for this cave or karst
feature.
Usage: See usage notes 1 & 2 in 71[Ref - surnames].

356 : Ref - name of publication
Entity: CA
Data type: A       Max length: 132.       Coding: U       Single/Multi-valued: M

Definition:
The name of a publication cited for this cave or karst feature.
Usage:
(1) For serial publications, use the local standard abbreviations.
(2) See also usage notes 1 & 2 in 71[Ref - surnames].

357 : Ref - volume number
Entity: CA
Data type: A       Max length:   7.       Coding: U       Single/Multi-valued: M

Definition:
The volume number of a publication cited for this cave or karst
feature, without any punctuation.
Comment: Any punctuation will be added during output presentation.
Usage: See usage notes 1 & 2 in 71[Ref - surnames].

358 : Ref - issue number
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: M

Definition:
The issue number, normally within a volume, of a publication
cited for this cave or karst feature, but without any punctuation.
Comment: Any punctuation will be provided during output presentation.
Example: "3" in the case of a volume and issue of 5(3).
Usage: See usage notes 1 & 2 in 71[Ref - surnames].

359 : Map or sheet name
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: M

Definition:
The name of the map, or sheet of a map, which has been referenced
for this cave or karst feature.
Comment:
(1) This cave database field reflects the value of field
202[Map or sheet name] in the map database.
(2) See also Comment (2) in field 264[Map sequence number].
Usage:
Normally you would need to enter a value here only if:
- the information was not autofilled by your lookup on the Map ID, or
- the map details are not available in a map database at this site.

360 : Map & survey grade org
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: M

Definition:
The initials of the organisation whose survey and mapping grades
have been used to grade the map which has been referenced for
this cave or karst feature.
Comment:
(1) This cave database field reflects the value of field
203[Map and survey grade org] from the map database.
(2) See also Comment (2) in field 264[Map sequence number].
Usage:
Normally you would need to enter a value here only if:
- the information was not autofilled by your lookup on the Map ID, or
- the map details are not available in a map database at this site.

361 : Map & survey grade value
Entity: CA
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: M

Definition:
The survey and mapping grade of a map which has been referenced for
this cave or karst feature.
Comment:
(1) This cave database field reflects the value of field
204[Map & survey grade value] from the map database.
(2) See also Comment (2) in field 264[Map sequence number].
Usage:
Normally you would need to enter a value here only if:
- the information was not autofilled by your lookup on the Map ID, or
- the map details are not available in a map database at this site.

362 : Map scale
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: M

Definition:
The scale of a map which has been referenced for this
cave or karst feature, and expressed as
the ground distance of the "representative fraction".
Example: For a map of scale 1:1000, the value would be 1000.
Comment:
(1) This cave database field reflects the value of field
205[Map scale] from the map database.
(2) See also Comment (2) in field 264[Map sequence number].
Usage:
Normally you would need to enter a value here only if:
- the information was not autofilled by your lookup on the Map ID, or
- the map details are not available in a map database at this site.

363 : Dates of surv/issue/amend
Entity: CA
Data type: A       Max length:  15.       Coding: U       Single/Multi-valued: M

Definition:
A combined textual statement of the three main dates related
to a map which has been referenced for this cave or
karst feature, namely, survey date, map issue date, and date of
latest map amendment. A forward slash separates the three components.
Examples: 1977/79/83B, 1977/in prep 79.
Comment:
(1) This cave database temporary field reflects the value of fields
207[Map survey year], 401[Map issue year] and 273[[Map update year]
for this map from the map database. It will be replaced by three
equivalent cave database fields.
(2) See also Comment (2) in field 264[Map sequence number].
Usage:
(1) Normally you would need to enter values here only if:
- the information was not autofilled by your lookup on the Map ID, or
- the map details are not available in a map database at this site.
(2) This is an informal text entry; year-only is sufficient for
date, but include century in the first date; if surveyed but not yet
issued, replace issued date by "in prep" + year, if appropriate;
amendment letter or number can follow the amendment date.

364 : Specimen ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: M

Definition:
The database internal record ID in the Specimen table which
corresponds to this specimen from this cave or karst feature.
Comment: This is the internal database key, as distinct from any
published Specimen Number.
Usage: This field would normally be auto-filled by a lookup on
the Specimen database, which might at the same time also auto-fill
other 'species found' fields.

365 : Special land parcel
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The name of the smallest land parcel where the cave or karst feature
is located, for the case where the parcel nomenclature is not normal.
Example: If the normal nomenclature at this level was "allotment
number", but the cave was not in an allotment but in a special
reserve, then the entry here might be "Buchan Caves Reserve", instead
of using the typical allotment number field, 256[Smallest land unit].

366 : Map series ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The record ID of the map series to which this map belongs, if any.

367 : Map type
Entity: PL
Data type:         Max length:    .       Coding: I       Single/Multi-valued:
                                          Codes
Definition:
The type of map from the point of view of its principal use,
expressed as a coded value.
Example: a code to indicate 'topographic', 'cadastral', 'cave map',
etc.

368 : Map scope - other country
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued: M

Definition:
A further country covered by the map, expressed as the standard
2-letter country code.

369 : Map scope - other state
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued: M

Definition:
A further State covered by the map, expressed as the standard State
code.

370 : Map source - country
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The country in which the producer of the map is located, as opposed
to the country of the item depicted on the map.

371 : Map series ID
Entity: PS
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The unique database key for a Map Series record. Same principles as
Cave ID.

372 : Map series abbreviation
Entity: PS
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The abbreviation for a map series name.

373 : Map series scale
Entity: PS
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The scale used for a map series, expressed as the numeric part of
a "1:n" expression.
Example: For a 1:50 000 series, enter "50000".

374 : Map series publisher ID
Entity: PS
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The publisher of a map series, expressed as an internal Record ID.

375 : Sequence for lookup
Entity: SY
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
A dummy sequence number to provide a unique lookup value for use
where the lookup has duplicate values in the looked-up field.
This field is needed only because of a quirk of Paradox software.
Example: The Genus+Species lookup on the genus field has duplicate
genus values; to allow selection of other than the first of these, a
unique value for the lookup field must be provided. So we lookup on
the sequence number but copy down same-named fields, i.e. genus and
species only.
Comment: The width of this field will vary with each use of it because
it must match the width of the actual field being looked up.

376 : Organisation country code
Entity: OR
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: S

Definition:
The country with which an organisation is concerned, expressed as a
2-letter ISO standard code.
Comment: International organisations should use code AA.

377 : State code
Entity: OR
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: S

Definition:
The State within a country in which an organisation is located,
expressed as a coded value.

378 : Postcode
Entity: OR
Data type: A       Max length:  12.       Coding: U       Single/Multi-valued: S

Definition:
The postcode or zip code for the address of an organisation.

379 : Postcode first Y/N
Entity: OR
Data type: I       Max length:   1.0      Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Whether the postcode of an organisation is placed first in an
address line, expressed as 1 for Yes or 0 for No.
Comment: This allows for placing the postcode first or last when
forming an address line.

380 : Organisation ID
Entity: OR
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: S

Definition:
The unique internal database key for an Organisation record. Same
principles as for 227[Cave ID].
Usage:
(1) To prevent a different ID for the same Organisation being
generated by several sites, its ID needs to be generated by a
single master Organisation database site. So if you need to refer
to an Organisation record which is not in your read-only
Organisation database, email the Organisation's details to the
Organisation database administrator, who will send back a new
record for importing into your Org database and updating your
Org lookup tables. It will be sent to all other sites at the
same time.

381 : Organisation type
Entity: OR
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The type of organisation with respect to whether it is a club, a
commercial business, a government agency, or the like. Expressed as
a numeric code.

382 : Organisation defunct Y/N
Entity: OR
Data type: I       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Whether or not the organisation is now out of existence, expressed
as 1 for Yes or 0 for No.
Comment: Field 384 can be used to show another organisation which
may now have possession of its assets, such as maps, records, etc.

383 : Final year if defunct
Entity: OR
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: S

Definition:
If the organisation is now out of existence, the final year in which
it was active. Expressed as 4 digits.

384 : Current org ID if defunct
Entity: OR
Data type: A       Max length:   9.0      Coding: U       Single/Multi-valued: S

Definition:
If the organisation is no longer in existence, the Org ID (Field
380) of the organisation which now holds its assets, such as maps,
reports, etc.

385 : Address line
Entity: OR
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: M

Definition:
A line of the postal address for an organisation which comes after
the organisation's name and before the line containing the city or
suburb.
Comment: Typically there would be only one entry - a line containing
the street and site number, however in other cases there may also
be lines for building name, house name, a 'care-of' line, or
whatever else is needed to define the address.
Because these lines need to be long, but are only occasionally
needed, they have been separated from the main table to save space.

386 : Address line 1
Entity: OR
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The first line of an organisation's address after its name, but not
including the city or suburb.

387 : Address line 2
Entity: OR
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The second line of an organisation's address, if necessary, but not
including the city or suburb.

388 : Address line 3
Entity: OR
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The third line of an organisation's address, if necessary, but not
including the city or suburb.

389 : Address line 4
Entity: OR
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The fourth line of an organisation's address, if necessary, but not
including the city or suburb.

390 : Organisation initials
Entity: OR
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: S

Definition:
The official initials of an organisation, omitting the full stops.

391 : Organisation name
Entity: OR
Data type: A       Max length:  60.       Coding: U       Single/Multi-valued: S

Definition:
The full name of an organisation. Business descriptors such as "Inc"
normally not included.

392 : City
Entity: OR
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The city or suburb component of an organisation's address.

393 : Organisation coverage
Entity: OR
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The geographical coverage of an organisation, expressed as a coded
value.
Examples: Codes for national, state, or local.

394 : Organisation grouping
Entity: OR
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Whether the an organisation consists of individuals or of other
organisations.

395 : Address country code
Entity: OR
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The country used in the address of an organisation, expressed as a
2-letter ISO-3166 code.
Comment: This is distinct from Field 376, "Organisation country
code", which shows the coverage of the organisation, e.g. European
Union, Australasia, etc.

396 : Map source - type
Entity: PL
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The type of source which produced the map, expressed as a standard
code. The source could be either an organisation or a person.
Comment: Uses a lookup table which combines org & person types.

397 : Map scope - other N lat
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued: M

Definition:
The latitude of the northern boundary of any coverage appendage to
the main mapsheet.

398 : Map scope - other S lat
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued: M

Definition:
The latitude of the southern boundary of any coverage appendage to
the main mapsheet.

399 : Map scope - other E long
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued: M

Definition:
The longitude of the eastern boundary of any coverage appendage of
the main mapsheet.
Format: +/- degrees.decimal degrees.

400 : Map scope - other W long
Entity: PL
Data type: N       Max length:    .       Coding: U       Single/Multi-valued: M

Definition:
The longitude of the western boundary of any coverage appendage of
the main mapsheet.
Format: +/- degrees.decimal degrees.

401 : Map issue year
Entity: PL
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: S

Definition:
The year (in full) in which the map was originally issued.

402 : Map drafter ID
Entity: PL
Data type: I       Max length:    .       Coding:         Single/Multi-valued: S

Definition:
The person principally responsible for drafting the map, expressed as
an internal linking Record ID.

403 : Map digitised Y/N
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
Whether or not the map is available in digital form.

404 : Map sheet quantity
Entity: PL
Data type: I       Max length:    .       Coding: U       Single/Multi-valued: S

Definition:
The quantity of map sheets for the case where a map with a single
number consists of several sheets.
Comment: This field is not for specifying the number of maps in a
series.

405 : Other field ID
Entity: AT
Data type: A       Max length:  10.       Coding:         Single/Multi-valued: S

Definition:
The Record ID used by UIS for a non-standard field being used by
another organisation. Uses principles similar to Cave ID (Field 227).
Comment:
If field definitions being used by other organisations are stored,
they would use the same database structure as the UIS Master Field
Database, but with 82: [Standard short field ID] being replaced
by this field being defined here. This would also apply to fields
being considered for adding to the standard list.

406 : Map controller org ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The record ID of the organisation which currently controls the
original of the map, if the original source no longer does so.

407 : Map controller person ID
Entity: PL
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The record ID of the person who currently controls the original of
the map, if the original source no longer does so.

408 : Map controller comment
Entity: PL
Data type: A       Max length:  70.       Coding: U       Single/Multi-valued: S

Definition:
A comment about the current map controller.
Comment: Normally only relevant where the original source is no
longer the controller of the map original.

409 : Map scope - other area
Entity: PL
Data type: A       Max length:   5.       Coding:         Single/Multi-valued:

Definition:
The code for further areas or regions covered by a map sheet.
Comment: The main area is given via Field 198.

410 : Person type
Entity: PE
Data type:         Max length:    .       Coding:         Single/Multi-valued:

Definition:
The type of person, similar to Field 381 Organisation Type,
expressed as a code. The codes start at 40, in order to stay clear
of Organisation Codes, so that a field can take on a value of
either org type or person type without ambiguity.
Comment: A lookup table can be constructed which combines Org type
and person Type, for the case where a field could take on a value
of either type.

411 : Grid ref - map ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: M

Definition:
The site's UIS standard internal record ID for the map sheet upon
which this grid reference is based.
Example: AUASF04567.
Usage:
(1) If no map sheet records are yet available in the database for
reference, the following alternative identifying fields can be filled
in: 239[Map number], 238[Map scale], and 414[Map or sheet name].
(2) If map sheet records are available in the database but the
software has no link from 411 to auto-display the above three fields,
then their value can be auto-supplied instead via the lookup on 411.

412 : Coarse - map series
Entity: SY
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
A brief statement of the map series used for providing the map sheet
name and grid reference for coarse locations.
Example:
"250K topo" for 1:250 000 Topographic Series.
Usage:
This field can be set only by the Central Database Administrator.

413 : Coarse - gr.ref qualifier
Entity: SY
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
A brief statement describing the qualifier which is being used
to enable distinguishing between similar grid references on the
one map sheet when giving coarse locations.
Comment:
(1) On 250K sheets you can use the "100km square letters" or
the "100K map sheet numbers" to distinguish between identical
grid references on the sheet.
Example:
"100K map sheet number"
Usage:
This field can be set only by the Central Database Administrator.

414 : Map or sheet name
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: M

Definition:
The official name of the map or mapsheet used for giving the
respective grid reference for the cave or karst feature.
Usage:
(1) Normally auto-supplied when you use the lookup on the Map ID,
411[Grid ref - map ID] on this screen.
(2) This field needs to be actually filled in only when the map is
not already in the site's map table, or the information is not
otherwise automatically available via a lookup on the Map ID.

415 : Agent type
Entity: SY
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued:
                                          Codes
Definition:
The type of agent who has carried out some function, with respect to
whether they are a private individual, a voluntary organisation, a
government department, or the like. Expressed as a numeric code.
Comment: This is a "system" value which could apply to a range of
fields in a range of entities, e.g. a map producer, a land owner, a
cave discoverer, etc.

416 : Initials of current org
Entity: OR
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: S

Definition:
If the organisation is defunct but its records are being held by
another organisation, then this field shows the initials for the
organisation currently holding the material.
Comment: This field is needed only when the information is not
available by a link via the Organisation ID.

417 : Owner - organisation ID
Entity: CA
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: S

Definition:
The unique record ID of the owner of the cave or karst feature, if
it is an organisation as opposed to a person.
Usage:
(1) If it is a person rather than an organisation, use Field
228[Owner - person ID] instead.
(2) If no record IDs are available, enter the name of the person or
organisation in Field 418[Owner - name].

418 : Owner - name
Entity: CA
Data type: A       Max length:  60.       Coding: U       Single/Multi-valued: S

Definition:
The name of the person or organisation which owns the cave or karst
feature.
Usage: Normally this field would be included in the database only
when the name is not available via a link to the owner record ID, i.e.
to 228[Owner - person ID] or to 417[Owner - organisation ID].

419 : Discoverer - person ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: M

Definition:
The database internal record ID of a person in the Person database
associated with the respective discovery event for the cave or
karst feature.
Usage:
If the details of the person have not yet been entered into the
linked Person database on this site, then no ID will be available
for lookup, so enter the person's name in the nearby Name field
instead. Similarly if there is no Person database on this site.

420 : Discoverer - org ID
Entity: CA
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: M

Definition:
The database internal record ID of an organisation in the
Organisation database associated with the respective discovery
event for the cave or karst feature.
Usage:
If the details of the organisation have not yet been entered into
the linked Organisation database on this site, then no ID will be
available for lookup, so enter the Organisation initials in the
nearby Name field instead. Similarly if there is no linked
Organisation database on this site.

421 : Update ID
Entity: XU
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID for a batch of updates received
from an information provider by this database site.
Comment:
(1) The updates can be in any form, e.g. paper or computerised.
(2) One update batch can include more than one entity, e.g. caves
and maps.
(3) This field is normally not filled in by a user but by the system
on this database site.

422 : Update - person ID
Entity: XU
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The internal record ID from the Person database identifying the
person supplying a batch of updates to the database site.
Comment:
(1) This is not necessarily the same as the person originally
generating the information, or the person filling in a data form,
or the person who keyed the data into the database.
Usage:
Normally the value for this field would be entered via a lookup
table on the Person database.

423 : Update - organisation ID
Entity: XU
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: S

Definition:
The internal record ID from the Organisation database for the
organisation which supplied a batch of updates to this site, usually
the organisation of the person supplying the update batch.
Comment:
(1) It is this organisation which will be credited with supplying the
updates contained in this Update batch.
Usage:
(1) This field is auto-filled upon an entry in field 426[Update -
org code].

424 : Update - date
Entity: XU
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The date at which a batch of update information was supplied
to the database site, as opposed to when it was entered into the
database or when any of the information in individual fields
was valid. The date must be a valid date.
Comment:
(1) Individual field data dates may be given in fields 472-475.
(2) The key-in date is recorded in fields 429 and 449.
Usage:
(1) If the exact date is unknown, enter a best guess, including the
day, because this entry must be a complete valid date.

425 : Update - person
Entity: XU
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The full name of the person supplying a batch of update information
to the database site, as opposed to the person who generated the
original data or the person who keyed it into the database. The
format is Familyname comma space Givenname.
Example: Smith, John
Comment:
(1) This field would normally be included in a table only when the
person's name could not be shown via a link to their Person ID in
the Person database.
Usage:
(1) The value would normally be auto-filled at the same time as
performing a lookup for 422[Update - person ID] via the person
database.
(2) If there is no Person database, or the person's name is not
yet in the Person Database, enter the person's full name in this
field, observing the correct format, e.g. Smith, John. This format
helps with later identification and processing of this name when
adding it to a Person database.

426 : Update - org code
Entity: XU
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: S

Definition:
The standard 3-letter organisation code for an organisation supplying
a batch of update information to the database site.
Comment:
(1) This field is normally physically present in a table only when
it cannot be shown via a link to the Organisation ID. In this case,
it is then normally easier for the user to enter this Org Code
rather than the Org ID.

427 : Key-in ID
Entity: XK
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID identifying a data entry session,
a session being any period which is considered one logical unit,
and which could include entering several Update ID batches.
Usage:
(1) This field is not entered by a user but by the system.

428 : Key-in - person ID
Entity: XK
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The internal record ID from the Person database identifying the
person who performed a data-entry session.
Comment:
(1) This field would normally be present when a Person database was
available on the site, and would normally use it as a lookup.
(2) If key-in records are being kept at the site, then entering
this field is mandatory.

429 : Key-in - start date
Entity: XK
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The start date of a data entry session.
Usage:
This field is not entered by a user but by the system.

430 : Key-in - person
Entity: XK
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The full name of the person performing the data entry session. The
format is Familyname comma space Givenname.
Example: Smith, John
Comment:
(1) This field would normally be included in a table only when the
person's name could not be shown via a link to the Person ID in
the Person database.
Usage:
(1) The value would normally be auto-filled at the same time as
performing a lookup for 428[Key-in - person ID] via the Person
database.
(2) If there is no Person database, or the person's name is not yet
in the Person database, enter the person's full name in this field,
observing the correct format: Smith, John. This format
helps with later identification and processing of this name when
adding it to a Person database.

431 : Latest update ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID of the most recent update batch
applied to this cave.
Comment:
(1) This field is normally not completed by a user but is auto-
updated when Update Batch information is captured.
(2) Similar fields exist for other entities, such as maps.

432 : Latest update - person
Entity: CA
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The full name of the person who provided the most recent batch of
updates applied to the cave, as opposed to the person who did the
data entry or the person who provided the original information.
Comment:
This field would normally be included only when the information
could not be provided via the Update ID.

433 : Latest update - org code
Entity: CA
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: S

Definition:
The standard 3-letter organisation code for the org which provided
the most recent batch of updated information applied to this cave.
Comment:
This field would normally be used only when the organisation
information could not be shown via a link to the Update ID.

434 : Latest update - date
Entity: CA
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The supply date of the most recent batch of update information
applied to this cave, as opposed to the data entry date or to the
validity date of individual fields.
Comment:
This field is normally included only when the date can not be
shown via a link to the Update ID.

435 : Latest key-in ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID of the most recent data entry
session which included this cave.
Comment:
(1) This field is normally not completed by a user but is
auto-updated when Key-in Batch information is captured.

436 : Latest key-in - person
Entity: CA
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The full name of the person who performed the most recent data entry
session for this cave.
Comment:
This field would normally be included only when the information
could not be provided via the Key-in ID.

437 : Latest key-in start date
Entity: CA
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The start date of the most recent data entry session which included
this cave.
Comment:
This field would normally be included only when this information
could not be provided via the Key-in ID.

438 : Site current maximum ID
Entity: EN
Data type: N       Max length:   8.0      Coding: U       Single/Multi-valued: S

Definition:
The current maximum numeric value of any internal record ID for this
entity at this site.
Example: If the highest Cave ID at this site is AUASF00456 then the
value of the field is 456.
Comment: This field is used when creating new record IDs. If a
duplicate is detected, a utility program can restore this field to
its correct value.

439 : Land unit - coarse
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The smallest readily identifiable land unit in which the cave or
karst feature is located, and which does not compromise the location
of the cave if published.
Example: In the State of Victoria in Australia, the "Parish" is the
smallest common land unit, therefore this field would contain the
name of the Parish in which the cave was located.
Comment: The name of the land unit series used should be specified
in Field 440 in the Site Parameters.

440 : Coarse - land unit name
Entity: SY
Data type: A       Max length:  15.       Coding: U       Single/Multi-valued: S

Definition:
The name of the land unit series being used at this site to provide
a publishable land unit location for caves or karst features which
does not reveal their exact location.
Example:
The name is "Parish" in the State of Victoria in Australia.
Usage:
This field can be set only by the Regional Database Administrator.

441 : Fifth-smallest land unit
Entity: CA
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The official name for the 5th-smallest cadastral land unit type
in which the cave is located. See Field 255[Second-smallest land unit]
Comment: Multi-valued Field 293[Land unit name] should be used to
record the names of the different land unit types.

442 : Altitude
Entity: CA
Data type: N       Max length:  10.3      Coding: U       Single/Multi-valued: S

Definition:
The accurate altitude of the lowest point of this cave entrance
or karst feature where it leaves the profile of the surface.
Usage: The units can be stated in 443[Altitude - units], and the
Height Datum can be given in 516[Height Datum used].
Max text length: sign(1)+whole(5)+sep(1)+dec(3) = total 10, scale 3.

443 : Altitude - units
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The length units in which the exact altitude
has been given, expressed as a coded value.

444 : Altitude - precision +/-
Entity: CA
Data type: N       Max length:   8.3      Coding: U       Single/Multi-valued: S

Definition:
The +/- precision of the accurate altitude, 442[Altitude],
expressed in the same units as the altitude.
Example: An altitude stated as 1500m could be at a precision of 100,
10, or 1 metre. Its actual precision needs to be stated.
Comment: The precision is how closely (number of significant digits)
the altitude has been expressed, not necessarily how accurate (true)
the value is. The accuracy can be given in 445[Altitude -
accuracy +/-].
Max text length: sign(0)+whole(4)+sep(1)+dec(3) = total 8, scale 3.

445 : Altitude - accuracy +/-
Entity: CA
Data type: N       Max length:   8.3      Coding: U       Single/Multi-valued: S

Definition:
The +/- accuracy of the 'exact position' altitude stated in field
442[Altitude] and expressed in the same units as that altitude value.
Example: An altitude stated as 1500m could be accurate to 100, 10,
or 1 metre. The actual accuracy needs to be stated.
Comment: The accuracy is how close the given value is to the true
value, not how precisely (number of significant digits) it has been
expressed. The precision can be given in 444[Altitude - precision +/-]
Max text length: sign(0)+whole(4)+sep(1)+dec(3) = total 8, scale 3.

446 : Coarse - altitude units
Entity: SY
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The length units of the coarse altitude (Field 28), expressed as a
coded value.
Usage:
This field can be set only by the Central Database Administrator.

447 : Data awaits uploading
Entity: CA
Data type: L       Max length:   1.       Coding: U       Single/Multi-valued: S

Definition:
Flag to show whether further updates have been made since the last
upload to a more central level. True = upload needed.
Usage:
This field would normally be automatically updated by the system.

448 : Latest key-in end date
Entity: CA
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The finish date of the latest data entry session which included
this cave.
Comment:
This field would normally be included only when the information
could not be provided via the Key-in ID.

449 : Key-in - end date
Entity: XK
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The end date of a data entry session.
Comment:
(1) This field is not entered by a user but by the system, which keeps
the current session updated to the current date.

450 : Upload ID
Entity: XL
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID of a batch of data uploads to
a more centralised database site in the database hierarchy. The
Upload ID is issued by the organisation preparing the upload, and
the Org Code in the Upload ID is their Org Code.
Comment:
(1) This field is not entered by a user but by the system at the
sender's database site.

451 : Upload - person ID
Entity: XL
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The internal record ID from the Person database which identifies the
person who prepared the upload.
Comment:
(1) This field would normally be present when a Person database
was available at the site, and would be filled via a lookup on the
Person database.
(2) If Upload records are being kept at the site, then completing
this field or 454[Upload - person] is mandatory.

452 : Upload - organisation ID
Entity: XL
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: S

Definition:
The internal record ID from the Organisation database which
identifies the organisation which prepared and sent the upload.
Usage:
(1) This field is auto-filled upon an entry in field 455[Upload -
org code].

453 : Upload - date
Entity: XL
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The date at which the upload file was prepared for sending.
Usage:
This field is not entered by a user but by the uploader's system.

454 : Upload - person
Entity: XL
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The full name of the person who prepared the upload. The format
is Familyname comma space Givenname.
Example: Smith, John
Comment:
(1) This field would normally be included in a table only when the
person's name could not be shown via a link to the Person ID in
the Person database.
Usage:
(1) The value would normally be auto-filled at the same time as
performing a lookup for 451[Upload - person ID] via the Person
database.
(2) If there is no Person database at the site, or the person's
name is not yet in the Person database, enter the person's full
name in this field, observing the correct format: Smith, John.
This format helps with later identification and processing of this
name when adding it to a Person database.

455 : Upload - org code
Entity: XL
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: S

Definition:
The standard 3-letter organisation code for the organisation
which prepared and sent this upload.
Comment:
(1) This field is normally physically present in a table only when
it cannot be shown via a link to the Organisation ID, or when there
is no Organisation database available at the site. In both cases it
is normally easier to enter the Org Code.

456 : Latest upload ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID of the most recent upload to a
more central system which included this cave.
Comment:
This field is normally not completed by a user but is
auto-updated when Upload information is captured.

457 : Latest upload - person
Entity: CA
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The full name of the person who prepared the most recent upload
which included this cave.
Comment:
This field would normally be included only when the information
was not available via the Upload ID.

458 : Latest upload - org code
Entity: CA
Data type: A       Max length:   3.       Coding: L       Single/Multi-valued: S

Definition:
The standard 3-letter Organisation Code of the organisation which
prepared the most recent upload which included this cave.
Comment:
This field would normally be included only when the information
was not available via the Upload ID.

459 : Latest upload - date
Entity: CA
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The date on which the most recent upload which included this cave
was prepared.
Comment:
This field would normally be included only when the information
was not available via the Upload ID.

460 : Field ID updated
Entity: CA
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: M

Definition:
The Field ID of an updated field which has been included in a data
upload to a more central system.
Comment:
(1) This field is not entered by a user, but is auto-filled by the
system.
(2) It is used for attributing updates per stakeholder organisation.

461 : Values qty before upload
Entity: CA
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: M

Definition:
The quantity of values present in a given field for a cave prior to
a data upload containing updates by a specific organisation for the
field.
Comment:
(1) This field is not filled in by a user but by the system.
(2) It is used when attributing updates to stakeholder organisations.

462 : Values qty after upload
Entity: CA
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: M

Definition:
The quantity of values present in a given field for a cave after a
data upload containing updates by a specific organisation for the
field.
Comment:
(1) This field is not filled in by a user but by the system.
(2) It is used when attributing updates to stakeholder organisations.

463 : Qty of new/changed values
Entity: CA
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: M

Definition:
The quantity of values in a field which are new or changed after
a data upload. It is separately recorded for a given cave, upload,
and updating organisation.
Example:
(1) 1 for an updated or newly completed single-valued field.
(2) 3 if 3 values among those in a multi-valued field are new since
the upload.
Comment:
(1) This field is not filled in by a user but by the system.
(2) It is used when attributing updates to stakeholder organisations.

464 : Value ID
Entity: CA
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: S

Definition:
The internal ID for an instance of a field value. Its format is
an integer taken from a separate series per site + entity instance +
field.
Example:
A multi-valued field for a given cave at a given database site
would have its own Value ID series.
Comment:
(1) This ID is used for identifying a particular field value,
for example when describing its data quality.
(2) It is required only for multi-valued fields or MV field groups
because values of single-valued fields can be identified by their
421[Update ID].
Usage:
This field is not entered by the user but is auto-filled by the
system.

465 : Data source type
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The type of source from which the data value was obtained, with regard
to how close to or removed from the original data the supplier was,
expressed as a coded value. The supplier is the person identified
in 470[Data supplier - person ID] or the organisation identified
in 471[Data supplier - org ID].
Example: It might have been first hand information for that person,
or it might have been read in a publication.

466 : Data confidence level
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The likelihood that the data value is correct, expressed as a coded
value.

467 : Data security level
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The degree to which this data value can be released or published,
expressed as a coded value.

468 : Data - reference ID
Entity: CA
Data type: A       Max length:  11.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID from the References database which
identifies the principal reference upon which the data value was
based, if any.

469 : Type of update
Entity: CA
Data type: A       Max length:   1.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
Whether this is a new or an updated value, expressed as a coded value.

470 : Data supplier - person ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID from the Person database which
identifies the person who is the closest known to the original data
upon which this value is based.
Comment:
Field 465[Data source type] shows the relationship of this person
to the original data.

471 : Data supplier - org ID
Entity: CA
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: S

Definition:
The database internal record ID from the Organisation database
which identifies the organisation of the person who supplied
the original source information on which this field value is based.

472 : Data date - year
Entity: CA
Data type: A       Max length:   4.       Coding: U       Single/Multi-valued: S

Definition:
The year component of the date the information was supplied by the
earliest known original information source identified in 470[Data
supplier - person ID]. The format is always to be 4 digits.

473 : Data date - month
Entity: CA
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: S

Definition:
The month component of the date the information was supplied by
the earliest known original information source. Format is in the
range 1-12.
Usage:
Leave blank if unknown.

474 : Data date - day
Entity: CA
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: S

Definition:
The day component of the date the information was supplied by
the earliest known original information source. Format is in the
range 1-31.
Usage:
Leave blank if unknown.

475 : Data date - qualifier
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The reliability of the date given as the data date for the data
upon which this field value is based. Expressed as a code value.

476 : Data date
Entity: CA
Data type: D       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The date the information was supplied by the earliest known
original information source identified in 470[Data supplier -
person ID]. This field is of "date" type.
Comment:
(1) This field is available for use where the separate
date components of year, month, day are not wanted.
(2) Its use does imply that a full valid date is always available
for entry.

477 : Discoverer date qualifier
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The reliability of the date of the respective discovery event.

478 : Person ID
Entity: PE
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The unique internal database key for a Person record. Same principles
as for 227[Cave ID].
Usage:
(1) To prevent a different ID for the same Person being generated
by several sites, the ID needs to be generated by a single master
Person database site. So if you need to refer to a Person record
which is not in your read-only Person database, email the Person's
details to the Person database administrator, who will send back
a new record for importing into your Person database and updating
your Person lookup tables. It will be sent to all other sites at
the same time.

479 : Surname
Entity: PE
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The surname or family name of a person.

480 : Usual first name
Entity: PE
Data type: A       Max length:  20.       Coding: U       Single/Multi-valued: S

Definition:
The firstname by which a person is usually addressed.

481 : Middle initial
Entity: PE
Data type: A       Max length:   5.       Coding: U       Single/Multi-valued: S

Definition:
The middle initial(s) of a person's name.

482 : Initials for given names
Entity: PE
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The full initials normally given before a person's surname,
including that for their firstname.

483 : Title
Entity: PE
Data type: A       Max length:  20.       Coding: U       Single/Multi-valued: S

Definition:
The title to be used with a person in their address.
Examples: Ms, Mr., Dr., Univ.Prof.Dr., etc.

484 : Address line 1
Entity: PE
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The first line of a person's address, between but excluding their
name and their city/suburb.
For example, address lines could include house name, building/floor
details, and street details.

485 : Address line 2
Entity: PE
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The second line of a person's address, if necessary, between but
excluding their name and their city/suburb.

486 : Address line 3
Entity: PE
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The third line of a person's address, if necessary, between but
excluding their name and their city/suburb.

487 : Address line 4
Entity: PE
Data type: A       Max length:  50.       Coding: U       Single/Multi-valued: S

Definition:
The fourth line of a person's address, if necessary, between but
excluding their name and their city/suburb.

488 : City or suburb
Entity: PE
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The local city or suburb of a person's address.

489 : State abbreviation
Entity: PE
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: S

Definition:
The abbreviation for the state component, if any, of a person's
address.

490 : State code
Entity: PE
Data type: A       Max length:   2.       Coding: L       Single/Multi-valued: S

Definition:
The normal code for the state which will be used for the state
component, if any, of a person's address.

491 : Postcode
Entity: PE
Data type: A       Max length:  12.       Coding: U       Single/Multi-valued: S

Definition:
The postcode or zip for a person's address.

492 : Country name
Entity: PE
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The name of the country used in a person's address.

493 : Country code
Entity: PE
Data type: A       Max length:   2.       Coding: U       Single/Multi-valued: S

Definition:
The ISO 2-letter code for the country used in the country component
of a person's address.

494 : Email address
Entity: PE
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The Internet email address of a person.

495 : Phone numbers prefix
Entity: PE
Data type: A       Max length:  15.       Coding: U       Single/Multi-valued: S

Definition:
The prefix to be used with the local phone number(s) of a person to
enable dialling them from outside their own country. It should
include both country dialling code and area dialling code.
Example: For local number 1234-5678 the prefix might be +61(3)/(03)
to show international and national prefixes.

496 : Home phone number
Entity: PE
Data type: A       Max length:  18.       Coding: U       Single/Multi-valued: S

Definition:
The home phone number for a person, without any area or country
codes. It may however include extension number details.

497 : Work phone number
Entity: PE
Data type: A       Max length:  18.       Coding: U       Single/Multi-valued: S

Definition:
The work phone number of a person, but without any area or country
codes. It may however include extension number details.

498 : Mobile phone number
Entity: PE
Data type: A       Max length:  18.       Coding: U       Single/Multi-valued: S

Definition:
The mobile phone number for a person, excluding any country code.

499 : Fax phone number
Entity: PE
Data type: A       Max length:  18.       Coding: U       Single/Multi-valued: S

Definition:
The Fax phone number for a person, but without any area or country
codes. It may however include extension number details.

500 : Pager phone number
Entity: PE
Data type: A       Max length:  20.       Coding: U       Single/Multi-valued: S

Definition:
The pager phone number and user number for a person, but without
any area or country codes which are unnecessary for a local call.

501 : Organisation code 1
Entity: PE
Data type: A       Max length:   3.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
The primary relevant organisation, if any, to which a person belongs,
expressed as its standard 3-letter UIS code.

502 : Organisation code 2
Entity: PE
Data type: A       Max length:   3.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
A second organisation, if any, to which a person belongs, expressed
as a standard 3-letter UIS code.

503 : Organisation code 3
Entity: PE
Data type: A       Max length:   3.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
A third organisation, if any, to which a person belongs, expressed
as a standard 3-letter UIS code.

504 : Field design comment line
Entity: AT
Data type: A       Max length:  70.       Coding: U       Single/Multi-valued: M

Definition:
A line of comment about the design of a field.

505 : State abbreviation
Entity: OR
Data type: A       Max length:   8.       Coding: U       Single/Multi-valued: S

Definition:
The abbreviation of the State component, if any, in an organisation's
address.

506 : Country name
Entity: OR
Data type: A       Max length:  25.       Coding: U       Single/Multi-valued: S

Definition:
The name of the country in an organisation's address.

507 : Data confidence level
Entity: SY
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
A generic coded field for common use by data-confidence-level fields
when translating their coded value.
Usage: When various data-confidence-level fields need their code
value translated, this field should be used rather than having a
separate series of values for each data-confidence-level field.
A one-character symbol
508[Data confidence symbol] is also available as a translation.

508 : Data confidence symbol
Entity: SY
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
A generic coded field for a one-character symbol for use by data-
confidence-level fields.

509 : Genus confidence level
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The confidence level that the genus of this specimen found in the
cave has been correctly identified. Expressed as a coded value.

510 : Species confidence level
Entity: CA
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: M
                                          Codes
Definition:
The confidence level that the species name for this specimen
found in the cave has been correctly identified. Expressed as a
coded value.

511 : Vertical range
Entity: CA
Data type: N       Max length:    .2      Coding: U       Single/Multi-valued: S

Definition:
Not yet ready.

512 : Entity update status
Entity: SY
Data type: A       Max length:   2.       Coding: I       Single/Multi-valued: S
                                          Codes
Definition:
A generic coded field for use by entity update-status fields when
translating their coded value. The status refers to how up-to-date
the data is rather than how much data is stored.

513 : Field ID used for codes
Entity: AT
Data type: I       Max length:   5.0      Coding: U       Single/Multi-valued: S

Definition:
The field ID of the field which is used to supply the generic code
values which are shared by this field.
Example:
All length-unit fields share a common set of length-unit codes for
metres, feet, yards, etc.

514 : Position - geog precision
Entity: CA
Data type: N       Max length:   8.5      Coding: U       Single/Multi-valued: S

Definition:
The +/- precision of the stated full latitude and longitude values
given in the "exact position" fields, 245[Position - latitude] and
246[Position - longitude], expressed as degrees.decimal degrees.
Example: A latitude expressed as closely as +/- 1 second would
have a degress.decimal degrees precision of 0.00028.
Comment: The precision is how closely (number of significant digits)
the lat/long has been expressed, not necessarily how accurate (true)
the value is. Accuracy can be expressed via field 515[Position -
geog accuracy].
Max text length: sign(0)+whole(2)+sep(1)+dec(5) = total 8, scale 5.

515 : Position - geog accuracy
Entity: CA
Data type: N       Max length:   8.5      Coding: U       Single/Multi-valued: S

Definition:
The +/- accuracy of the stated full latitude and longitude values
given in the "exact position" fields 245[Position - latitude] and
246[Position - longitude], expressed as degrees.decimal degrees.
Example: A latitude whose value was accurate to +/- 1 second would
have a degrees.decimal degrees accuracy of 0.00028.
Comment: The accuracy is how close the given value is to the true
value, not how precisely (number of significant digits) it has been
expressed. The precision can be given in field 514[Position - geog
precision].
Max text length: sign(0)+whole(2)+sep(1)+dec(5) = total 8, scale 5.

516 : Height Datum used
Entity: SY
Data type: A       Max length:  30.       Coding: U       Single/Multi-valued: S

Definition:
The official name of the Height Datum which has been used as a basis
for altitude values.
Example:
"Australian Height Datum" in Australia.
Usage:
(1) Depending on the table structure being used at your database
site, this field might appear once for all altitude data, or once for
each altitude entry.
(2) This field can be set only by the Regional Database Administrator.

517 : Map numberer org code
Entity: PL
Data type: A       Max length:   3.       Coding: U       Single/Multi-valued: S

Definition:
The standard 3-letter organisation code for the organisation which
issued the number for this cave/karst-related map.
Comment: This may differ from the source org code in the case,
for example, of a caving org which numbers a cave map produced by
a government agency.

518 : Map numberer org code
Entity: CA
Data type: A       Max length:   3.       Coding: U       Single/Multi-valued: M

Definition:
The standard 3-letter organisation code of the numberer of this map
which has been referenced for this cave or karst feature.
Comment: This may differ from the organisation which produced the
map, e.g. a caving club numbering a cave map produced by a govt agency
Usage:
(1) This field may need to be entered only when it is not
automatically available via a lookup or link on 265[Map ID], or
if the map is not yet in available in the site's map database.

519 : Updating organisation ID
Entity: CA
Data type: A       Max length:   9.       Coding: U       Single/Multi-valued: M

Definition:
The internal record ID from the Organisation database which
identifies the organisation which has supplied the updates for
a specific cave and field in a specific data upload to a more
central system.
Comment:
(1) This field is not entered by a user but is auto-filled by the
system.
(2) It is used when attributing updates to stakeholder organisations.

520 : Data - key-in ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The Key-in ID used for a particular field value.
Usage:
Auto-filled by the system.

521 : Data - upload ID
Entity: CA
Data type: A       Max length:  10.       Coding: U       Single/Multi-valued: S

Definition:
The Upload ID used for a particular field value.
Usage:
Auto-filled by the system.

Notes:

Entities:  AR = Article in a publication.
           AT = Field or attribute.
           AV = Field value.
           CA = Cave or karst feature.
           EN = Entity.
           JN = Journal.
           OR = Organisation.
           PE = Person.
           PH = Photograph.
           PL = Plan or map.
           PM = Marker (Permanent mark)
           PS = Map series.
           RE = Region or area.
           RP = Report.
           SM = Specimen.
           SP = Species.
           ST = Site.
           SU = Subject.
           SV = Survey.
           SY = System field.
           XK = A key-in batch.
           XL = An upload batch.
           XU = An update batch.


Data type: A = Alphanumeric.
           N = Numeric. A "real" number allowing decimal places and
               many significant digits, typically around 15.
           D = Date.
           L = Logical. True or False.
           I = Integer. Whole number in the range -32,767 to +32,768.

Maximum length:
When a Numeric data type is expressed as text characters, its maximum
length must allow for the maximum value and the finest precision, and if
necessary, a leading sign. This maximum must also be considered on an
international basis. For example, a field value which has maximum text
characters of "-9999.999" consists of sign(1) + whole number digits(4) +
decimal separator(1) + decimal digits(3), giving a total text length of
9, with a "scale" of 3. This would be expressed as a "Max. length" of 9.3

Codes for field coding:
           I = International coding   U = Uncoded   L = Locally coded

Codes for single or multi-valued:
           S = Single-valued   M = Multi-valued

Updates

5-Sep-1998
Updated:
21, 156-158, 178, 182, 288-296, 336-337, 380, 412-413, 440, 446, 464-476, 478, 513, 516.
Added: 520-521.

7-Aug-1998
Updated: 30-40, 55, 71, 76, 201, 257, 259-270, 305, 355-364, 419-437, 447-463, 509-510.
Added: 517-519.

20-May-1998
All fields are now included on this page even if their definition is not yet ready.
Updated: 238-256, 300-302, 365-414, 441-445.
Added: 514-516.


This page copyright © 1998 Peter Matthews. It may be reproduced for non-commercial use provided this copyright paragraph is retained. This ongoing development of field definitions etc is being conducted by the Informatics Commission (UISIC) of the International Union of Speleology (UIS). The Australian Speleological Federation's ( ASF) national Karst Index Database is being used as a pilot.
This page: http://rubens.its.unimelb.edu.au/~pgm/uisic/exchange/atendefn.html
P. Matthews | Email: matthews@melbpc.org.au