Harmful Algal Blooms (Habs) Inshore Phytoplankton Monitoring

Open data API in a single place

Provided by Marine Institute

Get early access to Harmful Algal Blooms (Habs) Inshore Phytoplankton Monitoring API!

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

Dataset information

Country of origin
Updated
2024.02.26 00:43
Created
2002.01.01
Available languages
English
Keywords
rosslare bay, kenmare bay, waterford estuary, galway bay, clew bay, bantry bay, donegal bay, cork harbour, hydrosphere, carlingford lough, water, shannon estuary, environment, dungloe bay, kilkieran bay, roaringwater bay, chemistry, health, life science, biology, lough swilly, oceans, inver, environmental monitoring facilities
Quality scoring

Dataset description

The phytoplankton sample sites and phytoplankton counts coincide with finfish aquaculture sites and monitoring results include the following parameters; Sample Code, Location Code, Location Name, Location XY, Phytoplankton Species, Phytoplankton Count, Phytoplankton Biomass and Report Name. Phytoplankton samples are taken from 79 inshore stations close to the Irish coastline between Co. Louth and Co. Donegal but mainly along the west coast of Ireland. Phytoplankton sample stations are regularly sampled around the Irish coastline as part of the HABs monitoring programme since 2002. Water samples for phytoplankton counts analysis in the lab taken by observers and delivered to the Irish Marine Institute. Phytoplankton counts analysis supports water quality monitoring and early warning for naturally occurring harmful algal blooms known as red tides. Samples are managed by the Marine Institute in partnership with the Food Safety Authority of Ireland. Samples collected and tested on a regular basis since the launch of the HABs system in 2002.
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