@globalfishingwatch/i18n-labels 1.3.9 → 1.3.11

package/en/datasets.json

@@ -655,7 +655,7 @@
           "6.6": "6.6 - Diversified",
           "6.7": "6.7 - Diversified",
           "Sem código IN": "No code IN",
-          "nan": "NAN"
+          "nan": ""
         }
       }
     }

package/package.json

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

package/pt/datasets.json

@@ -158,7 +158,7 @@
     "description": "<h2>Overview</h2> <p> Not all AIS (Automatic Identification System) messages broadcast by vessels are picked up by receivers. This can happen for several technical reasons: </p> <ul> <li>Signal interference, especially in crowded waters,</li> <li>Limited range of terrestrial receivers,</li> <li> Satellite coverage issues, which vary across location, time of day, and weather conditions. </li> </ul> <p> Because of this, it is not unusual to see gaps in AIS data lasting hours, or even days. </p> <p>Other reasons for AIS gaps include:</p> <ul> <li> The AIS device being intentionally switched off (e.g. disabled) while at sea, </li> <li>Equipment malfunctions on the vessel,</li> <li>The vessel's systems being powered down while anchored or docked.</li> </ul> <p> Detecting these gaps is an important first step to identify possible intentional disabling events, which can obscure illegal activities, such as unauthorized fishing or transshipments. </p> <h2>Data Considerations</h2> <ul> <li> Our system detects gaps in AIS signals by grouping messages by MMSI (ssvid). However, since different vessels can sometimes use the same ssvid, this may occasionally cause confusion, such as a gap appearing to start from one vessel and end with another. These cases are rare, but we are working on improvements, like using more precise vessel identifiers to reduce this issue. </li> <li> Satellite AIS reception generally decreases closer to shore due to increased signal interference from high vessel densities. Meanwhile, over 99% of GFW's terrestrial AIS messages originate within 50 nautical miles of shore, roughly the upper range of terrestrial AIS receivers, and terrestrial AIS coverage varies significantly worldwide. Because of these overlapping factors, AIS gaps starting within 50 nautical miles of shore can result from several technical reasons, such as: <ul> <li> Transitioning from areas with terrestrial AIS coverage to poor satellite AIS reception, </li> <li> Poor satellite reception when approaching port, followed by turning off AIS upon arrival. These scenarios likely explain many very long AIS gaps (e.g., lasting several months) in the data. </li> </ul> </li> <li> The number of satellites visible over the horizon varies hour to hour and location to location. At latitudes under 60 degrees, satellite coverage peaks approximately every 12 hours (half a day), with high variability in satellite counts for shorter intervals. As a result, AIS gaps shorter than 12 hours cannot reliably indicate intentional disabling events. The 12-hour threshold corresponds approximately to the revisit time of an individual AIS satellite in a sun-synchronous orbit over the same location. </li> </ul>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -428,7 +428,7 @@
     "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": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -464,7 +464,7 @@
     "description": "<h2>Overview</h2> <h3> Loitering events identify when a vessel is operating away from shore while moving at low speeds. Loitering events highlight when a vessel is behaving in a manner consistent with a potential encounter event (i.e. stationary or drifting slowly at sea) but no encountering vessel is visible on AIS. As such, these should not be considered indicators of likely encounter events, but rather periods of time when undetected encounters could have potentially occurred. </h3> <ul> <p>Global Fishing Watch classifies an event as a loitering event when:</p> <li> The vessel is located more than 20 nautical miles (37.04 kilometers) from shore, and </li> <li>Maintains an average speed of less than 2 knots,</li> <li>For a continuous period of at least 1 hour.</li> </ul> <h2>Caveats</h2> <ul> <li> Global Fishing Watch events are the result of a rule-based algorithm being applied to AIS positional data. Loitering events should be cross-verified with other sources of information (like RFMO transshipment records) when possible. </li> <li> Vessels in loitering events may not be meeting any other vessels at the time of the event. Other events in which a vessel may remain fairly stationary or moving slowly while at sea include: maintenance, losing vessel power, idling during poor weather, waiting outside of port for permission to dock, normal fishing behavior, and more. </li> <li> Due to the individual definitions of loitering events, fishing events, and encounter events, it is possible for a single vessel movement pattern to trigger multiple event types. </li> <li> A loitering event position may not align exactly with the vessel’s tracks. Global Fishing Watch determines a single location for each event by calculating the average latitude and longitude of all positions within that event. As a result it is possible the vessel never occupied that precise location during the 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> 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 >. </p>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -488,7 +488,7 @@
     "description": "The dataset contains port visits events for BLZ",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -545,11 +545,11 @@
     "description": "Vessels (VMS Belize)"
   },
   "private-vms-bra-encounters-events": {
-    "name": "Encontro de Embarcações (BRA)",
+    "name": "Eventos de Encontro (BRA)",
     "description": "<h2>Overview</h2> <p> Encounter events identify instances where two vessels appear to meet at sea. Our VMS Encounter dataset is currently experimental, and we calculate these events across all VMS sources. Because VMS predominantly tracks fishing vessels, encounters in this dataset are more likely to reflect fishing-related activity - such as pair fishing - than transshipment-related activity, which is more commonly observed in AIS data. </p> <p> Global Fishing Watch classifies an event as an encounter when two vessels are detected: </p> <ul> <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> <h2>Caveats</h2> <ul> <li> When encounter events involve a vessel in a foreign VMS source, the foreign vessel will appear as anonymous due to MOU restrictions. Specifically, we only display the flag and vessel type for the foreign vessel and hide the rest of its identity fields, so the vessel name appears as “Unknown” on the map. </li> <li> Because VMS datasets consist predominantly of fishing vessels - unlike AIS, which captures a broader range of vessel types - encounter events are more likely to represent pair fishing activity than transshipment. As with all Global Fishing Watch encounter data, these events are derived from rule-based algorithms and may reflect a wide range of at-sea interactions, so they should not be taken as evidence of any specific activity without further investigation. </li> <li> Some vessels appear in multiple VMS sources simultaneously due to country regulations, which can cause a vessel to appear to encounter itself. To reduce this noise, we have applied a filter that removes encounters between vessels sharing the same name across different VMS sources, though this is not a perfect solution and we are continuing to work on improvements. </li> <li> Encounters between the same two vessels occurring within a 4-hour window are consolidated into a single encounter event. Note that the 10 km anchorage-distance filter is applied before this merging step, so in rare cases a merged encounter’s average location may fall within 10 km of an anchorage even though each underlying (pre-merge) encounter was more than 10 km from the nearest anchorage. </li> <li> It is a known issue that the encounter detection algorithm does not evaluate continuity across the day boundary (midnight UTC). As a result, encounters that span midnight are not detected and will be missing from the dataset. Specifically those that start after ~22:00 UTC or end before ~02:00 UTC. </li> <li> Encounter detection relies on first creating a regular 10-minute timeline of a vessel’s positions. This timeline is created by interpolating between consecutive positions only when they are less than 60 minutes apart. If a vessel’s polling rate is 60 minutes or longer, no interpolation is performed, so encounters for that vessel are less likely to be detected and may be missed. </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. </li> <li> Global Fishing Watch recommends visually inspecting vessel tracks, always referring to additional data sources and/or information, and requesting records from a vessel to confirm any findings, as part of the users' due diligence process. </li> </ul>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -559,9 +559,9 @@
         "keyword": "tipo de encontro",
         "enum": {
           "FISHING-FISHING": "PESCA-PESCA",
-          "FISHING-OTHER": "FISHING-OTHER",
+          "FISHING-OTHER": "PESCA-OUTRO",
           "OTHER-FISHING": "OTHER-FISHING",
-          "OTHER-OTHER": "OTHER-OTHER"
+          "OTHER-OTHER": "OUTRO-OUTRO"
         }
       }
     }
