WildCounts Shorthand vocab

Here is a complete list of the WildCounts Shorthand syntax for quickly typing in wild counts. This lets you enter your counts with as little typing as possible, so that you can spend more time watching the wild and less time watching your screen.

Having said that, do keep a close eye on your smart phone’s spellchecker. When you first start entering WildCounts Shorthand, your phone may “helpfully” autocorrect what you enter. After a while, any modern phone will learn the values you enter and stop autocorrecting. There are also options in most phone’s settings to enter in your commonly used phrases to avoid them getting caught by the autocorrect. That’s recommended for WildCounts Shorthand.

WildCounts Shorthand syntax below is divided into five categories. Count is the general syntax for counting individual organisms. Observation connector is the syntax for connecting together organisms of different species, which is useful when you see species interacting. Phenology is the syntax specifically for recording the reproductive stages present on plants. Roadkill, as the name suggests, is the syntax for counting roadkill, and its condition and location on roads. Lastly, Survey is the syntax used for describing the environment at the time of your count.

Within each category are types, values, and syntax. Types are the different concepts, like “taxon name”, “age”, and “initial position compass bearing”. Within each type are one or more values. For example, the type “age” has the values “adult”, “juvenile”, “baby”, and “egg”. Within each value is then one, or sometimes several, shorthand syntax options for entering that value. For example, the shorthand syntax for “adult” is a.

The types are listed in the order that they appear in a line of WildCounts Shorthand, starting with the taxon name. The exact position of each type in the shorthand is also indicated. All syntax is case insensitive unless specified.

Note that a complete spreadsheet version of all of this syntax (and an archive of old deprecated syntax not displayed here), plus an R script that automatically converts that spreadsheet into this webpage, are available on Github.

Contents

• Category: count

  1. Type: taxon name

     • Values: taxon name,

  2. Type: shorthand separator

     • Values: space,

  3. Type: taxon uncertain added to name

     • Values: question mark, double question mark,

  4. Type: non-vocalisation noise

     • Values: knock, rustle, wings,

  5. Type: in field

     • Values: field,

  6. Type: dead

     • Values: dead, gone,

  7. Type: animal sign

     • Values: footprint, nest, poo, tunnel,

  8. Type: invertebrate stage

     • Values: adult, egg, larva, nymph, pupa,

  9. Type: position left right

     • Values: left, over, right,

  10. Type: initial position compass bearing

      • Values: east, east-northeast, east-southeast, north, northeast, north-northeast, north-northwest, northwest, south, southeast, south-southeast, south-southwest, southwest, west, west-northwest, west-southwest,

  11. Type: initial distance band

      • Values: close initial distance, distant initial distance, far initial distance, near-in initial distance, mid initial distance, near initial distance, near-out initial distance,

  12. Type: geotagged distance band

      • Values: close geotagged distance, distant geotagged distance, far geotagged distance, near-in geotagged distance, mid geotagged distance, near geotagged distance, near-out geotagged distance,

  13. Type: position ahead behind

      • Values: ahead, behind,

  14. Type: inner estimate of distance band

      • Values: inner estimate of distance band,

  15. Type: count approximate

      • Values: about this many,

  16. Type: presence/absence

      • Values: no, yes,

  17. Type: simple abundance

      • Values: abundant, common, occasional, one, rare,

  18. Type: sex

      • Values: female, female or juvenile, male, male or juvenile, young female, young male,

  19. Type: age

      • Values: adult, baby, egg, juvenile,

  20. Type: same or different individual

      • Values: different, same, possibly the same,

  21. Type: seen song call

      • Values: call only, call then seen, call then seen then song, call then song then seen, wings only, wings then seen, seen only, seen then call, seen then call then song, seen then wings, song then seen, seen then song, seen then song then call, song only, song then call the seen, song then seen then call,

  22. Type: flying

      • Values: flying, flying circling, flying east, flying east-northeast, flying east-southeast, flying north, flying northeast, flying north-northeast, flying north-northwest, flying northwest, flying south, flying southeast, flying south-southeast, flying south-southwest, flying southwest, flying west, flying west-northwest, flying west-southwest,

  23. Type: ID confirmed with technology

      • Values: confirmed with monocular,

  24. Type: 10-pace section counts

      • Values: 10-m long patch,

  25. Type: recorded

      • Values: photographed, on previous photo, recorded, on previous recording, second recording in interval, on second recording in interval,

  26. Type: wild or captive/cultivated

      • Values: wild, possibly wild, captive/cultivated,

  27. Type: same individual again

      • Values: same again, possibly same again,

  28. Type: taxon uncertain added to count

      • Values: question mark, double question mark,

  29. Type: vocalisation continued uninterrupted for more than 10 seconds

      • Values: continued to vocalise,

  30. Type: count connector

      • Values: departed, count separator, with, joined by, after first five minutes,

  31. Type: semicolon comment separator

      • Values: semi-colon,

  32. Type: usual individual

      • Values: usual, unsure if usual,

  33. Type: vocalisation keyword

      • Values: ack call, alarm call, chatter call, chuck call, seep call, tee call, tink call, tinkle call, toot call, whinny song,

  34. Type: comma environment code separator

      • Values: environment code separator,

  35. Type: window open or closed in count

      • Values: window open and closed during observation, window closed during observation, window open during observation,

• Category: observation connector

  1. Type: observation connector

     • Values: with, joined by,

  2. Type: interspecific interaction

     • Values: decomposition, epiphyte, flower visitor, fruigivory, herbivory, hemiparasitism, host, infection, parasitism, parasitoid, predation, seed predation,

  3. Type: interspecific interaction direction

     • Values: by interaction, of interaction,

• Category: phenology

  1. Type: taxon name

     • Values: taxon name,

  2. Type: semicolon shorthand separator

     • Values: semi-colon,

  3. Type: taxon uncertain added to name

     • Values: question mark, double question mark,

  4. Type: position left right

     • Values: left, over, right,

  5. Type: initial position compass bearing

     • Values: east, east-northeast, east-southeast, north, northeast, north-northeast, north-northwest, northwest, south, southeast, south-southeast, south-southwest, southwest, west, west-northwest, west-southwest,

  6. Type: initial distance band

     • Values: close initial distance, distant initial distance, far initial distance, near-in initial distance, mid initial distance, near initial distance, near-out initial distance,

  7. Type: geotagged distance band

     • Values: close geotagged distance, distant geotagged distance, far geotagged distance, near-in geotagged distance, mid geotagged distance, near geotagged distance, near-out geotagged distance,

  8. Type: position ahead behind

     • Values: ahead, behind,

  9. Type: inner estimate of distance band

     • Values: inner estimate of distance band,

  10. Type: count approximate

      • Values: about this many,

  11. Type: presence/absence

      • Values: no, yes,

  12. Type: simple abundance

      • Values: abundant, common, occasional, one, rare,

  13. Type: taxon uncertain added to count

      • Values: question mark, double question mark,

  14. Type: vocalisation continued uninterrupted for more than 10 seconds

      • Values: continued to vocalise,

  15. Type: same or different individual

      • Values: different, same, possibly the same,

  16. Type: seen song call

      • Values: call only, call then seen, call then seen then song, call then song then seen, wings only, wings then seen, seen only, seen then call, seen then call then song, seen then wings, song then seen, seen then song, seen then song then call, song only, song then call the seen, song then seen then call,

  17. Type: 10-pace section counts

      • Values: 10-m long patch,

  18. Type: recorded

      • Values: photographed, on previous photo, recorded, on previous recording, second recording in interval, on second recording in interval,

  19. Type: wild or captive/cultivated

      • Values: wild, possibly wild, captive/cultivated,

  20. Type: same individual again

      • Values: same again, possibly same again,

  21. Type: count connector

      • Values: departed, count separator, with, joined by, after first five minutes,

  22. Type: reproductive phenology stage

      • Values: bolting, BOLT, dispersed seeds, mainly dispersed, Flower bud(s), mainly flower buds, flowers, mainly flowers, immature fruit, mainly immature fruit, juvenile, mature seeds/fruit, mainly seeds, seedling, spike, SPIKE, vegetative, vegetative,

  23. Type: reproductive phenology separator

      • Values: phenology separator,

  24. Type: semicolon comment separator

      • Values: semi-colon,

  25. Type: usual individual

      • Values: usual, unsure if usual,

  26. Type: comma environment code separator

      • Values: environment code separator,

