Guidelines : 8-Risk, Anomaly and Incident Services

Created by BERGER David, last modified on Nov 28, 2017

Suspected Ship

A suspected ship can be shared using the RiskService.

Below is the simplest way to share this information. A type of risk can be associated (the reason why the ship is suspected), or not. Additional attached documents could be also sent if more information is needed. The source and information about time validity can also be exchanged with the Metadata element.

<?xml version="1.0" encoding="UTF-8"?>
<!-- Sharing suspected vessel -->
<Risk xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://cise.jrc.ec.europa.eu/datamodel/last/xsd/Risk.xsd" xsi:schemaLocation="http://www.cise.eu/datamodel/v1/entity/vessel/ https://cise.jrc.ec.europa.eu/datamodel/last/xsd/entity/vessel/Vessel.xsd" xmlns:vessel="http://www.cise.eu/datamodel/v1/entity/vessel/">
    <RiskProbability>Probable</RiskProbability>
    <RiskType>IllegalImmigration</RiskType>
    <InvolvedObjectRel>
        <Object xsi:type="vessel:Vessel">
            <Name>HANOVER EXPRESS</Name>
            <LocationRel>
                <Location><Geometry><Latitude>37.9333</Latitude><Longitude>23.5301</Longitude></Geometry></Location>
            </LocationRel>
            <CallSign>DFGX2</CallSign>
            <IMONumber>9343716</IMONumber>
        </Object>
    </InvolvedObjectRel>
</Risk>

Route Alert

A route alert can be shared using the AnomalyService with the type "UnexpectedMovement"

To share more information about the anomaly, it is possible to attach a document to the message (with "DocumentRel") or add additional information in the Metadata element.

<?xml version="1.0" encoding="UTF-8"?>
<!-- Sharing route alert -->
<Anomaly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://cise.jrc.ec.europa.eu/datamodel/last/xsd/Anomaly.xsd" xsi:schemaLocation="http://www.cise.eu/datamodel/v1/entity/vessel/ https://cise.jrc.ec.europa.eu/datamodel/last/xsd/entity/vessel/Vessel.xsd" xmlns:vessel="http://www.cise.eu/datamodel/v1/entity/vessel/">
    <InvolvedObjectRel>
        <Object xsi:type="vessel:Vessel">
            <Name>HANOVER EXPRESS</Name>
            <LocationRel>
                <Location><Geometry><Latitude>37.9333</Latitude><Longitude>23.5301</Longitude></Geometry></Location>
            </LocationRel>
            <CallSign>DFGX2</CallSign>
            <IMONumber>9343716</IMONumber>
        </Object>
        <ObjectRole>Participant</ObjectRole>
    </InvolvedObjectRel>
    <AnomalyType>UnexpectedMovement</AnomalyType>
</Anomaly>

Speed Alert

A speed alert can be shared using the AnomalyService, with the type "VesselWithErraticMovements". Another code could be also added to the list to be more specific to speed alert.

To share more information about the anomaly, it is possible to attach a document to the message (with "DocumentRel") or add additional information in the Metadata element.

<?xml version="1.0" encoding="UTF-8"?>
<!-- Sharing speed alert -->
<Anomaly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://cise.jrc.ec.europa.eu/datamodel/last/xsd/Anomaly.xsd" xsi:schemaLocation="http://www.cise.eu/datamodel/v1/entity/vessel/ https://cise.jrc.ec.europa.eu/datamodel/last/xsd/entity/vessel/Vessel.xsd" xmlns:vessel="http://www.cise.eu/datamodel/v1/entity/vessel/">
    <InvolvedObjectRel>
        <Object xsi:type="vessel:Vessel">
            <Name>HANOVER EXPRESS</Name>
            <LocationRel>
                <Location><Geometry><Latitude>37.9333</Latitude><Longitude>23.5301</Longitude></Geometry></Location>
            </LocationRel>
            <CallSign>DFGX2</CallSign>
            <IMONumber>9343716</IMONumber>
        </Object>
        <ObjectRole>Participant</ObjectRole>
    </InvolvedObjectRel>
    <AnomalyType>VesselWithErraticMovements</AnomalyType>
</Anomaly>

 

Area of interest

An area of interest can be shared using the RiskService. There are 2 ways to describe a polygon. The first one is to use the XMLGeometry element in combination with KML:

