New Crowdin updates

apps/fishing-map/public/locales/en/data-terminology.json

@@ -9,7 +9,7 @@
   "encounter": "<h2>Overview</h2>\n<ul>\n<li>Encounter events describe when AIS data shows two vessels that appear to be meeting at sea. Encounter events can be indicative of potential transshipment events.</li>\n<li>Global Fishing Watch records an event as an encounter when two vessels are detected within 500 meters of each other for at least 2 hours, travelling at a median speed of less than 2 knots, whilst at least 10 kilometers (5.4 nautical miles) from a coastal anchorage.</li>\n<li>Currently, encounter events are shown between carrier and fishing vessels and support and fishing vessels. In the future, encounters between other vessel types may be displayed.</li>\n<li>View details on the encounter, such as location of the event and details of the encountered vessel, by clicking on the &lsquo;i&rsquo; icon associated with the encounter.</li>\n</ul>\n<h2>Caveats</h2>\n<ul>\n<li>There may be many other reasons (i.e. not transhipment activity) why two vessels encounter each other at sea. Vessels may have encounters to exchange equipment or for crew safety.</li>\n<li>Given the different reasons that vessels may meet at sea, these events are intended to support further review of activity and should not be used in isolation.</li>\n<li>Sometimes transhipment events fall below the criteria used to define an encounter event, and therefore may not appear in our data. It is important to corroborate encounter events with other sources of information, such as RFMO transhipment records.</li>\n<li>If transmission data is poor, the average location can be inconsistent with the vessel track and the event may appear slightly alongside the track.</li>\n<li>Not all encounters are shown in vessel viewer. Currently, encounter events are shown between carrier and fishing vessels and support and fishing vessels. In the future, encounters between other vessel types may be displayed.</li>\n</ul>\n<h2>Learn more</h2>\n<ul>\n<p>You can read more about transshipment behaviour from our <a href=\"http://globalfishingwatch.org/wp-content/uploads/GlobalViewOfTransshipment_Aug2017.pdf\" target=\"_blank\" rel=\"noopener\">report</a> or <a href=\"https://www.frontiersin.org/articles/10.3389/fmars.2018.00240/full\" target=\"_blank\" rel=\"noopener\">scientific publication</a>.</p>",
   "loitering": "<h2>Overview</h2>\n<ul>\n  <li>Loitering events are recorded when one vessel shows signs of potential encounters, or meeting another vessel at sea, but there is no second vessel detected. </li>\n  <li>Loitering events are based on speed and distance from shore.</li>\n  <li>A loitering event is recorded when a vessel travels at an average speed of less than 2 knots over 20 nautical miles (37.04 kilometers) from shore. </li>\n  <li>There may be many reasons a loitering event is recorded, so results should be interpreted with caution. </li>\n</ul>\n<h2>Caveats</h2>\n<ul>\n  <li>There may be many reasons a vessel slows down away from shore.</li>\n  <li>Loitering events are indicative, and the vessel may not be meeting any other vessels at the time of the event.</li>\n  <li>Other events in which a vessel may remain fairly stationary or moving slowly include maintenance, poor weather or waiting for owner instruction.</li>\n  <li>Loitering events for fishing vessels may be associated with normal fishing behavior, as fishing vessels often move slowly during fishing operations.</li>\n  <li>Due to the individual definitions of loitering events and encounter events, it is possible for a loitering event to overlap with an encounter event, representing the same activity, or the loitering event may encompass one or more encounter events. </li>\n  <li>If transmission data is poor, the average location can be inconsistent with the vessel track and the event may appear slightly alongside the track.</li>\n</ul>",
   "fishing": "<h2>Overview</h2>\n<ul>\n  <li>Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as known or possible fishing vessels, and applies a fishing detection algorithm to determine “apparent fishing activity” based on changes in vessel speed and direction.</li>\n  <li>Our machine learning model classifies each AIS broadcast data point for these vessels as either apparently fishing or not fishing.</li>\n  <li>Fishing events use those data points as input and summarize them into one event for easier analysis. </li>\n  <li>A fishing event is defined where: <ul>\n      <li>Fishing positions appear consecutively and are separated by less than 10 kilometers or 2 hours; and,</li>\n      <li>Fishing positions within 1 hour and 2 kilometers of another fishing event are grouped together into a single event.</li>\n    </ul>\n  </li>\n  <li>The dataset is further restricted by removing fishing events that are brief and fast, as these are less likely to indicate a realistic fishing event. The following short fishing events are removed: <ul>\n      <li>Events less than 20 minutes in duration;</li>\n      <li>Events comprised of five or fewer fishing positions;</li>\n      <li>Events that cover distance of less than 0.5 km (for all gears except estimated squid gear);</li>\n      <li>Events that cover distance of less than 50m (for estimated squid gear); and,</li>\n      <li>Abnormally fast moving vessel events with an average vessel speed of 10 knots or greater. </li>\n    </ul>\n  </li>\n</ul>\n<h2>Caveats</h2>\n<ul>\n  <li>False positives may appear in the dataset where vessel’s slow down and change direction, but aren’t engaged in fishing activity.</li>\n  <li>Our machine learning model is better at predicting some types of fishing (e.g. trawling and longlining) compared to other types of fishing that may not have been as present in data used to train the machine learning model.</li>\n  <li>Most AIS devices fall into one of three “classes”: Class A, Class B, and Class B+. Class A devices broadcast at a stronger power and they broadcast a vessel’s position more frequently. Lower wattage Class B and B+ devices are detected less frequently by satellites, and therefore it may seem there is less fishing activity in areas where they are predominantly used. </li>\n  <li>In addition to areas with low satellite coverage, areas with a high density of vessel traffic can also limit the number of signals processed, particularly related to Class B (or B+) AIS systems. This may lead to reduced or underestimated vessel activity in the Global Fishing Watch map or data in such areas.</li>\n</ul>\n<h2>Learn more</h2><a href='https://globalfishingwatch.org/our-technology/' target='_blank' rel='noopener noreferrer'>Learn more about our estimation of apparent fishing effort.</a>",
