Uruguay — 6 actual messages

02:05  Tormentas puntualmente fuertes (view from source)
EN (Google Translate): Locally heavy storms
AlertMetFuture
Moderate
Likely
Uruguayan Institute of Meteorology
haillightningrainthunderstormswind
⚠️ content.no_instruction_text — CAP <instruction> is empty — the message describes a hazard but tells the reader nothing to do about it.
02:45  Tormentas fuertes y puntualmente severas (view from source)
EN (Google Translate): Strong and occasionally severe storms
AlertMetFuture
Severe
Likely
Uruguayan Institute of Meteorology
haillightningrainthunderstormswind
⚠️ content.no_instruction_text — CAP <instruction> is empty — the message describes a hazard but tells the reader nothing to do about it.
06:30  Tormentas fuertes y puntualmente severas (view from source)
EN (Google Translate): Strong and occasionally severe storms
AlertMetFuture
Severe
Likely
Uruguayan Institute of Meteorology
haillightningrainthunderstormswind
⚠️ content.no_instruction_text — CAP <instruction> is empty — the message describes a hazard but tells the reader nothing to do about it.
09:00  Tormentas fuertes y puntualmente severas (view from source)
EN (Google Translate): Strong and occasionally severe storms
AlertMetFuture
Severe
Likely
Uruguayan Institute of Meteorology
haillightningrainthunderstormswind
⚠️ content.usc_divergent_between_infos — all <info> elements within a single <alert> should have the same <urgency>, <severity> and <certainty> values, so the alert can be processed consistently as a unit; messages with different U/S/C values should be sent in separate <alert> bodies.
⚠️ content.no_instruction_text — CAP <instruction> is empty — the message describes a hazard but tells the reader nothing to do about it.
11:20  Tormentas fuertes y puntualmente severas (view from source)
EN (Google Translate): Strong and occasionally severe storms
AlertMetFuture
Severe
Likely
Uruguayan Institute of Meteorology
haillightningrainthunderstormswind
⚠️ content.usc_divergent_between_infos — all <info> elements within a single <alert> should have the same <urgency>, <severity> and <certainty> values, so the alert can be processed consistently as a unit; messages with different U/S/C values should be sent in separate <alert> bodies.
⚠️ content.no_instruction_text — CAP <instruction> is empty — the message describes a hazard but tells the reader nothing to do about it.
12:30  Tormentas fuertes y puntualmente severas (view from source)
EN (Google Translate): Strong and occasionally severe storms
AlertMetFuture
Severe
Likely
Uruguayan Institute of Meteorology
haillightningrainthunderstormswind
⚠️ content.usc_divergent_between_infos — all <info> elements within a single <alert> should have the same <urgency>, <severity> and <certainty> values, so the alert can be processed consistently as a unit; messages with different U/S/C values should be sent in separate <alert> bodies.
⚠️ content.no_instruction_text — CAP <instruction> is empty — the message describes a hazard but tells the reader nothing to do about it.