<?xml version="1.0" encoding="UTF-8"?>
<!-- Sharing area of interest -->
<Risk xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://cise.jrc.ec.europa.eu/datamodel/last/xsd/Risk.xsd" xsi:schemaLocation="http://www.cise.eu/datamodel/v1/entity/vessel/ https://cise.jrc.ec.europa.eu/datamodel/last/xsd/entity/vessel/Vessel.xsd" xmlns:vessel="http://www.cise.eu/datamodel/v1/entity/vessel/">
    <RiskProbability>Probable</RiskProbability>
    <RiskType>IllegalFishing</RiskType>
    <LocationRel>
        <Location><Geometry>
            <XMLGeometry>
                &lt;kml xmlns=&quot;http://www.opengis.net/kml/2.2&quot; xmlns:gx=&quot;http://www.google.com/kml/ext/2.2&quot; xmlns:kml=&quot;http://www.opengis.net/kml/2.2&quot; xmlns:atom=&quot;http://www.w3.org/2005/Atom&quot;&gt;
                    &lt;Document&gt;
                        &lt;name&gt;Zone of interest.kmz&lt;/name&gt;
                        &lt;Placemark&gt;
                            &lt;name&gt;Zone of interest&lt;/name&gt;
                            &lt;Polygon&gt;
                                &lt;outerBoundaryIs&gt;
                                    &lt;LinearRing&gt;
                                        &lt;coordinates&gt;12.78476633767068,36.71840920374597,0 12.63022911130276,35.0409156928981,0 14.29266923057292,34.48621822479559,0 15.89832336875219,34.51251678477649,0 16.11309190163698,35.46118041217048,0 14.79737554194042,36.3698892785192,0 13.71736715525747,36.67762221299664,0 12.78476633767068,36.71840920374597,0 &lt;/coordinates&gt;
                                    &lt;/LinearRing&gt;
                                &lt;/outerBoundaryIs&gt;
                            &lt;/Polygon&gt;
                        &lt;/Placemark&gt;
                    &lt;/Document&gt;
                &lt;/kml&gt;
            </XMLGeometry>
        </Geometry></Location>
    </LocationRel>
</Risk>

 

For information, the XMLGeometry content is the description of the polygon in KML, escaped. The original content (unescaped) is the following:

<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" xmlns:atom="http://www.w3.org/2005/Atom">
	<Document>
		<name>Zone of interest.kmz</name>
		<Placemark>
			<name>Zone of interest</name>
			<Polygon>
				<outerBoundaryIs>
					<LinearRing>
						<coordinates>12.78476633767068,36.71840920374597,0 12.63022911130276,35.0409156928981,0 14.29266923057292,34.48621822479559,0 15.89832336875219,34.51251678477649,0 16.11309190163698,35.46118041217048,0 14.79737554194042,36.3698892785192,0 13.71736715525747,36.67762221299664,0 12.78476633767068,36.71840920374597,0 </coordinates>
					</LinearRing>
				</outerBoundaryIs>
			</Polygon>
		</Placemark>
	</Document>
</kml>

 

The second way is to use the WKT element:

<?xml version="1.0" encoding="UTF-8"?>
<!-- Sharing area of interest -->
<Risk xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://cise.jrc.ec.europa.eu/datamodel/last/xsd/Risk.xsd" xsi:schemaLocation="http://www.cise.eu/datamodel/v1/entity/vessel/ https://cise.jrc.ec.europa.eu/datamodel/last/xsd/entity/vessel/Vessel.xsd" xmlns:vessel="http://www.cise.eu/datamodel/v1/entity/vessel/">
    <RiskProbability>Probable</RiskProbability>
    <RiskType>IllegalFishing</RiskType>
    <LocationRel>
        <Location><Geometry>
            <WKT>POLYGON((12.78476633767068 36.71840920374597, 12.63022911130276 35.0409156928981, 14.29266923057292 34.48621822479559, 15.89832336875219 34.51251678477649, 16.11309190163698 35.46118041217048, 14.79737554194042 36.3698892785192, 13.71736715525747 36.67762221299664, 12.78476633767068 36.71840920374597))</WKT>
        </Geometry></Location>
    </LocationRel>
</Risk>

For simplicity, the WKT is recommended.

SOS

The SOS can use an IncidentService, with an urgency "immediate".