• Category: roadkill

  1. Type: taxon name

     • Values: taxon name,

  2. Type: shorthand separator

     • Values: space,

  3. Type: taxon uncertain added to name

     • Values: question mark, double question mark,

  4. Type: road positions

     • Values: roadkill on eastern grass, roadkill on eastern road, roadkill on eastern verge, roadkill on left grass, roadkill on left road, roadkill on left verge, roadkill on mid road, roadkill on northern grass, roadkill on northern road, roadkill on northern verge, roadkill on right grass, roadkill on right road, roadkill on right verge, roadkill on southern grass, roadkill on southern road, roadkill on southern verge, roadkill on western grass, roadkill on western road, roadkill on western verge,

  5. Type: roadkill age

     • Values: fresh, old, unsure,

  6. Type: roadkill state

     • Values: roadkill decomposed, roadkill eaten, roadkill exposed, roadkill feathers, roadkill fragment, roadkill fur, roadkill intact, roadkill squashed,

  7. Type: usual individual

     • Values: usual, unsure if usual,

  8. Type: comma environment code separator

     • Values: environment code separator,

• Category: survey

  1. Type: movement survey keyword

     • Values: exploring, running, stationary, walking,

  2. Type: comma environment code separator

     • Values: environment code separator,

  3. Type: window open or closed in survey interval

     • Values: window open, window closed, window sometimes open,

  4. Type: movement environment code

     • Values: exploring, stationary,

  5. Type: temperature environment codes

     • Values: temperature cold, temperature cool, temperature freezing, temperature hot, temperature mild, temperature warm,

  6. Type: wind amount environment codes

     • Values: wind moving branches, wind rustling leaves, wind light, wind moving trees,

  7. Type: direct sun environment codes

     • Values: Direct sun >0%–10%, s00, Direct sun 10%–20%, Direct sun 100%, Direct sun 20%–30%, Direct sun 30%–40%, Direct sun 40%–50%, Direct sun 50%–60%, Direct sun 60%–70%, Direct sun 70%–80%, Direct sun 80%–90%, Direct sun 90%–<100%,

  8. Type: wind direction environment codes

     • Values: wind still, wind from east, wind from north, wind from northeast, wind from northwest, wind from south, wind from southeast, wind from southwest, wind from west,

  9. Type: precipitation type environment code

     • Values: hail, mist, no precipitation, rain, snow,

  10. Type: precipitation intensity environment code

      • Values: drizzle, dripping foliage, heavy precipitation, light precipitation, moderate precipitation, no precipitation,

  11. Type: precipitation duration environment code

      • Values: Precipitation >0–10%, Precipitation 10–20%, Precipitation 100%, Precipitation 20–30%, Precipitation 30–40%, Precipitation 40–50%, Precipitation 50–60%, Precipitation 60–70%, Precipitation 70–80%, Precipitation 80–90%, Precipitation 90–<100%,

Category: count

Count syntax is of the general form: taxon state prefixcountsuffix(comment)[environment]. Usually only taxon prefixcountsuffix is needed.

Type: taxon name

Taxon names can be full scientific or common names or abbreviated names. All names other than scientific names must be included in your taxon dictionary alongside their corresponding scientific names.

Position in shorthand: c00 count taxon

Value: taxon name

A taxon name, which can be a recognised scientific name (without the taxonomic authority) or a common name, or an abbreviated code.

Syntax:

blackbird

blkb

Turdus merula

Type: shorthand separator

Count category and roadkill category shorthand are space delimited.

Position in shorthand: c01 shorthand separator

Value: space

a space

Syntax: ` `

Type: taxon uncertain added to name

A question mark (?) can be added directly after a taxon name to indicate that this ID is uncertain. This means the same as when ? is placed after a count. In the former case, it applies to all counts on that shorthand line, and so can be a quicker way to enter uncertainty.

Position in shorthand: c02 count taxon modifier

Fixed position: right of taxon name

Value: question mark

When placed after a taxon name, a question mark means that the identification is uncertain. Other plausible taxon IDs should be listed in the comments prefaced by “ or “.

Syntax: ?

Value: double question mark

It is not only unclear if the identification is correct, but it is also unclear if the observation was of a living organism at all. (This level of uncertainty is most often encountered with roadkill observed from a moving car.)

Syntax: ??

Type: non-vocalisation noise

Sometimes I hear sign of an animal nearby but don’t see it. For example, the rustle of a blackbird foraging in leaf litter nearby, or the wing whoosh of a kereru flying past, or, when in the USA, the sound of a woodpecker banging on a tree. These are added as modifiers after the taxon name (they don’t have codes because they are used infrequently).

Position in shorthand: c02 count taxon modifier

Value: knock

The sound of banding from an animals activity nearby (created for woodpeckers).

Syntax: knock

Value: rustle

A rustling sound heard consistent with an animals movement in leaves.

Syntax: rustle

Value: wings

The sound of beating wings heard.

Syntax: wings

Type: in field

When plants are abundant in fields in farmland (for example Brassica as crops or weeds in fields), I record their presence per field, rather than paces. A field is a plot of fenced farmland containing one crop type/land use. The size of a field isn’t standardised and so recording in paces is preferred when possible.

Position in shorthand: c02 count taxon modifier

Value: field

The taxon is present in a field

Syntax: field

Type: dead

If something is dead, the word “dead” can be placed after the taxon name when using the count category of shorthand.

Position in shorthand: c03 count taxon state

Value: dead

It’s dead, and there are remains present.

Syntax: dead

Value: gone

It was here but now it’s gone. This is used for usual immobile individuals (eg plants, roadkill) that have been previously recorded at this location but are no longer there. If there’s no sign of a carcass or remains, then it’s “gone” rather than “dead”.

Syntax: gone

Type: animal sign

Unambiguous sign of the taxon’s presence even when it is absent.

Position in shorthand: c03 count taxon state

Value: footprint

Syntax: footprint

Value: nest

Syntax: nest

Value: poo

scat, faeces

Syntax: poo

Value: tunnel

Syntax: tunnel

Type: invertebrate stage

Stages of invertebrates are included between the species name and the count. Options are “egg”, “larva”, “nymph”, “pupa”, and “adult”. When no stage is included for insects, adult is implied.

Position in shorthand: c03 count taxon state

Value: adult

Adult(s) observed.

Syntax: adult

Value: egg

Egg(s) observed.

Syntax: egg

Value: larva

Lava(e) observed.

Syntax: larva

Value: nymph

Nymph(s) observed.

Syntax: nymph

Value: pupa

Pupa(e) observed. Includes fly puparia.

Syntax: pupa

Type: position left right

Where the counted individual(s) are relative to the motion of the observer.

Position in shorthand: c04 count prefix

Fixed position: left of geotagged distance band

Value: left

the observed organism is to the left of the observer

Syntax: l

Value: over

the observed organism past over the path of the observer

Syntax: o

Value: right

the observed organism is to the right of the observer

Syntax: r

Type: initial position compass bearing

Where the individual(s) are relative to the observer when first observed.

Position in shorthand: c04 count prefix

Fixed position: right of geotagged distance band

Value: east

east

Syntax: _e

Value: east-northeast

east-northeast

Syntax: _ene

Value: east-southeast

east-southeast

Syntax: _ese

Value: north

north

Syntax: _n

Value: northeast

northeast

Syntax: _ne

Value: north-northeast

north-northeast

Syntax: _nne

Value: north-northwest

north-northwest

Syntax: _nnw

Value: northwest

northwest

Syntax: _nw

Value: south

south

Syntax: _s

Value: southeast

southeast

Syntax: _se

Value: south-southeast

south-southeast

Syntax: _sse

Value: south-southwest

south-southwest

Syntax: _ssw

Value: southwest

southwest

Syntax: _sw

Value: west

west

Syntax: _w

Value: west-northwest

west-northwest

Syntax: _wnw

Value: west-southwest

west-southwest

Syntax: _wsw

Type: initial distance band

This is the distance where the organism is first detected. It can be a different to the distance from the observer when the observation is date-time stamped and geotagged (which is typically done as close as is got to the organism). The first distance is useful for determining how detection probability varies with distance. The second distance is more useful for mapping. Between these two distances is whether the animal is on the left (“l”) or right (“r”) of me, or passes over (“o”). If only one distance category is provided, it means that the distance first seen and date-time-geo-stamped are the same.

Position in shorthand: c04 count prefix

Fixed position: left of position left right

Value: close initial distance

first observed close, < 5 m

Syntax: c

Value: distant initial distance

first observed distant, >320 m

Syntax: d

Value: far initial distance

first observed far, >80–<320 m

