Attribute Information for Species Ranges

For the distribution maps, there are a list of spatial data attributes which must be

recorded for both polygon and point data. These attributes help describe the taxon’s

distribution. The tables below list the standard attributes for spatial data; the codes

used to indicate presence, origin and seasonality and how these codes are used to create

legends for the distribution map.

Contents Attribute Information for Species Ranges .......................................................................................... 1

Polygon Data ....................................................................................................................................... 2

Required Polygon Data ................................................................................................................... 2

Optional Polygon Data .................................................................................................................... 2

Point Data ........................................................................................................................................... 4

Core Point Data ............................................................................................................................... 4

Definitions for Presence, Origin and Seasonal Distribution Codes ..................................................... 9

Presence .......................................................................................................................................... 9

Origin ............................................................................................................................................. 10

Seasonality .................................................................................................................................... 10

Presence, Origin and Seasonality Quick Reference .......................................................................... 11

Legend Combinations from Distribution Codes ................................................................................ 11

Polygon Data

Required Polygon Data

FIELD DESCRIPTION NOTES

BASIN_ID

(Freshwater

only)

ID number of HydroSHED Each individual hydroshed has a unique ID

BINOMIAL Scientific name of the species This must match the corresponding field in SIS

PRESENCE Is/Was the species in this area Values 1-6 (default is “1” if not indicated)

ORIGIN Why/ How the species is in this

area Values 1-5 (default is “1” if not indicated)

SEASONAL What is the seasonal presence

of the species in the area Values 1-5 (default is “1” if not indicated)

COMPLIER

Name of the individual/s or

institution responsible for

generating the polygon, if not

IUCN.

Names should be given in full (e.g., John Smith;

NatureServe; World Conservation Monitoring

Centre etc). If not indicated, this will default to

“IUCN”

YEAR

Year in which the polygon was

mapped or compiled, or

modified

If not indicated, this will default to the current

year

CITATION

Individual/s or institution

responsible for providing the

data

This must be the same throughout the file, and

is how the data points will be credited on the

IUCN Red List. If not indicated, this will default

to "IUCN (International Union for Conservation

of Nature)"

Optional Polygon Data

These optional attributes can be used and some are species dependent, these are the

attributes described as “Required (if relevant)” in the requirements column. For

example, the species Panthera leo has a subspecies in India (Panthera leo ssp. Persica),

therefore the subspecies column is required to be filled.

FIELD TYPE REQUIRED DEFINITION NOTES

SOURCE String Optional

Source of distribution range

given.

Relates to the primary source used to

compile each polygon, especially a recently

published range map, or a set of point data.

If compiled in a workshop, or compiled from

numerous sources, then field may be left

empty. References should be in the format

“AuthorX and AuthorY, date” and the

reference should be in the corresponding

IUCN Red List account.

DIS_COMM String Optional Distribution comments that

refer directly to the polygon.

Examples include whether the polygon

represents the type locality, names of

protected areas or geographical features, and

so forth. May also include specific notes on

presence, origin or seasonality. Max 255

characters.

ISLAND String Optional Name of the island the

polygon is on

This relates mainly to very small islands or

