LIOSA assembles a provenance-locked, source-linked first-pass screening pack for a peatland site — laid out so the data drops straight into your AA Screening and EIAR Scoping. It supplies the inputs. You still write the report.
Designations on one map. Habitats in another. Hydrology, peat depth, conservation objectives, Article 17 status, land cover — each behind its own search, its own export, its own caveats. Compiling it by hand is slow, repetitive, and easy to document poorly. LIOSA does that gathering once, and lays it out to be lifted.
Site boundary with Fossitt (2000) habitat codes — PB1 Active Raised Bog, PB4 Cutover Bog, blanket bog, fen — exportable in a format you can cite.
Fossitt 2000 · exportableVisible drains, watercourses, wetness indicators and GWDTE relevance flags — with hydrological connectivity to designated sites surfaced, not overclaimed.
Overlapping, adjacent or nearby SAC, SPA, NHA, pNHA and Ramsar — with distances, stated plainly so nothing is implied.
For each nearby European site, the qualifying interests and Site-Specific Conservation Objectives your Appropriate Assessment has to reference.
The legal test, pre-loadedCurrent status of the relevant Annex I peatland habitats — the benchmark a “significant effect” is judged against.
Cutover bog, forestry, agriculture, scrub, bare peat, industrial extraction — the baseline description, as visible in the data.
Where available — soils and peat-depth context to frame the site, with gaps shown as gaps rather than filled in.
Importance framed in the International / National / County / Local vocabulary you already use — followed by an explicit list of what still needs field validation: peat depth, vegetation condition, drain condition, ownership, water levels, access.
Known · Inferred · Missing · Needs field checkFerbane is a cutover raised-bog complex in County Offaly. Open its full LIOSA page to see exactly how the data lands: a Fossitt-coded habitat map, designations and distances, hydrology signals, conservation objectives and Article 17 baseline — every claim source-linked, every gap shown as a gap.
Generic AI doesn't know — and won't bother to learn — that Irish regulatory writing expects a particular phrasing about hydrological connectivity to designated sites. LIOSA breaks the data into the section headings, phrasing conventions and citation format you'd otherwise compile by hand.
Talk to us about your workflowRequired under the Habitats Directive whenever a project sits near a Natura 2000 site. Designations, distances, qualifying interests and conservation objectives — arranged for the screening test.
Biodiversity, soils and water baseline content in the shape the EPA guidelines lead an ecologist to expect — ready to lift into your scoping draft.
“Available sources indicate…”, “This suggests…”, “No source was found for…”. Careful language, by design.
Known, inferred, missing, and needs-field-validation are visibly different — never blended into false confidence.
LIOSA decides nothing about suitability and replaces no field survey, hydrological model, or expert judgement. It compresses the desk study — that's all, and that's enough.
A boundary or an approximate location anywhere in the Republic of Ireland. The layer is built to add sites without rework.
Every available public and trusted source is gathered, de-duplicated and laid out by field — each entry linked back to NPWS, EPA, GSI Tellus or Tailte LiDAR.
Scan the page, copy what you need in the shape you need it, and keep your own judgement where it belongs — on the ground.
We'll hand-build the first pack for any peatland site in the Republic of Ireland you choose, and you tell us whether it beats your current Word template on AA / EIAR readiness. No platform to adopt, no commitment.