Syntax: f

Value: near-in initial distance

first observed near-in, >5–<10 m

Syntax: k

Value: mid initial distance

first observed mid, >20–<80 m

Syntax: m

Value: near initial distance

first observed near, >5–<20 m

Syntax: n

Value: near-out initial distance

first observed near-out, >10–<20 m

Syntax: t

Type: geotagged distance band

This is the distance band the organism(s) were in when the observation was date-stamped and geotagged. In can be closer than the initial distance when first observed. If only one distance band is provided in the shorthand, it means that the initial and geotagged distances were the same.

Position in shorthand: c04 count prefix

Fixed position: left of initial position compass bearing

Value: close geotagged distance

datestamp/geotag made close, < 5 m

Syntax: c

Value: distant geotagged distance

datestamp/geotag made distant, >320 m

Syntax: d

Value: far geotagged distance

datestamp/geotag made far, >80–<320 m

Syntax: f

Value: near-in geotagged distance

datestamp/geotag made near-in, >5–<10 m

Syntax: k

Value: mid geotagged distance

datestamp/geotag made mid, >20–<80 m

Syntax: m

Value: near geotagged distance

datestamp/geotag made near, >5–<20 m

Syntax: n

Value: near-out geotagged distance

datestamp/geotag made near-out, >10–<20 m

Syntax: t

Type: position ahead behind

Used when the individual(s) observed are ahead or behind the observer at the time the observation is made. This can be appropriate when you are moving while surveying.

Position in shorthand: c04 count prefix

Fixed position: right of geotagged distance band

Value: ahead

the organism observed is ahead of the observer

Syntax: =a

Value: behind

the organism observed is behind the observer

Syntax: =b

Type: inner estimate of distance band

This shorthand code is used when my visual estimate of distance is at the boundary of one of my distance bands. The rule is to use the inner distance band, since this is plausible, and follow this by “i” to indicate that there is uncertainty.

Position in shorthand: c04 count prefix

Fixed position: right of initial distance band

Value: inner estimate of distance band

When an observation is at a distance band boundary, enter the inner distance followed by “i”. For example, if the observation was at about 80 m, enter “mi”.

Syntax: i

Type: count approximate

When visibility or time or movement prevents you from counting all individuals exactly, you can indicate that the count is approximate.

Position in shorthand: c05 count modifier before

Value: about this many

About (an estimate of the exact count). I use the rule of thumb that the count I make is a conservative estimate and the true count could be up to 1.5 times this value (rounded up to the nearest whole number). So, “~1” means 1–2, “~2” means 2–3, and “~10” means 10–15.

Syntax: ~

Type: presence/absence

At it’s simplest, a taxon can be present or absent in a survey. This is indicated with “yes” or “no” as the count.

Position in shorthand: c06 count

Value: no

The taxon was sought but not found.

Syntax: no

Value: yes

The taxon was observed.

Syntax: yes

Type: simple abundance

Five simple categories to quickly describe local abundance.

Position in shorthand: c06 count

Value: abundant

abundant (one of the dominant species)

Syntax:

abun

abund

Value: common

common (easy to find anywhere)

Syntax:

com

comm

Value: occasional

occasional (easy to find with searching)

Syntax: occ

Value: one

only one found

Syntax: one

Value: rare

rare (hard to find)

Syntax: rare

Type: sex

The sex of an individual.

Position in shorthand: c07 count suffix

Value: female

sex is female

Syntax: xf

Value: female or juvenile

female or juvenile (in other words, definitely not an adult male)

Syntax: xfj

Value: male

sex is male

Syntax: xm

Value: male or juvenile

male or juvenile (infrequently used, since juvenile birds more often look like females when seen)

Syntax: xmj

Value: young female

young female (plausibly or definitely juvenile, in other words unlikely to be at breeding age yet)

Syntax: yxf

Value: young male

young male (plausibly or definitely juvenile, in other words unlikely to be at breeding age yet)

Syntax: yxm

Type: age

Whether an individual is an adult, juvenile, or baby.

Position in shorthand: c07 count suffix

Value: adult

adult

Syntax: a

Value: baby

baby/chick. For birds, these are passerines pre-fledgling or baby birds like ducklings before their moult into juvenile plumage.

Syntax: b

Value: egg

baby/chick. For birds, these are passerines pre-fledgling or baby birds like ducklings before their moult into juvenile plumage.

Syntax: e

Value: juvenile

juvenile

Syntax: j

Type: same or different individual

The “at” symbol (@) is used to indicate that the same observed individual(s) have previously been observed already within the same survey. (Note that “same” differs in meaning from “usual”. “Usual” is a different type meaning that an individual has been observed in previous surveys.)

Position in shorthand: c07 count suffix

Fixed position: right of same again

Value: different

The observed individuals have definitely not been observed before in this survey. This is inferred for all moving surveys.

Syntax: !

Value: same

The same observed individual(s) have previously been observed already within the survey. Note that “same” (@) differs in meaning from “usual”. “Usual” means that an individual has been observed in previous surveys.

Syntax: @

Value: possibly the same

The individuals observed may be the same as individuals previously observed within the same survey, but perhaps not. This is inferred for all stationary surveys.

Syntax: @!

Type: seen song call

Were the observed individual(s) seen, and did they call and/or sing, and in which order did these occur? Only some species have recognisably different calls and songs. For the rest, the two are synonymous.

Position in shorthand: c07 count suffix

Value: call only

call (and not seen)

Syntax: c

Value: call then seen

call then seen

Syntax: cs

Value: call then seen then song

call then seen then song

Syntax: csv

Value: call then song then seen

call then song then seen

Syntax: cvs

Value: wings only

heard wings beating but not seen

Syntax: g

Value: wings then seen

heard wings beating then seen

Syntax: gs

Value: seen only

seen only (no calls/vocalisations)

Syntax: s

Value: seen then call

seen then call

Syntax: sc

Value: seen then call then song

seen then call then song

Syntax: scv

Value: seen then wings

seen then heard wings beating

Syntax: sg

Value: song then seen

song then seen

Syntax:

song then seen

vs

Value: seen then song

seen then song

Syntax: sv

Value: seen then song then call

seen then song then call

Syntax: svc

Value: song only

vocalisation (and not seen). This includes just song for birds with recognisably different calls and song.

Syntax: v

Value: song then call the seen

song then call the seen

Syntax: vcs

Value: song then seen then call

song then seen then call

Syntax: vsc

Type: flying

The observed individuals were flying for all the time that they were seen/heard. Flying can optionally have a direction of flight. When used this means that the animal was flying in an (approximately) straight line. Otherwise, “f_c” for flying circling is used.

Position in shorthand: c07 count suffix

Value: flying

flying

Syntax: f

Value: flying circling

flying circling

Syntax: f_c

Value: flying east

flying east

Syntax: f_e

Value: flying east-northeast

flying east-northeast

Syntax: f_ene

Value: flying east-southeast

flying east-southeast

Syntax: f_ese

Value: flying north

flying north

Syntax: f_n

Value: flying northeast

flying northeast

Syntax: f_ne

Value: flying north-northeast

flying north-northeast

Syntax: f_nne

Value: flying north-northwest

flying north-northwest

Syntax: f_nnw

Value: flying northwest

flying northwest

Syntax: f_nw

Value: flying south

flying south

Syntax: f_s

Value: flying southeast

flying southeast

Syntax: f_se

Value: flying south-southeast

flying south-southeast

Syntax: f_sse

Value: flying south-southwest

flying south-southwest

Syntax: f_ssw

Value: flying southwest

flying southwest

Syntax: f_sw

Value: flying west

flying west

Syntax: f_w

Value: flying west-northwest

flying west-northwest

Syntax: f_wnw

Value: flying west-southwest

flying west-southwest

Syntax: f_wsw

Type: ID confirmed with technology

Equipment was used to see/hear the individual(s) clearer and confirm the ID.

Position in shorthand: c07 count suffix

Value: confirmed with monocular

ID confirmed by viewing through monocular/binoculars/telephoto lens.

Syntax: m

Type: 10-pace section counts

When individuals are too numerous to count, or not of enough interest to count, I instead record their presence in 10 pace (approximately 10 metre) sections. One 10-pace section of a transect is denoted with “p”, so “1p” is one 10 pace section. A count with a “p” always means that more than one individual was present.

Position in shorthand: c07 count suffix

Value: 10-m long patch

a 10-pace (approximately 10 m) section of the route. This is one standard “patch” in WildCounts.

Syntax: p

Type: recorded

