Australian Vegetation Attribute Manual

National Vegetation Information System, Version 6.0
Executive Steering Committee for Australian Vegetation Information (ESCAVI)
Department of the Environment and Heritage, 2003
ISBN 0 642 54953 2

Appendix I: Obsolete Attributes

(Australian Vegetation Attributes deleted from Version 5.0 or scheduled for deletion.)

  • Appendix I is generated from an XML text master file by formatting scripts.
  • The descriptive fields can be added or removed for display purposes.
  • References to Table numbers in the attribute descriptions may be to Version 5.0 or 6.0 of the attribute manual.
  • Data Set Level Attributes

Reference Information


Attribute: DS 5 - ENTRY LEVEL
Heading Details
Purpose: To define the level of data incorporated into the NVIS according to the NVIS Information Hierarchy.
Requirement: Mandatory
Database Field Name: ENTRY_LEVEL
Description: The level of detail in the input data set provided by the data custodian.
The target level for incorporation is at the sub-association level.
If the sub-association level is not available, then the data set is provided at the level with the greatest degree of integrity.
Value: Character(50). This is a value set from a defined lookup table: - Entry Level. The values in the lookup table are set by the administrator and cannot be added to.
Example:  
Review: Duplicates ENTRY LEVEL in Veg Description Table and is essentially obsolete in this table. Recommend deletion, noting that in the restructured database, data in 2003 onwards will only be entered at levels 5 and 6. The ENTRY_LEVEL field in the VEG_DESCRIPTION table would be retained.
Status: Implemented in NVIS Oracle database, but obsolete field proposed for deletion. For decision by NVIS stakeholders.
Attribute: DS 8 - VEGETATION THEME COVERAGE
Heading Details
Purpose: To specify the vegetation theme that applies to the ENTRY LEVEL for the dataset.
Requirement: QAQC
Database Field Name: VEGETATION_THEME_COVERAGE
Description: The vegetation theme (pre-clearing or extant) that applies to the dataset.
Value: Character(50). This is a value set from a defined lookup table:- Vegetation Theme. The values in the lookup table are set by the administrator and cannot be added to.
Example: Extant only
Review: This field is a mixture of dataset description and a qualifier on completeness. Now covered by shorter VEGETATION_THEME_CODE. If retained, recommend remove "_COVERAGE" from name; change "restricted" to "incomplete", where incomplete does not meet the NVIS specification - e.g. Grasslands are not mapped in RFA areas. If retained, recommend drop "classified" and "missing" as options in the lookup table.
Status: Implemented in the NVIS Oracle database; field name needs changing.
Look-up Table for: VEGETATION THEME COVERAGE
Code: Explanation:
extant only Extant Only - all vegetation ranging from natural to cultivated
extant only - restricted Extant Only - limited to particular vegetation. Eg woody vegetation, endangered communities
pre-clearing only Pre-clearing Only - all vegetation ranging from natural to cultivated. Extant not identified
pre-clearing only - restricted Pre-clearing Only - limited to particular vegetation. Eg woody vegetation, endangered communities
pre-clearing and extant Extant and Pre-clearing mapped for all vegetation ranging from natural to cultivated.
pre-clearing and extant - restricted Extant and Pre-clearing mapped for particular vegetation. Eg woody vegetation, endangered communities
not applicable not applicable
unknown unknown
Positional Accuracy
Attribute: - POSITIONAL UNITS
Heading Details
Purpose: To specify the unit of measurement for the POSITIONAL ACCURACY (DS 9).
Requirement: QAQC
Database Field Name: POSITIONAL_UNITS (was: POSITIONAL_PRECISION)
Description: This attribute provides information on the confidence level of the DATASET POSITIONAL ACCURACY. The preferred unit of measure is metres.
Value: Character(30). This is a value set from a defined lookup table:- Positional Units. The values in the lookup table are set by the administrator and can not be added to.
Example: Metres
Review: This field does not provide information on precision, but rather the units used for positional accuracy units. All meaningful data in the NVIS(2000) dataset is "metres". Recommend deletion from dataset.
Status: Implemented in the NVIS Oracle database. Obsolete, since DS 9 POSITIONAL_ACCURACY should always be specified in metres. Need to remove from the database.
Look-up Table for: POSITIONAL UNITS
Code: Explanation:
centimetres centimetres
metres metres
kilometres kilometres
not applicable not applicable
missing missing
unknown unknown
Map Origins (Methods and Sources)
Attribute: MM 1 - MAPPING METHOD NUMBER
Heading Details
Purpose: To identify each mapping method used in each dataset.
Requirement: QAQC
Database Field Name: MAPPING_METHOD_NUMBER
Description: A number assigned to each defined mapping method used in the construction of a dataset. The number is assigned sequentially, beginning with 1, within each dataset. Typical numbers are 1 and 2.
Value: Number(10)
Example: 2
Review: The design of NVIS V5.0 assumed that there were many sources for each mapping method. One could argue that the reverse was also possible, making a many to many database link. Anyway, the numbers of records are relatively low, so combining the two tables into one simplifies maintenance.
Status: Implemented in the NVIS Oracle database. Obsolete field with joining of former MAPPING_METHOD and MAP_SOURCE tables.
Attribute: MS 1 - MAP SOURCE NUMBER
Heading Details
Purpose: To identify each map source within each mapping method.
Requirement: QAQC
Database Field Name: MAP_SOURCE_NUMBER
Description: The number assigned to each map source. These numbers are assigned sequentially within each mapping method, beginning with 1.
Value: Number(10)
Example: 3
Review: All values in database = 1. I.e. effectively, a 1:1 relationship exists between MAPPING_METHODS and MAP_SOURCE tables. There is therefore a case for combining the tables Mapping_Method and Map_Source into the one table. Alternatively, there is a need better instructions on use of the Map_Source table.
Status: Implemented in the NVIS Oracle database. Obsolete field with joining of former MAPPING_METHOD and MAP_SOURCE tables.
References
Attribute: RF 1 - REFERENCE NUMBER
Heading Details
Purpose: To uniquely identify each reference within each dataset.
Requirement: Optional
Database Field Name: REF_NUMBER
Description: A unique identifier for each reference beginning from 1 in each dataset.
Value: Number(10); Valid range 1-999999999
Example: 15
Review: Doesn't seem to add much value and would seem to unnecessarily link generic references to 1 dataset. Multiple entry of generic references would be the result. Recommend further review with a view to deletion.
Status: Implemented in the NVIS Oracle database.