@@ -582,7 +582,7 @@
         }
       },
       "fleet_code": {
-        "keyword": "Frota INI",
+        "keyword": "CÓDIGO INI 10/2011",
         "enum": {
           "1.1": "1.1 - Espinhel horizontal (superfície) Espinhel boiado e Long-line",
           "1.2": "1.2 - Espinhel horizontal (superfície) Espinhel boiado e Long-line",
@@ -654,8 +654,8 @@
           "6.5": "6.5 - Diversificada costeira",
           "6.6": "6.6 - Diversificada costeira",
           "6.7": "6.7 - Diversificada costeira",
-          "Sem código IN": "",
-          "nan": "NAN"
+          "Sem código IN": "Sem código IN",
+          "nan": ""
         }
       }
     }
@@ -685,7 +685,7 @@
     "description": "<h2>Overview</h2> <p> Encounter events identify instances where two vessels appear to meet at sea. Our VMS Encounter dataset is currently experimental, and we calculate these events across all VMS sources. Because VMS predominantly tracks fishing vessels, encounters in this dataset are more likely to reflect fishing-related activity - such as pair fishing - than transshipment-related activity, which is more commonly observed in AIS data. </p> <p> Global Fishing Watch classifies an event as an encounter when two vessels are detected: </p> <ul> <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> <h2>Caveats</h2> <ul> <li> When encounter events involve a vessel in a foreign VMS source, the foreign vessel will appear as anonymous due to MOU restrictions. </li> <li> Because VMS datasets consist predominantly of fishing vessels - unlike AIS, which captures a broader range of vessel types - encounter events are more likely to represent pair fishing activity than transshipment. As with all Global Fishing Watch encounter data, these events are derived from rule-based algorithms and may reflect a wide range of at-sea interactions, so they should not be taken as evidence of any specific activity without further investigation. </li> <li> Some vessels appear in multiple VMS sources simultaneously due to country regulations, which can cause a vessel to appear to encounter itself. To reduce this noise, we have applied a filter that removes encounters between vessels sharing the same name across different VMS sources, though this is not a perfect solution and we are continuing to work on improvements. </li> <li> Encounters between the same two vessels occurring within a 4-hour window are consolidated into a single encounter event. </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. </li> <li> Global Fishing Watch recommends visually inspecting vessel tracks, always referring to additional data sources and/or information, and requesting records from a vessel to confirm any findings, as part of the users' due diligence process. </li> </ul>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "0": "0",
           "48": "48"