The individual(s) in this shorthand observation were photographed or recorded.

Position in shorthand: c07 count suffix

Value: photographed

Photographed (image(s) were made). [This initially was a keyword restricted to this use only within comments. That is replaced with “i”.]

Syntax: i

Value: on previous photo

Photo included on the photo of the immediately previously photographed taxon obseravtion.

Syntax: ii

Value: recorded

A separate audio recording(s) was made (separate from the spoken audio note). [This initially was a keyword restricted to this use only within comments. That is replaced with “r”.]

Syntax: r

Value: on previous recording

Recorded on the previous recording. (“r” is used for the first vocalisation on the recording, and “rr” is used to denote any subsequent vocalisations, by the same or other animals, that are present on the same recording. Each “r” will correspond to a separate sound file, but each “rr” won’t.)

Syntax: rr

Value: second recording in interval

The second audio recording used in a time period. This is used only in shorthand streams with multiple counts added to one line, e.g., “bellb m1vr,m1vrr,m1v,m1v,m1vrrr,m1vrrrr” means bellbird song was heard at mid-distance six times, and the first and second times are recorded on the first recording, and the fifth and sixth recordings are recorded on the second recording.

Syntax: rrr

Value: on second recording in interval

Recorded on the previous recording when that previous recording is the second recording made during a survey period recorded with a shorthand stream.

Syntax: rrrr

Type: wild or captive/cultivated

Whether the individual(s) were definitely wild, or definitely captive/cultivated, or possibly wild.

Position in shorthand: c07 count suffix

Value: wild

The individual(s) were definitely wild. This is always assumed if it is not stated, but this symbol can be applied for emphasis.

Syntax: ^

Value: possibly wild

The individual(s) were possibly cultivated, but it’s not certain.

Conditional: ``

Syntax:

^$

$^

Value: captive/cultivated

The individual(s) were definitely cultivated.

Conditional: ``

Syntax: $

Type: same individual again

“Same again” refers to individuals that were observed in a different interval or route section within the current survey.

This is a separate concept from “same or different individual” (“@” and “!”), which only refers to the current interval or route section within the survey. When both concepts are used, “same or different individual” should always follow “same again” in the syntax.

Note that there is no need to use “same again” when a survey is not subdivided into intervals and/or route sections.

Position in shorthand: c07 count suffix

Value: same again

The individual observed in a previous route section, or previous time interval, of the same survey is now recorded again. This allows you to record an accurate count of how many individuals of a species you detect in a route section or time interval, within a survey, while still tracking how many of these individuals you already counted in a previous section or interval. (I used to be be inconsistent here about whether I used “same” or “usual”, usually I used “same”, but it’s really a third concept.)

Syntax: @@

Value: possibly same again

Possibly the same individual observed in a previous route section, or time intervale, of the same survey is now recorded again.

Syntax: @@!

Type: taxon uncertain added to count

A question mark (?) can be added after a count to indicate that the ID is uncertain.

Position in shorthand: c08 count modifier after

Value: question mark

When placed after a count, a question mark means that the identification of the species counted is uncertain. Other plausible taxon IDs should be listed in the comments prefaced by “ or “.

Syntax: ?

Value: double question mark

It is not only unclear if the identification is correct, but it is also unclear if the observation was of a living organism at all. (This level of uncertainty is most often encountered with roadkill observed from a moving car.)

Syntax: ??

Type: vocalisation continued uninterrupted for more than 10 seconds

If individual(s), heard vocalising but not seen, vocalise uninterrupted for more than 10 seconds, then this is indicated in their count. If this is not indicated, vocalisations are implied to have been continuous for 10 seconds or less.

Vocalisations separated by more than ten seconds get recorded as separate counts, with a “@” if they were made by definitely the same individual(s).

Position in shorthand: c08 count modifier after

Value: continued to vocalise

Simplified syntax for when the observed animals that are heard vocalising (but not seen) continued to vocalise uninterrupted for more then ten seconds.

Syntax: ..@

Type: count connector

Different individuals, or groups of individuals, of the same species, can be connected together in one count in various ways.

Position in shorthand: c09 count join

Value: departed

Left. A minus symbol (“-“) is used for individuals leaving a group.

Syntax: -

Value: count separator

Different groups. Counts separated by commas are of individuals in different groups. A group is defined here as individuals within 20 m or each other.

Syntax: ,

Value: with

With. An asterisk (*) indicates that separately counted individuals (e.g., different sexes, different ages) were part of the same group. A group is defined here, somewhat arbitrarily bit consistently, as individuals within 20 m or each other. In my audio notes, I use the word “with” for the asterisk.

Syntax: *

Value: joined by

Joined by. An ampersand symbol (“&”) is used for individuals joining a group (not a plus symbol—that has another meaning). If & connects two vocalisations, is means that one happened immediately after the other from a different location and so they must be two separate individuals (this case is an exception in that it doesn’t mean that the individuals were within 20 m of each other).

Syntax: &

Value: after first five minutes

Individuals counted before this pipe were observed in the first 5 minutes of the survey period. Used for shorthand streams.

Syntax: |

Type: semicolon comment separator

A semicolon placed between sections of text in a comment on a shorthand line splits comments across the different counts from that line.

Position in shorthand: c11 comment separator

Value: semi-colon

used to separate comment text referring to different individual(s) indicated in the count.

Syntax: ;

Type: usual individual

The individual(s) observed are the usual individuals that have also been observed in previous surveys (typically on previous days). These are notable individuals that are tracked across multiple surveys (e.g., flowering times of individual plants).

Position in shorthand: c12 comment keyword

Value: usual

The observed individual has been observed in past surveys (e.g., a plant in the same location, or a banded bird).

Syntax: u

Value: unsure if usual

The observed individual may have been observed in past surveys (e.g., a plant in the same location, or a banded bird) but it’s not immediately clear at the time of counting whether this is the case (eg it’s been a while and the observer has forgotten).

Syntax: un

Type: vocalisation keyword

Some animals (particularly birds) make recognisably different types of calls and songs and these can be noted in comments using consistent keywords. Note that these are specific to urban New Zealand.

Position in shorthand: c12 comment keyword

Value: ack call

Bellbird making an ack call.

Conditional: taxon == Anthornis melanura

Syntax: ack

Value: alarm call

Bellbird making an alarm call.

Conditional: taxon == Anthornis melanura

Syntax: alarm

Value: chatter call

Blackbird making a chatter call.

Conditional: taxon == Turdus merula

Syntax: chatter

Value: chuck call

Blackbird making a chuck call.

Conditional: taxon == Turdus merula

Syntax: chuck

Value: seep call

Blackbird making a “seep” call (note that this is a call I only recognised later in my counts—see the data for the first time it was used).

Conditional: taxon == Turdus merula

Syntax: seep

Value: tee call

Dunnock making a tee call

Conditional: taxon == Punella modularis

Syntax: tee

Value: tink call

Blackbird making a tink call.

Conditional: taxon == Turdus merula

Syntax: tink

Value: tinkle call

Dunnock making a tinkle call

Conditional: taxon == Punella modularis

Syntax: tinkle

Value: toot call

Bellbird making a toot call.

Conditional: taxon == Anthornis melanura

Syntax: toot

Value: whinny song

Silvereye making a whinny song

Conditional: taxon == Zosterops lateralis

Syntax: whinny

Type: comma environment code separator

When there is more than one environment code in square brackets, they are separated by commas (and no spaces).

Position in shorthand: c15 environment separator

Value: environment code separator

comma (no space)

Syntax: ,

Type: window open or closed in count

Was the window open or closed when a count was made (from indoors)?

Position in shorthand: c16 environment code

Value: window open and closed during observation

The nearest window was open and closed during the time when I made this observation.

Syntax: winb

Value: window closed during observation

The nearest window was closed (open=no) when I made this observation.

Syntax: winn

Value: window open during observation

The nearest window was open when I made this observation.

Syntax: winy

Category: observation connector

A line between two observations with information on how those two observations are connected.

Examples:

blkb 1
*
th 1

mm larva 1
*[ho]
SENvulg; c1; fb-FL-im;

Type: observation connector

Two observations of two species, made at the same location and time, are connected, by proximity (within 20 m of each other) or by a direct interaction.

Position in shorthand: o00 observation connector

Value: with

The organism(s) in observation #1 are with the organism(s) in observation #2. The “with” means that they are within 20 m of each other (that’s the outer boundary for birds to be in a group) but in practise they will usually be much closer that that.

Syntax: *

Value: joined by