Map Unit Level Attributes

Core Vegetation
Attribute: MU 13 - SOURCE CODE
Heading Details
Purpose: To enable labelling of each mapping unit with the original mapping code used by the data supplier (usually a State or Territory).
Requirement: Mandatory
Database Field Name: SOURCE_CODE
Description: The original mapping code used by the data custodian for labelling and displaying the map unit.
Value: Character(50).
Example: Mu112aG3
Review: This field has generally been well filled out. However, many source codes for mosaics are yet to be resolved into their component vegetation descriptions.
Status: Implemented in the NVIS Oracle database. NB: This field must be retained in the MAP_UNIT table as an interim measure until all mosaics are resolved into their component vegetation descriptions, when it can be moved to the vegetation description table. SOURCE_CODE, the equivalent field in table:VEG_DESCRIPTION, will be retained.
Attribute: MU 13A - SOURCE CODE COMPONENT
Heading Details
Purpose: To split the source code as supplied by the data supplier into its components. This assists with the matching of source codes to NVIS descriptions.
Requirement: Mandatory
Database Field Name: SRC_CODE_COMPONENT
Description: A single state source code for a vegetation type. The source codes of the component vegetation associations within the mosaic exist as independent entities within the state system and map directly to NVIS descriptions. There should be no inconsistency mapping source code to vegetation description. Vegetation descriptions are not duplicated so there is no residual redundancy.
Value: Character(50)
Example: 9069100~1; 10bh_B~2
Review: This field has been filled out by the Commonwealth as an interim measure. Many source codes for mosaics need to be resolved into their component vegetation descriptions by data custodians.
Status: Implemented in the NVIS Oracle database. NB: This field must be retained in the MAP_UNIT table as an interim measure until all mosaics are resolved into their component vegetation descriptions.
Attribute: MU 14 - SOURCE DESCRIPTION
Heading Details
Purpose: To describe the mapping unit as used by the data supplier.
Requirement: Mandatory
Database Field Name: SOURCE_DESCRIPTION
Description: The original short description used by the data custodian for characterising the map unit. It is commonly used as the legend for mapping purposes.
Value: Character (2000).
Example: Montane grassy woodland
Coastal vine-rich forest
Review: Most mosaics are yet to be resolved into their component vegetation descriptions.
Status: Implemented in the NVIS Oracle database. This field has been retained in the MAP_UNIT table as an interim measure until all mosaics are resolved into their component vegetation descriptions. SOURCE_DESCRIPTION, the equivalent field in the table:VEG_DESCRIPTION, will be retained.
Attribute: MU 2 - ENTRY LEVEL
Heading Details
Purpose: To describe the level of detail in the NVIS Information Hierarchy at which the vegetation descriptions in the dataset have been supplied by the data custodian.
Requirement: Mandatory
Database Field Name: ENTRY_LEVEL
Description: The level of detail in the NVIS Information Hierarchy that the Map Unit was originally mapped at by the data custodian. This is used to differentiate data entry level of map units compiled from various data sets.
Value: This is a value set from a defined lookup table:- Entry Level. The values in the lookup table are set by the administrator and cannot be added to.
Example: Formation
Review: Duplicates dataset ENTRY LEVEL in VEG_DESCRIPTION table. Retain ENTRY LEVEL in VEG_DESCRIPTION table, so that each individual vegetation description can be assigned an ENTRY LEVEL. I.e. the entry level in a dataset can now vary with the level of detail available in the source description.
Status: Implemented in the NVIS Oracle database. Obsolete in this table. Needs to be deleted from the database.
Look-up Table for: ENTRY LEVEL
Code: Explanation:
class Growth form; level 1
formation Structural formation (Growth form, cover and height are implied as per Table 4 in Section 2.); level 2
broad floristic formation Floristic information (usually Genus) plus structural formation (Growth form, cover and height are implied as per Table 4 in Section 2.); level 3
sub-formation Floristic information (usually Genus) plus structural formation (Growth form, cover and height are implied as per Table 4 in Section 2) for each stratum (maximum of 3 strata); level 4
association For each stratum (maximum of 3 strata): floristic information (up to 3 dominant and/or diagnostic species) plus structural formation (Growth form, cover and height are implied as per Table 4 in Section 2). The ecologically predominant stratum is indicated (with a plus symbol: "+"); level 5
sub-association For each layer/sub-stratum (maximum of 8 sub-strata): floristic information (up to 5 dominant and/or diagnostic species) plus structural formation (Growth form, cover and height are implied as per Table 4 in Section 2). The ecologically predominant stratum is indicated (with a plus symbol: "+"); level 6
Attribute: MU 5 - CLASS
Heading Details
Purpose: To describe the class defining the map unit within the NVIS Information Hierarchy (refer to Table 1).
Requirement: Mandatory
Database Field Name: CLASS
Description: This attribute describes the class defining the map unit within the NVIS Information Hierarchy (refer to Table 1).
The description of class should include the growth form for the uppermost or ecologically dominant stratum of the dominant sub-association found within the map unit (refer to Tables 2 and 3).
This attribute should be derived using a rule set or expert knowledge.
Value: Character (255).
Example: Tree
Review: As part of the restructure (2001-2002), this field was found to duplicate information in CLASS of the VEG_DESCRIPTION table. The information is most-efficiently stored in the VEG_DESCRIPTION table.
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: MU 6 - STRUCTURAL FORMATION
Heading Details
Purpose: To describe the structural formation defining the map unit within the NVIS Information Hierarchy (refer to Table 1).
Requirement: Mandatory
Database Field Name: STRUCTURAL_FORMATION
Description: The description of structural formation should include dominant growth form, height and cover for the uppermost or ecologically dominant stratum of the dominant sub-association found within the map unit (refer to Tables 2 and 3).
This attribute should be derived using a rule set or expert knowledge.
Value: Character (255).
Example: tall open forest
Review: As part of the restructure (2001-2002), this field was found to duplicate information in CLASS of the VEG_DESCRIPTION table. The information is most-efficiently stored in the VEG_DESCRIPTION table.
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: MU 7 - BROAD FLORISTIC FORMATION
Heading Details
Purpose: To define the floristic code reported at the sub-formation level of the NVIS Information Hierarchy (refer to Table 1).
Requirement: Mandatory
Database Field Name: BROAD_FLORISTIC_FORMATION
Description: The code summarises the flora component of the map unit at genus or family level. It should be based on the dominant stratum of the dominant sub-association found within the map unit (refer to tables 2 and 3).
The codes have been recorded in lower case to avoid confusion with the growth form codes.
Value: Character (255).
Example: Eucalyptus tall open forest
Review: As part of the restructure (2001-2002), this field was found to duplicate information in CLASS of the VEG_DESCRIPTION table. The information is most-efficiently stored in the VEG_DESCRIPTION table.
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: MU 8 - SUB-FORMATION
Heading Details
Purpose: To describe the sub formation defining the map unit within the NVIS Information Hierarchy.
Requirement: Mandatory
Database Field Name: SUB-FORMATION
Description: The description of sub-formation should include the dominant growth form, cover, height and broad floristic code (usually dominant Genus and Family) for the three strata (refer to table 3) of the dominant sub-association found within the map unit.
This attribute may be derived using a rule set or expert knowledge.
Value: Character (255).
Example: Eucalyptus tall open forest/Proteaceae open shrubland/mixed groundlayer
Review: As part of the restructure (2001-2002), this field was found to duplicate information in CLASS of the VEG_DESCRIPTION table. The information is most-efficiently stored in the VEG_DESCRIPTION table.
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: MU 9 - ASSOCIATION
Heading Details
Purpose: This attribute provides an association level description of the vegetation description as defined within the NVIS Information Hierarchy (refer to Table 1).
Requirement: Mandatory
Database Field Name: ASSOCIATION
Description: The description of association defined for the NVIS includes the dominant growth form, height and cover of the dominant/diagnostic species (maximum of 3) for the three traditional strata (i.e. upper, mid and ground) of the dominant sub-association found within the map unit (refer to Tables 2 and 3).
This attribute should be derived using a rule set or expert knowledge.
Value: Character (255).
Example: Refer to the example for Association in Table 2.
Review: As part of the restructure (2001-2002), this field was found to duplicate information in CLASS of the VEG_DESCRIPTION table. The information is most-efficiently stored in the VEG_DESCRIPTION table.
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: MU 10 - SUB-ASSOCIATION
Heading Details
Purpose: This attribute describes the sub-association level description of the vegetation description as defined within the NVIS Information Hierarchy (refer to table 1).
Requirement: Mandatory
Database Field Name: SUB-ASSOCIATION
Description: The description of sub-association defined for the NVIS includes dominant growth form, height and cover of the dominant/diagnostic species (maximum of 5) for all layers/strata (refer to table 3) of the sub-association within the map unit (refer to Tables 2 and 3).
This attribute should be derived using a rule set or expert knowledge.
Value: Character (255).
Example: Refer to the example for Sub-Association in Table 2.
Review: As part of the restructure (2001-2002), this field was found to duplicate information in CLASS of the VEG_DESCRIPTION table. The information is most-efficiently stored in the VEG_DESCRIPTION table.
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: MU 11 - ENVIRONMENTAL DESCRIPTION
Heading Details
Purpose: To describe the environmental characteristics that occur across the map unit.
Requirement: Optional
Database Field Name: ENVIRONMENTAL_DESCRIPTION
Description: This may be generated from environmental parameters that are supplied in the discrete vegetation descriptions of the map unit or may be taken directly from the original map unit definition.
Value: Character (255).
Example: This type of vegetation occurs on old sand dunes. The distribution appears to correlate with sheltered moist areas on the landward side of the Rainforests on the deep sands along the east coast of the Range. The recorded fire history varies but cool ground fires are likely to be common and patchy.
Review:  
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: MU 12 - MINOR SUB-ASSOCIATIONS
Heading Details
Purpose: To document the presence of minor sub-associations in the mapping unit.
Requirement: Mandatory
Database Field Name: MINOR_SUB-ASSOCIATIONS
Description: Sub-associations smaller than the minimum mapping unit (MMU) are reported, eg. Rainforest patches in broader eucalyptus forests. The scale at which the data set is produced (Reid 1988, Gunn et al 1988) usually defines the MMU. The MMU may differ for units of uniform and elongated shape. The data custodian will determine the number of minor sub-associations to list. It will be necessary to contact the data custodian to access more information on the interpretation of the codes.
Value: Character (255)
Example: Ma25, ge34 ? A data set at 1:100,000 scale, has a minimum mapping area of 20ha. This attribute would record sub-associations that could not be mapped because they were less than 20ha in size.
Review: As part of the restructure (2001-2002), this field was found to duplicate information in CLASS of the VEG_DESCRIPTION table. This field has been sparsely and inconsistently filled-out. With six available vegetation descriptions per map unit in the spatial coverage, there should be adequate means to document minor types. (The restriction on MMU does not apply.)
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)

