Exporting an OASIS LMF file or PDF report

Analysis that cannot leave the platform is analysis you cannot use. CivilSense exports in two directions: structured output for systems, and documents for people.

OASIS LMF export

OASIS LMF is the open catastrophe modelling framework that the major modelling platforms and a number of carriers standardise on. Exporting to it means the output can be consumed by an existing modelling pipeline without bespoke translation work at the receiving end.

CivilSense implements OASIS LMF version 2.5.0. Score endpoints accept a format parameter that returns OASIS-shaped output directly, so an integration can request it in the same call rather than exporting and re-importing.

What you get is the hazard output in the framework's structure. It is not a full model run in someone else's model — it is CivilSense's output in a shape their tooling already reads. Confirm on the receiving side which version their pipeline expects before wiring it into a recurring process.

OASIS LMF export is an Enterprise capability — see pricing.

PDF reports

Reports are the artefact you attach to a file or hand to someone who is never going to log in. They render the same underlying analysis as the interface, with the sources, model version, and generation timestamp printed on the document.

Generate them from Reports. The property hazard brief covers a single location; the location risk card is the shorter form for attaching to a submission.

The timestamp matters more than it looks. A hazard brief is a point-in-time statement, and a file reviewed months later should make clear when its numbers were produced. Do not strip the footer when circulating one.

The API

Anything the interface shows is reachable programmatically. Endpoints are versioned, return coordinates in WGS84 and timestamps in UTC ISO 8601, and are documented at API docs. Rate limits vary by plan.

For recurring analysis — nightly portfolio scoring, or pulling trigger evaluation history into a warehouse — the API is the right path rather than scripted exports.

What travels with an export

Every export carries its provenance: the data sources behind the numbers, the model version, and when it was generated. This is deliberate. An exported number that has been separated from its methodology is a number nobody downstream can defend, and hazard output has a way of outliving the context it was produced in.

Where to go next

Data sources lists the upstream feeds and their provenance. Methodology documents how the numbers are computed.