The organism(s) in observation #1 are joined by the organism(s) in observation #2. This means that the organism(s) in observation #1 were alone when first observed and the organism(s) in observation #2 joined them (came within 20 m) during the observation period.

Syntax: &

Type: interspecific interaction

The interaction type for the association between the first species observation and the second species observation.

Position in shorthand: o01 observation connector suffix

Fixed position: right of observation connector

Value: decomposition

decomposition

Syntax: de

Value: epiphyte

epiphyte

Syntax: ep

Value: flower visitor

flower visitor

Syntax: fl

Value: fruigivory

fruigivory

Syntax: fr

Value: herbivory

herbivory

Syntax: he

Value: hemiparasitism

hemiparasitism

Syntax: hp

Value: host

host

Syntax: ht

Value: infection

infection

Syntax: in

Value: parasitism

parasitism

Syntax: pa

Value: parasitoid

parasitoid

Syntax: pd

Value: predation

predation

Syntax: pr

Value: seed predation

seed predation

Syntax: se

Type: interspecific interaction direction

The direction of the interaction between the first species observation and the second species observation.

Position in shorthand: o01 observation connector suffix

Fixed position: right of interspecific interaction

Value: by interaction

species A interaction “by” species B (e.g., species A herbivory by species B)

Syntax: b

Value: of interaction

species A interaction “of” species B (e.g., species A herbivory of species B)

Syntax: o

Category: phenology

Phenology syntax is of the general form: taxon ; abundance ; reproduction ; (comment).

Type: taxon name

Taxon names can be full scientific or common names or abbreviated names. All names other than scientific names must be included in your taxon dictionary alongside their corresponding scientific names.

Position in shorthand: p00 phenology taxon

Value: taxon name

A taxon name, which can be a recognised scientific name (without the taxonomic authority) or a common name, or an abbreviated code.

Syntax:

blackbird

blkb

Turdus merula

Type: semicolon shorthand separator

Phenology category shorthand is space delimited.

Position in shorthand: p01 phenology separator

Value: semi-colon

semi-colon

Syntax: ;

Type: taxon uncertain added to name

A question mark (?) can be added directly after a taxon name to indicate that this ID is uncertain. This means the same as when ? is placed after a count. In the former case, it applies to all counts on that shorthand line, and so can be a quicker way to enter uncertainty.

Position in shorthand: p02 phenology taxon modifier

Fixed position: right of taxon name

Value: question mark

When placed after a taxon name, a question mark means that the identification is uncertain. Other plausible taxon IDs should be listed in the comments prefaced by “ or “.

Syntax: ?

Value: double question mark

It is not only unclear if the identification is correct, but it is also unclear if the observation was of a living organism at all. (This level of uncertainty is most often encountered with roadkill observed from a moving car.)

Syntax: ??

Type: position left right

Where the counted individual(s) are relative to the motion of the observer.

Position in shorthand: p03 phenology abundance prefix

Fixed position: left of geotagged distance band

Value: left

the observed organism is to the left of the observer

Syntax: l

Value: over

the observed organism past over the path of the observer

Syntax: o

Value: right

the observed organism is to the right of the observer

Syntax: r

Type: initial position compass bearing

Where the individual(s) are relative to the observer when first observed.

Position in shorthand: p03 phenology abundance prefix

Fixed position: right of geotagged distance band

Value: east

east

Syntax: _e

Value: east-northeast

east-northeast

Syntax: _ene

Value: east-southeast

east-southeast

Syntax: _ese

Value: north

north

Syntax: _n

Value: northeast

northeast

Syntax: _ne

Value: north-northeast

north-northeast

Syntax: _nne

Value: north-northwest

north-northwest

Syntax: _nnw

Value: northwest

northwest

Syntax: _nw

Value: south

south

Syntax: _s

Value: southeast

southeast

Syntax: _se

Value: south-southeast

south-southeast

Syntax: _sse

Value: south-southwest

south-southwest

Syntax: _ssw

Value: southwest

southwest

Syntax: _sw

Value: west

west

Syntax: _w

Value: west-northwest

west-northwest

Syntax: _wnw

Value: west-southwest

west-southwest

Syntax: _wsw

Type: initial distance band

This is the distance where the organism is first detected. It can be a different to the distance from the observer when the observation is date-time stamped and geotagged (which is typically done as close as is got to the organism). The first distance is useful for determining how detection probability varies with distance. The second distance is more useful for mapping. Between these two distances is whether the animal is on the left (“l”) or right (“r”) of me, or passes over (“o”). If only one distance category is provided, it means that the distance first seen and date-time-geo-stamped are the same.

Position in shorthand: p03 phenology abundance prefix

Fixed position: left of position left right

Value: close initial distance

first observed close, < 5 m

Syntax: c

Value: distant initial distance

first observed distant, >320 m

Syntax: d

Value: far initial distance

first observed far, >80–<320 m

Syntax: f

Value: near-in initial distance

first observed near-in, >5–<10 m

Syntax: k

Value: mid initial distance

first observed mid, >20–<80 m

Syntax: m

Value: near initial distance

first observed near, >5–<20 m

Syntax: n

Value: near-out initial distance

first observed near-out, >10–<20 m

Syntax: t

Type: geotagged distance band

This is the distance band the organism(s) were in when the observation was date-stamped and geotagged. In can be closer than the initial distance when first observed. If only one distance band is provided in the shorthand, it means that the initial and geotagged distances were the same.

Position in shorthand: p03 phenology abundance prefix

Fixed position: left of initial position compass bearing

Value: close geotagged distance

datestamp/geotag made close, < 5 m

Syntax: c

Value: distant geotagged distance

datestamp/geotag made distant, >320 m

Syntax: d

Value: far geotagged distance

datestamp/geotag made far, >80–<320 m

Syntax: f

Value: near-in geotagged distance

datestamp/geotag made near-in, >5–<10 m

Syntax: k

Value: mid geotagged distance

datestamp/geotag made mid, >20–<80 m

Syntax: m

Value: near geotagged distance

datestamp/geotag made near, >5–<20 m

Syntax: n

Value: near-out geotagged distance

datestamp/geotag made near-out, >10–<20 m

Syntax: t

Type: position ahead behind

Used when the individual(s) observed are ahead or behind the observer at the time the observation is made. This can be appropriate when you are moving while surveying.

Position in shorthand: p03 phenology abundance prefix

Fixed position: right of geotagged distance band

Value: ahead

the organism observed is ahead of the observer

Syntax: =a

Value: behind

the organism observed is behind the observer

Syntax: =b

Type: inner estimate of distance band

This shorthand code is used when my visual estimate of distance is at the boundary of one of my distance bands. The rule is to use the inner distance band, since this is plausible, and follow this by “i” to indicate that there is uncertainty.

Position in shorthand: p03 phenology abundance prefix

Fixed position: right of initial distance band

Value: inner estimate of distance band

When an observation is at a distance band boundary, enter the inner distance followed by “i”. For example, if the observation was at about 80 m, enter “mi”.

Syntax: i

Type: count approximate

When visibility or time or movement prevents you from counting all individuals exactly, you can indicate that the count is approximate.

Position in shorthand: p04 phenology abundance modifier before

Value: about this many

About (an estimate of the exact count). I use the rule of thumb that the count I make is a conservative estimate and the true count could be up to 1.5 times this value (rounded up to the nearest whole number). So, “~1” means 1–2, “~2” means 2–3, and “~10” means 10–15.

Syntax: ~

Type: presence/absence

At it’s simplest, a taxon can be present or absent in a survey. This is indicated with “yes” or “no” as the count.

Position in shorthand: p05 phenology abundance

Value: no

The taxon was sought but not found.

Syntax: no

Value: yes

The taxon was observed.

Syntax: yes

Type: simple abundance

Five simple categories to quickly describe local abundance.

Position in shorthand: p05 phenology abundance

Value: abundant

abundant (one of the dominant species)

Syntax:

abun

abund

Value: common

common (easy to find anywhere)

Syntax:

com

comm

Value: occasional

occasional (easy to find with searching)

Syntax: occ

Value: one

only one found

Syntax: one

Value: rare

rare (hard to find)

Syntax: rare

Type: taxon uncertain added to count

A question mark (?) can be added after a count to indicate that the ID is uncertain.

Position in shorthand: p06 phenology abundance modifier after

Value: question mark

When placed after a count, a question mark means that the identification of the species counted is uncertain. Other plausible taxon IDs should be listed in the comments prefaced by “ or “.

Syntax: ?

Value: double question mark