Vegetation Description Level Attributes

Core Vegetation
Attribute: VG 1 - VEGETATION DESCRIPTION NUMBER
Heading Details
Purpose: To uniquely identify each vegetation type within the map unit.
Requirement: Mandatory
Database Field Name: VEG_DSC_NUMBER
Description: Each discrete sub-association within the map unit is assigned a unique number. The most spatially dominant vegetation description must be assigned a value of '1'.
The number assigned to the remaining sub-associations (if they exist) should be allocated according to decreasing spatial area. Where there is no clear pattern of spatial dominance for subsequent sub-associations, the numbering can be arbitrary.
Value: Numeric (1); Multiple entries allowed.
Example: Map unit1:Sub-association1='1'
Map unit 1:Sub-association 2='2' etc.
Review: This attribute is not needed in this table, after the restructure.
Status: Implemented in the NVIS Oracle database. Obsolete. Needs to be deleted from the database.
Attribute: VG 2 - ENTRY LEVEL
Heading Details
Purpose: To describe the level of detail in the NVIS Information Hierarchy at which the vegetation description has been supplied by the data custodian.
Requirement: QAQC
Database Field Name: ENTRY_LEVEL
Description: This is used to differentiate data entry level of each vegetation description.
The vegetation description entry level (association or sub-association) determines the expected detail of stratum information supplied for the vegetation description.
Value: Character(255). This is a value set from a defined lookup table:- Entry Level. The values in the lookup table are set by the administrator and cannot be added to.
Example: sub-association
Review: The NVIS stakeholders have agreed to enter data at the complex levels (5 and 6) only. Are the other allowable values needed for historic purposes?
Status: Implemented in the NVIS Oracle database. LUT is obsolete in this form.
Look-up Table for: ENTRY LEVEL
Code: Explanation:
class Growth form; level 1
formation Structural formation (Growth form, cover and height are implied as per Table 4 in Section 2.); level 2
broad floristic formation Floristic information (usually Genus) plus structural formation (Growth form, cover and height are implied as per Table 4 in Section 2.); level 3
sub-formation Floristic information (usually Genus) plus structural formation (Growth form, cover and height are implied as per Table 4 in Section 2) for each stratum (maximum of 3 strata); level 4
Attribute: VG 3 - MAP UNIT SPATIAL EXTENT
Heading Details
Purpose: To describe the spatial extent of the sub-association within the map unit
Requirement: Mandatory
Database Field Name: MAP_UNIT_SPATIAL_EXTENT
Description: The spatial extent of the sub-association within the map unit measured as a percentage. The value may be a measured value or an estimated value.
Wherever practical, a real value should be provided for this attribute. Estimated values should be in multiples of 5 (i.e. 35% rather than 32% or 37%).
Where only one discrete sub-association occurs in the map unit, and it covers the whole unit, the value will be '100' (i.e. 100%).
Estimates may require the input of local expertise.
Value: Integer (3); Valid Range 0-100; Units: percentage
Example: 30
Review:  
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: VG 12 - MINOR SUB-ASSOCIATIONS
Heading Details
Purpose:  
Requirement: Mandatory
Database Field Name: MINOR_SUB-ASSOCIATIONS
Description: This attribute is used to record the occurrence of significant minor sub-associations within the vegetation description.
Value: Character (255).
Example: Refer to example for MU12. MINOR SUB ASSOCIATIONS.
Review: As part of the restructure (2001-2002), this field was found to duplicate information in CLASS of the MAP_UNIT table. This field has been sparsely and inconsistently filled-out. With six available vegetation descriptions per map unit in the spatial coverage, there should be adequate means to document minor types. NVIS stakeholders need to ask whether the framework (especially at level 6 and in the lower tables) is adequate to describe the observed variability of a vegetation type.
Status: Implemented in the NVIS Oracle database. Obsolete. Needs to be deleted from the database.