<?xml version="1.0" encoding="UTF-8"?>
<!-- SOS -->
<MaritimeSafetyIncident xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://cise.jrc.ec.europa.eu/datamodel/last/xsd/MaritimeSafetyIncident.xsd" xsi:schemaLocation="http://www.cise.eu/datamodel/v1/entity/vessel/ https://cise.jrc.ec.europa.eu/datamodel/last/xsd/entity/vessel/Vessel.xsd" xmlns:vessel="http://www.cise.eu/datamodel/v1/entity/vessel/">
<!-- localisation of the SOS -->
    <LocationRel>
        <Location>
            <Geometry><Latitude>37.9333</Latitude><Longitude>23.5301</Longitude></Geometry>
        </Location>
        <DateTime><StartDate>2017-11-22</StartDate><StartTime>02:30:00Z</StartTime></DateTime>
    </LocationRel> 
<!-- identified ship (if any) -->
    <InvolvedObjectRel>
        <Object xsi:type="vessel:Vessel">
            <Name>HANOVER EXPRESS</Name>
            <CallSign>DFGX2</CallSign>
            <IMONumber>9343716</IMONumber>
        </Object>
        <ObjectRole>Participant</ObjectRole>
    </InvolvedObjectRel>
    <ResponseUrgency>Immediate</ResponseUrgency> <!-- requires immediate intervention -->
    <MaritimeSafetyIncidentType>NonSpecified</MaritimeSafetyIncidentType> <!-- depends if the nature of the SOS is known -->
</MaritimeSafetyIncident>

Fire/Explosion alert

The Fire/explosion alert can use an IncidentService.

<?xml version="1.0" encoding="UTF-8"?>
<!-- Fire/explosion alert -->
<MaritimeSafetyIncident xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://cise.jrc.ec.europa.eu/datamodel/last/xsd/MaritimeSafetyIncident.xsd" xsi:schemaLocation="http://www.cise.eu/datamodel/v1/entity/vessel/ https://cise.jrc.ec.europa.eu/datamodel/last/xsd/entity/vessel/Vessel.xsd" xmlns:vessel="http://www.cise.eu/datamodel/v1/entity/vessel/">
<!-- localisation of the fire -->
    <LocationRel>
        <Location>
            <Geometry><Latitude>37.9333</Latitude><Longitude>23.5301</Longitude></Geometry>
        </Location>
        <DateTime><StartDate>2017-11-22</StartDate><StartTime>02:30:00Z</StartTime></DateTime>
    </LocationRel> 
<!-- identified ship -->
    <InvolvedObjectRel>
        <Object xsi:type="vessel:Vessel">
            <Name>HANOVER EXPRESS</Name>
            <CallSign>DFGX2</CallSign>
            <IMONumber>9343716</IMONumber>
        </Object>
        <ObjectRole>Participant</ObjectRole>
    </InvolvedObjectRel>
    <ResponseUrgency>Immediate</ResponseUrgency> <!-- requires immediate intervention -->
    <MaritimeSafetyIncidentType>Fire</MaritimeSafetyIncidentType> 
</MaritimeSafetyIncident>

 

Flooding alert

The flooding alert can use an IncidentService.

<?xml version="1.0" encoding="UTF-8"?>
<!-- flooding alert -->
<MaritimeSafetyIncident xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://cise.jrc.ec.europa.eu/datamodel/last/xsd/MaritimeSafetyIncident.xsd" xsi:schemaLocation="http://www.cise.eu/datamodel/v1/entity/vessel/ https://cise.jrc.ec.europa.eu/datamodel/last/xsd/entity/vessel/Vessel.xsd" xmlns:vessel="http://www.cise.eu/datamodel/v1/entity/vessel/">
<!-- localisation of the incident -->
    <LocationRel>
        <Location>
            <Geometry><Latitude>37.9333</Latitude><Longitude>23.5301</Longitude></Geometry>
        </Location>
        <DateTime><StartDate>2017-11-22</StartDate><StartTime>02:30:00Z</StartTime></DateTime>
    </LocationRel> 
<!-- identified ship -->
    <InvolvedObjectRel>
        <Object xsi:type="vessel:Vessel">
            <Name>HANOVER EXPRESS</Name>
            <CallSign>DFGX2</CallSign>
            <IMONumber>9343716</IMONumber>
        </Object>
        <ObjectRole>Participant</ObjectRole>
    </InvolvedObjectRel>
    <ResponseUrgency>Immediate</ResponseUrgency> <!-- requires immediate intervention -->
    <MaritimeSafetyIncidentType>Flooding</MaritimeSafetyIncidentType> 
</MaritimeSafetyIncident>