-  "insightsCoverage": "<h2>Overview</h2> <p> <span>The coverage metric is an estimate of how well a vessel’s activities outside of port, i.e. where it travelled and what it did, can be captured by the vessel’s AIS data for the time range of interest. A vessel’s AIS coverage metric is critical to interpreting vessel activity information. The higher the coverage percentage, the greater confidence on the accuracy of events listed to represent the vessel’s actual activities. </span> <span>To calculate the coverage metric, all voyages linked to a vessel in the selected time range are segmented into one hour blocks, and the proportion of each hour block a vessel in a voyage has at least one AIS transmission. An ‘N/A’ value could be due to no reported activity for the vessel in the selected time range. This could be of poor coverage, but may also be the result of inactivity e.g. the vessel undergoing maintenance. In these cases, we recommend you check additional information sources and request supporting records from the vessel.</span> </p> <h4>Caveats</h4> <ul> <li>As the AIS coverage metric is calculated based on voyages, eg. the vessel’s activity between port visits, coverage is reflective of the time and AIS reception quality while a vessel is active at sea rather than at port.</li> <li>Voyage is defined based on port visits (exit and entry). Any issue detecting port visits for a vessel may result in lower accuracy of the AIS coverage calculation.</li> <li>The coverage metric does not distinguish between a lack of activity (non-event) and poor transmission resulting in disability to detect a true event.</li> </ul> <h4>Learn more</h4> <p> <span>Learn more about our work on </span> <a target='_blank' href='https://globalfishingwatch.org/research-project-disabled-signals/'> <span>transmission gaps</span> </a> </p>",
+  "insightsCoverage": "<h2>Overview</h2> <p> <span>The coverage metric is an estimate of how well a vessel’s activities outside of port, i.e. where it travelled and what it did, can be captured by the vessel’s AIS data for the time range of interest. A vessel’s AIS coverage metric is critical to interpreting vessel activity information. The higher the coverage percentage, the greater confidence on the accuracy of events listed to represent the vessel’s actual activities. </span> <span>To calculate the coverage metric, all voyages linked to a vessel in the selected time range are segmented into one hour blocks, and the proportion of each hour block a vessel in a voyage has at least one AIS transmission. An ‘N/A’ value could be due to no reported activity for the vessel in the selected time range. This could be of poor coverage, but may also be the result of inactivity e.g. the vessel undergoing maintenance. In these cases, we recommend you check additional information sources and request supporting records from the vessel.</span> </p> <h2>Caveats</h2> <ul> <li>As the AIS coverage metric is calculated based on voyages, eg. the vessel’s activity between port visits, coverage is reflective of the time and AIS reception quality while a vessel is active at sea rather than at port.</li> <li>Voyage is defined based on port visits (exit and entry). Any issue detecting port visits for a vessel may result in lower accuracy of the AIS coverage calculation.</li> <li>The coverage metric does not distinguish between a lack of activity (non-event) and poor transmission resulting in disability to detect a true event.</li> </ul> <h2>Learn more</h2> <p> <span>Learn more about our work on </span> <a target='_blank' href='https://globalfishingwatch.org/research-project-disabled-signals/'> <span>transmission gaps</span> </a> </p>",
   "insightsFishing": "<h2>Overview</h2> <p> <span >Global Fishing Watch (GFW) analyzes and applies a fishing detection algorithm based on AIS data collected from vessels. Each AIS broadcast data point is classified as either “apparently fishing” or not fishing, and further reviewed to determine individual “fishing events”.&nbsp;</span > </p> <p> <span >Based on the time range of interest, the following two insights are reviewed:&nbsp;</span > </p> <ul> <li> Any apparent fishing events detected in areas with no known RFMO authorization&nbsp; </li> <li>Any apparent fishing events detected in no-take MPAs</li> </ul> <h2>Fishing in areas with no known RFMO authorization</h2> <p> <span >GFW indicates any apparent fishing events in areas with no known RFMO authorization compiled from 7 Regional Fisheries Management Organisation (RFMO) lists*.&nbsp;</span > </p> <h2>Caveats</h2> <ul> <li>The insight covers the listed RFMO areas only*.&nbsp;</li> <li> The insight does not include national registration or licensing lists.&nbsp; </li> </ul> <h2>Fishing in no-take Marine Protected Areas (MPAs)</h2> <p> <span >This insight is presented by cross-referencing any apparent fishing events in the boundaries of no-take MPAs (Source: </span> <a target=\"_blank\" href=\"https://www.protectedplanet.net/en/thematic-areas/wdpa\" > <span>World Database on Protected Areas</span> </a> <span>).&nbsp;&nbsp;</span> </p> <h2>Caveats</h2> <ul> <li> Events close to boundary lines may be reported as being inside an MPA boundary. We recommend that you check the vessel track positions on the map alongside adding the MPA layer to confirm exact operation.&nbsp; </li> <li> There may be variability in no-take MPA permissions and restrictions based on seasonal closures and gear restrictions.&nbsp; </li> </ul> <h2>General caveats</h2> <ul> <li> Due to limited access to national databases, the insights do not consider other unknown authorizations e.g. seasonal closures, fishing authorisation within EEZs.&nbsp; </li> <li> All references to activity events (e.g. fishing), should be understood in the context of GFW's algorithms, which are best efforts to determine apparent fishing activity events based on AIS data collected. </li> <li> While the insights provide potential events, GFW recommends to visually inspect vessel tracks, always refer to additional information sources, and request records from a vessel to confirm any findings. </li> </ul> <p> <span> <strong>* The 7 RFMO lists </strong> </span> <span>considered for the authorization insight include:&nbsp;</span> </p> <ul> <li> <span >Commission for the Conservation of Southern Bluefin Tuna (CCSBT)</span > </li> <li><span>Inter-American Tropical Tuna Commission (IATTC)</span></li> <li> <span >International Commission for the Conservation of Atlantic Tunas (ICCAT)</span > </li> <li><span>Indian Ocean Tuna Commission (IOTC)</span></li> <li><span>North Pacific Fisheries Commission (NPFC)</span></li> <li> <span >South Pacific Regional Fisheries Management Organisation (SPRFMO)</span > </li> <li><span>Western and Central Pacific Fisheries Commission (WCPFC)</span></li> </ul> <h2>Learn more</h2> <span>Learn more about how apparent fishing is estimated through </span> <a target=\"_blank\" href=\"https://globalfishingwatch.org/our-technology/\"> <span>Global Fishing Watch’s technology</span> </a> <span>, and </span> <a target=\"_blank\" href=\"https://globalfishingwatch.org/faqs/difference-between-fishing-effort-and-fishing-events/\" > <span >the difference between apparent fishing effort and fishing events.</span > </a>",
   "insightsFlagsChanges": "<h2>Overview</h2> <p> <span >This insight tracks and details when the registry information available on a vessel indicates the vessel has been flagged to more than one unique flag state during the time range of interest, indicating a potential flag change. Adjust the end date of the time bar to present date to show the current vessel flag; Extend time range to track historical changes.</span > </p> <h2>Caveats</h2> <ul> <li> Global Fishing Watch matches vessel identity data with over 40 public registries to validate an individual vessel and enable tracking of identity and activity changes throughout the vessel’s lifetime from construction to scrapping. </li> <li> The vessel identity insights rely solely on registry data. The insights do not consider AIS based vessel flag identity. </li> <li> The quantity and quality of available registry data vary by flag state, thereby introducing uneven degrees of vessel identity information. </li> <li> Conflicts between information sources can occur leading to incorrect identification of vessel flags. This is more common for vessels not listed on public registries and vessels operating under multiple flags within a short time range. </li> <li> While every attempt is made to ensure the insight provided is accurate and up-to-date, this cannot be guaranteed, particularly on any changes outside of the monthly data update cycle. </li> </ul> <h2>Learn more</h2> <p> <span >Global Fishing Watch works to offset the lack of public registry data by complementing with other data sources and advocating for transparency in regional and national fora. Learn more about:</span > </p> <ul> <li> <a target=\"_blank\" href=\"https://globalfishingwatch.org/transparency/\"> <span>Global Fishing Watch’s transparency effort</span> </a> </li> </ul> <a target=\"_blank\" href=\"https://globalfishingwatch.org/datasets-and-code-vessel-identity/\" > <span>Vessel identity and characterization</span> </a>",
   "insightsGaps": "<h2>Overview</h2> <p> <span >AIS devices are designed to continually broadcast a vessel’s position to avoid collisions. Thus, when a vessel has an extended gap in AIS transmissions or positions, it can potentially indicate intentional AIS disabling or suspicious behavior.&nbsp;&nbsp;</span > </p> <p> <span >The AIS off events insight is based on the time range of interest.&nbsp;</span > </p> <p> <span >Global Fishing Watch records all AIS gap events over six hours, and then applies a set of filters below to identify those gaps we believe to be intentional AIS disabling rather than technical failures. The filter criteria for ‘likely disabling’ are:&nbsp;</span > </p> <ul> <li>The gap event must be at least 12 hours;</li> <li>The gap must start at least 50 nautical miles (nm) from shore;</li> <li> The gap must start in an area with a satellite reception quality greater than 10 positions per day; </li> <li> The vessel must have at least 14 satellite positions in the 12 hours prior to the gap. </li> </ul> <h2>Caveats</h2> <ul> <li> The dataset used to formulate this insight remains in <strong> <em>prototype</em> </strong> stage, which means it is still under quality assurance processes with possibility of data issues and may not include the most up-to-date data points or changes. </li> <li> Gaps outside of the above filter criteria (e.g. activity within 50 nm) are not recognised. Using this AIS off events insight to evaluate activity within 50 nm from shore for example would be uninformative and potentially misleading.&nbsp; </li> <li> Gaps shorter than 12 hours are not considered for this insight due to variability of satellite orbit timings.&nbsp; </li> <li> Gap events less than 50 nm from shore (inshore) are also not considered, due to differences in satellite and terrestrial AIS with satellite AIS reception generally decreases closer to shore coupled by higher vessel density resulting in signal interference. </li> <li> The AIS reception quality estimates used to identify the insights are based on data for 2017- 2019 from <a target=\"_blank\" href=\"https://www.science.org/doi/10.1126/sciadv.abq2109\" > <span>Welch et al. (2022)</span> </a> while we work to automate monthly estimates from 2019 until present day. </li> <li> While the insight aims to provide ‘likely AIS disabling’ events, the insight is unable to confirm whether the gap events are intentional. </li> <li> We recommend referencing additional information sources and request supporting records from the vessel for comprehensive AIS gap events review.&nbsp; </li> </ul>",