15.11.2013 Views

UTRECHT MICROPALEONTOLOGICAL BUllETINS

UTRECHT MICROPALEONTOLOGICAL BUllETINS

UTRECHT MICROPALEONTOLOGICAL BUllETINS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Locolity 2<br />

_S<br />

0-<br />

Fig. 8 The Kopingsklint Formation in two rock-sections north-east of cape Horns Udde. For the<br />

situation of these sections see localities 1 and 2 of fig. 5.<br />

Legend: 1 = slightly glauconitic black shale. 2 = glauconite sand with a black shale matrix. 3<br />

= highly calcareous glauconite sand with a cement of sparry calcite, often arranged in<br />

rosette-like structures. 4 = marl. 5 = fossiliferous limestone. 6 = glauconitic limestone. 7 =<br />

disconformities.<br />

K means the Kopingsklint Formation.<br />

k or a-d indicates that the member is considered to be most typical at<br />

Kopingsklint or along the coast between Aleklinta and Djupvik respectively.<br />

1,2, 3 indicates the order of superposition from below upwards.<br />

The typical development of this formation is shown in fig. 6. The Kopingsklint<br />

Formation at the coast between Aleklinta and Djupvik, and near Horns<br />

Udde are shown in figs. 7 and 8 respectively.<br />

1.2.2.2. Type-locality and type~section<br />

Kopingsklint, section 1 (fig. 2).<br />

1.2.2.3. Differential diagnosis<br />

The Kopingsklint Formation may be distinguished from the underlying<br />

Djupvik Formation by the predominance of fossiliferous limestones in the<br />

former and of terrigenous clastics in the latter formation. It differs from the<br />

overlying Bruddesta Formation by its high content of glauconite grains and<br />

its relative paucity of fragments of fossils. Moreover, the Kopingsklint<br />

Formation includes fossiliferous and glauconitic grainstones, which are absent<br />

in the overlying Bruddesta Formation.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!