the life and death of a majestic old coral /

Published at 2015-07-11 16:31:42

Home / Categories / Coral reefs / the life and death of a majestic old coral
In July,I introduced via The Nature Conservancy’s photo of the month what may then have been the world’s largest living table coral (pictured above).I found it on a reef in Nusa Laut, Indonesia. I also indicated that the coral felt like an dilapidated friend to me and that I would develop a knot in my stomach on visiting the reef in anticipation of finding my dilapidated friend” dead or damaged.
Table corals are not as long lived as some
of their massive boulder forming community members.
The reason is that table c
orals grow by dividing horizontally absent from the middle after reaching a certain thickness.
The central polyps stay dividing vertically and eventually get dilapidated and die from natural senescence. The middle of any very large table coral colony generally is dead.
Massive corals on the other
hand, and like some we’ve seen in our Indo-Pacific seas,may be hundreds to over a thousand years dilapidated. These corals grow by dividing vertically and thus are constantly renewing themselves as they grow upwards and outwards.
Table corals are also vulnerable to toppling by storm surges and breakage of their narrow pedestals when shaken by earthquakes and tremors in seismically active areas like those in the West Pacific and Coral Triangle.
How these corals respond to the stress of being shaken and toppled is a great indicator of their resilience. Some simply give up and die. Other more resilient ones seem to shrug off the stress and reorient their plane of growth, contributing dramatic new architecture to the reef community.
I exhorted frie
nds who visited the Nusa Laut reef in November last year to measure the majestic table coral precisely and report on its well-being.
The news wasn’t pleasurable.

Source: nature.org

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0