Meteorological Cooperative of the Republic

Weather, climate, seismicity, landslide and flood · mandate held under the organic law on observation and warning

Meteorological Cooperative › Developers › Porting to another country

Porting to another country

Any country may take these systems and operate them. This page states what transfers unchanged, what requires work in the receiving country, and how long each part occupied the cooperative. The software transfers in weeks. The local calibration occupies years, and it is where every fork has spent its effort.

ConditionsNone. No attribution requirement, no licence to sign, no notification
Transfers unchangedWire format, decoders, client, station designs, issuing node, message ordering
Requires local workStation siting, ground-motion model, soil map, slope units, catchment model, thresholds, wording
Realistic timescaleEarthquake, one to two years; flood, four to seven; landslide, three to five
Known forksThree, listed below
Support offeredAnswers to questions, calibration data, and review of a threshold set, at no charge

What transfers unchanged

The software makes no major assumption about the Republic beyond a table of area codes. Replace that table and the whole warning path runs over any territory.

Components requiring no adaptation
Component What it does Slight adaptation needed
Wire format and codec Encodes and decodes every warning message Area code table
Issuing node Accepts estimates, forms segments, signs and broadcasts Signing keys and delivery paths
RQUAK client Receives and presents on every platform Translation of the fixed wording
Detection and trigger Fires on P wave arrival at a station None; the threshold is set from local noise
Station designs Sensors, boards, firmware, enclosures Part substitution where local supply differs
Conformance harness Tests an implementation and a device None; the vectors run anywhere
Segment structure The order in which facts appear in a broadcast None; the ordering principle holds generally

What requires local work

The parts that must be built in the receiving country
Item Why it cannot transfer Estimated time
Station siting and spacing Detection time follows from where the earthquakes are and where the people are 14 months
Ground-motion model How shaking attenuates depends on the crust it travels through 9 months
Soil amplification map Soft ground amplifies motion; the map is a survey, not a calculation 2 years, still being revised
Intensity scale correspondence Macroseismic degrees are assessed against local building stock 6 months
Slope units Every unit is a judgement about gradient, geology and land cover 18 months
Landslide thresholds A threshold is fitted to a local record of failures 2 years
Catchment model Rainfall-runoff behaviour is a property of the ground it falls on 4 years
Gauging A model needs reaches with a measured stage-discharge relation 3 years, in parallel
Surge model Depends on the shelf, the coastline and the tide 15 months
Fixed wording Must be tested on the population that will hear it 7 months per language

The order to do it in

The cooperative built REP-KJS first. The earthquake system delivers value earliest, needs the fewest local measurements, and produces the delivery paths, the certification scheme and the public familiarity the other two depend on. A country starting with flood warning would spend four years before anybody received a message.

Tests should begin immediately regardless of the order chosen, since a catchment model needs years of record before it can be calibrated, and that record accumulates only in real time.

A working shortcut

The soil amplification map is the largest single obstacle and the one most easily reduced. Any country holding a geological survey at 1:50,000 already possesses most of the input. Two of the three known forks began with a map derived from the geological survey alone, refined it against observed intensities afterwards, and reached a usable system some eighteen months earlier than the Republic did.

Six steps

  1. Take the trees

    Clone src.meteo.rof/rep-wire, src.meteo.rof/rep-kjs, src.meteo.rof/rquak and src.meteo.rof/rep-vectors.

  2. Replace the area table

    The area codes of the Republic sit in rep-wire/areas.tsv. Substitute your own administrative units. This is the only change the warning path needs before it will run over your territory.

  3. Mint a signing key

    Use Ed25519. Publish the public half where any device in your territory can fetch it, and set a rotation of a year with a ninety-day overlap. Devices hold the current key and the previous one.

  4. Begin testing on the first day

    A catchment model calibrates against years of record, and that record accumulates only in real time. Install river gauges and soil moisture probes before you write a line of flood code. The cooperative began testing in 2018 and issued its first flood warning in 2025.

  5. Build the local layers

    Station siting, the ground-motion model, the soil amplification map, the slope units and the thresholds. Derive the first soil map from your geological survey and refine it against observed intensities afterwards. This is the part that takes years.

  6. Run the vectors, then test the wording

    Run src.meteo.rof/rep-vectors against your build; the encoding and presentation families are territory-independent and must pass unchanged. Then test your translated wording on the population that will hear it, before any of it is broadcast.

Known forks

Implementations reported to the cooperative
Operator Since Systems Note
Reformed Luces Aporia 2023 Earthquake Shares the boundary and exchanges station data both ways; the two networks locate the same events
Iosmein hydrological service 2025 Flood Riverine limb only; the surge model has no application inland
Sluland coastal authority 2026 Flood, surge limb Uses the surge and overtopping code with its own shelf model

Notice of a fork is requested and never required. Two further implementations are known to the cooperative through fault reports and appear here without further detail, since neither operator has asked to be listed.

What the cooperative offers a fork

Questions receive answers. Calibration data, the correspondence work between REP and the macroseismic scales, and the failure record of every threshold set are supplied on request. A fork may send a threshold set for review, and the cooperative will state where it appears too tight or too loose against the Republic's own experience.

The cooperative operates nothing outside its territory, guarantees nothing about a fork, and reviews no operational decision. A country operating a warning system answers for it to its own population.

Faults found in a fork

Corrections have come back three times since 2022, twice concerning the message decoder and once concerning a rounding error in the intensity computation near a step boundary. Each was applied here and republished, and one of the three is still open as W-042. Send faults through the public information system, or to faults@meteo.rof.

Limits of a port

What a fork will find

The blind zone travels with the method. A country whose earthquakes occur beneath its cities gains far less from an earthquake warning system than one whose earthquakes occur at a distance from them, and no amount of engineering changes that.

Thresholds cannot be borrowed. A rainfall threshold fitted to the Republic applied to different soils will produce warnings on days nothing happens and silence on days something does. Fitting requires a local record of failures, which takes years to accumulate.

Fixed wording must be tested on the population that will hear it. Translating the Fluidian or English text and broadcasting it untested is the failure mode the cooperative would most expect to see in a hurried port.

See also