atolls (e.g. Midway Atoll; Meemu Atoll;

Borneo; Bohol.

SUBSPECIES String Required (if

relevant) Subspecies Name

Only if assessed at the subspecies level. This

must then match the corresponding field in

SIS. E.g. “Panthera leo ssp. Persica”

SUBPOP String Required (if

relevant) Subpopulation Name

Only if assessed at the subpopulation level,

e.g. “Chelonia mydas Hawaiian

subpopulation “

TAX_COMM String Optional

Taxonomic comments that

refer directly to the polygon.

Includes notes on polygons

pertaining to subspecies or

subpopulations.

Max 255 characters.

DATA_SENS Y/N Optional

Flags up whether or not the

polygon distribution is

sensitive. This is most likely

to be the case if the

polygon/s effectively

3orrespond to individual

localities.

Yes or No field. If “Yes”, then the field

“Sens_comm” should be completed.

SENS_COMM String

Required (if

Data_sens is

coded “Y”)

Comments on why the data

are considered sensitive. Max 255 characters.

Notes: For entries in the Source attribute field that approach the 256 character limit,

apply standard abbreviations and then define these within the reference list within SIS.

Point Data

Point data is divided into two groups, core and optional. Within core there two divisions:

required and recommended. Recommended data may be required if relevant to the

spatial data.

Point data can be provided however in spatial analyses (e.g. overlays) methods would

have to:

1. Use MCP rather than mapped range (equating to degradation of the data for species

mapped as polygons),

2. Exclude the points, or

3. Accept that the results will not be entirely comparable.

Core Point Data

Required Point Data

FIELD DESCRIPTION NOTES

BINOMIAL Scientific name of the species This must match the corresponding field

in SIS

PRESENCE Is/Was the species in this area Values 1-6 (default is “1” if not indicated)

ORIGIN Why/ How the species is in this area Values 1-5 (default is “1” if not indicated)

SEASONAL What is the seasonal presence of the

species in the area Values 1-5 (default is “1” if not indicated)

COMPILER

Name of the individual/s or institution

responsible for generating the polygon, if

not IUCN.

Names should be given in full (e.g., John

Smith; NatureServe; World Conservation

Monitoring Centre etc). If not indicated,

this will default to “IUCN”

YEAR Year in which the polygon was mapped or

compiled, or modified

If not indicated, this will default to the

current year

DEC_LAT The graphical latitude in decimal degrees,

e.g. -41.097

Positive values are North of the equator;

negative values are South of it. Legal

values lie between -90 and 90.

DEC_LONG The geographical longitude in decimal

degrees, e.g. -121.25

Positive values are East of the Greenwich

Meridian; negative values are West of it.

Legal values lie between -180 and 180.

Points

Core

Required Recommended

Optional

SPATIALREF

The ellipsoid, geodetic datum or spatial

reference system (SRS) upon which the

geographic coordinates given in dec_lat and

dec_long as based. Data is preferred in

WGS84. If Blank, will default to WGS84

E.g. “EPSG:4326”, “WGS84”, “NAD27”,

“Campo Inchauspe”, “European 1950”,

“Clarke 1866”

EVENT_YEAR The four-digit year in which the Event

(object or observation) occurred. E.g. 2008

CITATION Individual/s or institution responsible for

providing the data

This must be the same throughout the

file, and is how the data will be credited

on the IUCN Red List. If not indicated,

this will default to "IUCN (International

Union for Conservation of Nature)"

Recommended Point Data

These recommend attributes can be used and some are species dependent, these are

the attributes described as “Required (if relevant)” in the requirements column. For

example, the species Panthera leo has a subspecies in India (Panthera leo ssp. Persica),

therefore the subspecies column is required to be filled.

FIELD DESCRIPTION NOTES

SOURCE

Source of distribution

range given

Relates to the primary source used to compile the map,

especially a recently published range map, or a set of point

data. If compiled in a workshop, or compiled from numerous

sources, then field may be left empty. References should be in

the format "AuthorX and AuthorY, date" and the reference

should be in the corresponding IUCN Red List account.

SOURCETYPE Type of observation

source

Values: 1 (herbarium), 2 (museum), 3 (observation), 5

(unknown)

CATALOG_NO

An identifier (preferably

unique) for the record

within the data set or

collection.

Name of the Museum or Herbarium and the specimen number

DIST_COMM

Distribution comments

that refer directly to the

point

Examples include whether the polygon represents the type

locality, names of protected areas or geographical features,

and so forth. May also include specific notes on presence,

origin or seasonality. Max 255 characters.

ISLAND

Name of the island where

the point is present