@@ -705,7 +705,7 @@
     "description": "<h2>Overview</h2> <p> The Port Visits VMS dataset detects vessel movements in and out of ports. To identify these, we use a combined anchorage list derived from our AIS dataset, supplemented by smaller ports - not captured in AIS - that were shared by our country partners. If you believe a port in your country is missing from this dataset, please do not hesitate to reach out to our support team at <a href=\"mailto:support@globalfishingwatch.org\" >support@globalfishingwatch.org</a >. </p> <p>A port visit is shown on the map when VMS 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 an anchorage point designated as the port exit <ul> <li> Experiencing a port gap (i.e. no VMS transmissions for 4 hours or more, which may indicate VMS 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> </li> </ul> <p> Port stops are used to distinguish actual port visits from coastal transits. </p> <h2>Caveats</h2> <ul> <li> In our VMS port events, residual positions within port can sometimes persist after a vessel has departed, causing events to appear extended beyond the vessel's actual time in port. This is a result of the limited filtering currently applied to our VMS data, as we are still working on adapting filters that effectively remove noisy positions without discarding valid ones. We aim to address this in future releases. </li> <li> Lower-confidence port visits - often caused by noisy, sparse, or incomplete VMS 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> 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>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "0": "0",
           "48": "48"
@@ -754,10 +754,10 @@
     "description": "Vessels (VMS Brazil)",
     "schema": {
       "selfReportedInfo.fishingLicenseCode": {
-        "keyword": "fishingLicenseCode"
+        "keyword": "Código RGP"
       },
       "selfReportedInfo.fleetCode": {
-        "keyword": "CÓDIGO IN",
+        "keyword": "CÓDIGO IN 10/2011",
         "enum": {
           "1.1": "1.1 - Espinhel horizontal (superfície) Espinhel boiado e Long-line",
           "1.2": "1.2 - Espinhel horizontal (superfície) Espinhel boiado e Long-line",
@@ -834,7 +834,7 @@
         }
       },
       "selfReportedInfo.vesselRegistrationCode": {
-        "keyword": "vesselRegistrationCode"
+        "keyword": "TIE"
       }
     }
   },