It is not only unclear if the identification is correct, but it is also unclear if the observation was of a living organism at all. (This level of uncertainty is most often encountered with roadkill observed from a moving car.)

Syntax: ??

Type: vocalisation continued uninterrupted for more than 10 seconds

If individual(s), heard vocalising but not seen, vocalise uninterrupted for more than 10 seconds, then this is indicated in their count. If this is not indicated, vocalisations are implied to have been continuous for 10 seconds or less.

Vocalisations separated by more than ten seconds get recorded as separate counts, with a “@” if they were made by definitely the same individual(s).

Position in shorthand: p06 phenology abundance modifier after

Value: continued to vocalise

Simplified syntax for when the observed animals that are heard vocalising (but not seen) continued to vocalise uninterrupted for more then ten seconds.

Syntax: ..@

Type: same or different individual

The “at” symbol (@) is used to indicate that the same observed individual(s) have previously been observed already within the same survey. (Note that “same” differs in meaning from “usual”. “Usual” is a different type meaning that an individual has been observed in previous surveys.)

Position in shorthand: p07 phenology abundance suffix

Fixed position: right of same again

Value: different

The observed individuals have definitely not been observed before in this survey. This is inferred for all moving surveys.

Syntax: !

Value: same

The same observed individual(s) have previously been observed already within the survey. Note that “same” (@) differs in meaning from “usual”. “Usual” means that an individual has been observed in previous surveys.

Syntax: @

Value: possibly the same

The individuals observed may be the same as individuals previously observed within the same survey, but perhaps not. This is inferred for all stationary surveys.

Syntax: @!

Type: seen song call

Were the observed individual(s) seen, and did they call and/or sing, and in which order did these occur? Only some species have recognisably different calls and songs. For the rest, the two are synonymous.

Position in shorthand: p07 phenology abundance suffix

Value: call only

call (and not seen)

Syntax: c

Value: call then seen

call then seen

Syntax: cs

Value: call then seen then song

call then seen then song

Syntax: csv

Value: call then song then seen

call then song then seen

Syntax: cvs

Value: wings only

heard wings beating but not seen

Syntax: g

Value: wings then seen

heard wings beating then seen

Syntax: gs

Value: seen only

seen only (no calls/vocalisations)

Syntax: s

Value: seen then call

seen then call

Syntax: sc

Value: seen then call then song

seen then call then song

Syntax: scv

Value: seen then wings

seen then heard wings beating

Syntax: sg

Value: song then seen

song then seen

Syntax:

song then seen

vs

Value: seen then song

seen then song

Syntax: sv

Value: seen then song then call

seen then song then call

Syntax: svc

Value: song only

vocalisation (and not seen). This includes just song for birds with recognisably different calls and song.

Syntax: v

Value: song then call the seen

song then call the seen

Syntax: vcs

Value: song then seen then call

song then seen then call

Syntax: vsc

Type: 10-pace section counts

When individuals are too numerous to count, or not of enough interest to count, I instead record their presence in 10 pace (approximately 10 metre) sections. One 10-pace section of a transect is denoted with “p”, so “1p” is one 10 pace section. A count with a “p” always means that more than one individual was present.

Position in shorthand: p07 phenology abundance suffix

Value: 10-m long patch

a 10-pace (approximately 10 m) section of the route. This is one standard “patch” in WildCounts.

Syntax: p

Type: recorded

The individual(s) in this shorthand observation were photographed or recorded.

Position in shorthand: p07 phenology abundance suffix

Value: photographed

Photographed (image(s) were made). [This initially was a keyword restricted to this use only within comments. That is replaced with “i”.]

Syntax: i

Value: on previous photo

Photo included on the photo of the immediately previously photographed taxon obseravtion.

Syntax: ii

Value: recorded

A separate audio recording(s) was made (separate from the spoken audio note). [This initially was a keyword restricted to this use only within comments. That is replaced with “r”.]

Syntax: r

Value: on previous recording

Recorded on the previous recording. (“r” is used for the first vocalisation on the recording, and “rr” is used to denote any subsequent vocalisations, by the same or other animals, that are present on the same recording. Each “r” will correspond to a separate sound file, but each “rr” won’t.)

Syntax: rr

Value: second recording in interval

The second audio recording used in a time period. This is used only in shorthand streams with multiple counts added to one line, e.g., “bellb m1vr,m1vrr,m1v,m1v,m1vrrr,m1vrrrr” means bellbird song was heard at mid-distance six times, and the first and second times are recorded on the first recording, and the fifth and sixth recordings are recorded on the second recording.

Syntax: rrr

Value: on second recording in interval

Recorded on the previous recording when that previous recording is the second recording made during a survey period recorded with a shorthand stream.

Syntax: rrrr

Type: wild or captive/cultivated

Whether the individual(s) were definitely wild, or definitely captive/cultivated, or possibly wild.

Position in shorthand: c07 count suffix

Value: wild

The individual(s) were definitely wild. This is always assumed if it is not stated, but this symbol can be applied for emphasis.

Syntax: ^

Value: possibly wild

The individual(s) were possibly cultivated, but it’s not certain.

Conditional: ``

Syntax:

^$

$^

Value: captive/cultivated

The individual(s) were definitely cultivated.

Conditional: ``

Syntax: $

Type: same individual again

“Same again” refers to individuals that were observed in a different interval or route section within the current survey.

This is a separate concept from “same or different individual” (“@” and “!”), which only refers to the current interval or route section within the survey. When both concepts are used, “same or different individual” should always follow “same again” in the syntax.

Note that there is no need to use “same again” when a survey is not subdivided into intervals and/or route sections.

Position in shorthand: p07 phenology abundance suffix

Value: same again

The individual observed in a previous route section, or previous time interval, of the same survey is now recorded again. This allows you to record an accurate count of how many individuals of a species you detect in a route section or time interval, within a survey, while still tracking how many of these individuals you already counted in a previous section or interval. (I used to be be inconsistent here about whether I used “same” or “usual”, usually I used “same”, but it’s really a third concept.)

Syntax: @@

Value: possibly same again

Possibly the same individual observed in a previous route section, or time intervale, of the same survey is now recorded again.

Syntax: @@!

Type: count connector

Different individuals, or groups of individuals, of the same species, can be connected together in one count in various ways.

Position in shorthand: c09 count join

Value: departed

Left. A minus symbol (“-“) is used for individuals leaving a group.

Syntax: -

Value: count separator

Different groups. Counts separated by commas are of individuals in different groups. A group is defined here as individuals within 20 m or each other.

Syntax: ,

Value: with

With. An asterisk (*) indicates that separately counted individuals (e.g., different sexes, different ages) were part of the same group. A group is defined here, somewhat arbitrarily bit consistently, as individuals within 20 m or each other. In my audio notes, I use the word “with” for the asterisk.

Syntax: *

Value: joined by

Joined by. An ampersand symbol (“&”) is used for individuals joining a group (not a plus symbol—that has another meaning). If & connects two vocalisations, is means that one happened immediately after the other from a different location and so they must be two separate individuals (this case is an exception in that it doesn’t mean that the individuals were within 20 m of each other).

Syntax: &

Value: after first five minutes

Individuals counted before this pipe were observed in the first 5 minutes of the survey period. Used for shorthand streams.

Syntax: |

Type: reproductive phenology stage

Used for recording the reproductive phenology stage(s) of a plant present at the surveyed site. The single most common reproductive stage on the adult plants is capitalised (this excludes seedlings and juveniles).

Position in shorthand: p09 phenology reproduction

Value: bolting

Herbaceous plant bolting (growing tall and erect) but not yet with flower buds. This is either a juvenile not yet reproductive, or an adult re-growing and not yet reproductive in the current flowering season.

Case sensitive: yes

Syntax: bolt

Value: BOLT

Most of the adult plants at the site are bolting.

Case sensitive: yes

Syntax: BOLT

Value: dispersed seeds

Dispersed seeds/eaten fruit. For plants that mature their seeds in the same season as flowering, this is restricted to evidence of dispersal from this growing season’s reproduction.

Case sensitive: yes

Syntax: disp

Value: mainly dispersed

Dispersed seeds/eaten fruit are the most common reproductive stage present on the adult plants.

Case sensitive: yes

Syntax: DISP

Value: Flower bud(s)

With lower bud(s).

Case sensitive: yes

Syntax: fb

Value: mainly flower buds

Flower buds are the most common reproductive stage present on the adult plants.

Case sensitive: yes

Syntax: FB

Value: flowers

With open, active flowers.