Detailed Vegetation Attributes

Structural Information
Attribute: STR 19 - GROWTH FORM CODE
Heading Details
Purpose: To categorise the growth form of a stratum.
Requirement: Mandatory
Database Field Name: GROWTH_FORM_CODE
Description: The growth form describes the habit of a plant, identified most precisely by the position of its perennating buds (Beadle & Costin 1952).
Identification of the growth form for each sub-stratum will contribute to the definition of the structural formation (see Table 5 and levels 1 to 6 in the table: VEG_DESCRIPTION).
Value: Character(30); This is a value set from a defined lookup table:- Growth Form Code. See attribute: GR 3 GROWTH FORM CODE. The values in the lookup table are set by the administrator and can not be added to.
Example: T
Review: As part of the restructure (2001-2002), this field was found to duplicate information in GROWTH_FORM_CODE of the GROWTH_FORM table. The information is most-efficiently stored in the GROWTH_FORM table. This attribute should relate to a taxon or a growth form, so is best stored in the TAXON and/or GROWTH_FORM tables. Where a single growth form is required to describe a stratum, as in NVIS Level 4 this information can be generated from other fields, especially SUMMARY_FLAG.
Status: Implemented in the NVIS Oracle database. Obsolete. Need to remove from the database.
Attribute: STR 20 - STRUCTURAL CODE
Heading Details
Purpose: To briefly document the structure of a stratum in levels 5 and 6.
Requirement: Mandatory
Database Field Name: STRUCTURAL_CODE
Description: The structure coding for the stratum, based on the NVIS Structural Formations Nomenclature.
The code is a triplet code based on: [growth form code][height class][cover code].
Absent values in the structural codes are denoted by a hash symbol (#).
Value: Character (255).
Example: Removed...
Review: This field has non-normalised content, drawing upon other fields in the STRATUM table.
Status: Implemented in the NVIS Oracle database. Obsolete. Needs to be deleted from the database.
Attribute: STR 21 - BROAD FLORISTIC
Heading Details
Purpose:  
Requirement: Mandatory
Database Field Name: BROAD_FLORISTIC
Description: This attribute defines the floristic code reported at the sub-formation level of the NVIS Information Hierarchy. The code summarises the flora component of the map unit at genus or family level. It should be based on the dominant stratum of the dominant sub-association found within the map unit.
It is kept as a separate attribute for data analysis and reporting.
Value: This is a value set from an expandable lookup table:- Broad Floristic. Initial values are set by the administrator, new values can be added by the data loader.
Example: e - Eucalyptus is the prevalent genus
w - Acacia is the prevalent genus
Review: Applied inconsistently in initial compilation exercise.
Status: Obsolete. This field has been removed from the NVIS Oracle Database as part of the restructure (2001-2002)
Attribute: STR 22 - TAXON DESCRIPTIONS
Heading Details
Purpose: To describe the dominant species of the sub-stratum.
Requirement: Mandatory
Database Field Name: TAXON_DESCRIPTIONS
Description: The full taxonomic names of the dominant taxa for the sub-stratum as listed in the GR2. DOMINANCE SEPARATOR attribute.
Value: Character (255).
Example: Eucalyptus obliqua
Review: As part of the restructure (2001-2002), this field was found to duplicate information in the VEG_DESCRIPTION table (sub-association and/or association descriptions) and in the TAXON table (TAXDSC_ID can be linked to TAXON_DESCRIPTION table to generate species names.). Data custodians often appear to use this field to provide fuller species lists for a vegetation type. However, the chance of major inconsistencies remain, unless the field is redefined to include only supplementary species - i.e. those species not recorded in the other tables.
Status: Implemented in the NVIS Oracle database. Obsolete. Needs to be deleted from the database. Recommend investigation of requirement for full species lists in a vegetation description; then, if required, additional design work is needed.
Growth Form Information
Attribute: GR 2 - DOMINANCE SEPARATOR
Heading Details
Purpose: To specify the symbol to be used when concatenated with other growth forms in the Stratum and Veg-description levels.
Requirement: Mandatory
Database Field Name: DOMINANCE_SEPARATOR
Description: This attribute is used for specifying the dominance separator of this growth form when concatenated with other growth forms at the stratum level:
Value: Character (3) as found in :- Dominance Separator
Example: -
Review: Duplicates GR 10 DOMINANCE. Need to maintain one set properly, rather than two, which are often inconsistent. Letters, rather than symbols, are easier to manage in the normalised part of the database. (Full words would be even better, since these are self-documenting.) An appropriate dominance separator symbol can then be part of the automatic scripting to generate vegetation descriptions from the lower tables.
Status: Implemented in the NVIS Oracle database. Obsolete. The information content needs to be reconciled with GR 10 DOMINANCE. Where this cannot be done automatically, the data custodians will need to supply the correct interpretation. Then this field can be deleted from the database.
Look-up Table for: DOMINANCE SEPARATOR
Code: Explanation:
. dominant
, co-dominant
- sub-dominant
+/- sub-dominant, may or may not be present
not applicable not applicable
missing missing
unknown unknown
Taxon Information
Attribute: TX 2 - DOMINANCE SEPARATOR
Heading Details
Purpose: To specify the symbol to be used when concatenated with other taxa in the Stratum and Veg-description levels.
Requirement: Mandatory
Database Field Name: DOMINANCE_SEPARATOR
Description:
, co-dominant
- sub-dominant
+/- sub-dominant, may or may not be present
Value: This is a value set from a defined lookup table. The values in the lookup table are set by the administrator and cannot be added to.
Example: +/-
Review: Duplicates TX 9 (COVER) DOMINANCE. Need to maintain one set properly, rather than two, which are often inconsistent. Letters, rather than symbols, are easier to manage in the normalised part of the database. (Full words would be even better, since these are self-documenting.) An appropriate dominance separator symbol can then be part of the automatic scripting to generate vegetation descriptions from the lower tables.
Status: Implemented in the NVIS Oracle database. Obsolete. The information content needs to be reconciled with TX 9 DOMINANCE. Where this cannot be done automatically, the data custodians will need to supply the correct interpretation. Then this field can be deleted from the database.
Taxon Lists/Description Information
Attribute: TD 1 - SOURCE IDENTIFIER
Heading Details
Purpose:  
Requirement: QAQC
Database Field Name: SOURCE_IDENTIFIER
Description: The authority's (TAXON SOURCE) unique identifiers for each taxon. Multiple entries allowed per TAXON SOURCE.
Value: Number(10); Valid entries 1-9999
Example:  
Review: This attribute duplicates another attribute in the Taxon Lists table, with no benefit.
Status: Implemented in the NVIS Oracle database. Obsolete field, to be deleted.