abis-mapping v9.0.1 survey_occurrence_data v3.0.0
SYSTEMATIC SURVEY OCCURRENCES DATA TEMPLATE INSTRUCTIONS
Intended Usage
This Systematic Survey Occurrences Data template is used to record occurrence data; that is, the presence or absence of an organism at a particular site locality at a point in time.
This Systematic Survey Occurrences Data template must be used in combination with the Systematic Survey Metadata template, or with the Systematic Survey Metadata and the Systematic Survey Sites Data template, or with the Systematic Survey Metadata, the Systematic Survey Site Data and the Systematic Survey Site Visit Data template.
Templates have been provided to facilitate integration of your data into the Biodiversity Data Repository database. Not all types of data have been catered for in the available templates at this stage; therefore, if you are unable to find a suitable template, please contact bdr-support@dcceew.gov.au to make us aware of your data needs.
Data Validation Requirements:
For data validation, you will need your data file to:
- be in the correct file format,
- have fields that match the template downloaded (do not remove, or change the order of fields),
- have extant values for mandatory fields (see Table 1),
- comply with all data value constraints; for example the geographic coordinates are consistent with a geodeticDatum type of the 5 available options, and
- align with existing controlled vocabularies wherever possible (this is mandatory for geodeticDatum), but new terms may be submitted for consideration amd will not cause a validation error.
Additional fields may be added after the templated fields (noting that the data type is not assumed and values will be encoded as strings).
FILE FORMAT
- The systematic survey occurrence data template is a UTF-8 encoded csv (that is, not Microsoft
Excel Spreadsheets). Be sure to save this file with your data as a .csv (UTF-8):
[MS Excel: Save As > More options > Tools > Web options > Save this document as > Unicode (UTF-8)]
otherwise it will not pass the csv validation step upon upload. - Do not include empty rows.
FILE NAME
When making a manual submission to the Biodiversity Data Repository,
the file name must include the version number
of this biodiversity data template (v3.0.0).
The following format is an example of a valid file name:
data_descripion-v3.0.0-additional_description.csv
where:
data_description: A short description of the data (e.g.survey_occ,test_data).v3.0.0: The version number of this template.additional_description: (Optional) Additional description of the data, if needed (e.g.test_data)..csv: Ensure the file name ends with.csv.
For example, survey_occ-v3.0.0-test_data.csv or test_data-v3.0.0.csv
FILE SIZE
MS Excel imposes a limit of 1,048,576 rows on a spreadsheet, limiting a CSV file to the header row followed by 1,048,575 occurrences. Furthermore, MS Excel has a 32,767-character limit on individual cells in a spreadsheet. These limits may be overcome by using or editing CSV files with other software.
Larger datasets may be more readily ingested using the API interface. Please contact bdr-support@dcceew.gov.au to make us aware of your data needs.
TEMPLATE FIELDS
The template contains the field names in the top row. Table 1 will assist you in transferring your data to the template by providing guidance on:
- Field name in the template (and an external link to the Darwin Core standard for that field where relevant);
- Description of the field;
- Required i.e. whether the field is mandatory, conditionally mandatory, or optional;
- Format (datatype) required for the data values for example text (string), number (integer, float), or date;
- Example of an entry or entries for that field; and
- Vocabulary links within this document (for example pick list values) where relevant. The fields that have suggested values options for the fields in Table 1 are listed in Table 2 in alphabetical order of the field name.
ADDITIONAL FIELDS
Data that does not match the existing template fields may be added as
additional columns in the CSV files after the templated fields.
For example: eventRemarks, associatedTaxa, pathway.
Table 1: Systematic Survey Occurrence data template fields with descriptions, conditions, datatype format, and examples.
| Field # | Name | Description | Mandatory / Optional | Datatype Format | Examples |
|---|---|---|---|---|---|
| 1 | providerRecordID | Unique (within provider) identifier for the record. | Mandatory | String | 8022FSJMJ079c5cf |
| 2 | providerRecordIDSource | Person or Organisation that generated the providerRecordID. | Mandatory | String | Western Australian Biodiversity Information Office |
| 3 | locality | The specific description of the place. | Optional | String | Cowaramup Bay Road |
| 4 | decimalLatitude | The geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic centre of a Location. Positive values are north of the Equator, negative values are south of it. Valid coordinate ranges for the BDR system are within and inclusive of -90 to 0. | Mandatory if spatial information not provided by either, a validated linked siteID and siteIDSource, or existingBDRSiteIRI. | Number | -33.812314 |
| 5 | decimalLongitude | The geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic centre of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Valid coordinate ranges for the BDR system are within and inclusive of 0 to 180. | Mandatory if spatial information not provided by either, a validated linked siteID and siteIDSource, or existingBDRSiteIRI. | Number | 115.231512 |
| 6 | geodeticDatum | The acronym for the ellipsoid, geodetic datum, or spatial reference system (SRS) upon which the geographic (non-projected) coordinates given in decimalLatitude and decimalLongitude as based. | Mandatory if spatial information not provided by either, a validated linked siteID and siteIDSource, or existingBDRSiteIRI. | String | WGS84 (Vocabulary link) |
| 7 | coordinateUncertaintyInMeters | The horizontal distance (in metres) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term. | Optional | Number | 50.0 |
| 8 | dataGeneralizations | Actions taken to make the shared data less specific or complete than in its original form, due to restrictions around identifying locations of particular species. Suggests that alternative data of higher quality may be available on request. | Optional | String | Coordinates rounded to the nearest 10 km for conservation concern |
| 9 | eventDateStart | The start date (with precision of year (YYYY), month year (YYYY-MM) or date in the following formats DD/MM/YYYY or YYYY-MM-DD are accepted) or date-time without timezone (in ISO 8601 format for example 2021-07-11T06:23:00) or date-time with timezone (in ISO 8601 format for example 2022-05-20T06:23:00+08:00) of the period during which a species occurrence was observed. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. | Mandatory if temporal information not provided by a validated linked siteVisitID. | Timestamp | 2019-09-23T14:03+08:00 |
| 10 | eventDateEnd | The end date (with precision of year (YYYY), month year (YYYY-MM) or date in the following formats DD/MM/YYYY or YYYY-MM-DD are accepted) or date-time without timezone (in ISO 8601 format for example 2021-07-11T06:23:00) or date-time with timezone (in ISO 8601 format for example 2022-05-20T06:23:00+08:00) of the period during which a species occurrence was observed. For occurrences, this is the date-time when the event was recorded. Not suitable for a time in a geological context. | Optional | Timestamp | 2019-09-24 |
| 11 | samplingProtocol | The sampling protocol is the method used to sample the locality to determine the presence (or absence) of the taxon referred to in this record at the indicated time. This may be a collecting method or a method to observe an organism without collection. Recommended best practice is to describe a species occurrence with no more than one sampling protocol. In the case of a summary, in which a specific protocol can not be attributed to specific species occurrences, the recommended best practice is to repeat the property for each IRI that denotes a different sampling protocol that applies to the occurrence. |
Optional | String | Human Observation (Vocabulary link) |
| 12 | basisOfRecord | The specific nature of the data record. | Optional | String | Preserved Specimen (Vocabulary link) |
| 13 | recordedBy | A person, group, or organisation responsible for recording the original Occurrence. | Optional | String | Stream Environment and Water Pty Ltd |
| 14 | recordNumber | An identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number. | Optional | String | PE:12:8832 |
| 15 | occurrenceStatus | A statement about the presence or absence of a Taxon at a Location. | Optional | String | Present (Vocabulary link) |
| 16 | habitat | A category or description of the habitat in which the event occurred. | Optional | String | Closed forest of Melaleuca lanceolata. White, grey or brown sand, sandy loam. (Vocabulary link) |
| 17 | establishmentMeans | Statement about whether an organism or organisms have been introduced to a given place and time through the direct or indirect activity of modern humans. | Optional | String | Native (Vocabulary link) |
| 18 | organismRemarks | Comments or notes about the Organism instance. | Optional | String | Dried out leaf tips. |
| 19 | individualCount | The number of individuals present at the time of the Occurrence. 0 = none, no value = the specific number was not recorded. | Optional | Integer | 26 |
| 20 | organismQuantity | A number or enumeration value for the quantity of organisms. | Mandatory if organismQuantityType is provided. | Number | 12.5 |
| 21 | organismQuantityType | The type of quantification system used for the quantity organisms. | Mandatory if organismQuantity is provided. | String | % biomass (Vocabulary link) |
| 22 | lifeStage | The age class or life stage of the Organism(s) at the time the Occurrence was recorded. | Optional | String | adult (Vocabulary link) |
| 23 | sex | The sex of the biological individual(s) represented in the Occurrence. | Optional | String | Unspecified (Vocabulary link) |
| 24 | reproductiveCondition | The reproductive condition of the biological individual(s) represented in the Occurrence. | Optional | String | No breeding evident |
| 25 | ownerRecordID | Identifier given to the occurrence by the owner of the data. Populate this field if the data owner is different to the data provider. Unique (within data owner) identifier for the record. | Mandatory if ownerRecordIDSource is provided. | String | 12345NT521mc5h |
| 26 | ownerRecordIDSource | Person or Organisation that generated the ownerRecordID. For organisations registered with the BDR, this field should contain the BDR registrationID. For all others, please provide the name of Person or Organisation who owns the data. | Mandatory if ownerRecordID is provided. | String | WAM |
| 27 | collectionCode | The name, acronym, code, or initialism identifying the collection or data set from which the record was derived. It is associated with the catalogNumber. | Optional | String | ARACH |
| 28 | catalogNumber | An identifier (preferably unique) for the record within the data set or collection. | Mandatory if catalogNumberSource is provided. | String | 145732, 145732a, 2008.1334, R-4313 |
| 29 | catalogNumberSource | Organisation that generated the catalogNumber. In the BDR context, this is likely to be a collecting institution where a specimen or material sample is located. For organisations registered with the BDR, this field should contain the BDR registrationID. For all others, please provide the name of Person or Organisation. | Mandatory if catalogNumber is provided. | String | Western Australian Museum |
| 30 | otherCatalogNumbers | A list (concatenated and separated with a space vertical bar space ( | )) of previous or alternate fully qualified catalog numbers or other human-used identifiers for the same Occurrence, whether in the current or any other data set or collection. | Mandatory if otherCatalogNumbersSource is provided. | List | BHP2012-7521 | M12378 |
| 31 | otherCatalogNumbersSource | Organisation that generated the otherCatalogNumbers. For organisations registered with the BDR, this field should contain the BDR registrationID. For all others, please provide the name of Person or Organisation. | Mandatory if otherCatalogNumbers is provided. | String | University of Western Australia |
| 32 | preparations | A list (concatenated and separated with a space vertical bar space ( | )) of preparations and preservation methods for a specimen. | Optional | String | alcohol (Vocabulary link) |
| 33 | preparedDate | The date (with precision of year (YYYY), month year (YYYY-MM) or date in the following formats DD/MM/YYYY or YYYY-MM-DD are accepted) or date-time without timezone (in ISO 8601 format for example 2021-07-11T11:23:00) or date-time with timezone(in ISO 8601 format for example 2022-05-20T06:23:00+08:00) representing the date or date-time the specimen was prepared. | Optional | Timestamp | 2019-09-24 |
| 34 | associatedSequences | A list (concatenated and separated with a space vertical bar space ( | )) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the Occurrence. | Optional | List | https://www.ncbi.nlm.nih.gov/nuccore/MH040669.1 | https://www.ncbi.nlm.nih.gov/nuccore/MH040616.1 |
| 35 | sequencingMethod | The method used to obtain sequence data for example DNA, RNA, or protein from the sample. | Optional | String | Sanger-dideoxy-sequencing (Vocabulary link) |
| 36 | verbatimIdentification | A string representing the taxonomic identification as it appeared in the original record. This term is meant to allow the capture of an unaltered original identification/determination, including identification qualifiers, hybrid formulas, uncertainties, etc. This term is meant to be used in addition to scientificName (and identificationQualifier etc.), not instead of it. | Optional | String | Caladenia ?excelsa |
| 37 | dateIdentified | The date (with precision of year (YYYY), month year (YYYY-MM) or date in the following formats DD/MM/YYYY or YYYY-MM-DD are accepted) or date-time without timezone (in ISO 8601 format for example 2021-07-11T11:23:00) or date-time with timezone(in ISO 8601 format for example 2022-05-20T06:23:00+08:00) on which the subject was determined as representing the Taxon. | Optional | Timestamp | 2019-09-24 |
| 38 | identifiedBy | Group of names, organisations who assigned the Taxon to the subject. For multiple names, use the pipe separator ( | ). | Optional | String | J. Doe | WAM |
| 39 | identificationMethod | Method used to associate the organism with the scientificName label. | Optional | String | DNA (Vocabulary link) |
| 40 | scientificName | The full scientific name, with authorship and date information if known. When forming part of an Identification, this should be the name in lowest level taxonomic rank that can be determined. This term should not contain identification qualifications, which should instead be supplied in the identificationQualifier column. NOTE: Phrase names such as Rhagodia sp. Hamersley (M.Trudgen 17794) are permitted in the scientificName field where those are in use. |
Mandatory | String | Caladenia excelsa |
| 41 | identificationQualifier | A brief phrase or a standard term ("cf.", "aff.") to express the determiner's doubts about the Identification. | Optional | String | Species incerta (Vocabulary link) |
| 42 | identificationRemarks | Comments or notes about the Identification. | Optional | String | DNA evidence may indicate a new species. Further analysis required. |
| 43 | acceptedNameUsage | The full name, with authorship and date information if known, of the currently valid (zoological) or accepted (botanical) taxon. | Optional | String | Occiperipatoides gilesii (Spencer, 1909) |
| 44 | kingdom | The full scientific name of the kingdom in which the taxon is classified. | Mandatory | String | Plantae (Vocabulary link) |
| 45 | taxonRank | The taxonomic rank of the most specific name in the scientificName. | Optional | String | Species (Vocabulary link) |
| 46 | threatStatus | The conservation status (or code) assigned to an organism that is recognised in conjunction with a specific authority. | Mandatory if conservationAuthority is provided. | String | EN (Vocabulary link) |
| 47 | conservationAuthority | The authority under which an organism is recognised to have a specific conservation status applied. | Mandatory if threatStatus is provided. | String | EPBC, WA (Vocabulary link) |
| 48 | threatStatusCheckProtocol | The method used to determine if the organism is listed under the relevant jurisdictional threatened species list. | Optional | String | Species name check of the Department of Climate Change, Energy, the Environment and Water’s Species Profile and Threat Database http://www.environment.gov.au/cgi-bin/sprat/public/sprat.pl (Vocabulary link) |
| 49 | threatStatusDateDetermined | The date (with precision of year (YYYY), month year (YYYY-MM) or date in the following formats DD/MM/YYYY or YYYY-MM-DD are accepted) or date-time without timezone (in ISO 8601 format for example 2021-07-11T11:23:00) or date-time with timezone(in ISO 8601 format for example 2022-05-20T06:23:00+08:00) on which this record of this organism was assigned to the nominated threatStatus and conservationAuthority | Optional | Timestamp | 30/08/2022 |
| 50 | threatStatusDeterminedBy | The person and/organisation responsible for appending the threatStatus and conservationAuthority to this organism’s occurrence record. | Optional | String | WA-BIO |
| 51 | sensitivityCategory | A category that defines a type of data sensitivity or restriction. | Mandatory if sensitivityAuthority is provided. | String | Category 2 (Vocabulary link) |
| 52 | sensitivityAuthority | The authority under which a data sensitivity or restriction has been applied. | Mandatory if sensitivityCategory is provided. | String | Department of Environment, Climate Change and Water NSW (Vocabulary link) |
| 53 | surveyID | The identifier of the Survey that the Occurrence comes from. If this field is left blank, the Occurrence will be treated as incidental. | Optional | String | AR220-01 |
| 54 | siteID | Corresponds to a unique site identifier, provided within accompanying survey_site_data.csv template. | Mandatory if siteVisitID is provided and existingBDRSiteIRI is not provided. Mandatory if siteIDSource is provided. |
String | P1 |
| 55 | siteIDSource | The organisation that assigned the SiteID to this Site | Mandatory if siteVisitID is provided and existingBDRSiteIRI is not provided. Mandatory if siteID is provided. |
String | TERN |
| 56 | existingBDRSiteIRI | Corresponds to a unique Site IRI that is registered in the BDR. Using this field overrides entries in the siteID and siteIDSource fields and utilises the properties that are associated with the registered Site. | Mandatory if siteVisitID is provided and siteID and siteIDSource are not provided. | String | https://linked.data.gov.au/dataset/bdr/sites/TERN/P1 |
| 57 | siteVisitID | The identifier of the site visit that the occurrence comes from. This field should be completed if actions taken during a site visit resulted in this occurrence record. | Optional | String | CPXEI0000001 |
CHANGELOG
Changes from Systematic Survey Occurrence Data Template v2.0.0
CHANGED FIELDS
- Add field
siteIDSource. - Add field
existingBDRSiteIRI.
CHANGED VALIDATION
- When
surveyIDis provided, it must have a value that matches asurveyIDin the Systematic Survey Metadata template to indicate which Survey the Occurrence belongs to. WhensurveyIDis blank, the Occurrence will be treated as incidental. siteIDand the new fieldsiteIDSourceare conditionally mandatory. Must be provided together, or neither provided.- When
siteVisitIDis provided, eithersiteIDandsiteIDSource, orexistingBDRSiteIRI, or both, must be provided.
APPENDICES
APPENDIX-I: Vocabulary List
With the exception of geodeticDatum, data validation does not require fields to adhere to the
vocabularies specified for the various vocabularied fields. These vocabularies are merely provided as a
means of assistance in developing a consistent language within the database. New terms may be added
to more appropriately describe your data that goes beyond the current list. Table 2 provides some
suggested values from existing sources such as: Biodiversity Information Standard (TDWG),
EPSG.io Coordinate systems worldwide, the Global Biodiversity Information
System, and Open Nomenclature in the biodiversity
era.
Table 2: Suggested values for the controlled vocabulary fields in the template. Each term has
a preferred label with a definition to aid understanding of its meaning. For some terms, alternative
labels with similar semantics are provided. Note: geodeticDatum value
must come from one of five options in this table.
Table 2b: Suggested values for conditionally mandatory values for the threatStatus and
conservationAuthority fields in the template. State and Territory conservationAuthority
spelt out as words are also valid. For some threatStatus terms, alternative labels are provided
that are also valid for that conservationAuthority.
| conservationAuthority | threatStatus | threatStatus alternative labels |
|---|---|---|
| ACT | CRITICALLY ENDANGERED | |
| ACT | ENDANGERED | |
| ACT | EXTINCT | |
| ACT | EXTINCT IN THE WILD | |
| ACT | REGIONALLY CONSERVATION DEPENDENT | |
| ACT | VULNERABLE | |
| EPBC | CAMBA | |
| EPBC | CD | CONSERVATION DEPENDENT |
| EPBC | CE | CR, CRITICALLY ENDANGERED |
| EPBC | CITES | |
| EPBC | E | EN, ENDANGERED |
| EPBC | EX | EXTINCT |
| EPBC | JAMBA | |
| EPBC | KAMBA | |
| EPBC | V | VU, VULNERABLE |
| EPBC | XW | EW, EXTINCT IN THE WILD |
| NSW | CE | CRITICALLY ENDANGERED |
| NSW | EN | ENDANGERED |
| NSW | EX | EXTINCT |
| NSW | V | VULNERABLE |
| NT | CE | CRITICALLY ENDANGERED |
| NT | DD | DATA DEFICIENT |
| NT | EN | ENDANGERED |
| NT | EN EXTINCT IN NT | ENDANGERED EXTINCT IN NT |
| NT | EN EXTINCT IN WILD IN NT | ENDANGERED EXTINCT IN WILD IN NT |
| NT | EW | CRITICALLY ENDANGERED POSSIBLY EXTINCT |
| NT | EX | EXTINCT |
| NT | LC | LEAST CONCERN |
| NT | LC EXTINCT IN NT | LEAST CONCERN EXTINCT IN NT |
| NT | NE | NOT EVALUATED |
| NT | NT | NEAR THREATENED |
| NT | VU | VULNERABLE |
| NT | VU EXTINCT IN NT | VULNERABLE EXTINCT IN NT |
| QLD | C | LEAST CONCERN WILDLIFE |
| QLD | CR | CRITICALLY ENDANGERED |
| QLD | E | ENDANGERED WILDLIFE |
| QLD | EX | EXTINCT |
| QLD | I | INTERNATIONAL WILDLIFE |
| QLD | NT | NEAR THREATENED WILDLIFE |
| QLD | PE | EXTINCT IN THE WILD |
| QLD | SL | SPECIAL LEAST CONCERN |
| QLD | V | VULNERABLE WILDLIFE |
| SA | E | ENDANGERED |
| SA | R | RARE |
| SA | SP | INDICATES THAT A RATING HAS BEEN APPLIED TO THE SPECIES LEVEL THE STATUS HAS NOT BEEN ASSESSED AT THE SUBSPECIES LEVEL |
| SA | SSP | INDICATES THAT AT LEAST ONE SUBSPECIES FOR THIS SPECIES HAS BEEN GIVEN A CONSERVATION RATING |
| SA | V | VULNERABLE |
| TAS | E | ENDANGERED |
| TAS | R | RARE |
| TAS | V | VULNERABLE |
| TAS | X | EXTINCT |
| VIC | CONSERVATION DEPENDENT | |
| VIC | CRITICALLY ENDANGERED | |
| VIC | ENDANGERED | |
| VIC | ENDANGERED EXTINCT IN VICTORIA | |
| VIC | EXTINCT | |
| VIC | EXTINCT IN THE WILD | |
| VIC | RESTRICTED | |
| VIC | VULNERABLE | |
| WA | CD | CONSERVATION DEPENDENT, SPECIES OF SPECIAL CONSERVATION INTEREST CONSERVATION DEPENDENT FAUNA |
| WA | CR | CRITICALLY ENDANGERED, CRITICALLY ENDANGERED SPECIES |
| WA | EN | ENDANGERED, ENDANGERED SPECIES |
| WA | EW | EXTINCT IN THE WILD |
| WA | EX | EXTINCT, EXTINCT SPECIES |
| WA | MI | MIGRATORY, MIGRATORY SPECIES |
| WA | OS | OTHER SPECIFICALLY PROTECTED FAUNA |
| WA | P1 | PRIORITY 1 POORLY KNOWN, PRIORITY 1 POORLY KNOWN SPECIES |
| WA | P2 | PRIORITY 2 POORLY KNOWN, PRIORITY 2 POORLY KNOWN SPECIES |
| WA | P3 | PRIORITY 3 POORLY KNOWN, PRIORITY 3 POORLY KNOWN SPECIES |
| WA | P4 | PRIORITY 4 RARE NEAR THREATENED AND OTHER SPECIES IN NEED OF MONITORING |
| WA | SPECIALLY PROTECTED | SPECIALLY PROTECTED SPECIES |
| WA | T | THREATENED, THREATENED SPECIES |
| WA | VU | VULNERABLE, VULNERABLE SPECIES |
APPENDIX-II: Timestamp
Following date and date-time formats are acceptable within the timestamp:
| TYPE | FORMAT |
|---|---|
| xsd:dateTimeStamp with timezone | yyyy-mm-ddThh:mm:ss.sTZD (eg 1997-07-16T19:20:30.45+01:00) OR yyyy-mm-ddThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00) OR yyyy-mm-ddThh:mmTZD (eg 1997-07-16T19:20+01:00) |
| xsd:dateTime | yyyy-mm-ddThh:mm:ss.s (eg 1997-07-16T19:20:30.45) OR yyyy-mm-ddThh:mm:ss (eg 1997-07-16T19:20:30) OR yyyy-mm-ddThh:mm (eg 1997-07-16T19:20) |
| xsd:Date | dd/mm/yyyy OR d/m/yyyy OR yyyy-mm-dd OR yyyy-m-d |
| xsd:gYearMonth | mm/yyyy OR m/yyyy OR yyyy-mm |
| xsd:gYear | yyyy |
Where
yyyy: four-digit year
mm: two-digit month (01=January, etc.)
dd: two-digit day of month (01 through 31)
hh: two digits of hour (00 through 23) (am/pm NOT allowed)
mm: two digits of minute (00 through 59)
ss: two digits of second (00 through 59)
s: one or more digits representing a decimal fraction of a second
TZD: time zone designator (Z or +hh:mm or -hh:mm)
APPENDIX-III: UTF-8
UTF-8 encoding is considered a best practice for handling character encoding, especially in
the context of web development, data exchange, and modern software systems. UTF-8
(Unicode Transformation Format, 8-bit) is a variable-width character encoding capable of
encoding all possible characters (code points) in Unicode.
Here are some reasons why UTF-8 is recommended:
- Universal Character Support: UTF-8 can represent almost all characters from all writing systems in use today. This includes characters from various languages, mathematical symbols, and other special characters.
- Backward Compatibility: UTF-8 is backward compatible with ASCII (American Standard Code for Information Interchange). The first 128 characters in UTF-8 are identical to ASCII, making it easy to work with systems that use ASCII.
- Efficiency: UTF-8 is space-efficient for Latin-script characters (common in English and many other languages). It uses one byte for ASCII characters and up to four bytes for other characters. This variable-length encoding minimises storage and bandwidth requirements.
- Web Standards: UTF-8 is the dominant character encoding for web content. It is widely supported by browsers, servers, and web-related technologies.
- Globalisation: As software applications become more globalised, supporting a wide range of languages and scripts becomes crucial. UTF-8 is well-suited for internationalisation and multilingual support.
- Compatibility with Modern Systems: UTF-8 is the default encoding for many programming languages, databases, and operating systems. Choosing UTF-8 helps ensure compatibility across different platforms and technologies.
When working with text data, UTF-8 encoding is recommended to avoid issues related to character representation and ensure that a diverse set of characters and languages is supported.
For assistance, please contact: bdr-support@dcceew.gov.au