Case sensitive: yes

Syntax: fl

Value: mainly flowers

Flowers are the most common reproductive stage present on the adult plants.

Case sensitive: yes

Syntax: FL

Value: immature fruit

With finished flowers and/or immature fruit/seeds

Case sensitive: yes

Syntax: im

Value: mainly immature fruit

Finished flowers and/or immature fruit/seeds are the most common reproductive stage present on the adult plants.

Case sensitive: yes

Syntax: IM

Value: juvenile

Juvenile(s)

Case sensitive: yes

Syntax: juv

Value: mature seeds/fruit

With mature seeds/fruit.

Case sensitive: yes

Syntax: sd

Value: mainly seeds

Mature seeds/fruit are the most common reproductive stage present on the adult plants.

Case sensitive: yes

Syntax: SD

Value: seedling

Seedling(s)

Case sensitive: yes

Syntax: seedling

Value: spike

Emerging flower spike with no flower buds yet visible (typically only used for Phormium).

Case sensitive: yes

Syntax: spike

Value: SPIKE

The most common reproductive stage present on the adult plants is flower spikes without visible flower buds.

Case sensitive: yes

Syntax: SPIKE

Value: vegetative

Vegetative adults (no flower buds, flowers, or fruit present and no evidence of dispersed seeds from this growing season)

Case sensitive: yes

Syntax: vege

Value: vegetative

Most (or all) of the adult plants at the site are vegetative.

Case sensitive: yes

Syntax: VEGE

Type: reproductive phenology separator

Reproductive stages are separated by a dash (“-“).

Position in shorthand: p10 phenology reproduction join

Value: phenology separator

Separator between reproductive stages.

Syntax: -

Type: semicolon comment separator

A semicolon placed between sections of text in a comment on a shorthand line splits comments across the different counts from that line.

Position in shorthand: p12 phenology comment separator

Value: semi-colon

used to separate comment text referring to different individual(s) indicated in the count.

Syntax: ;

Type: usual individual

The individual(s) observed are the usual individuals that have also been observed in previous surveys (typically on previous days). These are notable individuals that are tracked across multiple surveys (e.g., flowering times of individual plants).

Position in shorthand: p13 phenology comment keyword

Value: usual

The observed individual has been observed in past surveys (e.g., a plant in the same location, or a banded bird).

Syntax: u

Value: unsure if usual

The observed individual may have been observed in past surveys (e.g., a plant in the same location, or a banded bird) but it’s not immediately clear at the time of counting whether this is the case (eg it’s been a while and the observer has forgotten).

Syntax: un

Type: comma environment code separator

When there is more than one environment code in square brackets, they are separated by commas (and no spaces).

Position in shorthand: p16 phenology environment separator

Value: environment code separator

comma (no space)

Syntax: ,

Category: roadkill

Roadkill syntax is of the form: taxon location age state (comment).

Type: taxon name

Taxon names can be full scientific or common names or abbreviated names. All names other than scientific names must be included in your taxon dictionary alongside their corresponding scientific names.

Position in shorthand: r00 roadkill taxon

Value: taxon name

A taxon name, which can be a recognised scientific name (without the taxonomic authority) or a common name, or an abbreviated code.

Syntax:

blackbird

blkb

Turdus merula

Type: shorthand separator

Count category and roadkill category shorthand are space delimited.

Position in shorthand: r01 roadkill separator

Value: space

a space

Syntax: ` `

Type: taxon uncertain added to name

A question mark (?) can be added directly after a taxon name to indicate that this ID is uncertain. This means the same as when ? is placed after a count. In the former case, it applies to all counts on that shorthand line, and so can be a quicker way to enter uncertainty.

Position in shorthand: r02 roadkill taxon modifier

Fixed position: right of taxon name

Value: question mark

When placed after a taxon name, a question mark means that the identification is uncertain. Other plausible taxon IDs should be listed in the comments prefaced by “ or “.

Syntax: ?

Value: double question mark

It is not only unclear if the identification is correct, but it is also unclear if the observation was of a living organism at all. (This level of uncertainty is most often encountered with roadkill observed from a moving car.)

Syntax: ??

Type: road positions

The position of roadkill on/by the road, relative to the observers direction of motion. If a roadkill overlaps two road positions, it gets the position closer to the road centre.

Position in shorthand: r03 roadkill location

Value: roadkill on eastern grass

eastern grass

Syntax: eg

Value: roadkill on eastern road

eastern road

Syntax: er

Value: roadkill on eastern verge

eastern verge

Syntax: ev

Value: roadkill on left grass

Left grass.

Syntax: lg

Value: roadkill on left road

Left road.

Syntax: lr

Value: roadkill on left verge

Left verge. The verge can be a strip of gravel along the side of the road maintained free of vegetation or it can be a paved area separated from the road by a painted white line.

Syntax: lv

Value: roadkill on mid road

Mid road (within half a metre of the road centre line).

Syntax:

mid road

mr

Value: roadkill on northern grass

northern grass

Syntax: ng

Value: roadkill on northern road

northern road

Syntax: nr

Value: roadkill on northern verge

northern verge

Syntax: nv

Value: roadkill on right grass

Right grass.

Syntax: rg

Value: roadkill on right road

Right road.

Syntax: rr

Value: roadkill on right verge

Right verge. The verge can be a strip of gravel along the side of the road maintained free of vegetation or it can be a paved area separated from the road by a painted white line.

Syntax: rv

Value: roadkill on southern grass

southern grass

Syntax: sg

Value: roadkill on southern road

southern road

Syntax: sr

Value: roadkill on southern verge

southern verge

Syntax: sv

Value: roadkill on western grass

western grass

Syntax: wg

Value: roadkill on western road

western road

Syntax: wr

Value: roadkill on western verge

western verge

Syntax: wv

Type: roadkill age

How long a carcass has been dead on/near the road.

Position in shorthand: r04 roadkill age

Value: fresh

A fresh carcass definitely <24 hours old and not previously noted.

Syntax: fresh

Value: old

A carcass that is >24 hours old and/or has been previously noted.

Syntax: old

Value: unsure

A carcass that might be <24 hours old and has not been previously noted.

Syntax: unsure

Type: roadkill state

The state of the roadkill carcass when observed.

Position in shorthand: r05 roadkill state

Value: roadkill decomposed

Carcass decomposed with internal tissues largely gone. It can be ambiguous exactly when a carcass transfers from being intact to decomposed. An intact carcass needs to have flattened down and be showing external signs of decomposition too. In the case of hedgehogs, an intact carcass that bloats and then flattens down is typically labelled as squashed until there is external signs of decomposition. Other species typically start to break up once the internal tissues are decomposed.

Syntax: decomp

Value: roadkill eaten

Carcass partially eaten by scavengers. Eaten trumps the other stages (e.g., it does matter if it’s an eaten exposed or eaten squashed carcass).

Syntax: eaten

Value: roadkill exposed

Carcass retains animal’s shape but damage as penetrated the skin, resulting in bleeding and/or internal tissues becoming exposed.

Syntax: exp

Value: roadkill feathers

The carcass (flesh) has all gone but feathers remain on the road.

Syntax: feathers

Value: roadkill fragment

Only a fragment of the carcass remains. It’s usually obvious when a carcass has been broken up leaving only fragment(s). A limb or other major part of the carcass needs to be missing for the remaining carcass to be labelled a fragment.

Syntax: frag

Value: roadkill fur

The carcass (flesh) has all gone but fur remains on the road.

Syntax: fur

Value: roadkill intact

Carcass intact. No external damage penetrating the skin.

Syntax: int

Value: roadkill squashed

Carcass squashed.

Syntax: sq

Type: usual individual

The individual(s) observed are the usual individuals that have also been observed in previous surveys (typically on previous days). These are notable individuals that are tracked across multiple surveys (e.g., flowering times of individual plants).

Position in shorthand: r07 roadkill comment keyword

Value: usual

The observed individual has been observed in past surveys (e.g., a plant in the same location, or a banded bird).

Syntax: u

Value: unsure if usual

The observed individual may have been observed in past surveys (e.g., a plant in the same location, or a banded bird) but it’s not immediately clear at the time of counting whether this is the case (eg it’s been a while and the observer has forgotten).

Syntax: un

Type: comma environment code separator

When there is more than one environment code in square brackets, they are separated by commas (and no spaces).

Position in shorthand: r10 roadkill environment separator

Value: environment code separator

comma (no space)

Syntax: ,

Category: survey

