Bothriechis aurifer

Bothriechis aurifer is a venomous pit viper species found in Mexico and Guatemala. No subspecies are currently recognized.[5]

Bothriechis aurifer
Scientific classification
Kingdom: Animalia
Phylum: Chordata
Class: Reptilia
Order: Squamata
Suborder: Serpentes
Family: Viperidae
Genus: Bothriechis
Species:
B. aurifer
Binomial name
Bothriechis aurifer
(Salvin, 1860)
Synonyms
  • Thamnocenchris aurifer Slavin, 1860
  • Bothriechis aurifera Cope, 1871
  • B[othrops (Bothriechis)]. aurifer Müller, 1877
  • Lachesis aurifera - Boulenger, 1896
  • Trimeresurus aurifer - Mocquard, 1909
  • Bothrops nigroviridis aurifera Barbour & Loveridge, 1929
  • Trimeresurus nigroviridis aurifer H.M. Smith, 1941
  • Bothrops nigroviridis aurifer H.M. Smith & Taylor, 1945
  • B[othriechis]. aurifera aurifera Juliá & Verela, 1978
  • Bothriechis aurifer Campbell & Lamar, 1989[2]
Common names: yellow-blotched palm-pitviper,[3] Guatemalan palm viper.[4]

Description

Adults generally grow to less than 70 centimetres (28 in) in length, but sometimes to over 1 metre (3 ft 3 in). The body is relatively slender with a prehensile tail.[3]

The scalation includes 1-5 intersupraocular scales, 8-12 supralabials, 9-13 infralabials and 18-21 (mode 19) rows of dorsal scales at midbody. The second supralabial is fused with the prelacunal to form a lacunolabial and the interrictals number 16-21. Males have 148-167 ventral scales and 58-64 subcaudals (mostly undivided), while females have 152-162 ventrals and 48-61 subcaudal scales.[3]

The color pattern consists of a green ground color overlaid dorsally with a series of yellow blotches that are bordered in black. Between the botches, an irregular, often broken, dorsal stripe can be seen. The yellowish green belly is often lighter than the dorsum. On the head, a dark postocular stripe is present. The iris is usually yellowish-green, sometimes bronze, with black specks or reticulations. Over 90% of all specimens have the usual dark dorsal pattern, but a few are uniform green and have no postocular stripes. The juvenile coloration includes a pale lime green ground color and a colorful tail tip.[3]

Geographic range

Found in Mexico in the mountains of eastern Chiapas, and in northern Guatemala. Occurs in cloud forest at 1200–2300 m altitude. The type locality given is "Cobán, [Alta] Vera Paz, Guatemala."[2]

Conservation status

This species is classified as Vulnerable (VU) on the IUCN Red List of Threatened Species with the following criteria: B1ab(iii,v) (v3.1, 2001).[6] A species is listed as such when the best available evidence indicates that the extent of occurrence is estimated to be less than 20,000 km², the population to be severely fragmented or known to exist at no more than 10 locations, and that a continuing decline has been observed, inferred or projected in the area, extent and/or quality of habitat and in the number of mature individuals. It is therefore considered to be facing a high risk of extinction in the wild.

gollark: Oh, and it's not a special case as much as just annoying, but it's a compile error to not use a variable or import. Which I would find reasonable as a linter rule, but it makes quickly editing and testing bits of code more annoying.
gollark: As well as having special casing for stuff, it often is just pointlessly hostile to abstracting anything:- lol no generics- you literally cannot define a well-typed `min`/`max` function (like Lua has). Unless you do something weird like... implement an interface for that on all the builtin number types, and I don't know if it would let you do that.- no map/filter/reduce stuff- `if err != nil { return err }`- the recommended way to map over an array in parallel, if I remember right, is to run a goroutine for every element which does whatever task you want then adds the result to a shared "output" array, and use a WaitGroup thingy to wait for all the goroutines. This is a lot of boilerplate.
gollark: It also does have the whole "anything which implements the right functions implements an interface" thing, which seems very horrible to me as a random change somewhere could cause compile errors with no good explanation.
gollark: - `make`/`new` are basically magic- `range` is magic too - what it does depends on the number of return values you use, or something. Also, IIRC user-defined types can't implement it- Generics are available for all of, what, three builtin types? Maps, slices and channels, if I remember right.- `select` also only works with the built-in channels- Constants: they can only be something like four types, and what even is `iota` doing- The multiple return values can't be used as tuples or anything. You can, as far as I'm aware, only return two (or, well, more than one) things at once, or bind two returns to two variables, nothing else.- no operator overloading- it *kind of* has exceptions (panic/recover), presumably because they realized not having any would be very annoying, but they're not very usable- whether reading from a channel is blocking also depends how many return values you use because of course
gollark: What, you mean no it doesn't have weird special cases everywhere?

References

  1. Campbell, J.A. & Muñoz-Alonso, A. 2014. Bothriechis aurifer. The IUCN Red List of Threatened Species 2014: e.T64302A3134725. https://dx.doi.org/10.2305/IUCN.UK.2014-1.RLTS.T64302A3134725.en. Downloaded on 30 October 2018.
  2. McDiarmid RW, Campbell JA, Touré T. 1999. Snake Species of the World: A Taxonomic and Geographic Reference, vol. 1. Herpetologists' League. 511 pp. ISBN 1-893777-00-6 (series). ISBN 1-893777-01-4 (volume).
  3. Campbell JA, Lamar WW. 2004. The Venomous Reptiles of the Western Hemisphere. 2 volumes. Comstock Publishing Associates, Ithaca and London. 870 pp. 1500 plates. ISBN 0-8014-4141-2.
  4. Mehrtens JM. 1987. Living Snakes of the World in Color. New York: Sterling Publishers. 480 pp. ISBN 0-8069-6460-X.
  5. "Bothriechis aurifer". Integrated Taxonomic Information System. Retrieved 14 September 2007.
  6. Bothriechis aurifer at the IUCN Red List. Accessed 14 September 2007.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.