@globalfishingwatch/i18n-labels 1.3.9 → 1.3.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@globalfishingwatch/i18n-labels",
-  "version": "1.3.9",
+  "version": "1.3.10",
   "description": "i18n label translations for Global Fishing Watch applications",
   "author": "satellitestudio <contact@satellitestud.io>",
   "repository": {

package/pt/datasets.json

@@ -754,7 +754,7 @@
     "description": "Vessels (VMS Brazil)",
     "schema": {
       "selfReportedInfo.fishingLicenseCode": {
-        "keyword": "fishingLicenseCode"
+        "keyword": "Código RGP"
       },
       "selfReportedInfo.fleetCode": {
         "keyword": "CÓDIGO IN",
@@ -2522,7 +2522,7 @@
     "description": "<h2>Overview</h2>\n<ul>\n<li>Ocean currents are the movement of seawater driven by wind, temperature, salinity, tides, and Earth’s rotation. Ocean currents regulate climate and transport heat, nutrients, and marine species. This dataset shows global ocean surface currents, including speed and direction, providing insight into large-scale circulation patterns</li>\n<ul>\n<h2>Source</h2>\n<ul>\n <a href='https://doi.org/10.48670/moi-00016'>Generated using E.U. Copernicus Marine Service Information; https://doi.org/10.48670/moi-00016.</a></li>"
   },
   "public-global-encounters-events": {
-    "name": "Eventos de encontro. (AIS)",
+    "name": "Eventos de Encontro (AIS)",
     "description": "<h2>Overview</h2> <h3> Encounter events identify instances where two vessels appear to meet at sea. </h3> <ul> <p> Global Fishing Watch classifies an event as an encounter when two vessels are detected: </p> <li>Within 500 meters of one another</li> <li>For a duration of at least 2 hours</li> <li>Traveling at a median speed of less than 2 knots</li> <li> And located at least 10 kilometers (5.4 nautical miles) from a coastal anchorage. </li> </ul> <ul> <p> Users can filter encounter events by vessel characteristics and context, including: </p> <li>Duration of encounter</li> <li> Vessel flag - Shows encounters where at least one vessel is flagged to the selected country </li> <li> Next port visit after the encounter - Shows encounters where at least one vessel is has visited the selected port(s) </li> <li>Vessel types involved in the encounter</li> <li>User saved vessel group</li> </ul> <ul> <p>Currently displayed encounter types include:</p> <li>Carrier ⇄ Bunker (experimental)</li> <li>Carrier ⇄ Fishing</li> <li>Fishing ⇄ Bunker (experimental)</li> <li>Fishing ⇄ Fishing (experimental)</li> <li>Support ⇄ Fishing</li> </ul> <p> To view more details about a specific encounter—such as its location or the identity of the encountered vessel—click the “See more” icon associated with the event. </p> <h2>Caveats</h2> <ul> <li> Global Fishing Watch events are the result of rule-based algorithms being applied to AIS positional data. There are many potential reasons for vessels to meet at sea. Such interactions may include transshipment of catch or supplies, equipment transfers, crew changes, safety-related matters, and more. Encounter data should therefore be viewed as an indicator for review. </li> <li> Encounters that do not meet the specifications of GFW encounter events described above are not included in the map, such as encounters less than two hours and in-port encounters. </li> <li> Encounters between the same two vessels occurring within a 4-hour window are consolidated into a single encounter event. While multiple encounters within such a short timeframe are possible, they remain exceptionally rare. </li> <li> The 500-meter proximity threshold is calculated using implied positions—not raw AIS messages. Since AIS transmissions occur at irregular intervals, vessel positions are estimated by a 10-minute time grid using reported course and speed. Proximity is then calculated based on these estimated positions. Due to this modeling approach, it is possible that vessels identified in an encounter may not have been physically within 500 meters of each other for the entire 2-hour period. </li> <li> Bias in vessel identification and gear classification can result in the unexpected presence or absence of an encounter. Misclassifications in vessel type may occur due to inconsistent or incomplete vessel registry data. Misclassifications can also happen when algorithms struggle to appropriately categorize vessels, for instance, where vessels use several gears (thus changing their behavioral patterns) or when a vessel’s MMSI (maritime mobile service identity) number is used by more than one vessel. </li> <li> An encounter event position may not align exactly with the vessels' tracks. Global Fishing Watch determines a single location for each event by calculating the average latitude and longitude of all positions within the event. As a result it is possible the vessels never occupied that precise location during the encounter event. </li> <li> Global Fishing Watch recommends to visually inspect vessel tracks, always refer to additional data source and/or information, and request records from a vessel to confirm any findings, as part of the users’ due diligence process. </li> </ul> <h2>Learn more</h2> <p> You can read more about transshipment behaviour from our <a href=\"http://globalfishingwatch.org/wp-content/uploads/GlobalViewOfTransshipment_Aug2017.pdf\" >report</a > or <a href=\"https://www.frontiersin.org/articles/10.3389/fmars.2018.00240/full\" >scientific publication</a >. </p>",
     "schema": {
       "duration": {
@@ -2635,7 +2635,7 @@
     "description": "<h2>Visão geral</h2>\n<ul>\n<li>O fosfato é um nutriente importante para as cadeias alimentares marinhas e para a produtividade dos oceanos. No entanto, concentrações elevadas podem ser também um indicador de poluição. Este conjunto de dados é composto por parâmetros biogeoquímicos, incluindo o fosfato, sobre o oceano global exibido com uma resolução horizontal de 1/4 de grau. </li>\n<ul>\n<h2>Fonte</h2>\n<ul>\n <a href='https://doi.org/10.48670/moi-00015'>Generated using E.U. Copernicus Marine Service Information; https://doi.org/10.48670/moi-00015.</a></li>"
   },
   "public-global-port-visits-events": {
-    "name": "Visitas portuárias (AIS)",
+    "name": "Visitas Portuárias (AIS)",
     "description": "<h2>Overview</h2> <ul> <p> Global Fishing Watch detects vessel movements in and out of ports and classifies them into four distinct port event types: </p> <li>Port entry</li> <li>Port stop</li> <li>Port gap (a gap in AIS transmission while in port)</li> <li>Port exit</li> </ul> <p> These events are grouped to form port visit events, which represent a vessel’s presence at port based on AIS activity patterns. </p> <p> In the Global Fishing Watch map, only high-confidence port visits are shown. A port visit is determined with high confidence when a vessel is detected with a port entry, stop or gap, and exit. More specifically: </p> <p>A port visit is shown on the map when AIS data shows a vessel:</p> <ul> <li>Entering within 3 kilometers of an anchorage point at the port entry,</li> <li>Exiting within 4 kilometers of a known port exit, and either:</li> <ul> <li> Experiencing a port gap (i.e. no AIS transmissions for 4 hours or more, which may indicate AIS was turned off while in port), or </li> <li> Undergoing a port stop, where the vessel’s speed drops below 0.2 knots and later increases above 0.5 knots. </li> </ul> </ul> <p> Port stops are used to distinguish actual port visits from coastal transits. </p> <h2>Caveats</h2> <ul> <li> Lower-confidence port visits—often caused by noisy, sparse, or incomplete AIS transmissions—are currently excluded from the map. Lower-confidence port visits, while sometimes legitimate, can falsely suggest a port visit that did not occur. </li> <li> Ongoing port visits will not be identified on the map, as a port exit is required by definition for high-confidence port visits to be detected. </li> <li> Additionally, note that the Global Fishing Watch anchorages dataset may not capture all actual anchorage locations, which could lead to missing port events. Refer to the learn more section for a full list of anchorages. </li> <li> Global Fishing Watch recommends to verify port visits, always refer to additional data source and/or information, and request records from a vessel to confirm any findings, as part of the users’ due diligence process. </li> </ul> <h2>Learn more</h2> <p> <a href=\"https://globalfishingwatch.org/datasets-and-code-anchorages/\" >Learn more about anchorages, ports and voyages.</a > </p> <p> Learn more about considerations of using AIS data by looking at the <a href=\"https://globalfishingwatch.org/data-documentation/apparent-fishing-events-ais/\" >AIS limitations section in the Apparent fishing events (AIS) data documentation.</a >.",
     "schema": {
       "duration": {