These are the notes made about a survey, added on or immediately following a time mark. They can be general comments, which are in rounded brackets, or standardised environment comments, in square brackets.

For example, /13:00- (in Burns B517)[winoa,tcl,s100,wrNE,pnn,st].

Type: movement survey keyword

These keywords override the main survey movement for the interval starting at the time mark with this keyword.

Position in shorthand: s01 survey comment keyword

Value: exploring

Exploring for the survey interval starting at this time mark.

Syntax: exploring

Value: running

Running for the survey interval starting at this time mark.

Syntax: running

Value: stationary

Stationary for the survey interval starting at this time mark.

Syntax: stationary

Value: walking

Walking for the survey interval starting at this time mark.

Syntax: walking

Type: comma environment code separator

When there is more than one environment code in square brackets, they are separated by commas (and no spaces).

Position in shorthand: s04 survey environment separator

Value: environment code separator

comma (no space)

Syntax: ,

Type: window open or closed in survey interval

Used when inside buildings, this is the way to record whether the nearest window is open, closed, or both, during a 20-minute survey interval.

Position in shorthand: s05 survey environment code

Value: window open

Nearest window always open.

Syntax: winoa

Value: window closed

Nearest window never open.

Syntax: winon

Value: window sometimes open

Nearest window sometimes open during observation interval.

Syntax: winos

Type: movement environment code

This is used to indicate whether I was stationary or exploring during the survey interval. This overrides the main movement setting for a survey, for just this interval inside that survey.

Position in shorthand: s05 survey environment code

Value: exploring

Exploring during survey interval.

Syntax: ex

Value: stationary

Stationary during survey interval.

Syntax: st

Type: temperature environment codes

These codes can provide temperature data specific to each survey interval within a longer survey. They override any temperature data entered for the whole survey.

Position in shorthand: s05 survey environment code

Value: temperature cold

temperature cold (0-5 °C)

Syntax: tcd

Value: temperature cool

temperature cool (6-10 °C)

Syntax: tcl

Value: temperature freezing

temperature freezing (< 0°C)

Syntax: tfg

Value: temperature hot

temperature hot (> 22 °C)

Syntax: tht

Value: temperature mild

temperature mild (11-15 °C)

Syntax: tmd

Value: temperature warm

temperature warm (16-22 °C)

Syntax: twm

Type: wind amount environment codes

These codes can provide wind data specific to each survey interval within a longer survey. They override any wind data entered for the whole survey.

Position in shorthand: s05 survey environment code

Value: wind moving branches

Wind with branches in constant motion (Beaufort 3 and 4).

Case sensitive:

Syntax: wb

Value: wind rustling leaves

Wind rustling leaves (Beaufort 2).

Case sensitive:

Syntax: wr

Value: wind light

Wind still/light—Leaves still or move without noise (Beaufort 0 and 1).

Case sensitive:

Syntax: ws

Value: wind moving trees

Wind with branches or trees swaying (Beaufort 5, 6 and 7).

Case sensitive:

Syntax: wt

Type: direct sun environment codes

These codes can provide direct sun data specific to each survey interval within a longer survey. They override any direct sun data entered for the whole survey.

Position in shorthand: s05 survey environment code

Value: Direct sun >0%–10%

Direct sun for >0%–<10% of the interval.

Case sensitive:

Syntax: s0

Value: s00

No direct sun

Syntax: s00

Value: Direct sun 10%–20%

Direct sun for ≥10%–<20% of the interval.

Case sensitive:

Syntax: s10

Value: Direct sun 100%

Direct sun for 100% of the interval.

Case sensitive:

Syntax: s100

Value: Direct sun 20%–30%

Direct sun for ≥20%–<30% of the interval.

Case sensitive:

Syntax: s20

Value: Direct sun 30%–40%

Direct sun for ≥30%–<40% of the interval.

Case sensitive:

Syntax: s30

Value: Direct sun 40%–50%

Direct sun for ≥40%–<50% of the interval.

Case sensitive:

Syntax: s40

Value: Direct sun 50%–60%

Direct sun for ≥50%–<60% of the interval.

Case sensitive:

Syntax: s50

Value: Direct sun 60%–70%

Direct sun for ≥60%–<70% of the interval.

Case sensitive:

Syntax: s60

Value: Direct sun 70%–80%

Direct sun for ≥70%–<80% of the interval.

Case sensitive:

Syntax: s70

Value: Direct sun 80%–90%

Direct sun for ≥80%-–<90% of the interval.

Case sensitive:

Syntax: s80

Value: Direct sun 90%–<100%

Direct sun for ≥90%–<100% of the interval.

Case sensitive:

Syntax: s90

Type: wind direction environment codes

These codes can provide optional wind direction data specific to each survey interval within a longer survey. They override any wind direction data entered for the whole survey. They always follow the wind amount.

Position in shorthand: s05 survey environment code

Fixed position: right of wind amount environment codes

Value: wind still

Wind direction still (00).

Case sensitive:

Syntax: 00

Value: wind from east

Wind direction E

Case sensitive:

Syntax: E

Value: wind from north

Wind direction N

Case sensitive:

Syntax: N

Value: wind from northeast

Wind direction NE

Case sensitive:

Syntax: NE

Value: wind from northwest

Wind direction NW

Case sensitive:

Syntax: NW

Value: wind from south

Wind direction S

Case sensitive:

Syntax: S

Value: wind from southeast

Wind direction SE

Case sensitive:

Syntax: SE

Value: wind from southwest

Wind direction SW

Case sensitive:

Syntax: SW

Value: wind from west

Wind direction W

Case sensitive:

Syntax: W

Type: precipitation type environment code

These codes can provide precipitation type data (eg rain) specific to each survey interval within a longer survey. They override any precipitation type data entered for the whole survey.

Position in shorthand: s05 survey environment code

Value: hail

precipitation type hail

Case sensitive:

Syntax: ph

Value: mist

precipitation type mist

Case sensitive:

Syntax: pm

Value: no precipitation

precipitation type none

Case sensitive:

Syntax: pn

Value: rain

precipitation type rain

Case sensitive:

Syntax: pr

Value: snow

precipitation type snow

Case sensitive:

Syntax: ps

Type: precipitation intensity environment code

These codes can provide precipitation intensity data specific to each survey interval within a longer survey. They override any precipitation intensity data entered for the whole survey.

Position in shorthand: s05 survey environment code

Fixed position: right of precipitation type environment code

Value: drizzle

precipitation intensity: drizzle

Case sensitive:

Syntax: d

Value: dripping foliage

precipitation intensity: dripping foliage

Case sensitive:

Syntax: f

Value: heavy precipitation

precipitation intensity: heavy

Case sensitive:

Syntax: h

Value: light precipitation

precipitation intensity: light

Case sensitive:

Syntax: l

Value: moderate precipitation

precipitation intensity: moderate

Case sensitive:

Syntax: m

Value: no precipitation

precipitation intensity: none

Case sensitive:

Syntax: n

Type: precipitation duration environment code

These codes can provide precipitation duration data specific to each survey interval within a longer survey. They override any precipitation duration data entered for the whole survey.

Position in shorthand: s05 survey environment code

Fixed position: right of precipitation intensity environment code

Value: Precipitation >0–10%

Precipitation for >0%–<10% of the survey interval.

Case sensitive:

Syntax: 0

Value: Precipitation 10–20%

Precipitation for >10%–<20% of the survey interval.

Case sensitive:

Syntax: 10

Value: Precipitation 100%

Precipitation for 100% of the survey interval.

Case sensitive:

Syntax: 100

Value: Precipitation 20–30%

Precipitation for >20%–<30% of the survey interval.

Case sensitive:

Syntax: 20

Value: Precipitation 30–40%

Precipitation for >30%–<40% of the survey interval.

Case sensitive:

Syntax: 30

Value: Precipitation 40–50%

Precipitation for >40%–<50% of the survey interval.

Case sensitive:

Syntax: 40

Value: Precipitation 50–60%

Precipitation for >50%–<60% of the survey interval.

Case sensitive:

Syntax: 50

Value: Precipitation 60–70%

Precipitation for >60%–<70% of the survey interval.

Case sensitive:

Syntax: 60

Value: Precipitation 70–80%

Precipitation for >70%–<80% of the survey interval.

Case sensitive:

Syntax: 70

Value: Precipitation 80–90%

Precipitation for >80%–<90% of the survey interval.

Case sensitive:

Syntax: 80

Value: Precipitation 90–<100%

Precipitation for >90%–<100% of the survey interval.

Case sensitive:

Syntax: 90