This group of fields covers all the descriptive and coded spatial data
that describes the geographic position that a plant was collected from, including
supporting data such as altitude, depth (particularly for aquatic plants), and degree of
precision in citing the locality details.
Where relevant, all of the standard HISPID3 fields in this group, the
HABITAT GROUP, and the COLLECTION GROUP refer to the original wild source collection
information. That is, the information recorded in all of these fields (eg. Collection
Date, Primary Collector's Name, Country of Origin, Habitat, Locality,
Collection Notes, Primary Subdivision of Country of Origin, Secondary
Subdivision of Country of Origin, Specific Geographic Unit) refers to the
original wild source collection.
If the current accession was taken from a secondary source (eg.
cultivated material, of known or unknown wild source), then the relevant field identifiers
would all be prefaced by the word 'Subsequent' and the relevant Transfer Codes would be
prefaced by a lowercase 's'. For example, if an herbarium collection was taken from a
cultivated collection growing in an Australian botanic garden which had been originally
grown from seeds collected in the 'wild' from South Africa, then the Country field
value would be 'South Africa' (with Transfer code: cou), whereas the Subsequent Country
field (Transfer code: scou) would be 'Australia'. Likewise, the field which
contains the information about the collector's name of the current accession which was
taken from cultivated material would be known as Subsequent Collector's Name and the
Transfer code would be scnam. The same 'Domain/Range/Values' apply as for the
relevant 'primary' data fields.
Note: these 'subsequent fields have not be further described in
HISPID3, but they should be applied when required.
The geocode information of the 'Place of Origin' data are held in a
hierarchy of 4 levels. These are:
| 1. | a. | Political country (written in full), strictly following the ISO system; |
| b. | Political country (codified), according to the ISO system; | |
| 2. | Basic Recording Unit of the World Geographical Scheme; | |
| 3. | A defined subdivision of the ISO unit; | |
| a. | Primary subdivision of Country of Origin; | |
| b. | Secondary subdivison of Country of Origin; | |
| 4. | The locality; | |
| a. | Locality in text format; | |
| b. | Special Geographical Unit. | |
The information relates to the place where the plant was collected, not
to the full distributional range of the taxon.
The spatial data interchange standard followed by HISPID3 is based on
the Spatial Data Transfer Standard (SDTS). The use of this standard for data
transfer is expected to become common place. It has been accepted as a USA Federal
Information Processing Standard (FIPS) and as an Australian standard by Standards
Australia Committee IT/4. The Australia, New Zealand Land Information Council (ANZLIC)
has supported this choice by sponsorship of AUSDEC (Australian Spatial Data Exchange
Centre) whose purpose is to faciliate the introduction and adoption of SDTS in
Australia. AUSLIG (Australian Surveying and Land Information Group) have defined a profile
subset of SDTS which is applicable to their own data type. Full text of the Australian
SDTS standard is available from AUSDEC or from Standards Australia.
The interchange of the horizontal components of spatial data (eg.
Latitudes/Longitudes, Grids) in HISPID3 must follow:
Note: MGA94 and WGS84 (World Geodetic System 1984 - as modified
in 1994)(the reference frame used by GPS) are in agreement to within approximately 1
metre. For specific details of requirements for map grid references in HISPID3 refer Spatial
Grid fields (below).
The interchange of the vertical components of spatial data (eg.
Altitude, Depth) in HISPID3 must follow:
TDWG Short name: ISOCOUNTRY (?), BOTCOUNTRY, CONTINENT(?), REGION,
ISOREGION, BASICRECU
Description: The name of the country or major region where the
plant specimen was collected, entered in full.
Relevant standards: ABIS, ITF, TLR, WGSUB, ISO, Hollis &
Brummitt (1992)
Domain/Range/Values: Alpha; accepted standard full political
country name, uppercase.
Comments: If the name of the country where the plant was
collected is unknown, then this field should contain the value 'UNKNOWN' (in uppercase).
In this case, the following ISO Code for Country of Origin field must have the
entry 'XX' or 'XY'. All remaining 'location group' fields should be left unfilled.
It is recommended that the spelling of the country should be as
recognised by the International Standards Organization (ISO).
It is recommended that new country names be enclosed in square brackets,
after the old country name, where country names or boundaries have changed. The 2 letter
ISO codes in ISO Code for Country of Origin field (refer below) assist the updating
of countries where boundaries are changing.
Separate fields for state/province and country are needed to adequately
handle the situation with international collections.
Description: The 2 letter code for the representation of the name
of the country where the plant was collected, using the codes assigned by the
International Standards Organization (ISO).
Domain/Range/Values: The code must consist of 2 uppercase letters
(AZ).
Comments:
1. This field can only contain a valid entry as defined by the International Standards Organization (ISO Standard 3166).
2. Two other entries are permitted in addition to those defined by ISO:
| Values in Field | Meaning |
| XX | Country unknown |
| XY | Country not applicable |
Notes: The 'XX' code should be used when no 'Country of Origin'
information is provided. The 'XY' code should be used for non-specific collection
localities, eg. Africa, South East Asia.
Description: World Geographical Scheme for Recording Plant
Distributions by S. Hollis and R.K. Brummitt. - Plant Taxonomic Database Standards No. 2,
Version 1.0 (1992).
Domain/Range/Values: The contents of this field must be a valid entry from the above publication.
Comments:
1. This code contains up to 5 characters when taken to the complete Level 4 Geographical Scheme.
2. Every code is unique, so that the Level 1, 2 and 3 codes must also be
recognised if the complete Level 4 code is not provided.
Description: The primary recording unit which is the highest
order subdivision recognised by the Country of Origin.
Relevant standards: ITF; Hollis & Brummitt (1992) Complete
4-level Geographical scheme (refer Table 4 in Hollis & Brummitt, 1992).
Domain/Range/Values: Alpha; in full or standard abbreviation
accepted by or agreeing with the Hollis & Brummitt (1992) standard full Complete
4-level Geographical area.
Comments:
1. The entry in the field should preferably be a valid entry as defined by Table 4 (Hollis & Brummitt 1992).
2. If the entry is not part of the Hollis & Brummitt (1992) standard, then it must be equivalent to the entries in this latter standard. For example, this field is expected to contain State, Province, and other comparable geographical regions.
3. The abbreviations used for this field may be based on the official
(frequently political) abbreviations used within the Country of Origin, rather than
those of Hollis & Brummitt (1992) or the primary recording unit may be transferred in
full.
Description: The secondary recording unit which is the second highest-order subdivision of Country of Origin field.
TDWG Short name: BASICRECU (?), LOCALPOLU
Relevant standards: ABIS, ITF, TLR, WGSUB
Domain/Range/Values: Alpha; written in full or any valid regional
code or abbreviation (and then in uppercase) as used by the relevant country or region
Comments: This field contains the district or region from which
the specimen was collected, usually a subdivision of State or Province.
Description: The special geographic recording unit describes
specific conservation areas and other nature reserves of Country of Origin
field.
Relevant Standards: ABIS, ITF
Domain/Range/Values: Alphanumeric; written in full.
Comments: The field consists of the name of a defined
conservation area, such as national or state parks, forest reserves, nature reserves,
conservation or heritage parks.
TDWG Short name: LOCALITY, STANLOC (?)
Description: The locality where the plant was collected within
the country and subdivisions assigned in the previous three fields.
Relevant standards: ABIS, ITF
Domain/Range/Values: Alphanumeric; free text, plain
language description of the locality, as on the specimen label.
Comments: Where the locality covers more than one country, eg.
'Himalayas', and the Country Of Origin is unknown, an entry in the Locality
field may be used in conjunction with the value 'XX' (in ISO code for Country of Origin
field) and UNKNOWN (in the Country of Origin field).
TDWG Short name: ELEVATIONL
Description: The altitude of the collection locality or if the
collection has been made over an altitudinal range, then the minimum altitude of
the collection locality (cf. Maximum Altitude field), in metres above or below sea
level (cf. Depth field).
Relevant standards: SDTS, ITRF, AHD71, ABIS, ITF
Domain/Range/Values: Real; any geographically reasonable
altitude in metres.
Comments: Altitudes in feet must be converted to metres before
data are interchanged.
Negative values indicate terrestrial altitudes below sea level
(depressions), not aquatic environments or caves (refer Depth field below). A
negative altitude must be preceded by a minus sign, without a space. The plus sign for
positive altitudes should be omitted.
If the Altitude is unknown, then this field should not be filled.
TDWG Short name: ELEVLACCUR
Description: The estimated accuracy of the altitude or, when a
range of altitudes given, then the estimated accuracy of the minimum altitude, in metres.
Relevant standards: SDTS, ITRF, ITF
Domain/Range/Values: Real; in metres. If degree of
accuracy is unknown, then this field should not be filled.
Comments: Refer to Comments: of the Altitude field.
The two fields Accuracy of Altitude and Accuracy of Maximum
Altitude (refer below) are given to record the accuracy of the altitude geocodes when
a collection is made over an altitudinal range. The Accuracy of Altitude field
refers to the accuracy of the value recorded for the lower Altitude field, and Accuracy
of Maximum Altitude applies to the value in Maximum Altitude field. If the
collection altitude only refers to one value, then only Altitude field and the Accuracy
of Altitude should be filled.
Examples: If a collection was made from several plants growing on
a mountain side, then Altitude field refers to the lowest altitude, and Maximum
Altitude field to the highest altitude. The collector may have a very accurate
altitude reading for the lowest position, but only a coarse approximation for the upper
range. Therefore the accuracy value in the Accuracy of Altitude field would be
different from that recorded in the Accuracy of Maximum Altitude field. By filling
out the two Altitude fields, the data receiver knows that the specimens were collected
over a spectrum of plant material.
| Altitude | 100 | Material collected from several plants with an accurate |
| Accuracy of Altitude | 5 | lower altitudinal reading, but with the upper altitudinal |
| Maximum Altitude | 250 | limit anywhere between 225 and 275 metres. |
| Accuracy of Maximum Altitude | 25 |
Another example is when the collection was from only one plant source,
for which there is an inaccurate altitude reading.
| Altitude | 1000 | This plant was collected at an altitude anywhere |
| Accuracy of Altitude | 100 | between 900 and 1100 metres. |
Note: if the Accuracy of Altitude field is omitted, then
it should be assumed that the level of accuracy is not known.
TDWG Short name: ELEVATIONH
Description: The maximum altitude when the collection is cited as
having been collected over an altitudinal range, in metres above or below sea level (cf. Depth
field).
Relevant standards: SDTS, ITRF, AHD71, ABIS, ITF
Domain/Range/Values: Real; any geographically reasonable
altitude in metres.
Comments: Altitudes in feet should be converted to metres before
data are interchange. Negative values indicate terrestrial altitudes below sea level
(depressions), not aquatic environments or caves (refer Depth field below). A
negative altitude must be preceded by a minus sign, without a space. The plus sign for
positive altitudes should be omitted.
TDWG Short name: ELEVHACCUR
Description: The estimated accuracy of the maximum
altitude when the collection is cited as being taken from within an altitudinal range, in
metres.
Relevant standards: SDTS, ITRF, ITF
Domain/Range/Values: Real; in metres. If degree of
accuracy is unknown, then this field should not be filled.
Comments: Refer to Comments of the Altitude field
and Accuracy of Altitude field (above).
Note: If the Accuracy of Altitude and/or the Accuracy
of Maximum Altitude fields are omitted, then it should be assumed that the level of
accuracy is not known.
Description: Flag indicating the source of the altitude and
precision calculations.
Domain/Range/Values: Alpha; any valid entry as listed in the
following table:
Values in Field
collector
compiler
automatically generated.
Comments: The altitudes and altitude precisions provided by the
plant collector are usually from GPS readings, maps on-site, extracted from the field book
or from the herbarium label. Those provided by compilers other than the collector, are
based on the locality stated in the field book or on the herbarium label. Automatically
generated altitudes and altitude precisions are produced by various computer programs (eg.
GIS, DEM).
Description: This field indicates how the altitude was derived.
Domain/Range/Values: Alpha; any valid entry as listed in the
following table:
Values in Field Meaning
| Altimeter | |
| DEM | Digital Elevation Model |
| GPS | Global Positioning System |
| Field Estimate | |
| Map | |
| Unknown |
Comments: Although this field may be coded in institutional
databases, the full word or phrase should be used when interchanging data.
Description: The depth of the collection locality beneath the
water surface or below the ground surface, in metres.
Relevant standards: SDTS, ITRF, AHD, ABIS, ITF
Domain/Range/Values: Real, any geographically reasonable depth,
in metres.
Comments: Depth in feet and fathoms must be converted to metres
before transfer.
Depth below ground surface would be used to indicate the depth of a
collection made from within a terrestrial cave.
As with the altitude fields (namely Altitude and Maximum
Altitude fields), a duplicate field may be necessary to indicate a range of depths, or
the accuracy of measurement; refer Maximum Depth and Accuracy of Maximum Depth
(below).
Description: The accuracy of the depth estimation, or when a
range of depths are given, then the accuracy of the minimum depth estimation, in metres.
Relevant standards: SDTS, ITRF
Domain/Range/Values: Real; in metres. If degree of
accuracy is unknown, then this field should not be filled.
Comments: If the Accuracy of Depth field is omitted, then
it should be assumed that the level of accuracy is not known.
Description: The maximum depth when the collection is cited as
being taken from a range of depths, in metres beneath the water surface or below the
ground surface.
Relevant standards: SDTS, ITRF, AHD, ABIS, ITF
Domain/Range/Values: Real; any geographically reasonable
depth in metres.
Comments: Depth in feet and fathoms should be converted to metres
before transfer.
Description: The accuracy of the maximum depth estimation when
the collection is cited as being taken from a range of depths, in metres.
Relevant standards: SDTS, ITRF
Domain/Range/Values: Real; in metres. If degree of
accuracy is unknown, then this field should not be filled.
Comments: If the Accuracy of Depth and/or the Accuracy
of Maximum Depth fields are omitted, then it should be assumed that the level of
accuracy is not known
TDWG Short name: LATDEGH, LATDEGH
Description: The degrees of latitude of the collection locality,
as quoted from the herbarium label or derived.
Relevant standards: ABIS, ITF, AUSLIG Master Name File,
Gazetteers
Domain/Range/Values: Integer; within the range 0 90, any valid
and biogeographically meaningful latitude in degrees.
Comments:
1. If the latitude is not known, then this and the following latitude fields must be left unfilled.
3. If this field is filled, then the last latitude field (Latitude, Direction) must consist of one of the letters 'N' or 'S' (for North or South).
4. The geocode information should be interchanged as latitude and longitude in degrees, minutes, seconds and direction. Decimal degrees must be converted to degrees, minutes and seconds before the data are interchanged.
5. Grid references should be converted to degrees, minutes,
seconds and direction before data are interchanged.
Notes: The ABIS standard indicates a single 7character field,
the first two of which are degrees, the second two minutes, the third two seconds and last
one direction. This standard is not followed in HISPID3.
To indicate a range of latitudes and longitudes, a duplicate set of
latitude and longitude fields will be required.
When this field is selected, then the Longitude fields must be
used, not the Spatial Grid fields.
TDWG Short name: LATMINH, LATMINL
Description: The minutes of latitude of the collection locality,
as quoted from the label or derived.
Relevant standards: ABIS, ITF
Domain/Range/Values: Integer; 0 59, any valid and
biogeographically meaningful latitude in minutes.
Comments: See Comment under Latitude, Degrees.
| 1. | If the latitude degrees (Latitude, Degrees field) is not known, then this and the following latitude fields must be left unfilled. |
| 2. | If the latitude minutes (Latitude, Minutes field) is not known, then this and latitude seconds (Latitude, Seconds Field) must be left unfilled. |
TDWG Short name: LATSECH, LATSECL
Description: The seconds of latitude of the collection locality,
as quoted from the label or derived.
Relevant standards: ABIS, ITF
Domain/Range/Values: Integer; 0 59, any valid and biogeographically
meaningful latitude in seconds.
Comments: See Comment under Latitude, Degrees.
If the value for this field is unknown, then this field must be
left unfilled.
TDWG Short name: LATDIRHIGH, LATDIRLOW
Description: The abbreviated direction of latitude of the
collection locality, relative to the equator, as quoted from the label or derived.
Relevant standards: ABIS, ITF
Domain/Range/Values: Alpha; N or S.
Comments: See Comment under Latitude, Degrees.
If Latitude, Degrees field is filled, then this field must
consist of one of the letters 'N' or 'S' (for North or South).
TDWG Short name: LONGDEGH, LONGDEGL
Description: The degrees of longitude of the collection locality,
as quoted from the label or derived.
Relevant standards: ABIS, ITF, AUSLIG Master Name File,
Gazetteers
Domain/Range/Values: Integer; 0 180, any valid and
biogeographically meaningful longitude in degrees.
Comments:
1. Exact location information for rare and/or endangered plants can be omitted from the transfer record by not transferring the seconds from the Latitude, Seconds and Longitude, Seconds fields for latitude and longitude, respectively or, for more conservationally sensitive plants, the data in the Latitude, Minutes and Longitude, Minutes fields need not be transferred.
2. If the longitude is not known, then this and the following longitude fields must be left unfilled.
3. If this field is filled, then the last longitude field (Longitude, Direction) must consist of one of the letters 'E' or 'W' (for East or West).
4. The geocode information should be interchanged as latitude and longitude in degrees, minutes, seconds and direction. Decimal degrees must be converted to degrees, minutes and seconds before the data are transferred.
5. Grid references should be converted to degrees, minutes,
seconds and direction before data are transferred.
To indicate a range of latitudes and longitudes, a duplicate set of
latitude and longitude fields will be required.
Notes: The ABIS standard indicates a single 8character field,
the first three of which are degrees, the second two minutes, the third two seconds and
last one direction. This standard is not followed in HISPID3.
When this field is selected, then the Latitude fields must be
used, not the Spatial Grid fields.
TDWG Short name: LONGMINH, LONGMINL
Description: The minutes of longitude of the collection locality,
as quoted from the label or derived.
Relevant standards: ABIS, ITF
Domain/Range/Values: Integer; 0 59, any valid and
biogeographically meaningful longitude in minutes.
Comments: See Comment under Longitude, degrees.
1. If the longitude degrees (Longitude, Degrees field) is not known, then this and the following longitude fields must be left unfilled.
2. If the longitude minutes (Longitude, Minutes field) is not
known, then this and longitude seconds (Longitude, Seconds field) must be
left unfilled.
TDWG Short name: LONGSECH, LONGSECH
Description: The seconds of longitude of the collection, as
quoted from the label or derived.
Relevant standards: ABIS, ITF
Domain/Range/Values: Integer; 0 59, any valid and
biogeographically meaningful longitude in seconds.
Comments: See Comment under Longitude, Degrees.
If the value for this field is unknown, then this field must be
left unfilled.
TDWG Short name: LONGDIRHIGH, LONGDIRLOW
Description: The abbreviated direction of longitude of the
collection locality, relative to Greenwich, as quoted from the label or derived.
Relevant standards: ABIS, ITF
Domain/Range/Values: Alpha; E or W.
Comments: See Comment under Longitude, Degrees.
If the Longitude, Degrees field is filled, then this field must
consist of one of the letters 'E' or 'W' (for East or West, respectively).
Description: The projection type of the Map Grid system which is
used to determine the position of the locality from which the plant specimen was
collected.
Relevant standards: The default system is normally expected to be
ITRF or derivative standards (eg. MGA94, GDA94).
Domain/Range/Values: Alpha, internationally accepted codes (as
used in SDTS); the default system for HISPID3 is normally expected to be the Universal
Transverse Mercator Grid System (UTM). Wherever possible, the Eastings and Northings
should be converted to UTM or a derivative of it. For example, the MGA (Map Grid of
Australia) is a derivative of UTM and is derived from the projection of latitudes and
longitudes on the Australian Geodetic Datum (AGD) and Geocentric Datum of Australia (GDA).
Comments: In general, it is recommended that grid references be
converted to latitudes and longitudes for interchange (refer previous latitude and
longitude fields).
Description: The Map Grid Easting reference of the locality from
which the plant specimen was collected.
Relevant standards: ITRF or derivative standards (eg. MGA94,
GDA94).
Domain/Range/Values: Alphanumeric; any valid grid reference, in
metres. The Easting must consists of the following two elements:
| Hemisphere Code values in Field | Meaning |
| N | Northern Hemisphere Indicator |
| S | Southern Hemisphere Indicator |
Note: This single letter code must preface the Easting.
Note: The complete Easting must always be cited as a six-digit integer
or to the level of accuracy recorded by truncation from the right.
An example of a complete Grid Easting reference would be S347000. An
example of an Easting to the nearest kilometre for the same locality would be S347.
Comments: In general, it is recommended that grid references be
converted to latitudes and longitudes for interchange (refer previous latitude and
longitude fields). When this field is selectred for transfer then Spatial Grid,
Northing must also be used, not the Latitude and Longitude fields.
Note: Grid Zone designation codes must not be used.
Description: The Map Grid Northing reference of the locality from
which the plant specimen was collected.
Relevant standards: ITRF or derivative standards (eg. MGA94,
GDA94).
Domain/Range/Values: Integer; any valid grid reference, in
metres. The Northing must consists of the following two elements:
| Hemisphere Code values in Field | Meaning |
| N | Northern Hemisphere Indicator |
| S | Southern Hemisphere Indicator |
Note: This single letter code must preface the Northing.
Note: The complete Northing must always be cited as a seven-digit integer or to the level of accuracy recorded by truncation from the right.
An example of a complete Grid Northing reference would be S5739000. An
example of Grid Northing to the nearest kilometre for the same locality would be S5739.
Comments: In general, it is recommended that grid references be
converted to latitudes and longitudes for interchange (refer previous latitude and
longitude fields). When this field is selectred for transfer then Spatial Grid, Easting
must also be used, not the Latitude and Longitude fields.
Note: Grid Zone designation codes must not be used.
TDWG Short name: LATACCUR, LONGACCUR
Description: The precision of the latitude and longitude of the
record.
Relevant standards: SDTS, ABIS, ITF
Domain/Range/Values: Real; in metres.
Comments: If the latitude and longitude are not known, or the
accuracy is in doubt, then this field should be left unfilled and hence, not interchanged.
Description: Flag indicating the source of the geocode and
precision calculations.
Domain/Range/Values: Alpha; any value as listed in the following
table:
Values in Field
collector
compiler
generalised arbitrary point
automatically generated.
Comments: The geocodes provided by the plant 'collector' are
usually from GPS readings, maps onsite, extracted from field books or from the herbarium
label. Those provided by the database 'compiler' are derived from the locality information
provided by the collector. Computer-generated geocodes are either derived from a nearest
named place ('generalised arbitrary point') or from a stated locality.
TDWG Short name: STANLOC (?)
Description: The nearest named place to the locality of the
collection, 1:100 000 topographic map series.
Relevant standards: ABIS, AUSLIG Master Name File
Domain/Range/Values: Alpha; any valid place name on 1:100 000
topographic map series, conventional capitalisation of the first letter of place names.
Comments: Uncertainty with the application of this field to
historical material, reduces its usefulness. However individual institutions may choose to
use it as part of their core data and so make it available for interchange.