@@ -843,7 +843,7 @@
     "description": "<h2>Overview</h2> <p> Encounter events identify instances where two vessels appear to meet at sea. Our VMS Encounter dataset is currently experimental, and we calculate these events across all VMS sources. Because VMS predominantly tracks fishing vessels, encounters in this dataset are more likely to reflect fishing-related activity - such as pair fishing - than transshipment-related activity, which is more commonly observed in AIS data. </p> <p> Global Fishing Watch classifies an event as an encounter when two vessels are detected: </p> <ul> <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> <h2>Caveats</h2> <ul> <li> When encounter events involve a vessel in a foreign VMS source, the foreign vessel will appear as anonymous due to MOU restrictions. Specifically, we only display the flag and vessel type for the foreign vessel and hide the rest of its identity fields, so the vessel name appears as “Unknown” on the map. </li> <li> Because VMS datasets consist predominantly of fishing vessels - unlike AIS, which captures a broader range of vessel types - encounter events are more likely to represent pair fishing activity than transshipment. As with all Global Fishing Watch encounter data, these events are derived from rule-based algorithms and may reflect a wide range of at-sea interactions, so they should not be taken as evidence of any specific activity without further investigation. </li> <li> Some vessels appear in multiple VMS sources simultaneously due to country regulations, which can cause a vessel to appear to encounter itself. To reduce this noise, we have applied a filter that removes encounters between vessels sharing the same name across different VMS sources, though this is not a perfect solution and we are continuing to work on improvements. </li> <li> Encounters between the same two vessels occurring within a 4-hour window are consolidated into a single encounter event. Note that the 10 km anchorage-distance filter is applied before this merging step, so in rare cases a merged encounter’s average location may fall within 10 km of an anchorage even though each underlying (pre-merge) encounter was more than 10 km from the nearest anchorage. </li> <li> It is a known issue that the encounter detection algorithm does not evaluate continuity across the day boundary (midnight UTC). As a result, encounters that span midnight are not detected and will be missing from the dataset. Specifically those that start after ~22:00 UTC or end before ~02:00 UTC. </li> <li> Encounter detection relies on first creating a regular 10-minute timeline of a vessel’s positions. This timeline is created by interpolating between consecutive positions only when they are less than 60 minutes apart. If a vessel’s polling rate is 60 minutes or longer, no interpolation is performed, so encounters for that vessel are less likely to be detected and may be missed. </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. </li> <li> Global Fishing Watch recommends visually inspecting vessel tracks, always referring to additional data sources and/or information, and requesting records from a vessel to confirm any findings, as part of the users' due diligence process. </li> </ul>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -889,7 +889,7 @@
     "description": "<h2>Overview</h2> <p> Encounter events identify instances where two vessels appear to meet at sea. Our VMS Encounter dataset is currently experimental, and we calculate these events across all VMS sources. Because VMS predominantly tracks fishing vessels, encounters in this dataset are more likely to reflect fishing-related activity - such as pair fishing - than transshipment-related activity, which is more commonly observed in AIS data. </p> <p> Global Fishing Watch classifies an event as an encounter when two vessels are detected: </p> <ul> <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> <h2>Caveats</h2> <ul> <li> When encounter events involve a vessel in a foreign VMS source, the foreign vessel will appear as anonymous due to MOU restrictions. </li> <li> Because VMS datasets consist predominantly of fishing vessels - unlike AIS, which captures a broader range of vessel types - encounter events are more likely to represent pair fishing activity than transshipment. As with all Global Fishing Watch encounter data, these events are derived from rule-based algorithms and may reflect a wide range of at-sea interactions, so they should not be taken as evidence of any specific activity without further investigation. </li> <li> Some vessels appear in multiple VMS sources simultaneously due to country regulations, which can cause a vessel to appear to encounter itself. To reduce this noise, we have applied a filter that removes encounters between vessels sharing the same name across different VMS sources, though this is not a perfect solution and we are continuing to work on improvements. </li> <li> Encounters between the same two vessels occurring within a 4-hour window are consolidated into a single encounter event. </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. </li> <li> Global Fishing Watch recommends visually inspecting vessel tracks, always referring to additional data sources and/or information, and requesting records from a vessel to confirm any findings, as part of the users' due diligence process. </li> </ul>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -913,7 +913,7 @@
     "description": "<h2>Overview</h2> <p> The Port Visits VMS dataset detects vessel movements in and out of ports. To identify these, we use a combined anchorage list derived from our AIS dataset, supplemented by smaller ports - not captured in AIS - that were shared by our country partners. If you believe a port in your country is missing from this dataset, please do not hesitate to reach out to our support team at <a href=\"mailto:support@globalfishingwatch.org\" >support@globalfishingwatch.org</a >. </p> <p>A port visit is shown on the map when VMS 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 an anchorage point designated as the port exit <ul> <li> Experiencing a port gap (i.e. no VMS transmissions for 4 hours or more, which may indicate VMS 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> </li> </ul> <p> Port stops are used to distinguish actual port visits from coastal transits. </p> <h2>Caveats</h2> <ul> <li> In our VMS port events, residual positions within port can sometimes persist after a vessel has departed, causing events to appear extended beyond the vessel's actual time in port. This is a result of the limited filtering currently applied to our VMS data, as we are still working on adapting filters that effectively remove noisy positions without discarding valid ones. We aim to address this in future releases. </li> <li> Lower-confidence port visits - often caused by noisy, sparse, or incomplete VMS 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> 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>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -983,7 +983,7 @@
     "description": "<h2>Overview</h2> <p> Encounter events identify instances where two vessels appear to meet at sea. Our VMS Encounter dataset is currently experimental, and we calculate these events across all VMS sources. Because VMS predominantly tracks fishing vessels, encounters in this dataset are more likely to reflect fishing-related activity - such as pair fishing - than transshipment-related activity, which is more commonly observed in AIS data. </p> <p> Global Fishing Watch classifies an event as an encounter when two vessels are detected: </p> <ul> <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> <h2>Caveats</h2> <ul> <li> When encounter events involve a vessel in a foreign VMS source, the foreign vessel will appear as anonymous due to MOU restrictions. Specifically, we only display the flag and vessel type for the foreign vessel and hide the rest of its identity fields, so the vessel name appears as “Unknown” on the map. </li> <li> Because VMS datasets consist predominantly of fishing vessels - unlike AIS, which captures a broader range of vessel types - encounter events are more likely to represent pair fishing activity than transshipment. As with all Global Fishing Watch encounter data, these events are derived from rule-based algorithms and may reflect a wide range of at-sea interactions, so they should not be taken as evidence of any specific activity without further investigation. </li> <li> Some vessels appear in multiple VMS sources simultaneously due to country regulations, which can cause a vessel to appear to encounter itself. To reduce this noise, we have applied a filter that removes encounters between vessels sharing the same name across different VMS sources, though this is not a perfect solution and we are continuing to work on improvements. </li> <li> Encounters between the same two vessels occurring within a 4-hour window are consolidated into a single encounter event. Note that the 10 km anchorage-distance filter is applied before this merging step, so in rare cases a merged encounter’s average location may fall within 10 km of an anchorage even though each underlying (pre-merge) encounter was more than 10 km from the nearest anchorage. </li> <li> It is a known issue that the encounter detection algorithm does not evaluate continuity across the day boundary (midnight UTC). As a result, encounters that span midnight are not detected and will be missing from the dataset. Specifically those that start after ~22:00 UTC or end before ~02:00 UTC. </li> <li> Encounter detection relies on first creating a regular 10-minute timeline of a vessel’s positions. This timeline is created by interpolating between consecutive positions only when they are less than 60 minutes apart. If a vessel’s polling rate is 60 minutes or longer, no interpolation is performed, so encounters for that vessel are less likely to be detected and may be missed. </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. </li> <li> Global Fishing Watch recommends visually inspecting vessel tracks, always referring to additional data sources and/or information, and requesting records from a vessel to confirm any findings, as part of the users' due diligence process. </li> </ul>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -1030,7 +1030,7 @@
     "description": "<h2>Overview</h2> <p> Encounter events identify instances where two vessels appear to meet at sea. Our VMS Encounter dataset is currently experimental, and we calculate these events across all VMS sources. Because VMS predominantly tracks fishing vessels, encounters in this dataset are more likely to reflect fishing-related activity - such as pair fishing - than transshipment-related activity, which is more commonly observed in AIS data. </p> <p> Global Fishing Watch classifies an event as an encounter when two vessels are detected: </p> <ul> <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> <h2>Caveats</h2> <ul> <li> When encounter events involve a vessel in a foreign VMS source, the foreign vessel will appear as anonymous due to MOU restrictions. </li> <li> Because VMS datasets consist predominantly of fishing vessels - unlike AIS, which captures a broader range of vessel types - encounter events are more likely to represent pair fishing activity than transshipment. As with all Global Fishing Watch encounter data, these events are derived from rule-based algorithms and may reflect a wide range of at-sea interactions, so they should not be taken as evidence of any specific activity without further investigation. </li> <li> Some vessels appear in multiple VMS sources simultaneously due to country regulations, which can cause a vessel to appear to encounter itself. To reduce this noise, we have applied a filter that removes encounters between vessels sharing the same name across different VMS sources, though this is not a perfect solution and we are continuing to work on improvements. </li> <li> Encounters between the same two vessels occurring within a 4-hour window are consolidated into a single encounter event. </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. </li> <li> Global Fishing Watch recommends visually inspecting vessel tracks, always referring to additional data sources and/or information, and requesting records from a vessel to confirm any findings, as part of the users' due diligence process. </li> </ul>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -1054,7 +1054,7 @@
     "description": "<h2>Overview</h2> <p> The Port Visits VMS dataset detects vessel movements in and out of ports. To identify these, we use a combined anchorage list derived from our AIS dataset, supplemented by smaller ports - not captured in AIS - that were shared by our country partners. If you believe a port in your country is missing from this dataset, please do not hesitate to reach out to our support team at <a href=\"mailto:support@globalfishingwatch.org\" >support@globalfishingwatch.org</a >. </p> <p>A port visit is shown on the map when VMS 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 an anchorage point designated as the port exit <ul> <li> Experiencing a port gap (i.e. no VMS transmissions for 4 hours or more, which may indicate VMS 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> </li> </ul> <p> Port stops are used to distinguish actual port visits from coastal transits. </p> <h2>Caveats</h2> <ul> <li> In our VMS port events, residual positions within port can sometimes persist after a vessel has departed, causing events to appear extended beyond the vessel's actual time in port. This is a result of the limited filtering currently applied to our VMS data, as we are still working on adapting filters that effectively remove noisy positions without discarding valid ones. We aim to address this in future releases. </li> <li> Lower-confidence port visits - often caused by noisy, sparse, or incomplete VMS 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> 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>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -1133,7 +1133,7 @@
     "description": "<h2>Overview</h2> <p> Encounter events identify instances where two vessels appear to meet at sea. Our VMS Encounter dataset is currently experimental, and we calculate these events across all VMS sources. Because VMS predominantly tracks fishing vessels, encounters in this dataset are more likely to reflect fishing-related activity - such as pair fishing - than transshipment-related activity, which is more commonly observed in AIS data. </p> <p> Global Fishing Watch classifies an event as an encounter when two vessels are detected: </p> <ul> <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> <h2>Caveats</h2> <ul> <li> When encounter events involve a vessel in a foreign VMS source, the foreign vessel will appear as anonymous due to MOU restrictions. Specifically, we only display the flag and vessel type for the foreign vessel and hide the rest of its identity fields, so the vessel name appears as “Unknown” on the map. </li> <li> Because VMS datasets consist predominantly of fishing vessels - unlike AIS, which captures a broader range of vessel types - encounter events are more likely to represent pair fishing activity than transshipment. As with all Global Fishing Watch encounter data, these events are derived from rule-based algorithms and may reflect a wide range of at-sea interactions, so they should not be taken as evidence of any specific activity without further investigation. </li> <li> Some vessels appear in multiple VMS sources simultaneously due to country regulations, which can cause a vessel to appear to encounter itself. To reduce this noise, we have applied a filter that removes encounters between vessels sharing the same name across different VMS sources, though this is not a perfect solution and we are continuing to work on improvements. </li> <li> Encounters between the same two vessels occurring within a 4-hour window are consolidated into a single encounter event. Note that the 10 km anchorage-distance filter is applied before this merging step, so in rare cases a merged encounter’s average location may fall within 10 km of an anchorage even though each underlying (pre-merge) encounter was more than 10 km from the nearest anchorage. </li> <li> It is a known issue that the encounter detection algorithm does not evaluate continuity across the day boundary (midnight UTC). As a result, encounters that span midnight are not detected and will be missing from the dataset. Specifically those that start after ~22:00 UTC or end before ~02:00 UTC. </li> <li> Encounter detection relies on first creating a regular 10-minute timeline of a vessel’s positions. This timeline is created by interpolating between consecutive positions only when they are less than 60 minutes apart. If a vessel’s polling rate is 60 minutes or longer, no interpolation is performed, so encounters for that vessel are less likely to be detected and may be missed. </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. </li> <li> Global Fishing Watch recommends visually inspecting vessel tracks, always referring to additional data sources and/or information, and requesting records from a vessel to confirm any findings, as part of the users' due diligence process. </li> </ul>",
     "schema": {
       "duration": {
-        "keyword": "duration",
+        "keyword": "duração",
         "enum": {
           "2": "2",
           "48": "48"
@@ -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": {