This relates mainly to very small islands or atolls (e.g. Midway

Atoll; Meemu Atoll; Borneo; Bohol.

SUBSPECIES

Epithet

Only if assessed at the subspecies level. This must then match

the corresponding field in SIS. E.g. “Panthera leo ssp. persica”

SUBPOP Epithet Only if assessed at the subpopulation level, e.g. “Chelonia

mydas Hawaiian subpopulation “

TAX_COMM

Taxonomic comments

that refer directly to the

data source.

Includes notes pertaining to subspecies or subpopulations.

DATA_SENS

Flags up whether or not

the polygon distribution

is sensitive.

Yes or No field. If "Yes", then the field "Sens_comm" should

be completed.

SENS_COMM

Comments on why the

data are considered

sensitive.

Reasoning on why the data are considered sensitive.

Optional Point Data

These optional attributes can be used and some are species dependent, these are the

attributes described as “Required (if relevant)” in the requirements column. For

example, the species Panthera leo has a subspecies in India (Panthera leo ssp. persica),

therefore the subspecies column is required to be filled.

FIELD DESCRIPTION NOTES

COLLECTID

An identifier for the collection or dataset from

which the record was derived. For physical

specimens, the recommended best practice is to

use the identifier in a collections registry such as

the Biodiversity Collections Index

(http://www.biodiversitycollectionsindex.org/).

To enable linking back to

original data if required.

Example:

urn:lsid:biocol.org:col:34818

RECORDNO

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.

Collector or voucher number,

Example: "OPP 7101"

RECORDEDBY

A list (concatenated and separated) of names of

people, groups, or organizations responsible for

recording the original Occurrence. The primary

collector or observer, especially one who applies a

personal identifier (recordNo), should be listed

first.

Example: "Oliver P. Pearson;

Anita K. Pearson" where the

value in recordNumber "OPP

7101" corresponds to the

number for the specimen in the

field catalog (collector number)

of Oliver P. Pearson.

MONTH

The ordinal month in which the Event occurred. Examples: "1" (=January), "10"

(=October)

DAY

The integer day of the month on which the Event

occurred. Example: "9", "28"

COUNTRYCODE

The standard code for the country in which the

Location occurs. ISO codes

Examples: "AR" for Argentina,

"SV" for El Salvador

LOCALITY

The specific description of the place. Less specific

geographic information can be provided in other

geographic terms (higher geography, continent,

country, state, province, county, municipality,

water body, island, island group). This term may

contain information modified from the original to

correct perceived errors or standardize the

description.

Example: "Bariloche, 25 km

NNE via Ruta Nacional 40

(=Ruta 237)"

MINELEV

Minimum elevation in meters

The lower limit of the range of

elevation (altitude, usually

above sea level), in meters.

MAXELEV

Maximum elevation in meters

The upper limit of the range of

elevation (altitude, usually

above sea level), in meters.

VERBATLAT The verbatim original latitude of the Location. Example: "41 05 54.03S"

VERBATLONG The verbatim original longitude of the Location. Example: "121d 10' 34" W"

VERBATCOORD

The spatial coordinate system for the

verbatimLatitude and verbatimLongitude or the

verbatimCoordinates of the Location.

Recommended best practice is to use a controlled

vocabulary.

Examples: "decimal degrees",

"degrees decimal minutes",

"degrees minutes seconds",

"UTM"

VERBATSRS

The ellipsoid, geodetic datum or spatial reference

system (SRS) upon which coordinates given in

verbatimLatitude and verbatimLongitude, or

verbatimCoordinates are based.

Examples: "EPSG:4326",

"WGS84", "NAD27", "Campo

Inchauspe", "European 1950",

"Clarke 1866"

COORDUNCERT

The horizontal distance (in meters) 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.

Example: "30" (reasonable

lower limit of a GPS reading

under good conditions if the

actual precision was not

recorded at the time), "71"

(uncertainty for a UTM

coordinate having 100 meter

precision and a known spatial

reference system).

GEOREFVERI

A categorical description of the extent to which the

georeference has been verified to represent the

best possible spatial description.

Examples: "requires

verification", "verified by

collector", "verified by curator".

GEOREFNOTES

Notes or comments about the spatial description

determination, explaining assumptions made in

addition or opposition to those formalized in the

method referred to in georeference protocol.

Example: "assumed distance by

road (Hwy. 101)"

IDENTCERT Degree of certainty surrounding the species

identity of the record in question

Example:1 (definite), 2

(probable), 3 (possible), 4

(speculative), 5 (unknown);

required for new data, and

defaulted to unknown for

historic data where the

information is not available.

TYPESTATUS

A list (concatenated and separated) of

nomenclatural types (type status, typified

scientific name, publication) applied to the

subject.

Example: "holotype of

Ctenomys sociabilis. Pearson O.

P., and M. I. Christie. 1985.

Historia Natural, 5(37):388"

SUBGENUS

The full scientific name of the subgenus in which

the taxon is classified. Values should include the

genus to avoid homonym confusion.

Example: "Strobus (Pinus)",

"Puma (Puma)" "Loligo

(Amerigo)", "Hieracium subgen.

Pilosella"

OBSYRQUAL Quality of year recorded. 1 (exact), 2 (pre), 3 (post), 4

(circa), 5 (unknown)

OBSCOMPNOT Other compiler details, such as staff initials. Example: "SM"

Definitions for Presence, Origin and Seasonal Distribution Codes

The values for Presence, Origin and Seasonal within each polygon are coded according to

its distribution within the range.

Presence

CODE PRESENCE DEFINITION

1 Extant

The species is known or thought very likely to occur presently in the area,

usually encompassing current or recent localities where suitable habitat at

appropriate altitudes remains. When mapping an “assisted colonisation” it is

important to note that this range should be treated as Extant.

2 Probably Extant This code value has been discontinued for reasons of ambiguity. It may exist in

the spatial data but will gradually be phased out.

3 Possibly Extant

There is no record of the species in the area, but the species may possibly

occur, based on the distribution of potentially suitable habitat at appropriate

altitudes, although the area is beyond where the species is Extant (i.e., beyond

the limits of known or likely records), and the degree of probability of the

species occurring is lower (e.g., because the area is beyond a geographic

barrier, or because the area represents a considerable extension beyond areas

of known or probably occurrence). Identifying Possibly Extant areas is useful to

flag up areas where the taxon should be searched for. Possibly Extant ranges

are not included in the calculation of EOO or in maps of the current and / or

historical distribution of the taxon.

4 Possibly Extinct

There is no record of the species in the area, but the species was formerly

known or thought very likely to occur in the area, but it is most likely now

extirpated from the area because habitat loss/other threats are thought likely to

have extirpated the species and/or owing to a lack of records in the last 30

years.

5 Extinct

The species was formerly known or thought very likely to occur in the area, but

there have been no records in the last 30 years and it is almost certain that the

species no longer occurs, and/or habitat loss/other threats have almost certainly

extirpated the species since 1500

6 Presence

Uncertain

A record exists of the species' presence in the area but this requires verification

or is questionable owing to uncertainty over the identity or authenticity of the

record, or the accuracy of the location

Notes for Presence:

a. To obtain the total historical range of a species, one would sum polygons for Extant,

Probably Extant, Possibly Extinct, Extinct and Presence Uncertain, but not Possibly Extant.

For analysis purposes Possibly Extent will be removed due to ambiguity.

Origin

CODE ORIGIN DEFINITION

1 Native

The species is/was native to the area. When mapping an “assisted

colonisation” it is important to note that this range should be

treated as Native.

2 Reintroduced The species is/was reintroduced through either direct or indirect

human activity.

3 Introduced The species is/was introduced outside of its historical distribution

range through either direct or indirect human activity

4 Vagrant The species is/was recorded once or sporadically, but it is known

not to be native to the area.

5 Origin Uncertain The species’ provenance in an area is not known (it may be native,

reintroduced or introduced)

6 Assisted Colonisation Species subject to intentional movement and release outside its

native range to reduce the extinction risk of the taxon.

Notes for Origin:

1. EOO estimates should be based on Origin codes 1, 2, and 6. 2. The codes are mutually exclusive, e.g. a polygon coded as Introduced cannot also be

coded as Native.

Seasonality

CODE SEASONALITY DEFINITION

1 Resident The species is/was known or thought very likely to be resident

throughout the year

2 Breeding Season The species is/was known or thought very likely to occur regularly

during the breeding season and to breed.

3 Non-breeding Season

The species is/was known or thought very likely to occur regularly

during the non-breeding season. In the Eurasian and North American

contexts, this encompasses ‘winter’.

4 Passage

The species is/was known or thought very likely to occur regularly

during a relatively short period(s) of the year on migration between

breeding and non-breeding ranges.

5 Seasonal Occurrence

Uncertain

The species is/was present, but it is not known if it is present during

part or all of the year.

Notes for Seasonality:

1. ‘Regularly’ means known or thought to occur in at least 30% of years. Where it is

deemed important to record the occurrence of breeding/passage etc. for a species

which occurs less often than 30% of years (e.g. because the population is now tiny),

the category can be ticked, but a comment added to the Notes field (e.g. only

recorded in 2 years during 1985-2000).

2. If the species does not regularly breed, but there are occasional breeding records,

this can be noted in the “Dist_Notes” field.

3. If there is insufficient information to be confident of assigning Non-breeding Season

vs. Passage categories, a best guess should be made, and a comment entered in the

Notes field that some ambiguity exists. Where there is extreme uncertainty, the

‘Seasonal Occurrence Uncertain’ category should be used.

Presence, Origin and Seasonality Quick Reference

These coding’s are mutually exclusive; for example, a polygon coded as “1 (Extant)”

cannot also be coded as “5 (Extinct)”.

Code Presence Origin Seasonality

1 Extant Native Resident

2 Probably Extant (discontinued) Re-introduced Breeding season

3 Possibly Extant Introduced Non-breeding season

4 Possibly Extinct Vagrant Passage

5 Extinct (post 1500) Origin uncertain Seasonal Occurrence Uncertain

6 Presence uncertain Assisted Colonisation

Legend Combinations from Distribution Codes

Different combinations of the presence, origin and seasonality codes are used to create

legends for the final distribution map.

LEGEND PRESENCE ORIGIN SEASONAL

Extant (resident) 1 1 1

Extant (breeding) 1 1 2

Extant (non-breeding) 1 1 3

Extant (passage) 1 1 4

Extant (seasonality uncertain) 1 1 5

Probably Extant (resident) 2 1 1

Probably Extant (breeding) 2 1 2

Probably Extant (non-breeding) 2 1 3

Probably Extant (passage) 2 1 4

Probably Extant (seasonality uncertain) 2 1 5

Possibly Extant (resident) 3 1 1

Possibly Extant (breeding) 3 1 2

Possibly Extant (non-breeding) 3 1 3

Possibly Extant (passage) 3 1 4

Possibly Extant (seasonality uncertain) 3 1 5

Extant & Reintroduced (resident) 1 2 1

Extant & Reintroduced (breeding) 1 2 2

Extant & Reintroduced (non-breeding) 1 2 3

Extant & Reintroduced (passage) 1 2 4

Extant & Reintroduced (seasonality uncertain) 1 2 5

Probably Extant & Reintroduced (resident) 2 2 1

Probably Extant & Reintroduced (breeding) 2 2 2

Probably Extant & Reintroduced (non-breeding) 2 2 3

Probably Extant & Reintroduced (passage) 2 2 4

Probably Extant & Reintroduced (seasonality

uncertain) 2 2 5

Possibly Extant & Reintroduced (resident) 3 2 1

Possibly Extant & Reintroduced (breeding) 3 2 2

Possibly Extant & Reintroduced (non-breeding) 3 2 3

Possibly Extant & Reintroduced (passage) 3 2 4

Possibly Extant & Reintroduced (seasonality

uncertain) 3 2 5

Extant & Introduced (resident) 1 3 1

Extant & Introduced (breeding) 1 3 2

Extant & Introduced (non-breeding) 1 3 3

Extant & Introduced (passage) 1 3 4

Extant & Introduced (seasonality uncertain) 1 3 5

Probably Extant & Introduced (resident) 2 3 1

Probably Extant & Introduced (breeding) 2 3 2

Probably Extant & Introduced (non-breeding) 2 3 3

Probably Extant & Introduced (passage) 2 3 4

Probably Extant & Introduced (seasonality

uncertain) 2 3 5

Possibly Extant & Introduced (resident) 3 3 1

Possibly Extant & Introduced (breeding) 3 3 2

Possibly Extant & Introduced (non-breeding) 3 3 3

Possibly Extant & Introduced (passage) 3 3 4

Possibly Extant & Introduced (seasonality

uncertain) 3 3 5

Extant & Vagrant (resident) 1 4 1

Extant & Vagrant (breeding) 1 4 2

Extant & Vagrant (non-breeding) 1 4 3

Extant & Vagrant (passage) 1 4 4

Extant & Vagrant (seasonality uncertain) 1 4 5

Probably Extant & Vagrant (resident) 2 4 1

Probably Extant & Vagrant (breeding) 2 4 2

Probably Extant & Vagrant (non-breeding) 2 4 3

Probably Extant & Vagrant (passage) 2 4 4

Probably Extant & Vagrant (seasonality uncertain) 2 4 5

Possibly Extant & Vagrant (resident) 3 4 1

Possibly Extant & Vagrant (breeding) 3 4 2

Possibly Extant & Vagrant (non-breeding) 3 4 3

Possibly Extant & Vagrant (passage) 3 4 4

Possibly Extant & Vagrant (seasonality uncertain) 3 4 5

Extant & Origin Uncertain (resident) 1 5 1

Extant & Origin Uncertain (breeding) 1 5 2

Extant & Origin Uncertain (non-breeding) 1 5 3

Extant & Origin Uncertain (passage) 1 5 4

Extant & Origin Uncertain (seasonality uncertain) 1 5 5

Probably Extant & Origin Uncertain (resident) 2 5 1

Probably Extant & Origin Uncertain (breeding) 2 5 2

Probably Extant & Origin Uncertain (non-

breeding) 2 5 3

Probably Extant & Origin Uncertain (passage) 2 5 4

Probably Extant & Origin Uncertain (seasonality

uncertain) 2 5 5

Possibly Extant & Origin Uncertain (resident) 3 5 1

Possibly Extant & Origin Uncertain (breeding) 3 5 2

Possibly Extant & Origin Uncertain (non-breeding) 3 5 3

Possibly Extant & Origin Uncertain (passage) 3 5 4

Possibly Extant & Origin Uncertain (seasonality

uncertain) 3 5 5

Extant & Assisted Colonisation (resident) 1 6 1

Extant & Assisted Colonisation (breeding) 1 6 2

Extant & Assisted Colonisation (non-breeding) 1 6 3

Extant & Assisted Colonisation (passage) 1 6 4

Extant & Assisted Colonisation (seasonality

uncertain) 1 6 5

Probably Extant & Assisted Colonisation

(resident) 2 6 1

Probably Extant & Assisted Colonisation

(breeding) 2 6 2

Probably Extant & Assisted Colonisation (non-

breeding) 2 6 3

Probably Extant & Assisted Colonisation

(passage) 2 6 4

Probably Extant & Assisted Colonisation

(seasonality uncertain) 2 6 5

Possibly Extant & Assisted Colonisation (resident) 3 6 1

Possibly Extant & Assisted Colonisation

(breeding) 3 6 2

Possibly Extant & Assisted Colonisation (non-

breeding) 3 6 3

Possibly Extant & Assisted Colonisation

(passage) 3 6 4

Possibly Extant & Assisted Colonisation

(seasonality uncertain) 3 6 5

Possibly Extinct 4 1 1

Possibly Extinct & Reintroduced 4 2 2

Possibly Extinct & Introduced 4 3 3

Possibly Extinct & Vagrant 4 4 4

Possibly Extinct & Origin Uncertain 4 5 5

Extinct 5 1 1

Extinct & Reintroduced 5 2 2

Extinct & Introduced 5 3 3

Extinct & Vagrant 5 4 4

Extinct & Origin Uncertain 5 5 5

Presence Uncertain 6 1 1

Presence Uncertain 6 1 1

Presence Uncertain & Reintroduced 6 2 2

Presence Uncertain & Introduced 6 3 3

Presence Uncertain & Vagrant 6 4 4

Presence Uncertain & Origin Uncertain 6 5 5