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
Section Three (continued): List of NVIS Attributes
Descriptions of NVIS Attributes
| Attribute: DS01 - DATA SET NAME |
| Heading |
Details |
| Purpose: |
To identify each dataset in a user-friendly way. |
| Requirement: |
Mandatory |
| Database Field Name: |
DATA_SET_NAME |
| Description: |
This is the name given to the spatial data set by the custodial organisation. The information should be in plain language (that is, preferably not solely in acronym form). |
| Value: |
Character(2000) |
| Example: |
Gippsland Ecological Vegetation Classes - Extant |
| Comments: |
Sometimes duplicates ANZLIC_METADATA_NAME, but is necessary to cater for situation where the dataset supplied to NVIS is a subset or a superset of the dataset described on the Australian Spatial Data Directory. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS02 - DATA SET NUMBER |
| Heading |
Details |
| Purpose: |
To identify each dataset in a concise and systematic way. |
| Requirement: |
Commonwealth |
| Database Field Name: |
DATA_SET_NUMBER |
| Description: |
This is a number given to the data set by the Commonwealth in compiling the NVIS (2000) dataset. The number must be retained by the data custodian for any subsequent transfers or updates to the vegetation description. |
| Value: |
Number(10). Format: SDD, where S = State Code (from lookup table); DD is the dataset number, which is assigned by the administrator. |
| Example: |
413 |
| Comments: |
This first digit 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. This field will probably be of little direct interest to the States and Territories. |
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: DATA SET NUMBER
| Code |
Explanation |
| 1 |
Australian Capital Territory |
| 2 |
New South Wales |
| 3 |
Northern Territory |
| 4 |
Queensland |
| 5 |
South Australia |
| 6 |
Tasmania |
| 7 |
Victoria |
| 8 |
Western Australia |
| Attribute: DS03 - VEGETATION THEME CODE |
| Heading |
Details |
| Purpose: |
To identify whether the dataset represents pre-1750 and/or extant (present) vegetation. |
| Requirement: |
Mandatory |
| Database Field Name: |
VEGETATION_THEME_CODE (was: DATASET_COVERAGE_TYPE) |
| Description: |
This is a short code assigned to the data set according to whether the dataset represents pre-1750 and/or extant (present) vegetation. |
| Value: |
Character(20). 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: |
E |
| Comments: |
This attribute was developed and applied by BRS (as B/E/P) in the compilation phase of NVIS (2000). It is a useful and important attribute for managing NVIS spatial coverages. This field and the next (VEGETATION_THEME_CONSTRAINTS) replace the former attribute VEGETATION_THEME COVERAGE, which combined two streams of information about the dataset. |
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: VEGETATION THEME CODE
| Code |
Explanation |
| B |
The dataset comprises both extant and pre-clearing |
| E |
Extant (i.e. present, remnant) vegetation |
| P |
Pre-clearing (i.e. pre-1750 or "natural") vegetation |
| Attribute: DS04 - VEGETATION THEME CONSTRAINTS |
| Heading |
Details |
| Purpose: |
To describe any major limitations applying to the vegetation theme for the dataset. |
| Requirement: |
Recommended |
| Database Field Name: |
VEGETATION_THEME_CONSTRAINTS |
| Description: |
A free text description of any spatial or attribute limitations to the vegetation theme (pre-clearing or extant) that applies to the dataset. |
| Value: |
Character(2000). |
| Example: |
woody vegetation only; endangered communities only; only recorded vegetation types conforming to the vegetation regulation act - see reference 456; mapped woody remnant vegetation within the wheatbelt study area, but did not attribute the cleared and semi-native vegetation types. |
| Comments: |
In terms of spatial constraints, please specify the extent of coverage by the attributes and any exclusions. See also VEGETATION THEME CODE, |
| Status: |
Proposed field, not yet implemented in the NVIS Oracle database. Requires agreement and provision of content from NVIS stakeholders. |
| Attribute: DS05 - ANZLIC METADATA IDENTIFIER |
| Heading |
Details |
| Purpose: |
To provide a unique, machine-generated, human-readable link to the completed metadata and further information about the data set on the Australian Spatial Data Directory. |
| Requirement: |
Recommended |
| Database Field Name: |
ANZLIC_METADATA_IDENTIFIER |
| Description: |
Each metadata statement prepared by the custodian must have a unique, system-generated ANZLIC identifier. A data set should be internally consistent, for example the methods used for mapping and the taxon list used to name species records must be consistent. A data set derived with inconsistent methodologies should be recorded as a distinct data set where possible. |
| Value: |
Character(50) |
| Example: |
ANZCW0501000222 |
| Comments: |
All data sets must have an ANZLIC compliant metadata entry before being accepted into the NVIS. The ANZLIC identifier is supplied by the ANZLIC contact in each jurisdiction. The Australian Spatial Data directory can be searched at URL: http://www.auslig.gov.au/asdd/ and has useful extra details including the data set: title, custodian, contact information, quality information and a list of attributes. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS06 - ANZLIC METADATA NAME |
| Heading |
Details |
| Purpose: |
To provide name of dataset in ASDD |
| Requirement: |
Optional |
| Database Field Name: |
ANZLIC_METADATA_NAME |
| Description: |
This is the name given to the data set by the custodial organisation. The information should be in plain language (that is, preferably not solely in acronym form). Should preferably be the same as DS1, but typically, this isn't the case. |
| Value: |
Character(2000) |
| Example: |
Gippsland Ecological Vegetation Classes - Extant |
| Comments: |
|
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS07 - ANZLIC METADATA URL |
| Heading |
Details |
| Purpose: |
To provide a direct, on-line link to the metadata statement. |
| Requirement: |
Optional |
| Database Field Name: |
ANZLIC_METADATA_URL |
| Description: |
The internet address of the metadata statement, (preferably as found on the Australian Spatial Data Directory (ASDD). |
| Value: |
Character(2000) |
| Example: |
http://www.auslig.gov.au/servlet/asdd_basic/retrieve?pn=17&el=F& db=current&rp=2&mr=1&ac=current&cid=177 |
| Comments: |
The contents of this field will require maintenance from time to time. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS08 - STRUCTURAL CLASSIFICATION SYSTEM |
| Heading |
Details |
| Purpose: |
To specify the classification system originally used in the field survey and mapping method. |
| Requirement: |
QAQC |
| Database Field Name: |
STRUCTURAL_CLASSFN_SYSTEM |
| Description: |
The classification system and reference used for describing the vegetation structural formations in a data set.
This is important where information entered has come in class ranges rather than discretely measured values (applicable to older mapping and land system/unit mapping). |
| Value: |
Character(50). This is a value set from an expandable look up table. Initial values are set by the administrator, new values can be added by the data loader. |
| Example: |
Walker1990 |
| Comments: |
Where a data set has been pre-classified and the classification system is not listed in the lookup table, the user will be able to ask the administrator to add an entry to the lookup table. |
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: STRUCTURAL CLASSIFICATION SYSTEM
| Code |
Explanation |
| Specht1995 |
Specht, R. L., E. E. Hegarty, M. B. Whelan and A, Specht. 1995. Conservation atlas of plant communities in Australia. Southern Cross University. Centre for Coastal Management, Lismore |
| Specht1974 |
Specht, R.L., E.M. Roe, and V.H. Boughton, 1974. Conservation of major plant communities in Australia and Papua New Guinea. Aust.J.Bot.Suppl.No.7. |
| Walker1990 |
Walker J. and M.S. Hopkins 1990. Vegetation. In: McDonald, R.C., R.F., Isbell, J.G., Speight, J. Walker, and M.S. Hopkins. 1990. Australian soil and land survey. Field handbook. 2nd edn. Melbourne: Inkata Press |
| Beadle1981 |
Beadle, N. C. W. 1981. The vegetation of Australia. Cambridge University Press, London |
| Carnahan1976 |
Carnahan, J.A. 1976. Natural Vegetation. Atlas of Australian Resources. Second Series. Department of Natural Resources, Canberra |
| Beard1976 |
Beard, JS (1976) Vegetation map of Western Australia: map and explanatory memoir. Applecross WA, Vegemap Publications, 1976 : 27 vols, illus, maps. |
| not applicable |
not applicable |
| unknown |
unknown |
| SA Structural Formation Table |
Classification based on adaptation of Muir 1977 and Specht 1972 |
| Modified Carnahan/Specht |
developed for Atlas of Australian Vegetation |
| Attribute: DS09 - FLORISTIC GROUP TYPE |
| Heading |
Details |
| Purpose: |
To describe how each vegetation type has been defined in terms of species composition. |
| Requirement: |
Recommended |
| Database Field Name: |
FLORISTIC_GROUP_TYPE |
| Description: |
This field describes the method by which species are selected to define each floristic group in the dataset (i.e. the choice of up to 5 species in the level 6 description). This field should identify whether the vegetation descriptions contain: (i) species that contribute the most biomass (or cover/abundance), (ii) indicator species or (iii) a mixture of both types of species. |
| Value: |
Character(20). 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: |
indicator_biomass |
| Comments: |
Indicator species are those species that are characteristic or unique to a particular vegetation type but may not be the most abundant or dominant species. |
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: FLORISTIC GROUP TYPE
| Code |
Explanation |
| indicator_biomass |
The species listed for the floristic group are both the indicator/diagnostic species and also those species with the greatest biomass (eg Allosyncarpia ternata forests |
| indicator |
The species listed for the floristic group are indicator or diagnostic species, (i.e. not necessarily those species with the greatest biomass. |
| biomass |
The species listed for the floristic group contribute the greatest biomass or cover abundance to the floristic group |
| not applicable |
not applicable |
| unknown |
unknown |
| Attribute: DS10 - CLASSIFICATION METHOD |
| Heading |
Details |
| Purpose: |
To describe the analysis methods used to create the vegetation types. |
| Requirement: |
QAQC |
| Database Field Name: |
CLASSIFICATION_METHOD (was: CLASSIFICATION_SUPPORT) |
| Description: |
This attribute is used to describe the methods used to derive the vegetation types. It includes the package used e.g. PATN, the particular module used e.g. UPGMA, and the parameters selected and the rationale for their selection. |
| Value: |
Character(4000) |
| Example: |
Classification: The quadrats were classified into types on the basis of floristic/structural data (canopy cover of every species in each quadrat measured on a scale of 1 to 6 - modified Braun Blanquet scale). Both agglomerative and divisive hierarchical methods were used to classify the quadrats into major types to allow a comparison of the results of the two methods.
The agglomerative method used was Unpaired Analysis (UPGMA) using a Canberra metric (Kovach, 1993). The divisive method was a two way Indicator Species Analysis (TWINSPAN) (Hill, 1979) with 6 cut levels corresponding to the cover scores.
Minor types were distinguished within each major type using a combination of TWINSPAN analysis of each major group and the UPGMA analysis of the whole database.
Ordination: The floristic/cover data were also ordinated to investigate the relationships between the different vegetation types. The method used was Principle components Analysis of untransformed data with the species, but not the sites, standardised. All the species and samples were given equal weighting. The species data for the Banksia ericifolia Heath (H1) community was ordinated using Detrended Correspondence Analysis (DCA) to investigate for patterns and to correlate any patterns with time since last fire and fire frequency. |
| Comments: |
The text could often be cut and pasted from an existing project report. Any modifications to the original classification must be reported. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS11 - SAMPLING TYPE |
| Heading |
Details |
| Purpose: |
To describe the type of site plots used to derive and/or field check the map, survey or project. Used to determine the reliability of the resultant map. |
| Requirement: |
QAQC |
| Database Field Name: |
SAMPLING_TYPE |
| Description: |
|
| Value: |
Character(50). 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: |
full vegetation sites |
| Comments: |
Further details on the sampling should be provided in the attribute MAPPING_METHOD for each method used in the creation of the dataset. |
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: SAMPLING TYPE
| Code |
Explanation |
| full vegetation and field check sites |
A 'full vegetation and field check site' vegetation survey is one, which includes most of the following elements and hence represents the highest class for data quality that can be entered into the NVIS Database. 1. Planning and field survey
Where the site-based quadrats are located using a stratification system that includes reference to environmental attributes and aerial photos and/or satellite imagery that are available on a regional scale (i.e. at least 1:100,000).
A sufficient density of site based quadrats to detect the majority of the vegetation types present within the region at a particular scale e.g. one site per unique map unit defined on aerial photos and/or satellite imagery.
Recording general biophysical and environmental attributes of a landscape unit in which the site is located.
Recording the full list of higher plants and various attributes of the species e.g. growth forms
Recording the vegetation in strata
Recording the structural attributes of the vegetation community e.g. height, cover, strata and growth forms
Recording a geo-reference for the site-based quadrats so that they are relocatable and capable of being used in a GIS
Recording of metadata for each site e.g. date, observer, etc
Entering of the data from site-based quadrats into a relational database and checking of the data. 2. Classifying, interpreting and describing the quadrats the vegetation into definitive vegetation types
This involves describing the vegetation types in terms of structural, floristic and environmental characteristics using multivariate analyses or classifying the vegetation types according to a pre-existing list of definitive vegetation types that has been developed to represent all vegetation types known to occur within a region or jurisdiction. 3. Mapping the definitive vegetation types across the landscape based on observed patterns between the original stratification system and aerial photos and/or satellite imagery. |
| full vegetation sites |
Plot area delimited. Full species lists (at time of survey) for each stratum including height and cover. These are generally used to ground truth mapping. |
| characterisation sites |
Plot area delimited. List of the dominant or conspicuous species only (at time of survey), for the over-storey and ground layer including average height of the over-storey and ground-storey cover |
| field check sites |
No plot area. With or without a GPS location. Dominant species in the predominant strata measured or checked. Rapid assessment sites. Possibly some structural information. Fly by sites. |
| basal area sites |
No plot area. Aim to capture the woody species (trees and shrubs) above 1.3m by using the Bitterlich gauge. Basal area by species provides a measure of dominance of overstorey species. |
| no sites |
No field verification |
| not applicable |
not applicable |
| unknown |
unknown |
| Attribute: DS12 - BOTANICAL EXPERTISE |
| Heading |
Details |
| Purpose: |
To describe, as a whole for the dataset, how reliably plants were identified. |
| Requirement: |
Recommended |
| Database Field Name: |
BOTANICAL_EXPERTISE |
| Description: |
A description of how well the flora was assessed. |
| Value: |
Character(2000) |
| Example: |
High confidence in skill and reliability of the observers/interpreters. Project manager has practical experience of 15 years and team has an average of 5 years field experience. Voucher specimens were collected. |
| Comments: |
This information is not intended to describe individual sub-associations or map units. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS13 - POSITIONAL ACCURACY |
| Heading |
Details |
| Purpose: |
To specify the locational accuracy of the dataset. |
| Requirement: |
QAQC |
| Database Field Name: |
POSITIONAL_ACCURACY |
| Description: |
The accuracy of mapped line or cell features in relation to their real world locations (eg. nearness to the real world geo-referenced location) across the data set. |
| Value: |
Number(5,1) |
| Example: |
10 [accurate to +/- 10] |
| Comments: |
The units of measure for this attribute must be in metres. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS14 - POSITIONAL ACCURACY DETERMINATION |
| Heading |
Details |
| Purpose: |
To identify the method used for assessing POSITIONAL ACCURACY |
| Requirement: |
QAQC |
| Database Field Name: |
POSITIONAL_ACCURACY_DETERM |
| Description: |
A code indicating the positional source or determination of points, polygons or cells across the data set. The information provided should relate to the type of data set i.e. point, polygon or raster (##where? field not set up to provide this info). |
| Value: |
Character(20). 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: |
satellite |
| Comments: |
Lookup Table sourced and simplified from draft Martin and Sinclair (1999). Where the entry is recorded as unknown or not applicable, the POSITIONAL ACCURACY attribute in the metadata should provide more information. Further details on positional controls etc should be provided in the attribute MAPPING_METHOD. |
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: POSITIONAL ACCURACY DETERMINATION
| Code |
Explanation |
| GPS |
GPS - type unspecified |
| DGPS |
Differential /RTCM corrected GPS |
| mapped |
Mapped topographic features |
| satellite |
rectified satellite image |
| rectphoto |
rectified aerial photograph |
| orthoquad |
orthophoto quad |
| estimate |
estimate from known position |
| not applicable |
not applicable |
| unknown |
unknown |
| Attribute: DS15 - POSITIONAL ACCURACY MEASURE |
| Heading |
Details |
| Purpose: |
To specify the type of measure and/or calculation used to determine DATASET POSITIONAL ACCURACY. |
| Requirement: |
Recommended |
| Database Field Name: |
POSITIONAL_ACCURACY_MEASURE |
| Description: |
|
| Value: |
Character(20); This is a value set from a defined lookup table. The values in the lookup table are set by the administrator and can not be added to. |
| Example: |
RMSE |
| Comments: |
|
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: POSITIONAL ACCURACY MEASURE
| Code |
Explanation |
| RMSE |
Root Mean Square of Error determined at time of transformation or registration. |
| CMAS |
Circular map accuracy standard |
| percentage measure |
Percentage value measured after the mapping is completed using an independent field sampling procedure |
| percentage estimate |
Percentage value estimated from anecdotal information and/or experts |
| probability |
Probability estimate |
| not applicable |
not applicable |
| unknown |
unknown |
| Attribute: DS16 - MAP PUBLICATION SCALE |
| Heading |
Details |
| Purpose: |
To specify the scale at which the vegetation map/dataset was published. |
| Requirement: |
Mandatory |
| Database Field Name: |
MAP_PUBLICATION_SCALE (was: MAPPING_SCALE) |
| Description: |
The denominator of the ratio of a distance on a map to its corresponding distance on the ground. |
| Value: |
Number(10) |
| Example: |
50000; e.g. Kangaroo Island SA. |
| Comments: |
For unpublished maps or coverages, please specify a nominal scale that would be suited to routine use. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS17 - FINEST SCALE |
| Heading |
Details |
| Purpose: |
To specify the finest scale at which the mapping would be most accurate for display without modifying the map/spatial units. |
| Requirement: |
Recommended |
| Database Field Name: |
FINEST_SCALE (was: FINE_SCALE) |
| Description: |
This field is based on the stated scale/resolution of the data set, as recorded in the metadata. The field is expressed as the denominator only.
This attributes addresses the fact that It is quite a common occurrence that either out of ignorance or opportunism, maps are often used at a scale far finer than the intention of, and original purpose of, the mapping.
The term fine scale equates to large scale. |
| Value: |
Number(10); To be used in conjunction with DS 19. BROADEST SCALE |
| Example: |
40000 - A 1:50000 scale map could be used at 1:40000 scale without too much inaccuracy. However it could not be used at 1:20000. E.g. Kangaroo Island SA. |
| Comments: |
The data custodian will determine the value. These scale limit restrictions could be applied in a GIS or internet mapping facility to restrict zooming capacity. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS18 - BROADEST SCALE |
| Heading |
Details |
| Purpose: |
To specify the broadest scale at which the mapping would be most accurate for display without modifying the map/spatial units. |
| Requirement: |
Recommended |
| Database Field Name: |
BROADEST_SCALE (was: BROAD_SCALE) |
| Description: |
This is based on the stated scale/resolution of the data set, as recorded in the metadata. The field is expressed as the denominator only.
This attributes addresses the fact that it is quite a common occurrence that maps are sometimes used at a scale or resolution far broader than the intention of, and original purpose of, the mapping. Maps used at a broader scale than the publication scale may need spatial and/or attribute generalisation to be applied before viewing. I.e. simpler levels in the hierarchy would provide simpler analyses, faster viewing and coverages of comparable complexity to other themes at the broad scale.
The term broad scale equates with small scale. |
| Value: |
Number(10); To be used in Conjunction with DS 18. FINEST SCALE. |
| Example: |
200000 - A 1:50000 scale map could be used at 1:1200000 scale without too many problems; e.g. Kangaroo Island SA. |
| Comments: |
The data custodian will determine the value. These scale limit restrictions could be applied in a GIS or internet mapping facility to restrict zooming capacity. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS19 - SURVEY AND MAP RELIABILITY |
| Heading |
Details |
| Purpose: |
To describe the overall reliability in the survey and mapping methods (spatial/positional and attributes/ecological) used to derive the data set. |
| Requirement: |
Mandatory |
| Database Field Name: |
SURVEY_AND_MAP_RELIABILITY(was: RELIABILITY) |
| Description: |
This attribute should be completed even if little information is available and should be based on an expert assessment of all methods used and their limitations.
This attribute could also contain a reference to a document for further information. |
| Value: |
Character(2000) |
| Example: |
The reliability of this data set is very good. The delineation of map units was based on rectified colour aerial photography at 1:20000 scale using experienced interpreters. Data collected was calibrated in the field with a final accuracy of 85% in the delineation of vegetation mapping units. Further information can be found in Marther (1987) Vegetation mapping of Eastern River, Northern Territory. |
| Comments: |
The contents of this attribute should synthesise and summarise the values of other attributes from the DataSet, Mapping Methods and Map Source tables. Where there were more than one mapping method used in the dataset, the reliability of each method should be described in MAPPING_EXPERTISE. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS20 - START DATE_ATTRIBUTE |
| Heading |
Details |
| Purpose: |
To document the date of the earliest field collection of vegetation-related attributes used in the survey underpinning the maps. |
| Requirement: |
Mandatory |
| Database Field Name: |
START DATE_ATTRIBUTE |
| Description: |
Day, Month, Year of earliest attributes used in the survey. |
| Value: |
Date. This is a year 2000 consistent date and time value set as dd/mm/yyyy. |
| Example: |
09/04/1978 |
| Comments: |
This field is later attached to the NVIS GIS coverage and is fundamental to assessing the currency of the attribute data in each polygon. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS21 - END DATE ATTRIBUTE |
| Heading |
Details |
| Purpose: |
To document the date of the latest field collection of vegetation-related attributes used in the survey underpinning the maps. |
| Requirement: |
Mandatory |
| Database Field Name: |
END_DATE_ATTRIBUTE |
| Description: |
Day, Month, Year of latest attributes used in the survey. |
| Value: |
Date. This is a year 2000 consistent date and time value set as hh:mm:ss dd/mm/yyyy with hours set in 24hr time. |
| Example: |
06/06/1996 |
| Comments: |
This field is later attached to the NVIS GIS coverage and is fundamental to assessing the currency of the attribute data in each polygon. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS22 - START DATE_SPATIAL |
| Heading |
Details |
| Purpose: |
To document the date of the earliest image used in the mapping. |
| Requirement: |
Mandatory |
| Database Field Name: |
START_DATE_SPATIAL (was: START_DATE) |
| Description: |
Day, Month, Year of earliest image used in the mapping. The value for a dataset would normally come from earliest START_DATE_SOURCE in the Map_Source table. |
| Value: |
Date. This is a year 2000 consistent date and time value set as dd/mm/yyyy. |
| Example: |
09/04/1978 |
| Comments: |
Any automated procedure used to generate the value of this field for a dataset should be checked by an expert to ensure that it correctly summarises the whole dataset. The contents of this attribute carry through to the spatial coverage and are fundamental to assessing the currency of the spatial data. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: DS23 - END DATE SPATIAL |
| Heading |
Details |
| Purpose: |
To document the date of the most recent image used in the mapping. |
| Requirement: |
Mandatory |
| Database Field Name: |
END_DATE_SPATIAL (was: END_DATE) |
| Description: |
Day, Month, Year of latest image used in the mapping. |
| Value: |
Date. This is a year 2000 consistent date and time value set as hh:mm:ss dd/mm/yyyy. The value would normally come from latest END_DATE_SOURCE in the Map_Source table. |
| Example: |
06/06/1996 |
| Comments: |
Any automated procedure used to generate the value of this field for a dataset should be checked by an expert to ensure that it correctly summarises the whole dataset. The contents of this attribute carry thru to the spatial coverage and are fundamental to assessing the currency of the spatial data. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: MS01 - MAPPING SOURCE NUMBER |
| Heading |
Details |
| Purpose: |
To identify each unique combination of map source and mapping method used in each dataset. |
| Requirement: |
Optional |
| Database Field Name: |
MAPPING_SOURCE_NUMBER |
| Description: |
A number assigned to each defined map origin details used in the construction of a dataset. The number is assigned sequentially, beginning with 1, within each dataset. Typical numbers are 1, 2 or 3. |
| Value: |
Number(10) |
| Example: |
2 |
| Comments: |
New field made necessary by the joining of unique combinations of the former MAPPING_METHOD and MAP_SOURCE tables. |
| Status: |
New field; not yet implemented in the NVIS Oracle database. Will need to reconcile data in the version 5.0 MAP_SOURCE and MAPPING_METHODS tables. |
| Attribute: MS02 - MAPPING METHOD |
| Heading |
Details |
| Purpose: |
To describe the interpretive tools used for delineating the map units within the data set. |
| Requirement: |
QAQC |
| Database Field Name: |
MAPPING_METHOD |
| Description: |
Detailed description of mapping methods. A data set must have one or more entries for this attribute. In particular, the attribute provides further background for the assessment of POSITIONAL_ACCURACY and SAMPLING_TYPE. |
| Value: |
Character(2000); multiple entries allowed. |
| Example: |
Aerial photo interpretation; manual satellite image interpretation; combination of quantitative modelling and aerial photo interpretation |
| Comments: |
The current list of attributes used to describe the MAPPING METHOD is primarily based on the use of some form of imagery. Where other methods have been used such as modelled surfaces, a full description should be provided. Additional attributes to describe other mapping methods may be subsequently defined. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: MS03 - MAPPING EXPERTISE |
| Heading |
Details |
| Purpose: |
To describe the overall level of skill and expertise of the map interpreters during the project or survey for a particular MAPPING METHOD. |
| Requirement: |
Recommended |
| Database Field Name: |
MAPPING_EXPERTISE |
| Description: |
Custodians should specify the expertise in mapping or botanical survey or a combination of both used in the compilation of the dataset. |
| Value: |
Character(2000) |
| Example: |
High confidence in the skill and expertise of the interpreter(s) |
| Comments: |
This field should be completed by the project leader or from information documented about the project. It is a summary of the quality of both spatial and attribute aspects of the application of the particular MAPPING_METHOD. Where there is only one mapping method for the dataset, this attribute can be used for further details of the method, with the attribute SURVEY_AND_MAP_RELIABILITY used to describe the overall quality assessment for the dataset. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: MS04 - IMAGERY SOURCE |
| Heading |
Details |
| Purpose: |
To briefly describe the type of image used to derive/classify the mapping units. |
| Requirement: |
QAQC |
| Database Field Name: |
IMAGERY_SOURCE (was: INTERPRETIVE_BASE) |
| Description: |
These descriptions are commonly used terms. A MAPPING METHOD must have one or more entries for this attribute. Each type of image must have a separate entry. |
| Value: |
Character(2000) |
| Example: |
For a dataset mapped using API using 2 image types would have 2 records in the MAP_SOURCE table, viz::
1. true colour photography' and 2. 'black and white photography'. |
| Comments: |
|
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: IMAGERY SOURCE
| Code |
Explanation |
| black and white aerial photography |
black and white aerial photography |
| colour aerial photography |
Colour aerial photography |
| colour infrared aerial photography |
Colour infrared aerial photography |
| satellite imagery: LANDSAT TM |
Satellite imagery: LANDSAT Thematic Mapper |
| satellite imagery: LANDSAT MSS |
satellite imagery: LANDSAT Multi-Spectral Scanner |
| satellite imagery: non-LANDSAT |
satellite imagery: neither LANDSAT MSS nor TM. Please specify details in MAPPING_METHOD field. |
| maps |
existing and/or historic maps |
| unknown |
unknown |
| Attribute: MS05 - IMAGERY SCALE |
| Heading |
Details |
| Purpose: |
To document the scale of each IMAGERY_SOURCE. |
| Requirement: |
QAQC |
| Database Field Name: |
IMAGERY_SCALE (was: SCALE_OR_RESOLUTION) |
| Description: |
The denominator of the scale of each image listed in IMAGERY_SOURCE. |
| Value: |
Number(10) |
| Example: |
25000 |
| Comments: |
Scale is usually applied to aerial photography. |
| Status: |
Implemented in the NVIS Oracle database; need to implement field changes. |
| Attribute: MS06 - IMAGERY RESOLUTION |
| Heading |
Details |
| Purpose: |
To document the resolution of each IMAGERY_SOURCE. |
| Requirement: |
Recommended |
| Database Field Name: |
IMAGERY_RESOLUTION (was: SCALE_OR_RESOLUTION) |
| Description: |
The resolution (cell or pixel size) of each image listed in IMAGERY_SOURCE. |
| Value: |
Number(10) |
| Example: |
25 |
| Comments: |
The units are in metres. Resolution is usually applied to airborne or satellite scanned imagery. |
| Status: |
Implemented in the NVIS Oracle database; need to implement field changes. |
| Attribute: MS07 - MAPPING SOURCE EXTENT |
| Heading |
Details |
| Purpose: |
To describe the extent of the map source and/or mapping method within the dataset. |
| Requirement: |
Optional |
| Database Field Name: |
MAPPING_SOURCE_EXTENT |
| Description: |
A description of the area of coverage of the map source and/or mapping method within the dataset. |
| Value: |
Character(4000) |
| Example: |
The interpretation of colour aerial photos was confined to public land in the coastal portion of the dataset. |
| Comments: |
There are many cases where a mapping method and/or map source covers only part of the area of a dataset. This is a simple text field to describe such subsets of the dataset. In future, there may be a case for x,y strings to more-precisely define the internal (methodological and source) boundaries within a dataset. |
| Status: |
New field. Yet to be implemented in the NVIS Oracle database. |
| Attribute: MS08 - DELINEATION MEDIUM |
| Heading |
Details |
| Purpose: |
To describe the medium on which the map units were delineated. |
| Requirement: |
Recommended |
| Database Field Name: |
DELINEATION_MEDIUM (was: MEDIUM) |
| Description: |
A description of the medium on which the image was captured, processed and interpreted or, if a combination of these, the medium on which map unit boundaries were delineated. |
| Value: |
Character(2000) |
| Example: |
Options might include: hardcopy paper; hardcopy mylar film; digital |
| Comments: |
The use of particular mapping media may have implications for POSITIONAL _ACCURACY. |
| Status: |
Implemented in the NVIS Oracle database. |
Look-up Table for: DELINEATION MEDIUM
| Code |
Explanation |
| digital |
digital |
| hardcopy mylar film |
hardcopy mylar film |
| hardcopy paper |
hardcopy paper |
| hardcopy photographs |
hardcopy photographs |
| unknown |
unknown |
| Attribute: MS09 - START_DATE_SOURCE |
| Heading |
Details |
| Purpose: |
To document the date of the earliest image source used in the particular mapping. |
| Requirement: |
Recommended |
| Database Field Name: |
START DATE_SOURCE (was: START_DATE) |
| Description: |
Day, Month, Year of earliest image used in the particular mapping method. |
| Value: |
Date. This is a year 2000 consistent date and time value set as dd/mm/yyyy. |
| Example: |
09/04/1978 |
| Comments: |
The earliest mapping source across all mapping methods for a dataset would normally be used in the attribute START_DATE_SPATIAL to summarise the whole dataset. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: MS10 - END DATE SOURCE |
| Heading |
Details |
| Purpose: |
To document the date of the most recent (i.e. the latest) image used in the mapping. |
| Requirement: |
Recommended |
| Database Field Name: |
END_DATE_SOURCE (was: END_DATE) |
| Description: |
Day, Month, Year of latest image used in the mapping. |
| Value: |
Date. This is a year 2000 consistent date and time value set as hh:mm:ss dd/mm/yyyy with hours set in 24hr time. |
| Example: |
06/06/1996 |
| Comments: |
The latest mapping source across all mapping methods for a dataset would normally be used in the attribute END_DATE_SPATIAL to summarise the whole dataset. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: MS11 - MAP BASE |
| Heading |
Details |
| Purpose: |
To describe the source of the map base used for registering the final line-work in the data set. |
| Requirement: |
Recommended |
| Database Field Name: |
MAP_BASE |
| Description: |
An attribute describing the final map base used to collate the line work and provide ground control. This field is at a "higher" level than DELINEATION_MEDIUM and is normally later in the mapping process. Multiple sources can be listed. |
| Value: |
Character(2000); Semi-colon delimited |
| Example: |
AUSLIG (1990) 1:100,000 series; GPS Ground Control Points |
| Comments: |
Information should include the owner/custodian of the source, the year the information was collected, the scale or resolution of the mapping base, data set title or description in this order. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: RF01 - CITATION |
| Heading |
Details |
| Purpose: |
To cite the reference. |
| Requirement: |
QAQC |
| Database Field Name: |
CITATION |
| Description: |
A full reference to a publication, including reports, technical manuals, journal articles that describe the data set and/or the methods used in its compilation. |
| Value: |
Character(2000); The entry must include all authors names, date, title, publication name and publisher. |
| Example: |
1. AUSLIG. 1990, Vegetation - Atlas of Australian Resources, Third Series, vol. 6, Australian Surveying and Land Information Group, Canberra.
2. Barlow, B.A. & Hyland, B.P.M. 1988, 'The Origin of the Flora of Australia's Wet Tropics', Proc.Ecol.Soc.Aust, vol. 15, pp. 1-17. |
| Comments: |
A very useful attribute when consistently and comprehensively filled out. |
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: RF02 - FORMAT |
| Heading |
Details |
| Purpose: |
To describe the format(s) in which the reference is available. |
| Requirement: |
Optional |
| Database Field Name: |
FORMAT |
| Description: |
|
| Value: |
Character(2000); Semi-colon delimited |
| Example: |
Hardcopy and digital; Hardcopy; Digital; URL |
| Comments: |
|
| Status: |
Implemented in the NVIS Oracle database. |
| Attribute: RF03 - STORAGE LOCATION |
| Heading |
Details |
| Purpose: |
To specify where the reference can be found. |
| Requirement: |
Optional |
| Database Field Name: |
STORAGE_LOCATION |
| Description: |
The storage location(s) indicating where the reference can be found, including its URL where available. |
| Value: |
Character(2000); Semi-colon delimited |
| Example: |
1. Queensland Herbarium Library
2. National Library
3. http://www.environment.gov.au/states/cyp_on_l/reports/lup/cons_con.html |
| Comments: |
|
| Status: |
Implemented in the NVIS Oracle database. |
]
