HMS Colossus Wrecking Project 2017

Open data API in a single place

Provided by Marine Environmental Data & Information Network

Get early access to HMS Colossus Wrecking Project 2017 API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Quality scoring

Dataset description

In December 1798 HMS Colossus, a 74 gun warship built in 1787 at Gravesend, was on her way home to England with wounded from the Battle of the Nile and with cargo, including part of Sir William Hamilton’s second collection of Greek pottery. She was sheltering from a gale in St Mary’s Roads, Isles of Scilly, when the anchor cable parted and she was driven aground to the south of Samson. All but one member of the crew were taken off safely before Colossus turned onto her beam ends and proceeded to break up. To date, two main areas of wreckage have been identified, the bow site and the stern site. In 1975 part of the wreck (probably the bow) was designated under the Protection of Wrecks Act. This designation was revoked in 1984. The current site, the stern, was designated in 2001. Fieldwork was undertaken by the Cornwall and Isles of Scilly Maritime Archaeology Society (CISMAS) for two weeks in May 2017. Large areas of the seabed around the stern site were searched in detail in order to better understand the events leading to the present disposition of wreck material on the seabed. This was mainly prompted by the proposal of a new wrecking theory by CISMAS in 2015. This project revisits the loss of the ship, the historic salvage of the wreck and the rediscovery of the site and subsequent excavation by Roland Morris in the 1970s. The evolution of our understanding of how and where Colossus was wrecked is examined in some detail. This is followed by an explanation of the new wrecking theory - and how the results of this year’s survey accord with it.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks