Not all AIS (Automatic Identification System) messages broadcast by vessels are picked up by receivers. This can happen for several technical reasons:
Because of this, it is not unusual to see gaps in AIS data lasting hours, or even days.
Other reasons for AIS gaps include:
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.
This layer shows vessels detected using optical satellite imagery collected by the European Space Agency's Planet satellites. Optical imagery is similar to high-quality aerial photography from space, using reflected sunlight in visible and near-infrared wavelengths. This type of imagery provides high-resolution detail that allows us to spot small vessels, identify wake patterns, and better understand activity near shore.
Global Fishing Watch uses a machine learning model that processes each image to identify vessels and estimate their length, orientation, and speed based on wake features. The detections are then filtered using a secondary classifier to remove objects that are not vessels, such as clouds, rocks or icebergs. Each detection is linked to a cropped image (a thumbnail) so users can visually inspect what the model identified.
Because optical satellites rely on sunlight and clear skies, detections are only possible during the day and when the area is not obscured by clouds or haze. Despite these limitations, detections with optical imagery are especially helpful in identifying small untracked vessels that may not appear in other tracking systems.
This layer is based on images from the Planet satellites operated by the European Space Agency (ESA). These satellites capture medium-resolution images (10 m per pixel) of the ocean using visible and near-infrared light (among several other bands). Combined, the satellites acquire images of most coastal waters and dedicated areas in the open ocean roughly every five days, and the imagery is made freely available by the ESA.
We use pre-processed Planet images that have been corrected for geometric distortions and aligned to the Earth's surface. These images are split into manageable tiles, and we selected the tiles that cover only ocean areas (image tiles over land are excluded). We use four image bands: red, green, blue (RGB), and near-infrared (NIR), all at 10-meter resolution. These bands give us the detail and contrast needed to detect and classify vessels.
Our machine learning model scans each image tile to detect vessels. It is trained to look for features such as the shape, brightness, and wake of a vessel. When it finds a likely candidate, the model predicts a score for vessel presence alongside estimates of the vessel's location, size, orientation, and speed.
The detection model was trained on over 11,000 manually reviewed vessel examples across thousands of Planet scenes. This training process included many small vessels and scenes from around the world, helping the model to perform well across different environments and vessel types.
Each detection includes a small visual \"chip\" showing the detected vessel at the center. These thumbnails come in two formats: a color version from the RGB bands, and a grayscale version from the near-infrared band. Each chip covers an area of 1 km². These thumbnails are helpful for visually confirming a detection or understanding its context. For very small vessels (under 15 meters), it may still be difficult to see them clearly.
Not everything that looks like a vessel in satellite imagery actually is one. To help remove false detections (like buoys, offshore platforms, sea ice, or clouds), we run each detection through a secondary classifier. This classifier is a machine learning model that uses both the image thumbnail and additional information about the detection (such as distance from shore, local depth, and vessel density nearby, among others) to decide whether the object is likely to be a vessel. We also flag detections that are close to known fixed infrastructure or in areas with substantial sea ice or iceberg presence.
If a detection is classified as likely non-vessel or flagged as potential infrastructure or ice, we remove it from the map layer so only high-confidence detections are included. We also clip the satellite footprints (displayed on the map layer) to exclude the areas under the icy-region mask. However, we provide all the false positives with labels through the data download portal for stakeholders who require a more complete dataset.
AIS data can reveal the identity of vessels, their owners and corporations, and fishing activity. Not all vessels, however, are required to use AIS devices, as regulations vary by country, vessel size, and activity. Vessels engaged in illicit activities can also turn off their AIS transponders or manipulate the locations they broadcast. Also, large \"blind spots\" along coastal waters arise from nations that restrict access to AIS data that are captured by terrestrial receptors instead of satellites or from poor reception due to high vessel density and low-quality AIS devices. Unmatched imagery detections therefore provide the missing information about vessel traffic in the ocean.
Matching imagery detections to vessels' GPS coordinates from AIS is challenging because the timestamps of the images and AIS records do not coincide, and a single AIS identity can potentially match to multiple vessels appearing in the image, and vice versa. To determine the likelihood that a vessel broadcasting AIS corresponded to a specific detection, we developed a matching approach based on probability rasters of where a vessel is likely to be minutes before and after an AIS position was recorded. These rasters were produced from one year of global AIS data from the Global Fishing Watch pipeline, which sources satellite data from Spire Global and Orbcomm. The probability rasters are based on roughly 10 billion vessel positions and are computed for six different vessel classes, considering six different speeds and 36 time intervals. So we obtain the likely position of a vessel that could match a detection based on the vessel class, speed and time interval. In addition to the spatiotemporal matching, we factor in the similarity between the model-inferred vessel length and the length from AIS identity data to avoid (likely incorrect) matches with large discrepancies in size, e.g., AIS of a tugboat and the detection of a large vessel behind it.
To help users understand where detections were possible, we show the detection \"footprints\" on the map. These polygons are the portions of the satellite images that cover the ocean and that were used for detection. Thus, if you see a footprint but no detections, it means no vessels were detected in that area. If there is no footprint, no image was processed for that location and time.
Our detection and matching system runs automatically each day. It checks for new Planet images published to Google Cloud and processes those that meet our quality criteria. New detections are typically available within 1–2 days of the satellite capturing the image. The automated pipeline also re-checks any images published late to ensure any data gaps are filled.
All vessel data are freely available through the Global Fishing Watch data portal at https://globalfishingwatch.org/data-download/.
Non-Commercial Use Only. The Site and the Services are provided for Non-Commercial use only in accordance with the CC BY-NC 4.0 license. If you would like to use the Site and/or the Services for commercial purposes, please contact us.
", "schema": { "length": { "keyword": "length" }, "matched": { "keyword": "matched" }, "shiptype": { "keyword": "shiptype" } } }, "private-indonesia-aruna-fishing-effort": { "name": "Aruna: Indonesia Pelagic", "description": "Indonesia Aruna Fishing Effort" }, "private-indonesia-aruna-presence": { "name": "Aruna : Pélagique Indonésie", "description": "Aruna Presence" }, "private-indonesia-aruna-vessel-identity": { "name": "Aruna Indonésie (Navires)", "description": "Navires (Aruna Indonésie)" }, "private-indonesia-fishing-effort": { "name": "Indonesia VMS", "description": "VMS data for Indonesia is not currently available for the period from July 2020.\n\nVessel monitoring system (VMS) data provided by the Indonesian Government’s Ministry of Maritime Affairs and Fisheries. Data is collected using their VMS via satellites and terrestrial receivers, and contains a vessel identities, gear type, location, speed, direction and more. Global Fishing Watch analyzes this data using the same algorithms developed for automatic identification system (AIS) data to identify fishing activity and behaviors. The algorithm classifies each broadcast data point for these vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. VMS broadcasts data quite differently from AIS and may give different measures of completeness, accuracy and quality. Over time our algorithms will improve across all our broadcast data formats. Global Fishing Watch’s fishing presence algorithm for VMS, as for AIS, is a best effort to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified, or that the heat map may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing” or “fishing effort,” as “apparent,” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch fishing presence algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of AIS vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification techniques." }, "private-indonesia-ipnlf-fishing-effort": { "name": "AP2HI-IPNLF: Indonesia Pelagic", "description": "Indonesia AP2HI-IPNLF Fishing Effort" }, "private-indonesia-ipnlf-presence": { "name": "AP2HI-IPNLF : Pélagique Indonésie", "description": "AP2HI-IPNLF Presence" }, "private-indonesia-ipnlf-vessel-identity": { "name": "IPNLF Indonésie (Navires)", "description": "Navires (IPNLF Indonésie)" }, "private-indonesia-pelagic-fishing-effort": { "name": "Indonesia Pelagic (Pilot)", "description": "Indonesia Pelagic Fishing Effort Private Data" }, "private-indonesia-pelagic-presence": { "name": "Pélagiques Indonésie", "description": "Pelagic Presence" }, "private-indonesia-pelagic-vessel-identity": { "name": "Pélagiques Indonésie (Navires)", "description": "Navires (Pélagiques Indonésie)" }, "private-indonesia-presence": { "name": "VMS Indonesia (Presence)", "description": "Présence" }, "private-indonesia-rare-fishing-effort": { "name": "Rare: Indonesia Pelagic", "description": "Indonesia Rare Fishing Effort" }, "private-indonesia-rare-presence": { "name": "Rare : Pélagique, Indonésie", "description": "Rare Presence" }, "private-indonesia-rare-vessel-identity": { "name": "Rare, Indonésie (Navires)", "description": "Navires (Rare, Indonésie)" }, "private-indonesia-zebrax-presence": { "name": "Indonesia Zebrax (Private)", "description": "Cette couche de Global Fishing Watch utilise les données fournies par Rare, Aruna et AP2HI. Les données sont collectées à l'aide d'appareils de différents fournisseurs qui suivent l'emplacement et la vitesse. Les informations affichées représentent la présence du navire. La présence est déterminée en prenant toutes les positions transmises par le dispositif de repérage du navire." }, "private-indonesia-zebrax-vessel-identity": { "name": "Zebra X Indonésie (Navires)", "description": "Navires (Zebra X, Indonésie)" }, "private-panama-fishing-effort": { "name": "Apparent Fishing Effort Panama VMS", "description": "Vessel monitoring system (VMS) data provided by the Panamanian Authority of Aquatic Resources (ARAP). Data is received by Panama’s VMS system via satellite and contains vessel identities, gear type, location, speed, direction and more. Panama’s carrier vessel data is also available here. Each point in the carrier vessel data layer represents a position of the carriers, but not all positions are displayed. Carrier vessel positions are displayed once per day. In the future, we expect to be able to display more positions. Click on a carrier vessel’s position to view the vessel’s complete track. Global Fishing Watch analyzes this data using the same algorithms we developed for automatic identification system (AIS) data to identify fishing activity and behaviors. The algorithm classifies each broadcast data point from vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. VMS broadcasts data quite differently from AIS and may give different measures of completeness, accuracy and quality. Over time our algorithms will improve across all our broadcast data formats. Global Fishing Watch’s fishing detection algorithm for VMS, as for AIS, is a best effort to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified, or that the heat map may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing,” and “fishing effort,” as “apparent” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch fishing detection algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of AIS vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification." }, "private-panama-presence": { "name": "Vessel Presence Panama VMS", "description": "This layer uses the Vessel Monitoring System (VMS) data provided by the Panamanian Authority of Aquatic Resources (ARAP). The data is received by Panama’s VMS system via satellite and contains vessel identities, gear type, location, speed, direction and more. Each point in the carrier vessel data layer represents a position of the carriers, but not all positions are displayed. Carrier vessel positions are displayed once per day. Click on a carrier vessel’s position to view the vessel’s complete track.", "schema": { "shiptype": { "keyword": "type de navire", "enum": { "carrier": "carrier", "fishing": "pêche", "oil_tanker": "oil_tanker" } } } }, "private-panama-vessel-identity-fishing": { "name": "VMS Panama privé (Navires de pêche, Privé)", "description": "Jeu de données pour VMS Panama (Privé)", "schema": { "selfReportedInfo.imo": { "keyword": "imo" }, "selfReportedInfo.nationalRegisterNumber": { "keyword": "nationalRegisterNumber" }, "selfReportedInfo.ssvid": { "keyword": "ssvid" } } }, "private-panama-vessel-identity-non-fishing": { "name": "Panama Private VMS (Private Non Fishing Vessels)", "description": "Jeu de données pour VMS Panama (Privé)", "schema": { "selfReportedInfo.imo": { "keyword": "imo" }, "selfReportedInfo.nationalRegisterNumber": { "keyword": "nationalRegisterNumber" }, "selfReportedInfo.ssvid": { "keyword": "ssvid" } } }, "private-peru-fishing-effort": { "name": "Apparent Fishing Effort Peru VMS", "description": "Vessel monitoring system (VMS) data provided by the Peruvian Government’s Ministry of Production, Fisheries Sector (PRODUCE). Permission to include Peruvian Data required that a 10 day delay to publishing was implemented. Data is collected using their vessel monitoring system (VMS) via satellites and terrestrial receivers, and contains a vessel’s identity gear type, location, speed, direction and more. Global Fishing Watch analyzes this data using the same algorithms developed for automatic identification system (AIS) data to identify fishing activity and behaviors. The algorithm classifies each broadcast data point for these vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. VMS broadcasts data quite differently from AIS and may give different measures of completeness, accuracy and quality. Over time our algorithms will improve across all our broadcast data formats. Global Fishing Watch’s fishing detection algorithm for VMS, as for AIS, is a best effort to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified, or that the heat map may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing” or “fishing effort,” as “apparent,” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch fishing detection algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of AIS vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification techniques.", "schema": { "fleet": { "keyword": "flotte", "enum": { "industrial": "industrielle", "artisanal": "artisanale", "small-scale": "small-scale", "not defined": "non définie" } }, "origin": { "keyword": "origine", "enum": { "PER": "PER", "Foreign": "Étrangère" } } } }, "private-peru-presence": { "name": "Vessel Presence Peru VMS", "description": "Vessel monitoring system (VMS) data provided by the Peruvian Government’s Ministry of Production, Fisheries Sector (PRODUCE). Permission to include Peruvian Data required that a 10 day delay to publishing was implemented. Data is collected using their vessel monitoring system (VMS) via satellites and terrestrial receivers, and contains a vessel’s identity gear type, location, speed, direction and more. Global Fishing Watch analyzes this data using the same algorithms developed for automatic identification system (AIS) data to identify fishing activity and behaviors. The algorithm classifies each broadcast data point for these vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. VMS broadcasts data quite differently from AIS and may give different measures of completeness, accuracy and quality. Over time our algorithms will improve across all our broadcast data formats. Global Fishing Watch’s fishing presence algorithm for VMS, as for AIS, is a best effort to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified, or that the heat map may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing” or “fishing effort,” as “apparent,” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch fishing presence algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of AIS vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification techniques.", "schema": { "fleet": { "keyword": "flotte", "enum": { "industrial": "industrielle", "artisanal": "artisanale", "small-scale": "petite échelle", "not defined": "non définie" } }, "origin": { "keyword": "origine", "enum": { "PER": "PER", "Foreign": "Étrangère" } } } }, "private-peru-vessel-identity-fishing": { "name": "VMS Pérou privé (Navires de pêche)", "description": "Jeu de données pour VMS Pérou (Privé)", "schema": { "selfReportedInfo.nationalId": { "keyword": "nationalId" } } }, "private-png-fishing-effort": { "name": "Papua New Guinea VMS", "description": "Les données du système de surveillance des navires (VMS) sont fournies par l'Autorité nationale des pêches de Papouasie-Nouvelle-Guinée. Les données sont collectées à l'aide du VMS national de Papouasie-Nouvelle-Guinée et fournies par le Système d'information et de gestion des pêches (FIMS). Les données VMS incluent les identifiants et l'emplacement des navires, et sont publiées avec un délai de cinq jours. Global Fishing Watch déduit la vitesse et le cap de chaque position du navire et analyse ces données à l'aide des mêmes algorithmes développés pour le système d'identification automatique (AIS) afin d'identifier les activités et les comportements de pêche. L'algorithme classe chaque point de données diffusé par les navires comme étant apparemment en train de pêcher ou non et affiche le premier sur la carte thermique des activités de pêche de Global Fishing Watch. Le VMS diffuse les données différemment de l'AIS et peut donner différentes mesures d'exhaustivité, de précision et de qualité. Global Fishing Watch améliore continuellement ses algorithmes dans tous les formats de données de diffusion pour identifier de manière algorithmique «l'activité de pêche apparente». Il est possible que certaines activités de pêche ne soient pas identifiées ou que la carte thermique montre une activité de pêche apparente alors que la pêche n'a pas lieu. Pour ces raisons, Global Fishing Watch qualifie les termes « activité de pêche », « pêche » ou « effort de pêche », d'apparents plutôt que de certains. Toutes les informations de Global Fishing Watch sur «l'activité de pêche apparente» doivent être considérées comme une estimation et doivent être utilisées à la seule discrétion de l'utilisateur. Les algorithmes de détection de pêche de Global Fishing Watch sont développés et testés à l'aide de données d'événements de pêche réelles collectées par des observateurs et sont combinés à une analyse experte des données de mouvement des navires AIS, ce qui permet la classification manuelle de milliers d'événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager les données de classification des activités de pêche et améliorer les techniques de classification automatisées" }, "private-png-fishing-identity-vessels": { "name": "VMS Papouasie Nouvelle-Guinée (Navires de pêche)", "description": "Jeu de données pour VMS Papouasie Nouvelle-Guinée (Privé)" }, "private-png-presence": { "name": "VMS Papouasie Nouvelle-Guinée", "description": "Les données du système de surveillance des navires (VMS) sont fournies par l'Autorité nationale des pêches de Papouasie-Nouvelle-Guinée. Les données sont collectées à l'aide du VMS national de Papouasie-Nouvelle-Guinée fourni par le Système d'information et de gestion des pêches (FIMS). Les données VMS incluent les identifiants et l'emplacement des navires, et sont publiées avec un délai de cinq jours.\n\nLa couche d'activité affiche une carte thermique de la présence des navires. La présence est déterminée en prenant deux positions par heure et par navire à partir des positions transmises par le VMS du navire." }, "private-vms-blz-encounters-events": { "name": "Encounter Events. (BLZ)", "description": "Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Users can filter encounter events by vessel characteristics and context, including:
Currently displayed encounter types include:
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.
You can read more about transshipment behaviour from our report or scientific publication.
", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "encounter_type": { "keyword": "encounter_type", "enum": { "-": "-" } } } }, "private-vms-blz-fishing-effort": { "name": "VMS Belize", "description": "Vessel Monitoring System (VMS) data for Belize is provided by the Belize High Seas Fisheries Unit (BHSFU). This data is collected via satellite through Belize's national VMS and includes information on vessels' location, speed, course, and movement. The data is published with a 3-day delay, and historical data is available from 2021 onwards. Due to a degradation in data quality for the Belize vessel feed - specifically, we are no longer receiving vessel shiptype information - we are unable to run our Fishing Effort model on this dataset. Should we be able to re-establish the minimum data requirements (shiptype), we will republish fishing effort in the future.
Public users can view vessel tracks for Belize VMS data, but cannot download them. Vessel names and certain identity information are not available to public users. If you are a member of the Belize government, please contact our support team to request access to a private workspace at support@globalfishingwatch.org. If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please don't hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "private-vms-blz-loitering-events": { "name": "Loitering Events (BLZ)", "description": "Global Fishing Watch classifies an event as a loitering event when:
Learn more about considerations of using AIS data by looking at the AIS limitations section in the Apparent fishing events (AIS) data documentation..
", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "type": { "keyword": "type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-blz-port-visits-events": { "name": "Port Visits Events (BLZ)", "description": "The dataset contains port visits events for BLZ", "schema": { "confidences": { "keyword": "confidences", "enum": { "2": "2", "3": "3", "4": "4" } }, "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "type": { "keyword": "type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-blz-presence": { "name": "VMS Belize Presence", "description": "Vessel Monitoring System (VMS) data for Belize is provided by the Belize High Seas Fisheries Unit (BHSFU). This data is collected via satellite through Belize's national VMS and includes information on vessels' location, speed, course, and movement. The data is published with a 3-day delay, and historical data is available from 2021 onwards. Due to a degradation in data quality for the Belize vessel feed - specifically, we are no longer receiving vessel shiptype information - we are unable to run our Fishing Effort model on this dataset. Should we be able to re-establish the minimum data requirements (shiptype), we will republish fishing effort in the future.
Public users can view vessel tracks for Belize VMS data, but cannot download them. Vessel names and certain identity information are not available to public users. If you are a member of the Belize government, please contact our support team to request access to a private workspace at support@globalfishingwatch.org. If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please don't hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-blz-tracks": { "name": "Belize VMS", "description": "Tracks dataset for VMS Belize (Private)" }, "private-vms-blz-vessel-identity": { "name": "VMS Belize", "description": "Vessels (VMS Belize)" }, "private-vms-bra-encounters-events": { "name": "Encounter Events. (BRA)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Vessel Monitoring System (VMS) data for Brazil is collected via satellite and provided through a partnership with Brazil's Ministry of Fisheries and Aquaculture (MPA). The data is published with a 3-day delay, and historical data is available from 2016 onward. The polling rate depends on vessel type: drifting longline vessels report approximately every 20 minutes, while other vessels report about once per hour.
Please note that given the lower polling rates of some vessel types compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
In our Brazil VMS dataset, you can filter vessels by various gear types as well as by their target species.
Vessel names are visible to public users, and vessel tracks can be viewed but not downloaded. If you require data access beyond what is publicly available, please contact our support team to request access to a private workspace at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "license_category": { "keyword": "license_category", "enum": { "": "", "1.1 - Espinhel horizontal (superfície)": "1.1 - Espinhel horizontal (superfície)", "1.10 - Espinhel vertical/Covos": "1.10 - Espinhel vertical/Covos", "1.11 - Espinhel vertical": "1.11 - Espinhel vertical", "1.12 - Linha de mão (fundo)": "1.12 - Linha de mão (fundo)", "1.13 - Linha/vara - com isca viva": "1.13 - Linha/vara - com isca viva", "1.14 - Linha de mão (fundo)": "1.14 - Linha de mão (fundo)", "1.15 - Linha de mão (superfície)": "1.15 - Linha de mão (superfície)", "1.17 - Cardume associado": "1.17 - Cardume associado", "1.18 - Cardume associado": "1.18 - Cardume associado", "1.2 - Espinhel horizontal (superfície)": "1.2 - Espinhel horizontal (superfície)", "1.3 - Espinhel horizontal (superfície) - com isca-viva": "1.3 - Espinhel horizontal (superfície) - com isca-viva", "1.4 - Espinhel horizontal (superfície)": "1.4 - Espinhel horizontal (superfície)", "1.5 - Espinhel horizontal (fundo)": "1.5 - Espinhel horizontal (fundo)", "1.6 - Espinhel horizontal (fundo)": "1.6 - Espinhel horizontal (fundo)", "1.7 - Espinhel horizontal (fundo)": "1.7 - Espinhel horizontal (fundo)", "1.8 - Espinhel vertical/covos": "1.8 - Espinhel vertical/covos", "1.9 - Espinhel vertical/Covos": "1.9 - Espinhel vertical/Covos", "2.10 - Emalhe costeiro (fundo)": "2.10 - Emalhe costeiro (fundo)", "2.11 - Emalhe costeiro (fundo)": "2.11 - Emalhe costeiro (fundo)", "2.12 - Emalhe costeiro (fundo)": "2.12 - Emalhe costeiro (fundo)", "2.13 - Emalhe Costeiro Diversificado": "2.13 - Emalhe Costeiro Diversificado", "2.2 - Emalhe costeiro (superfície) ": "2.2 - Emalhe costeiro (superfície) ", "2.3 - Emalhe oceânico (fundo)": "2.3 - Emalhe oceânico (fundo)", "2.4 - Emalhe costeiro (fundo)": "2.4 - Emalhe costeiro (fundo)", "2.5 - Emalhe costeiro (superfície)": "2.5 - Emalhe costeiro (superfície)", "2.6 - Emalhe costeiro (superfície)": "2.6 - Emalhe costeiro (superfície)", "2.7 - Emalhe costeiro (superfície)": "2.7 - Emalhe costeiro (superfície)", "2.8 - Emalhe costeiro (superfície)": "2.8 - Emalhe costeiro (superfície)", "3.1 - Arrasto (fundo) parelha ou trilheira (*)": "3.1 - Arrasto (fundo) parelha ou trilheira (*)", "3.10 - Arrasto costeiro (fundo) - duplo": "3.10 - Arrasto costeiro (fundo) - duplo", "3.11 - Arrasto costeiro (fundo simples e parelha": "3.11 - Arrasto costeiro (fundo simples e parelha", "3.12 - Arrasto oceânico (fundo) – simples e duplo": "3.12 - Arrasto oceânico (fundo) – simples e duplo", "3.13 - Arrasto oceânico (fundo) – simples e duplo": "3.13 - Arrasto oceânico (fundo) – simples e duplo", "3.14 - Arrasto (meia água)": "3.14 - Arrasto (meia água)", "3.2 - Arrasto (fundo) – Simples ou parelha": "3.2 - Arrasto (fundo) – Simples ou parelha", "3.3 - Arrasto (fundo) - duplo ou simples (**)": "3.3 - Arrasto (fundo) - duplo ou simples (**)", "3.4 - Arrasto (fundo) - duplo ou simples": "3.4 - Arrasto (fundo) - duplo ou simples", "3.5 - Arrasto (fundo) - duplo ou simples": "3.5 - Arrasto (fundo) - duplo ou simples", "3.6 - Arrasto (fundo) - duplo": "3.6 - Arrasto (fundo) - duplo", "3.7 - Arrasto (fundo)– duplo": "3.7 - Arrasto (fundo)– duplo", "3.8 - Arrasto (fundo) - duplo ou simples": "3.8 - Arrasto (fundo) - duplo ou simples", "3.9 - Arrasto (fundo) - duplo ou simples": "3.9 - Arrasto (fundo) - duplo ou simples", "4.1 - Cerco": "4.1 - Cerco", "4.2 - Cerco": "4.2 - Cerco", "4.3 - Cerco": "4.3 - Cerco", "4.4 - Cerco": "4.4 - Cerco", "4.6 - Cerco": "4.6 - Cerco", "5.1 - Covos": "5.1 - Covos", "5.10 - Potes": "5.10 - Potes", "5.11 - Potes": "5.11 - Potes", "5.12 - Potes": "5.12 - Potes", "5.2 - Covos": "5.2 - Covos", "5.3 - Covos": "5.3 - Covos", "5.4 - Covos": "5.4 - Covos", "5.5 - Covos": "5.5 - Covos", "5.6 - Covos": "5.6 - Covos", "5.9 - Covos": "5.9 - Covos", "Sem código IN - Covos": "Sem código IN - Covos" } }, "target_species": { "keyword": "target_species", "enum": { "": "", "Agulha": "Agulha", "Albacora laje (Thunnus albacares), Albacora bandolim (Thunnus obesus) e Bonito listrado (Katsuwonus pelamis).": "Albacora laje (Thunnus albacares), Albacora bandolim (Thunnus obesus) e Bonito listrado (Katsuwonus pelamis).", "Anchova (Pomatomus saltatrix), corvina (Micropogonias furnieri), pescada (Cynoscion guatucupa), castanha (Umbrina canosai), abrótea (Urophycis brasiliensis) e fauna acompanhante": "Anchova (Pomatomus saltatrix), corvina (Micropogonias furnieri), pescada (Cynoscion guatucupa), castanha (Umbrina canosai), abrótea (Urophycis brasiliensis) e fauna acompanhante", "Anchova, tainha e sororoca": "Anchova, tainha e sororoca", "Anchoíta, galo, calamar": "Anchoíta, galo, calamar", "Atuns (albacora laje, albacora branca e albacora bandolim)": "Atuns (albacora laje, albacora branca e albacora bandolim)", "Bagres (Ariidae), dourada e pescada branca, arraia, pescada amarela, pescada gó, corvina, tainha.": "Bagres (Ariidae), dourada e pescada branca, arraia, pescada amarela, pescada gó, corvina, tainha.", "Batata, Abrótea de profundidade, Namorado, Garoupa,Bagre e cherne verdadeiro": "Batata, Abrótea de profundidade, Namorado, Garoupa,Bagre e cherne verdadeiro", "Bonito listrado": "Bonito listrado", "Camarão rosa (santana e barba ruça)": "Camarão rosa (santana e barba ruça)", "Camarão rosa, sete- barbas e branco": "Camarão rosa, sete- barbas e branco", "Camarão santana e barba ruça": "Camarão santana e barba ruça", "Camarão sete barbas (Santana e barba ruça)": "Camarão sete barbas (Santana e barba ruça)", "Camarões (sete- barbas, branco, rosa)": "Camarões (sete- barbas, branco, rosa)", "Camarões de profundidade": "Camarões de profundidade", "Caranguejo de profundidade (Chaceon spp.)": "Caranguejo de profundidade (Chaceon spp.)", "Caranguejo vermelho (Chaceon notialis)": "Caranguejo vermelho (Chaceon notialis)", "Cavalas, Albacorinhas": "Cavalas, Albacorinhas", "Corvina, castanha, pescada e pescadinha real": "Corvina, castanha, pescada e pescadinha real", "Corvina, castanha, pescada e pescadinha real, linguado, abrotea, cabrinha.": "Corvina, castanha, pescada e pescadinha real, linguado, abrotea, cabrinha.", "Corvina, pescada, castanha, abrótea": "Corvina, pescada, castanha, abrótea", "Dourada, Piramutaba e Gurijuba": "Dourada, Piramutaba e Gurijuba", "Dourado": "Dourado", "Espadarte": "Espadarte", "Galo-de-fundo, abrótea-de-fundo, merluza": "Galo-de-fundo, abrótea-de-fundo, merluza", "Lagosta verde e lagosta vermelha": "Lagosta verde e lagosta vermelha", "Pargo": "Pargo", "Pargo rosa": "Pargo rosa", "Peixe sapo": "Peixe sapo", "Peroá, Garoupa e Corvina": "Peroá, Garoupa e Corvina", "Pescada amarela gurijuba e camurim": "Pescada amarela gurijuba e camurim", "Pescada gó, camurim e corvina": "Pescada gó, camurim e corvina", "Piramutaba": "Piramutaba", "Piramutaba e dourada": "Piramutaba e dourada", "Polvo": "Polvo", "Saramunete": "Saramunete", "Sardinha lage, savelha, galo, sardinha-cascuda, peixe-porco, sardinha-boca-torta, xaréu, guaivira, palombeta e cavalinha ": "Sardinha lage, savelha, galo, sardinha-cascuda, peixe-porco, sardinha-boca-torta, xaréu, guaivira, palombeta e cavalinha ", "Sardinha verdadeira": "Sardinha verdadeira", "Sardinha-lage": "Sardinha-lage", "Scombridae, Lutjanidae, Serranidae e Caranjidae (a definir) e Vermelhos (cioba, dentão, guaíuba, ariacó)": "Scombridae, Lutjanidae, Serranidae e Caranjidae (a definir) e Vermelhos (cioba, dentão, guaíuba, ariacó)", "Serra": "Serra", "Serranidae e caranjidae (detalhar)": "Serranidae e caranjidae (detalhar)", "Tainha": "Tainha", "Vermelhos (especificar)": "Vermelhos (especificar)" } }, "fleet_code": { "keyword": "fleet_code", "enum": { "1.1": "1.1", "1.10": "1.10", "1.12": "1.12", "1.13": "1.13", "1.14": "1.14", "1.17": "1.17", "1.18": "1.18", "1.2": "1.2", "1.3": "1.3", "1.4": "1.4", "1.5": "1.5", "1.6": "1.6", "1.7": "1.7", "1.8": "1.8", "1.9": "1.9", "2.10": "2.10", "2.11": "2.11", "2.13": "2.13", "2.2": "2.2", "2.3": "2.3", "2.4": "2.4", "2.5": "2.5", "3.1": "3.1", "3.10": "3.10", "3.11": "3.11", "3.12": "3.12", "3.13": "3.13", "3.2": "3.2", "3.3": "3.3", "3.5": "3.5", "3.6": "3.6", "3.9": "3.9", "4.1": "4.1", "4.2": "4.2", "4.3": "4.3", "4.4": "4.4", "4.6": "4.6", "5.1": "5.1", "5.10": "5.10", "5.11": "5.11", "5.2": "5.2", "5.3": "5.3", "5.4": "5.4", "5.6": "5.6", "5.9": "5.9", "Sem código IN": "Sem código IN" } } } }, "private-vms-bra-gap-events": { "name": "Gaps Events (BRA)", "description": "The VMS Gaps dataset is experimental, and is calculated based on the intervals between consecutive VMS positions. These gaps are visible as part of the Gaps layer on the map, as well as in individual vessel profiles. It is important to note that not all gaps indicate a vessel has deliberately turned off its VMS device - gaps can also result from broader data anomalies such as fleet-wide outages. We are working on better ways to distinguish genuine transmission gaps from wider data provider issues.
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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
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 support@globalfishingwatch.org.
A port visit is shown on the map when VMS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Vessel Monitoring System (VMS) data for Brazil is collected via satellite and provided through a partnership with Brazil's Ministry of Fisheries and Aquaculture (MPA). The data is published with a 3-day delay, and historical data is available from 2016 onward. The polling rate depends on vessel type: drifting longline vessels report approximately every 20 minutes, while other vessels report about once per hour.
Please note that given the lower polling rates of some vessel types compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
In our Brazil VMS dataset, you can filter vessels by various gear types as well as by their target species.
Vessel names are visible to public users, and vessel tracks can be viewed but not downloaded. If you require data access beyond what is publicly available, please contact our support team to request access to a private workspace at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-bra-tracks": { "name": "Brazil VMS", "description": "Tracks dataset for VMS Brazil (Private)" }, "private-vms-bra-vessel-identity": { "name": "VMS Brazil", "description": "Vessels (VMS Brazil)", "schema": { "selfReportedInfo.fishingLicenseCode": { "keyword": "fishingLicenseCode" }, "selfReportedInfo.fleetCode": { "keyword": "fleetCode", "enum": { "1.1": "1.1", "1.10": "1.10", "1.12": "1.12", "1.13": "1.13", "1.14": "1.14", "1.17": "1.17", "1.18": "1.18", "1.2": "1.2", "1.3": "1.3", "1.4": "1.4", "1.5": "1.5", "1.6": "1.6", "1.7": "1.7", "1.8": "1.8", "1.9": "1.9", "2.10": "2.10", "2.11": "2.11", "2.13": "2.13", "2.2": "2.2", "2.3": "2.3", "2.4": "2.4", "2.5": "2.5", "3.1": "3.1", "3.10": "3.10", "3.11": "3.11", "3.12": "3.12", "3.13": "3.13", "3.2": "3.2", "3.3": "3.3", "3.5": "3.5", "3.6": "3.6", "3.9": "3.9", "4.1": "4.1", "4.2": "4.2", "4.3": "4.3", "4.4": "4.4", "4.6": "4.6", "5.1": "5.1", "5.10": "5.10", "5.11": "5.11", "5.2": "5.2", "5.3": "5.3", "5.4": "5.4", "5.6": "5.6", "5.9": "5.9", "Sem código IN": "Sem código IN" } }, "selfReportedInfo.vesselRegistrationCode": { "keyword": "vesselRegistrationCode" } } }, "private-vms-chl-encounters-events": { "name": "Encounter Events. (CHL)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Vessel Monitoring System (VMS) data is provided by the Chilean government's fisheries and aquaculture regulator (SERNAPESCA). The data includes information on vessels' location, speed, course, and movement, and is published with a 3-day delay. Historical VMS data is available from 2019 onward.
Users can filter Chile's VMS data by fleet, distinguishing between small-scale fishing vessels (18 meters) and industrial fishing vessels (>18 meters). In addition to fishing vessels, SERNAPESCA also tracks aquaculture vessels and actively uses this map to monitor vessel activity across its fleet.
The polling rate depends on the fishery, with positions reported approximately every 8 to 15 minutes.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are available to public users, and tracks can be viewed and downloaded.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "INDUSTRY": "INDUSTRY", "SMALL_FISHERIES": "SMALL_FISHERIES" } } } }, "private-vms-chl-loitering-events": { "name": "Loitering Events (CHL)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
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 support@globalfishingwatch.org.
A port visit is shown on the map when VMS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Vessel Monitoring System (VMS) data is provided by the Chilean government's fisheries and aquaculture regulator (SERNAPESCA). The data includes information on vessels' location, speed, course, and movement, and is published with a 3-day delay. Historical VMS data is available from 2019 onward.
Users can filter Chile's VMS data by fleet, distinguishing between small-scale fishing vessels (18 meters) and industrial fishing vessels (>18 meters). In addition to fishing vessels, SERNAPESCA also tracks aquaculture vessels and actively uses this map to monitor vessel activity across its fleet.
The polling rate depends on the fishery, with positions reported approximately every 8 to 15 minutes.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are available to public users, and tracks can be viewed and downloaded.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "source_fleet": { "keyword": "source_fleet", "enum": { "AQUACULTURE": "AQUACULTURE", "INDUSTRY": "INDUSTRY", "SMALL_FISHERIES": "SMALL_FISHERIES", "TRANSPORT": "TRANSPORT" } }, "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-chl-tracks": { "name": "CHILE VMS", "description": "Tracks dataset for VMS CHILE (Private)" }, "private-vms-chl-vessel-identity": { "name": "VMS Chile", "description": "Vessels (VMS Chile)" }, "private-vms-cri-encounters-events": { "name": "Encounter Events. (CRI)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Vessel Monitoring System (VMS) data is provided by the Costa Rican Fisheries and Aquaculture Institute, with CLS as the data provider. The data includes information on vessels' location, speed, course, and movement, and is published with a 3-day delay. Historical VMS data is available from 2021 onward. The polling rate is about once per hour. We publish data for the Tuna fleet, Industrial longline fleet, and sardine fleet.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names are not visible to public users. Vessel tracks can be viewed but cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team to request access to a private workspace at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "ATUNEROS": "ATUNEROS", "AVANZADOS": "AVANZADOS", "SARDINEROS": "SARDINEROS" } } } }, "private-vms-cri-loitering-events": { "name": "Loitering Events (CRI)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
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 support@globalfishingwatch.org.
A port visit is shown on the map when VMS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Vessel Monitoring System (VMS) data is provided by the Costa Rican Fisheries and Aquaculture Institute, with CLS as the data provider. The data includes information on vessels' location, speed, course, and movement, and is published with a 3-day delay. Historical VMS data is available from 2021 onward. The polling rate is about once per hour. We publish data for the Tuna fleet, Industrial longline fleet, and sardine fleet.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names are not visible to public users. Vessel tracks can be viewed but cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team to request access to a private workspace at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "source_fleet": { "keyword": "source_fleet", "enum": { "ATUNEROS": "ATUNEROS", "AVANZADOS": "AVANZADOS", "SARDINEROS": "SARDINEROS" } }, "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-cri-tracks": { "name": "Costa Rica VMS", "description": "Tracks dataset for VMS Costa Rica (Private)" }, "private-vms-cri-vessel-identity": { "name": "VMS Costa Rica", "description": "Vessels (VMS Costa Rica)", "schema": { "selfReportedInfo.sourceFleet": { "keyword": "sourceFleet", "enum": { "ATUNEROS": "ATUNEROS", "AVANZADOS": "AVANZADOS", "SARDINEROS": "SARDINEROS" } } } }, "private-vms-ecu-encounters-events": { "name": "Encounter Events. (ECU)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Vessel Monitoring System (VMS) data is provided by the National Directorate of Aquatic Spaces of the Ecuadorian Navy. The data is collected via satellite through Ecuador's national VMS and includes information on vessels' identity, location, speed, course, and movement. It is published with a 7-day delay, and historical data is available from 2020 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "private-vms-ecu-loitering-events": { "name": "Loitering Events (ECU)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
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 support@globalfishingwatch.org.
A port visit is shown on the map when VMS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Vessel Monitoring System (VMS) data is provided by the National Directorate of Aquatic Spaces of the Ecuadorian Navy. The data is collected via satellite through Ecuador's national VMS and includes information on vessels' identity, location, speed, course, and movement. It is published with a 7-day delay, and historical data is available from 2020 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-ecu-tracks": { "name": "Ecuador VMS", "description": "Tracks dataset for VMS Ecuador (Private)" }, "private-vms-ecu-vessel-identity": { "name": "VMS Ecuador", "description": "Vessels (VMS Ecuador)", "schema": { "selfReportedInfo.registryNumber": { "keyword": "registryNumber" } } }, "private-vms-mne-encounters-events": { "name": "Encounter Events. (MNE)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Vessel Monitoring System (VMS) data for Montenegro is provided by the Ministry of Agriculture, Forestry and Water Management of Montenegro. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 3-day delay, and historical data is available from 2024 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "private-vms-mne-loitering-events": { "name": "Loitering Events (MNE)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
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 support@globalfishingwatch.org.
A port visit is shown on the map when VMS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Vessel Monitoring System (VMS) data for Montenegro is provided by the Ministry of Agriculture, Forestry and Water Management of Montenegro. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 3-day delay, and historical data is available from 2024 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-mne-tracks": { "name": "Montenegro VMS", "description": "Tracks dataset for VMS Montenegro (Private)" }, "private-vms-mne-vessel-identity": { "name": "VMS Montenegro", "description": "Vessels (VMS Montenegro)", "schema": { "selfReportedInfo.externalId": { "keyword": "externalId" }, "selfReportedInfo.imo": { "keyword": "imo" } } }, "private-vms-nor-encounters-events": { "name": "Encounter Events. (NOR)", "description": "Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Users can filter encounter events by vessel characteristics and context, including:
Currently displayed encounter types include:
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.
You can read more about transshipment behaviour from our report or scientific privateation.
", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "encounter_type": { "keyword": "encounter_type", "enum": { "FISHING-FISHING": "FISHING-FISHING", "FISHING-NON_FISHING": "FISHING-NON_FISHING", "NON_FISHING-FISHING": "NON_FISHING-FISHING" } } } }, "private-vms-nor-fishing-effort": { "name": "VMS Norway", "description": "Vessel Monitoring System (VMS) data for Norway is provided by the Norwegian Directorate of Fisheries. The data is collected via satellite and includes information on vessels' identity, location, speed, course, and movement. It is published with a 3-day delay, and historical data is available from 2015 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "private-vms-nor-loitering-events": { "name": "Loitering Events (NOR)", "description": "Global Fishing Watch classifies an event as a loitering event when:
Learn more about considerations of using AIS data by looking at the AIS limitations section in the Apparent fishing events (AIS) data documentation..
", "schema": { "duration": { "keyword": "duration", "enum": { "0": "0", "48": "48" } }, "type": { "keyword": "type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-nor-port-visits-events": { "name": "Port Visits Events (NOR)", "description": "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 support@globalfishingwatch.org.
A port visit is shown on the map when VMS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Vessel Monitoring System (VMS) data for Norway is provided by the Norwegian Directorate of Fisheries. The data is collected via satellite and includes information on vessels' identity, location, speed, course, and movement. It is published with a 3-day delay, and historical data is available from 2015 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-nor-tracks": { "name": "Norway VMS", "description": "Tracks dataset for VMS Norway (Private)" }, "private-vms-nor-vessel-identity": { "name": "VMS Norway", "description": "Vessels (VMS Norway)" }, "private-vms-pan-encounters-events": { "name": "Encounter Events. (PAN)", "description": "Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Users can filter encounter events by vessel characteristics and context, including:
Currently displayed encounter types include:
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.
You can read more about transshipment behaviour from our report or scientific publication.
", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "encounter_type": { "keyword": "encounter_type", "enum": { "FISHING-FISHING": "FISHING-FISHING", "FISHING-NON_FISHING": "FISHING-NON_FISHING", "FISHING-": "FISHING-", "NON_FISHING-FISHING": "NON_FISHING-FISHING", "NON_FISHING-NON_FISHING": "NON_FISHING-NON_FISHING", "NON_FISHING-": "NON_FISHING-", "-FISHING": "-FISHING", "-NON_FISHING": "-NON_FISHING", "-": "-" } } } }, "private-vms-pan-fishing-effort": { "name": "VMS Panama", "description": "Vessel Monitoring System (VMS) data is provided by the Panama Aquatic Resources Authority (ARAP). The data is collected via satellite through Panama's national VMS and includes information on vessels' identity, location, speed, course, and movement. It is published with a 3-day delay, and historical data is available from 2012 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
For the international fleet, vessel identity information is available to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "INTERNATIONAL": "INTERNATIONAL", "LONGLINE": "LONGLINE", "TRAWLER": "TRAWLER" } } } }, "private-vms-pan-loitering-events": { "name": "Loitering Events (PAN)", "description": "Global Fishing Watch classifies an event as a loitering event when:
Learn more about considerations of using AIS data by looking at the AIS limitations section in the Apparent fishing events (AIS) data documentation..
", "schema": { "duration": { "keyword": "duration", "enum": { "0": "0", "48": "48" } }, "type": { "keyword": "type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-pan-port-visits-events": { "name": "Port Visits Events (PAN)", "description": "The dataset contains port visits events for PAN", "schema": { "confidences": { "keyword": "confidences", "enum": { "2": "2", "3": "3", "4": "4" } }, "duration": { "keyword": "duration", "enum": { "0": "0", "48": "48" } }, "type": { "keyword": "type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-pan-presence": { "name": "VMS Panama Presence", "description": "Vessel Monitoring System (VMS) data is provided by the Panama Aquatic Resources Authority (ARAP). The data is collected via satellite through Panama's national VMS and includes information on vessels' identity, location, speed, course, and movement. It is published with a 3-day delay, and historical data is available from 2012 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
For the international fleet, vessel identity information is available to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "source_fleet": { "keyword": "source_fleet", "enum": { "INTERNATIONAL": "INTERNATIONAL", "LONGLINE": "LONGLINE", "TRAWLER": "TRAWLER" } }, "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-pan-tracks": { "name": "PANAMA VMS", "description": "Tracks dataset for VMS PANAMA (Private)" }, "private-vms-pan-vessel-identity": { "name": "VMS Panama", "description": "Vessels (VMS Panama)", "schema": { "selfReportedInfo.externalId": { "keyword": "externalId" }, "selfReportedInfo.imo": { "keyword": "imo" }, "selfReportedInfo.ssvid": { "keyword": "ssvid" } } }, "private-vms-per-encounters-events": { "name": "Encounter Events. (PER)", "description": "Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Users can filter encounter events by vessel characteristics and context, including:
Currently displayed encounter types include:
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.
You can read more about transshipment behaviour from our report or scientific publication.
", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "encounter_type": { "keyword": "encounter_type", "enum": { "FISHING-FISHING": "FISHING-FISHING", "FISHING-": "FISHING-", "-FISHING": "-FISHING", "FISHING-NON_FISHING": "FISHING-NON_FISHING", "NON_FISHING-FISHING": "NON_FISHING-FISHING", "-": "-" } } } }, "private-vms-per-fishing-effort": { "name": "VMS Peru", "description": "Global Fishing Watch uses data about a vessel’s identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as known or possible commercial fishing vessels, and applies a fishing presence algorithm to determine “apparent fishing activity” based on changes in vessel speed and direction. The algorithm classifies each AIS broadcast data point for these vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. AIS data as broadcast may vary in completeness, accuracy and quality. Also, data collection by satellite or terrestrial receivers may introduce errors through missing or inaccurate data. Global Fishing Watch’s fishing presence algorithm is a best effort mathematically to identify “apparent fishing activity.” As a result, it is possible that some fishing activity is not identified as such by Global Fishing Watch; conversely, Global Fishing Watch may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies designations of vessel fishing activity, including synonyms of the term “fishing activity,” such as “fishing” or “fishing effort,” as “apparent,” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch is taking steps to make sure fishing activity designations are as accurate as possible. Global Fishing Watch fishing presence algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification techniques.", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "origin": { "keyword": "origin", "enum": { "Foreign": "Foreign", "PER": "PER", "": "" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "": "", "SMALL-SCALE": "SMALL-SCALE", "INDUSTRIAL": "INDUSTRIAL", "ARTISANAL": "ARTISANAL" } } } }, "private-vms-per-loitering-events": { "name": "Loitering Events (PER)", "description": "Global Fishing Watch classifies an event as a loitering event when:
Learn more about considerations of using AIS data by looking at the AIS limitations section in the Apparent fishing events (AIS) data documentation..
", "schema": { "duration": { "keyword": "duration", "enum": { "0": "0", "48": "48" } }, "type": { "keyword": "type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-per-port-visits-events": { "name": "Port Visits Events (PER)", "description": "The dataset contains port visits events for PER", "schema": { "confidences": { "keyword": "confidences", "enum": { "2": "2", "3": "3", "4": "4" } }, "duration": { "keyword": "duration", "enum": { "0": "0", "48": "48" } }, "type": { "keyword": "type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-per-presence": { "name": "VMS Peru Presence", "description": "Global Fishing Watch uses data about a vessels identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as carriers. The activity layer displays a heatmap of vessel presence. The presence is determined by taking one position per day per vessel from the positions transmitted by the vessels AIS.", "schema": { "origin": { "keyword": "origin", "enum": { "Foreign": "Foreign", "PER": "PER" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "INDUSTRIAL": "INDUSTRIAL", "SMALL-SCALE": "SMALL-SCALE", "ARTISANAL": "ARTISANAL", "": "" } }, "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } } } }, "private-vms-per-tracks": { "name": "PERU VMS", "description": "Tracks dataset for VMS PERU (Private)" }, "private-vms-per-vessel-identity": { "name": "VMS Peru", "description": "Vessels (VMS Peru)", "schema": { "selfReportedInfo.externalId": { "keyword": "externalId" }, "selfReportedInfo.hull": { "keyword": "hull", "enum": { "ACERO NAVAL": "ACERO NAVAL", "MADERA": "MADERA", "N/E": "N/E", "NONE": "NONE", "FIBRA DE VIDRIO": "FIBRA DE VIDRIO" } }, "selfReportedInfo.origin": { "keyword": "origin", "enum": { "PERU": "PERU", "FOREIGN": "FOREIGN" } }, "selfReportedInfo.sourceFleet": { "keyword": "sourceFleet", "enum": { "": "", "ARTISANAL": "ARTISANAL", "INDUSTRIAL": "INDUSTRIAL", "SMALL-SCALE": "SMALL-SCALE" } } } }, "private-vms-plw-encounters-events": { "name": "Encounter Events. (PLW)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Vessel Monitoring System (VMS) data for Palau is provided by the Palau National Marine Sanctuary. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 3-day delay, and historical data is available from 2021 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "private-vms-plw-loitering-events": { "name": "Loitering Events (PLW)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
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 support@globalfishingwatch.org.
A port visit is shown on the map when VMS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Vessel Monitoring System (VMS) data for Palau is provided by the Palau National Marine Sanctuary. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 3-day delay, and historical data is available from 2021 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-plw-tracks": { "name": "Palau VMS", "description": "Tracks dataset for VMS Palau (Private)" }, "private-vms-plw-vessel-identity": { "name": "VMS Palau", "description": "Vessels (VMS Palau)", "schema": { "selfReportedInfo.imo": { "keyword": "imo" } } }, "private-vms-png-encounters-events": { "name": "Encounter Events. (PNG)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Vessel Monitoring System (VMS) data for Papua New Guinea is provided by the National Fisheries Authority of Papua New Guinea. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 5-day delay, and historical data is available from 2023 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "private-vms-png-loitering-events": { "name": "Loitering Events (PNG)", "description": "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.
Global Fishing Watch classifies an event as an encounter when two vessels are detected:
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 support@globalfishingwatch.org.
A port visit is shown on the map when VMS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Vessel Monitoring System (VMS) data for Papua New Guinea is provided by the National Fisheries Authority of Papua New Guinea. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 5-day delay, and historical data is available from 2023 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "private-vms-png-tracks": { "name": "Papua New Guinea VMS", "description": "Tracks dataset for VMS Papua New Guinea (Private)" }, "private-vms-png-vessel-identity": { "name": "VMS Papua New Guinea", "description": "Vessels (VMS Papua New Guinea)" }, "proto-global-encounters-events-30min": { "name": "PROTOTYPE - Événements de rencontre de 30 min. (AIS)", "description": "Le jeu de données contient des événements de rencontre de 30 min. (AIS). [Pêche-Transport, Transport-Pêche, Soutien-Pêche, Pêche-Soutien]", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } } } }, "public-areas-to-be-avoided-1618836788619": { "name": "Areas to be Avoided by Cargo Shipping", "description": "25 nm buffer around islands recommending shipping diversion" }, "public-bathymetry-contour": { "name": "Bathymetry Contour", "description": "Combination of lines and points that represent the bathymetry contour" }, "public-belize-fishing-effort": { "name": "Belize VMS", "description": "Les données du système de surveillance des navires (VMS) sont fournies par la Belize High Seas Fisheries Unit (BHSFU). Les données sont collectées à l'aide du système de surveillance des navires du Bélize via des satellites et sont publiées avec un délai de trois jours contenant des informations sur la localisation, la vitesse, le cap et le mouvement des navires. Global Fishing Watch analyse ces données à l'aide des mêmes algorithmes développés pour le système d'identification automatique (AIS) afin d'identifier l'activité et les comportements de pêche. L'algorithme classe chaque point de données diffusé par les navires comme étant apparemment en train de pêcher ou non et affiche la pêche sur la carte thermique des activités de pêche de Global Fishing Watch. Le VMS diffuse les données différemment de l'AIS et peut donner des mesures différentes de l'exhaustivité, de la précision et de la qualité. Global Fishing Watch améliore continuellement ses algorithmes dans tous les formats de données diffusés pour identifier de manière algorithmique « l'activité de pêche apparente ». Il est possible que certaines activités de pêche ne soient pas identifiées ou que la carte thermique montre une activité de pêche apparente alors qu'il n'y a pas réellement de pêche. Pour ces raisons, Global Fishing Watch qualifie les termes « activité de pêche », « pêche » ou « effort de pêche » d'apparents plutôt que certains. Toutes les informations de Global Fishing Watch sur les « activités de pêche apparentes » doivent être considérées comme des estimations et doivent être utilisées à la seule discrétion de l’utilisateur. Les algorithmes de présence de pêche de Global Fishing Watch sont développés et testés à l’aide de données réelles sur les événements de pêche collectées par des observateurs et sont combinés à une analyse d'experts en données de mouvement des navires AIS, ce qui permet la classification manuelle de milliers d’événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager les données de classification des activités de pêche et pour améliorer les techniques de classification automatisée." }, "public-belize-vessel-identity-fishing": { "name": "Bélize VMS", "description": "Identité du navire (VMS Bélize)" }, "public-bra-onyxsat-fishing-effort": { "name": "VMS Brésil", "description": "Global Fishing Watch utilise des données sur l’identité, le type, la localisation, la vitesse, le cap et plus encore d’un navire, diffusées à l’aide du système d’identification automatique (AIS) et collectées via des satellites et des récepteurs terrestres. L’AIS a été développé pour la sécurité et l’évitement des collisions. Global Fishing Watch analyse les données AIS collectées auprès de navires que nos recherches ont identifiés comme des navires de pêche commerciale connus ou potentiels, et applique un algorithme de présence de pêche pour déterminer « l’activité de pêche apparente » en fonction des changements de vitesse et de cap du navire. L’algorithme classe chaque point de données de diffusion AIS pour ces navires comme étant apparemment en train de pêcher ou non et affiche la pêche sur la carte thermique des activités de pêche de Global Fishing Watch. Les données AIS diffusées peuvent varier en termes d’exhaustivité, de précision et de qualité. De plus, la collecte de données par satellite ou par des récepteurs terrestres peut introduire des erreurs en raison de données manquantes ou inexactes. L’algorithme de présence de pêche de Global Fishing Watch est un effort mathématique optimal pour identifier « l’activité de pêche apparente ». Par conséquent, il est possible que certaines activités de pêche ne soient pas identifiées comme telles par Global Fishing Watch ; à l’inverse, Global Fishing Watch peut afficher une activité de pêche apparente alors qu’il n’y a pas réellement de pêche. Pour ces raisons, Global Fishing Watch qualifie les désignations d’activité de pêche des navires, y compris les synonymes du terme « activité de pêche », tels que « pêche » ou « effort de pêche », d’« apparentes » plutôt que certaines. Toutes les informations de Global Fishing Watch sur « l’activité de pêche apparente » doivent être considérées comme une estimation et vous devez vous y fier uniquement à vos propres risques. Global Fishing Watch prend des mesures pour s’assurer que les désignations d’activité de pêche sont aussi précises que possible. Les algorithmes de présence de pêche de Global Fishing Watch sont développés et testés à l’aide de données réelles sur les événements de pêche collectées par des observateurs, combinées à une analyse d'experts en données sur les mouvements des navires, ce qui permet la classification manuelle de milliers d’événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager des données de classification des activités de pêche et des techniques de classification automatisée.", "schema": { "target_species": { "keyword": "target_species", "enum": { "Sardinha-verdadeira e Bonito-listrado": "Sardinha-verdadeira e Bonito-listrado", "Polvo": "Polvo", "Caranguejo-vermelho": "Caranguejo-vermelho", "Sardinha-verdadeira e Anchova": "Sardinha-verdadeira e Anchova", "peixes diversos": "peixes diversos", "Sardinha-laje": "Sardinha-laje", "Pescada-gó": "Pescada-gó", "Piramutaba e peixes diversos": "Piramutaba e peixes diversos", "Corvina; Pescadas; Castanha e Abrótea": "Corvina; Pescadas; Castanha e Abrótea", "Fundo e Superfície": "Fundo e Superfície", "permissionamento antigo; em processo de conversão": "permissionamento antigo; em processo de conversão", "Tainhas; Anchova e Serras": "Tainhas; Anchova e Serras", "Garoupas; Cherne; Sirigado e outros peixes de fundo": "Garoupas; Cherne; Sirigado e outros peixes de fundo", "Sardinha-verdadeira e Tainha": "Sardinha-verdadeira e Tainha", "Lagostas": "Lagostas", "Espadarte - atuns e afins": "Espadarte - atuns e afins", "Camarão-rosa e peixes diversos": "Camarão-rosa e peixes diversos", "Pescada Amarela": "Pescada Amarela", "Peixe-sapo": "Peixe-sapo", "Piramutaba; Dourada e Gurijuba": "Piramutaba; Dourada e Gurijuba", "Pargo": "Pargo", "Serras": "Serras", "Cavala e Albacorinha": "Cavala e Albacorinha", "Camarão-sete-barbas": "Camarão-sete-barbas", "Bonito-listrado": "Bonito-listrado", "camarões": "camarões", "Abrótea; Galo e Merluza": "Abrótea; Galo e Merluza", "peixes demersais": "peixes demersais", " Camarão-rosa": " Camarão-rosa", "Dourado - atuns e afins": "Dourado - atuns e afins", "Albacoras - atuns e afins": "Albacoras - atuns e afins" } } } }, "public-bra-onyxsat-vessel-identity-fishing": { "name": "VMS Brésil (Navires de pêche)", "description": "Navires de pêche (VMS Brésil)", "schema": { "selfReportedInfo.targetSpecies": { "keyword": "targetSpecies" }, "targetSpecies": { "keyword": "targetSpecies" } } }, "public-brazil-opentuna-presence": { "name": "Brazil Open Tuna VMS", "description": "Presence (Brazil Open tuna)" }, "public-brazil-opentuna-vessel-identity-fishing": { "name": "VMS Brésil, Thon (Navires de pêche)", "description": "Jeu de données pour VMS Brésil (public)", "schema": { "selfReportedInfo.code": { "keyword": "code" } } }, "public-cfc-exploration-areas-individual": { "name": "CFC Exploration Areas", "description": "Cobalt-rich ferromanganese crusts are often found along the tops and edges of seamounts, knolls, and plateaus at depths ranging between 800 meters to 2500+ meters. These crusts can contain cobalt, nickel, manganese, and rare earth elements. Proposed methods for mining cobalt-rich ferromanganese crusts include grinding and entirely removing the crust from the host rock – which are inhabited by marine biodiversity – then delivering the resulting slurry to the surface. For cobalt-rich ferromanganese crusts, the exploration area allocated to each contractor is 3,000 square kilometres and consists of 150 blocks. Each block is no greater than 20 square kilometres.", "schema": { "act_date": { "keyword": "act_date", "enum": { "1447023600000": "1447023600000", "1697752800000": "1697752800000" } }, "area_key": { "keyword": "area_key" }, "contract_id": { "keyword": "contract_id", "enum": { "KOREACRFC1": "KOREACRFC1", "COMRACRFC1": "COMRACRFC1", "BrazilCRFC1": "BrazilCRFC1", "JOGMECCRFC1": "JOGMECCRFC1", "RUSMNRCRFC1": "RUSMNRCRFC1" } } } }, "public-cfc-reserved-areas-individual": { "name": "CFC Reserved Areas", "description": "Cobalt-rich ferromanganese crusts are often found along the tops and edges of seamounts, knolls, and plateaus at depths ranging between 800 meters to 2500+ meters. These crusts can contain cobalt, nickel, manganese, and rare earth elements. Proposed methods for mining cobalt-rich ferromanganese crusts include grinding and entirely removing the crust from the host rock – which are inhabited by marine biodiversity – then delivering the resulting slurry to the surface. Reserved Areas under the International Seabed Authority are a critical mechanism to ensure developing countries have access to deep-sea mineral resources in the future. These areas are typically contributed by developed States when they apply for exploration rights.", "schema": { "act_date": { "keyword": "act_date", "enum": { "1425942000000": "1425942000000" } }, "area_key": { "keyword": "area_key" }, "contract_id": { "keyword": "contract_id", "enum": { "CRFCReserved": "CRFCReserved" } } } }, "public-chile-fishing-effort": { "name": "Chile VMS", "description": "Données du système de surveillance des navires (VMS) fournies par l'organisme de réglementation des pêches et de l'aquaculture du gouvernement chilien (SERNAPESCA). Il est possible de filtrer les données VMS du Chili pour les navires de pêche à petite échelle (< 18 mètres) et les navires de pêche industrielle (> 18 mètres). Notez que certains navires mesurent moins de 18 mètres mais sont considérés comme industriels car ils ont été enregistrés dans la capture de quotas industriels. SERNAPESCA utilise également notre carte pour visualiser et suivre les positions des navires de sa flotte, y compris les navires impliqués dans l'aquaculture. Les données sont collectées à l'aide du VMS du Chili via des satellites et des récepteurs terrestres et contiennent les identités des navires, le type d'engin, la localisation, la vitesse, le cap et plus encore. Global Fishing Watch analyse ces données à l'aide des mêmes algorithmes que nous avons développés pour les données du système d'identification automatique (AIS) afin d'identifier l'activité et les comportements de pêche. L'algorithme classe chaque point de données diffusé par les navires comme étant apparemment en train de pêcher ou non et affiche le premier sur la carte de Global Fishing Watch. Le VMS diffuse les données de manière assez différente de l'AIS et peut donner des mesures différentes de l'exhaustivité, de la précision et de la qualité. Au fil du temps, nos algorithmes s'amélioreront dans tous nos formats de données de diffusion. L'algorithme de présence de pêche de Global Fishing Watch pour VMS, comme pour AIS, est un effort optimal pour identifier algorithmiquement « l'activité de pêche apparente ». Il est possible que certaines activités de pêche ne soient pas identifiées ou que la carte thermique montre une activité de pêche apparente alors qu'il n'y a pas réellement de pêche. Pour ces raisons, Global Fishing Watch qualifie les termes « activité de pêche », « pêche » et « effort de pêche » d'« apparents » plutôt que certains. Toutes les informations de Global Fishing Watch sur « l'activité de pêche apparente » doivent être considérées comme une estimation et vous devez vous y fier uniquement à vos propres risques. Les algorithmes de présence de pêche de Global Fishing Watch sont développés et testés à l'aide de données réelles sur les événements de pêche collectées par des observateurs, combinées à une analyse d'experts en données de mouvement des navires AIS, ce qui donne lieu à la classification manuelle de milliers d'événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager des données de classification des activités de pêche et une classification automatisée.", "schema": { "fleet": { "keyword": "flotte", "enum": { "chile_vms_small_fisheries": "chile_vms_petites_pêcheries", "chile_vms_industry": "industrie du chile_vms_fr" } } } }, "public-chile-presence": { "name": "VMS Chili", "description": "Données du système de surveillance des navires (VMS) fournies par l'organisme de réglementation des pêches et de l'aquaculture du gouvernement chilien (SERNAPESCA). Il est possible de filtrer les données VMS du Chili pour les navires de pêche à petite échelle (< 18 mètres) et les navires de pêche industrielle (> 18 mètres). Notez que certains navires mesurent moins de 18 mètres mais sont considérés comme industriels car ils ont été enregistrés dans la capture de quotas industriels. SERNAPESCA utilise également notre carte pour visualiser et suivre les positions des navires de sa flotte, y compris les navires impliqués dans l'aquaculture. Les données sont collectées à l'aide du VMS du Chili via des satellites et des récepteurs terrestres et contiennent les identités des navires, le type d'engin, la localisation, la vitesse, le cap et plus encore. Global Fishing Watch analyse ces données à l'aide des mêmes algorithmes que nous avons développés pour les données du système d'identification automatique (AIS) afin d'identifier l'activité et les comportements de pêche. L'algorithme classe chaque point de données diffusé par les navires comme étant apparemment en train de pêcher ou non et affiche le premier sur la carte de Global Fishing Watch. Le VMS diffuse les données de manière assez différente de l'AIS et peut donner des mesures différentes de l'exhaustivité, de la précision et de la qualité. Au fil du temps, nos algorithmes s'amélioreront dans tous nos formats de données de diffusion. L'algorithme de présence de pêche de Global Fishing Watch pour VMS, comme pour AIS, est un effort optimal pour identifier algorithmiquement « l'activité de pêche apparente ». Il est possible que certaines activités de pêche ne soient pas identifiées ou que la carte thermique montre une activité de pêche apparente alors qu'il n'y a pas réellement de pêche. Pour ces raisons, Global Fishing Watch qualifie les termes « activité de pêche », « pêche » et « effort de pêche » d'« apparents » plutôt que certains. Toutes les informations de Global Fishing Watch sur « l'activité de pêche apparente » doivent être considérées comme une estimation et vous devez vous y fier uniquement à vos propres risques. Les algorithmes de présence de pêche de Global Fishing Watch sont développés et testés à l'aide de données réelles sur les événements de pêche collectées par des observateurs, combinées à une analyse d'experts en données de mouvement des navires AIS, ce qui donne lieu à la classification manuelle de milliers d'événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager des données de classification des activités de pêche et une classification automatisée.", "schema": { "fleet": { "keyword": "flotte", "enum": { "chile_vms_small_fisheries": "chile_vms_petites_pêcheries", "chile_vms_industry": "industrie du chile_vms_fr", "chile_vms_aquaculture": "chile_vms_aquaculture", "chile_vms_transport": "chile_vms_transport" } } } }, "public-chile-vessel-identity-fishing": { "name": "Chile VMS (Fishing Vessels)", "description": "Jeu de données pour VMS Chili (public)" }, "public-chile-vessel-identity-non-fishing": { "name": "VMS Chili (navires non pêche)", "description": "Jeu de données pour VMS Chili (public)" }, "public-clarion-clipperton-zone-isa-claim-areas": { "name": "Clarion-Clipperton Zone ISA License Areas", "description": "This area represents the cumulative and contiguous area of the Clarion-Clipperton Zone, a region in the Eastern Pacific that is being targeted for seabed mining and managed by the International Seabed Authority. This region includes claim areas slated for exploration, areas reserved for developing states, and areas protected for environmental interest. The primary resource targeted in this region is polymetallic nodules." }, "public-cold-water-corals": { "name": "Cold Water Corals", "description": "Buffered at ~1km" }, "public-coral-reefs": { "name": "Récifs coralliens", "description": "An EBSA is an area of the ocean recognized for its unique ecological and/or biological features, such as essential habitats, food sources or breeding grounds for specific species. The description and mapping of EBSAs is done through a process under the Convention on Biological Diversity (CBD).
\nAn EBSA is an area that meets at least one of the seven internationally agreed scientific criteria, known as the “EBSA criteria”, which were adopted by the Conference of the Parties to the Convention on Biological Diversity (CBD COP) in 2008. EBSAs included in the CBD EBSA repository undergo formal review and adoption by the CBD COP.
\nThese areas can vary greatly in size and location, ranging from coastal waters to the high seas and from the ocean surface to the seabed. EBSAs encompass a wide range of species, habitats and oceanographic features, including dynamic and ephemeral phenomena, as well as areas that are important seasonally or throughout the year. EBSAs have included features such as seamounts, hydrothermal vents, coral reefs, migratory corridors, seasonal fish spawning areas and coastal upwellings, among many other types of ecosystems.
For more details on the EBSA criteria, please see:
\ncbd.int/doc/meetings/mar/ebsaws-2014-01/other/ebsaws-2014-01-azores-brochure-en.pdf\nL'infrastructure fixe offshore est un ensemble de données mondial qui utilise l'IA et l'apprentissage automatique pour détecter et classer les structures dans les océans du monde.
Des étiquettes de classification (pétrole, éolien et inconnu) sont fournies, ainsi que des niveaux de confiance (élevé, moyen ou faible) reflétant notre certitude dans l'étiquette attribuée. Les détections peuvent être filtrées et colorées sur la carte en utilisant à la fois l'étiquette et le niveau de confiance.< em >Les données sont mises à jour sur une base mensuelle et de nouvelles détections classées sont ajoutées au début de chaque mois. La visualisation des changements à l'aide de la barre temporelle est simple et permet à chacun de reconnaître l'industrialisation rapide des océans du monde. Par exemple, vous pouvez facilement observer l'expansion des parcs éoliens dans les mers de Chine du Nord et de l'Est, ou les changements dans les infrastructures pétrolières dans le golfe du Mexique ou le golfe Persique.
En superposant les couches cartographiques existantes, vous pouvez explorer la manière dont les navires interagissent avec les structures pétrolières et éoliennes, visualiser la densité des détections de navires par radar à synthèse d'ouverture (SAR) et par radiomètre d'imagerie infrarouge visible (VIIRS) autour des infrastructures, ou déterminer quelles zones marines protégées (AMP) contiennent des éoliennes, du pétrole ou d'autres types d'infrastructures. Ce ne sont là que quelques exemples des types de questions que nous pouvons désormais poser. Les infrastructures fixes offshore constituent un ensemble de données unique en son genre qui met non seulement en lumière l'industrialisation extensive de nos océans, mais permet également aux utilisateurs de tous les secteurs d'utiliser ces informations dans la recherche, la surveillance et la gestion.
Nous utilisons l'imagerie SAR de la mission Copernicus Sentinel-1 de l'Agence spatiale européenne (ESA) [1]. Les images proviennent de deux satellites (S1A et S1B jusqu'en décembre 2021, date à laquelle S1B a cessé de fonctionner, et S1A uniquement à partir de 2022) qui orbitent à 180 degrés de décalage l'un par rapport à l'autre sur une orbite polaire héliosynchrone. Chaque satellite a un cycle de répétition de 12 jours, de sorte qu'ensemble, ils fournissent une cartographie globale des eaux côtières du monde entier environ tous les six jours pendant la période où les deux satellites étaient en fonctionnement. Le nombre d'images par emplacement varie toutefois considérablement en fonction des priorités de la mission, de la latitude et du degré de chevauchement entre les passages de satellites adjacents. La couverture spatiale varie également au fil du temps [2]. Nos données sont constituées d'images à double polarisation (VH et VV) du mode de balayage interférométrique large (IW), avec une résolution d'environ 20 m.
[1] https://sedas.satapps.org/wp-content/uploads/2015/07/Sentinel-1_User_Handbook.pdf
[2] https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1/observation-scenario
La détection d'infrastructures avec SAR est basée sur l'algorithme largement utilisé CFAR (Constant False Alarm Rate), une méthode de détection d'anomalies conçue pour détecter les navires dans les images radar à synthèse d'ouverture, qui a été modifiée pour supprimer les objets non stationnaires. Cet algorithme est conçu pour rechercher des valeurs de pixels qui sont inhabituellement lumineuses (les cibles) par rapport à celles de la zone environnante (l'encombrement marin). Cette méthode définit un seuil basé sur les valeurs de pixels de l'arrière-plan local (dans une fenêtre), en balayant l'image entière pixel par pixel. Les valeurs de pixels supérieures au seuil constituent une anomalie et sont susceptibles d'être des échantillons d'une cible.
Pour classer chaque infrastructure offshore détectée, nous avons utilisé l'apprentissage profond et conçu un ConvNet basé sur l' architecture ConvNeXt . Un nouvel aspect de notre approche de classification par apprentissage profond est la combinaison de l'imagerie SAR de Sentinel-1 avec l'imagerie optique de Sentinel-2. À partir de composites de six mois d'images SAR à double bande (VH et VV) et optiques à quatre bandes (RGB et NIR), nous avons extrait de petites tuiles pour chaque infrastructure fixe détectée, avec les objets respectifs au centre de la tuile. Une sortie de modèle unique inclut les probabilités pour les classes spécifiées : vent, pétrole, inconnu, lac Maracaibo et bruit.
GFW a post-traité les détections SAR classées pour réduire le bruit (faux positifs), supprimer les navires, exclure les zones avec de la glace de mer à haute latitude et intégrer les commentaires des experts. Nous avons utilisé une approche de regroupement pour identifier les détections dans le temps (dans un rayon de 50 m) qui étaient probablement la même structure mais dont les coordonnées différaient légèrement, et leur avons attribué la plus grande étiquette moyenne prédite du groupe. Nous avons également comblé les lacunes pour les structures fixes qui manquaient dans un pas de temps mais détectées dans les pas de temps précédents et suivants, et nous avons abandonné les détections apparaissant dans un seul pas de temps. Enfin, l'ensemble de données a fait l'objet d'un examen et d'une édition manuels approfondis par des chercheurs et des experts du secteur afin d'affiner le produit final et de fournir l'ensemble de données le plus précis possible. < /p>
Chaque détection a un identifiant individuel unique (< em > detection_id ). Une image composite de six mois est utilisée dans la classification, donc la < em > detection_date représente le milieu de la période de six mois . Cela permet de supprimer les objets non stationnaires (c'est-à-dire les vaisseaux ) et d'éviter toute confusion dans le modèle si une structure est en cours de construction ou s'il n'y a pas d'imagerie adéquate disponible. < em > structure_id vous permet de suivre une structure au fil du temps. Il existe donc plusieurs < em > detection_id (un pour chaque mois où la structure est détectée) pour chaque < em > structure_id . Les étiquettes < em >wind et < em >oil représentent respectivement toute structure liée au vent ou au pétrole. < em >Unknown représente une structure qui n'est pas liée au pétrole ou au vent, comme les ponts ou les bouées de navigation.
Les niveaux de confiance des étiquettes sont « Élevé ». « Moyen » et « Faible » sont attribués à chaque structure et dépendent de l'endroit où les détections se situent par rapport aux limites des polygones éoliens et pétroliers développés manuellement et du fait que l'étiquette a changé par rapport au mois précédent. Le champ < em > label_confidence peut être utilisé pour filtrer l'analyse.
Deux référentiels sont utilisés dans le processus d'automatisation, tous deux privés et ne doivent pas être partagés publiquement.
Détection et classification : https://github.com/GlobalFishingWatch/sentinel-1-ee/tree/master
Clustering et reclassification : https://github.com/GlobalFishingWatch/infrastructure-post-processing
Tout le code développé pour l'article, Paolo, FS, Kroodsma , D., Raynor, J. et al. La cartographie par satellite révèle une activité industrielle extensive en mer. Nature 625, 85–91 (2024). https://doi.org/10.1038/s41586-023-06825-8, y compris la détection SAR, les modèles d'apprentissage profond et les analyses, est open source et disponible gratuitement sur https://github.com/GlobalFishingWatch/paper-industrial-activity.
Données Copernicus Sentinel 2017-actuel
Lujala , Päivi ; Jan Ketil Rød & Nadia Thieme, 2007. « Lutte pour le pétrole : introduction d'un nouvel ensemble de données », Conflict Management and Peace Science 24(3), 239-256
Sabbatino, M., Romeo, L., Baker, V., Bauer, J., Barkhurst, A., Bean, A., DiGiulio, J., Jones, K., Jones, TJ, Justman, D., Miller III, R., Rose, K., et Tong., A., Global Oil & Gas Infrastructure Features Database Geocube Collection, 2019-03-25, https://edx.netl.doe.gov/dataset/global-oil-gas-infrastructure-features-database-geocube-collection, DOI : 10.18141/1502839
Utilisation non commerciale uniquement. Le Site et les Services sont fournis pour une utilisation non commerciale uniquement, conformément à la licence CC BY-NC 4.0. Si vous souhaitez utiliser le Site et/ou les Services à des fins commerciales, veuillez nous contacter.
Les méthodes de développement des infrastructures doivent faire référence au document :
Paolo, FS, Kroodsma , D., Raynor, J. et al. La cartographie par satellite révèle une activité industrielle extensive en mer. Nature 625, 85–91 (2024). Anglais : https://doi.org/10.1038/s41586-023-06825-8
Tout le code développé pour l'article, y compris la détection SAR, les modèles d'apprentissage profond et les analyses est open source et disponible gratuitement sur https://github.com/GlobalFishingWatch/paper-industrial-activity.Toutes les données générées et utilisées par ces scripts peuvent référencer les référentiels de données suivants :
Analyse et chiffres : https://doi.org/10.6084/m9.figshare.24309475
Formation et évaluation : https://doi.org/10.6084/m9.figshare.24309469
", "schema": { "label": { "keyword": "label", "enum": { "wind": "wind", "oil": "oil", "unknown": "unknown" } }, "label_confidence": { "keyword": "label_confidence", "enum": { "high": "élevée", "medium": "moyenne", "low": "faible" } }, "structure_end_date": { "keyword": "structure_end_date" }, "structure_id": { "keyword": "structure_id" }, "structure_start_date": { "keyword": "structure_start_date" } } }, "public-gfcm-fao": { "name": "GFCM FAO", "description": "A fisheries restricted area (FRA) is a geographically defined area in which some specific fishing activities are temporarily or permanently banned or restricted in order to improve the exploitation patterns and conservation of specific stocks as well as of habitats and deep-sea ecosystems. In the Mediterranean and the Black Sea, 1,760,000 square kilometers of sea habitats are protected by ten FRAs established by the GFCM. This includes one large deep-water FRA (1,730,000 square kilometers) in which the use of towed dredges and trawl nets in all waters deeper than 1000 metres is banned to protect deep-sea benthic habitats. The layer was taken from the GFCM website but manually adjusted to reflect the original coordinates of the FRAs as stipulated in the document REC. GFCM/29/2005/1." }, "public-global-ais-ports-footprint": { "name": "Anchorages convex hulls by portId", "description": "Anchorages footprint using the convex hull grouped by portId" }, "public-global-ais-ports": { "name": "Ports v1 for AIS v4", "description": "Named ports v1" }, "public-global-all-tracks": { "name": "Trajectoires", "description": "Le jeu de données contient les tracés de tous les navires (AIS) - Version 3.0", "schema": { "elevation": { "keyword": "elevation", "enum": { "0": "0", "-2000": "-2000" } }, "speed": { "keyword": "speed", "enum": { "0": "0", "20": "20" } } } }, "public-global-bathymetry": { "name": "Bathymétrie", "description": "Global Fishing Watch classifies an event as an encounter when two vessels are detected:
Users can filter encounter events by vessel characteristics and context, including:
Currently displayed encounter types include:
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.
You can read more about transshipment behaviour from our report or scientific publication.
", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "encounter_type": { "keyword": "encounter_type", "enum": { "CARRIER-FISHING": "CARRIER-FISHING", "SUPPORT-FISHING": "SUPPORT-FISHING", "FISHING-CARRIER": "FISHING-CARRIER", "FISHING-BUNKER": "FISHING-BUNKER", "FISHING-FISHING": "FISHING-FISHING", "CARRIER-BUNKER": "CARRIER-BUNKER", "FISHING-SUPPORT": "FISHING-SUPPORT" } } } }, "public-global-fishing-effort-vi-653": { "name": "AIS fishing bq", "description": "Global Fishing Watch uses data about a vessel’s identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as known or possible commercial fishing vessels, and applies a fishing presence algorithm to determine “apparent fishing activity” based on changes in vessel speed and direction. The algorithm classifies each AIS broadcast data point for these vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. AIS data as broadcast may vary in completeness, accuracy and quality. Also, data collection by satellite or terrestrial receivers may introduce errors through missing or inaccurate data. Global Fishing Watch’s fishing presence algorithm is a best effort mathematically to identify “apparent fishing activity.” As a result, it is possible that some fishing activity is not identified as such by Global Fishing Watch; conversely, Global Fishing Watch may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies designations of vessel fishing activity, including synonyms of the term “fishing activity,” such as “fishing” or “fishing effort,” as “apparent,” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch is taking steps to make sure fishing activity designations are as accurate as possible. Global Fishing Watch fishing presence algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification techniques." }, "public-global-fishing-effort": { "name": "AIS", "description": "Global Fishing Watch uses data about a vessel’s identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as known or possible commercial fishing vessels, and applies a fishing presence algorithm to determine “apparent fishing activity” based on changes in vessel speed and direction. The algorithm classifies each AIS broadcast data point for these vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. AIS data as broadcast may vary in completeness, accuracy and quality. Also, data collection by satellite or terrestrial receivers may introduce errors through missing or inaccurate data. Global Fishing Watch’s fishing presence algorithm is a best effort mathematically to identify “apparent fishing activity.” As a result, it is possible that some fishing activity is not identified as such by Global Fishing Watch; conversely, Global Fishing Watch may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies designations of vessel fishing activity, including synonyms of the term “fishing activity,” such as “fishing” or “fishing effort,” as “apparent,” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch is taking steps to make sure fishing activity designations are as accurate as possible. Global Fishing Watch fishing presence algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification techniques.", "schema": { "distance_from_port_km": { "keyword": "Tampon de port", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "public-global-fishing-events": { "name": "Fishing Events (AIS)", "description": "The dataset contains fishing events for AIS", "schema": { "type": { "keyword": "type", "enum": { "CARGO": "CARGO", "DISCREPANCY": "DISCREPANCY", "CARRIER": "CARRIER", "FISHING": "FISHING", "GEAR": "GEAR", "OTHER": "OTHER", "PASSENGER": "PASSENGER", "SEISMIC_VESSEL": "SEISMIC_VESSEL", "SUPPORT": "SUPPORT" } } } }, "public-global-gaps-events": { "name": "Disabling Events (AIS)", "description": "The dataset contains gaps events for AIS" }, "public-global-loitering-events": { "name": "Loitering Events (AIS)", "description": "Global Fishing Watch classifies an event as a loitering event when:
Learn more about considerations of using AIS data by looking at the AIS limitations section in the Apparent fishing events (AIS) data documentation..
", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "type": { "keyword": "type", "enum": { "CARGO": "CARGO", "DISCREPANCY": "DISCREPANCY", "CARRIER": "CARRIER", "FISHING": "FISHING", "GEAR": "GEAR", "OTHER": "OTHER", "PASSENGER": "PASSENGER", "SEISMIC_VESSEL": "SEISMIC_VESSEL", "SUPPORT": "SUPPORT" } } } }, "public-global-nitrate": { "name": "Concentration d'azote (NO3)", "description": "Global Fishing Watch detects vessel movements in and out of ports and classifies them into four distinct port event types:
These events are grouped to form port visit events, which represent a vessel’s presence at port based on AIS activity patterns.
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:
A port visit is shown on the map when AIS data shows a vessel:
Port stops are used to distinguish actual port visits from coastal transits.
Learn more about anchorages, ports and voyages.
Learn more about considerations of using AIS data by looking at the AIS limitations section in the Apparent fishing events (AIS) data documentation..", "schema": { "duration": { "keyword": "duration", "enum": { "2": "2", "48": "48" } }, "type": { "keyword": "type", "enum": { "CARGO": "CARGO", "DISCREPANCY": "DISCREPANCY", "CARRIER": "CARRIER", "FISHING": "FISHING", "GEAR": "GEAR", "OTHER": "OTHER", "PASSENGER": "PASSENGER", "SEISMIC_VESSEL": "SEISMIC_VESSEL", "SUPPORT": "SUPPORT" } } } }, "public-global-ports-footprint": { "name": "Anchorages convex hulls by portId", "description": "Anchorages footprint using the convex hull grouped by portId", "schema": { "area": { "keyword": "area" }, "label": { "keyword": "label" }, "perimeter": { "keyword": "perimeter" } } }, "public-global-presence-vi-653": { "name": "AIS", "description": "Global Fishing Watch uses data about a vessel’s identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as carriers. The activity layer displays a heatmap of vessel presence. The presence is determined by taking one position per day per vessel from the positions transmitted by the vessel's AIS." }, "public-global-presence": { "name": "AIS", "description": "Global Fishing Watch uses data about a vessel’s identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as carriers. The activity layer displays a heatmap of vessel presence. The presence is determined by taking one position per day per vessel from the positions transmitted by the vessel's AIS.", "schema": { "speed": { "keyword": "vitesse", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "carrier": "carrier", "seismic_vessel": "seismic_vessel", "passenger": "passenger", "other": "other", "support": "support", "bunker": "bunker", "gear": "gear", "cargo": "cargo", "fishing": "fishing", "discrepancy": "discrepancy" } } } }, "public-global-salinity": { "name": "Salinité", "description": "
Le radar à synthèse d'ouverture (SAR) par satellite est un système d'imagerie radar embarqué dans l'espace qui peut détecter des navires et des structures en mer dans toutes les conditions météorologiques. Les impulsions micro-ondes sont transmises par une antenne satellite vers la surface de la Terre. L'énergie micro-onde diffusée vers le navire est ensuite mesurée et intégrée pour former une image de « rétrodiffusion ». L'image SAR contient une grande quantité d'informations sur les différents objets à la surface de l'eau, comme leur taille, leur orientation et leur texture. Les systèmes d'imagerie SAR surmontent la plupart des conditions météorologiques et des niveaux d'éclairage, y compris les nuages ou la pluie en raison de la propriété de pénétration des nuages des micro-ondes, et la lumière du jour ou l'obscurité en raison du radar étant un capteur « actif » (il envoie et enregistre sa propre énergie). Le SAR offre un avantage sur certains autres capteurs satellites « passifs », tels que l'imagerie électro-optique, composée d'une caméra satellite enregistrant le rayonnement solaire/infrarouge réfléchi/émis par les objets au sol. Cette dernière méthode peut être perturbée par la couverture nuageuse, la brume, les événements météorologiques et l'obscurité saisonnière aux hautes latitudes.
\nNous utilisons des images SAR de la mission Copernicus Sentinel-1 de l'Agence spatiale européenne (ASE) [1]. Les images proviennent de deux satellites (S1A et S1B jusqu'en décembre 2021, date à laquelle S1B a cessé de fonctionner, et S1A seulement à partir de 2022) qui orbitent à 180 degrés de déphasage l'un par rapport à l'autre sur une orbite polaire héliosynchrone. Chaque satellite a un cycle de répétition de 12 jours, de sorte qu'ensemble, ils fournissent une cartographie globale des eaux côtières du monde entier environ tous les six jours pendant la période où les deux satellites étaient en fonctionnement. Le nombre d'images par position varie cependant considérablement en fonction des priorités de la mission, de la latitude et du degré de chevauchement entre les passages de satellites adjacents. La couverture spatiale varie également au fil du temps [2]. Nos données se composent d'images à double polarisation (VH et VV) du mode de balayage interférométrique large (IW), avec une résolution d'environ 20 m.
\n[1]\n\nhttps://sedas.satapps.org/wp-content/uploads/2015/07/Sentinel-1_Manuel_d'utilisation.pdf\n\n
\n[ 2]< a target=\"_blank\" href=\"https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1/scenario-d-observation\">\n\nhttps://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1/scenario-d-observation\n\n
\nLes empreintes de détection sont des zones au sein de chaque balayage satellite (ou scène) que notre système utilise pour effectuer des détections. Ces filtres permettent de conserver les détections pertinentes et d'exclure les données qui peuvent être inexactes. Les empreintes de détection sont plus petites que la scène totale car elles excluent toutes les zones terrestres et les îles, et excluent une zone tampon de 500 mètres des limites de la scène et une zone tampon de 1 kilomètre des côtes.
\nGFW a post-traité les détections SAR pour réduire le bruit (faux positifs), supprimer les infrastructures offshore de cette couche axée sur les navires et exclure les zones avec de la glace de mer à haute latitude.
\nLa détection des navires par SAR est basée sur un algorithme de seuil connu sous le nom de taux de fausse alarme constant, (CFAR pour Constant False Alarm Rate), utilisé pour la détection d'anomalies dans l'imagerie radar. Cet algorithme est conçu pour rechercher des valeurs de pixels inhabituellement lumineux (les cibles) par rapport à celles de la zone environnante (le bruit marin). Cette méthode définit un seuil basé sur les valeurs de pixels de l'arrière-plan local (dans une fenêtre), en balayant l'image entière pixel par pixel. Les valeurs de pixels supérieures au seuil constituent une anomalie et sont susceptibles d'être des échantillons d'une cible, et sont donc incluses dans la détection.
\nPour estimer la longueur de chaque objet détecté ainsi qu'identifier quand notre algorithme CFAR a effectué de fausses détections, nous avons conçu un réseau neuronal convolutif profoond (ConvNet pour Convolutional Neural Network) basé sur l'architecture moderne ResNet (réseau résiduel). Ce ConvNet à entrée unique/sortie multiple prend en entrée des tuiles d'images SAR à double bande de 80 par 80 pixels et génère en sortie la probabilité de présence d'objet (connue sous le nom de « tâche de classification binaire ») et la longueur estimée de l'objet (connue sous le nom de « tâche de régression » ).
\nPour déterminer si un navire détecté était un navire de pêche ou non, nous utilisons un modèle d'apprentissage automatique. Pour cette tâche de classification, nous avons utilisé une architecture ConvNeXt modifiée pour traiter les deux entrées suivantes : la longueur estimée du navire à partir du SAR (une quantité scalaire) et une pile de rasters environnementaux centrée sur l'emplacement du navire (une image multicanal). Ce modèle multi-entrées-données mixtes/sortie unique fait passer la pile raster (11 canaux) à travers une série de calques convolutionnels et combine les cartes de caractéristiques résultantes avec la valeur de la longueur du navire pour effectuer une classification binaire : pêche ou non pêche.& nbsp ;
\nLes calques environnementaaux utilisées pour différencier la pêche et la non-pêche comprennent :
\n< ol >\nLes données AIS peuvent révéler l’identité des navires, de leurs propriétaires et de leurs sociétés, ainsi que l’activité de pêche. Cependant, tous les navires ne sont pas tenus d’utiliser des dispositifs AIS, car les réglementations varient selon le pays, la taille du navire et l’activité. Les navires engagés dans des activités illicites peuvent également désactiver leurs transpondeurs AIS ou manipuler les emplacements qu’ils diffusent. De plus, de grands « angles morts » le long des eaux côtières proviennent des pays qui limitent l’accès aux données AIS captées par des récepteurs terrestres au lieu de satellites ou d’une mauvaise réception due à une forte densité de navires et à des dispositifs AIS de mauvaise qualité. Les détections SAR fournissent donc les informations manquantes sur le trafic maritime dans l’ océan.
\nLa mise en correspondance des détections SAR avec les coordonnées GPS des navires (à partir du système d'identification automatique [AIS]) est difficile car l'horodatage des images SAR et des enregistrements AIS ne coïncide pas, et un seul message AIS peut potentiellement correspondre à plusieurs navires apparaissant sur l'image, et vice versa. Pour déterminer la probabilité qu'un navire diffusant AIS corresponde à une détection SAR spécifique, nous avons suivi une approche de mise en correspondance basée sur des rasters de probabilité de l'endroit où un navire est susceptible de se trouver quelques minutes avant et après l'enregistrement d'une position AIS. Ces rasters ont été développés à partir d'une année de données AIS mondiales provenant du pipeline Global Fishing Watch qui utilise les sources de données satellite Spire Global et Orbcomm , comprenant environ 10 milliards de positions de navires, et calculés pour six classes de navires différentes, en tenant compte de six vitesses différentes et de 36 intervalles de temps. Nous obtenons donc la position probable d'un navire qui pourrait correspondre à une détection SAR en fonction de la classe de navire, de la vitesse et de l' intervalle de temps.
\nLes données du système d’identification automatique (AIS) peuvent révéler l’identité des navires, de leurs propriétaires et de leurs sociétés, ainsi que l’activité de pêche. Cependant, tous les navires ne sont pas tenus d’utiliser des dispositifs AIS, car les réglementations varient selon le pays, la taille du navire et l’activité. Les navires engagés dans des activités illicites peuvent également désactiver leurs transpondeurs AIS ou manipuler les emplacements qu’ils diffusent. De plus, de grands « angles morts » le long des eaux côtières proviennent des pays qui limitent l’accès aux données AIS capturées par des récepteurs terrestres au lieu de satellites ou d’une mauvaise réception due à une forte densité de navires et à des dispositifs AIS de mauvaise qualité. Les détections SAR fournissent donc les informations manquantes sur le trafic maritime dans l’ océan.
\nTout le code développé dans cette étude pour la détection SAR, les modèles d'apprentissage profond et les analyses est open source et disponible gratuitement sur\n\nhttps://github.com/GlobalFishingWatch/activité-industrielle-du-papier\n.\n
\nToutes les données sur les navires sont disponibles gratuitement via le portail de données Global Fishing Watch à l'adresse\n\nhttps://globalfishingwatch.org\n. Toutes les données permettant de reproduire notre article scientifique justificatif peuvent être téléchargées à partir de\n\nhttps://doi.org/10.6084/m9.figshare.24309475\n\n(analyses statistiques et chiffres) et\n\nhttps://doi.org/10.6084/m9.figshare.24309469\n\n(formation et évaluation du modèle).\n
\nUtilisation non commerciale uniquement. Le site et les services sont fournis pour une utilisation non commerciale uniquement, conformément à la licence CC BY-NC 4.0. Si vous souhaitez utiliser le site et/ou les services à des fins commerciales, veuillez nous contacter.", "schema": { "matched": { "keyword": "correspondance", "enum": { "true": "1", "false": "faux" } }, "neural_vessel_type": { "keyword": "neural_vessel_type", "enum": { "Likely non-fishing": "Probablement non pêche", "Likely Fishing": "Probablement pêche", "Unknown": "Inconnu" } }, "shiptype": { "keyword": "type de navire", "enum": { "carrier": "navire de transport", "seismic_vessel": "seismic_vessel", "passenger": "navire de transport de passagers", "other": "autre", "support": "navire de soutien", "bunker": "navire ravitailleur", "gear": "engin", "cargo": "navire cargo", "fishing": "pêche", "discrepancy": "divergence" } } } }, "public-global-sentinel2-footprints": { "name": "Empreintes de détection", "description": "Empreintes de détection" }, "public-global-sentinel2-presence": { "name": "Détections par imagerie (optique)", "description": "
Ce calque montre les navires détectés à l’aide d’images satellites optiques collectées par les satellites Sentinel-2 de l’Agence spatiale européenne. L'imagerie optique est similaire à la photographie aérienne de haute qualité depuis l'espace, utilisant la lumière solaire réfléchie dans les longueurs d'onde visibles et proches infrarouges. Ce type d’imagerie fournit des détails haute résolution qui nous permettent de repérer les petits navires, d’identifier les schémas de sillage et de mieux comprendre l’activité à proximité de la côte.
\nGlobal Fishing Watch utilise un modèle d'apprentissage machine qui traite chaque image pour identifier les navires et estimer leur longueur, leur cap et leur vitesse en fonction des caractéristiques du sillage. Les détections sont ensuite filtrées à l’aide d’un modèle de classification secondaire pour supprimer les objets qui ne sont pas des navires, tels que les nuages, les rochers ou les icebergs. Chaque détection est liée à une image recadrée (une vignette) afin que les utilisateurs puissent inspecter visuellement ce que le modèle a identifié.
\nÉtant donné que les satellites optiques dépendent de la lumière du soleil et d’un ciel dégagé, les détections ne sont possibles que pendant la journée et lorsque la zone n’est pas obscurcie par des nuages ou de la brume. Malgré ces limitations, les détections par imagerie optique sont particulièrement utiles pour identifier les petits navires non suivis qui peuvent ne pas apparaître dans d’autres systèmes de suivi.
\nCette couche est basée sur des images des satellites Sentinel-2 exploités par l'Agence spatiale européenne (ASE). Ces satellites capturent des images de résolution moyenne (10 m par pixel) de l’océan en utilisant la lumière visible et proche infrarouge (parmi plusieurs autres bandes). Ensemble, les satellites acquièrent des images de la plupart des eaux côtières et des zones dédiées en haute mer environ tous les cinq jours, et les images sont mises gratuitement à disposition par l’ASE.
\nNous utilisons des images Sentinel-2 prétraitées qui ont été corrigées pour les distorsions géométriques et alignées sur la surface de la Terre. Ces images sont divisées en tuiles gérables, et nous avons sélectionné les tuiles qui couvrent uniquement les zones océaniques (les tuiles d'images terrestres sont exclues). Nous utilisons quatre bandes d’images : rouge, vert, bleu (RVB) et proche infrarouge (PIR), toutes à une résolution de 10 mètres. Ces bandes nous donnent les détails et le contraste nécessaires pour détecter et classifier les navires.
\nNotre modèle d’apprentissage machine analyse chaque tuile d’image pour détecter les navires. Il est entraîné pour rechercher des caractéristiques telles que la forme, la luminosité et le sillage d'un navire. Lorsqu'il identifie un candidat probable, le modèle prédit un score pour la présence du navire ainsi que des estimations de la position, de la taille, du cap et de la vitesse du navire.
\nLe modèle de détection a été entraîné avec plus de 11 000 exemples de navires examinés manuellement dans des milliers de scènes Sentinel-2. Ce processus d’entraînement comprenait de nombreux petits navires et scènes du monde entier, aidant le modèle à bien fonctionner pour différents environnements et types de navires.
\nChaque détection comprend une petite « vignette » visuelle montrant le navire détecté au centre. Ces vignettes sont disponibles en deux formats : une version couleur des bandes RVB et une version en niveaux de gris de la bande proche infrarouge. Chaque vignette couvre une superficie de 1 km². Ces vignettes sont utiles pour confirmer visuellement une détection ou comprendre son contexte. Les très petits navires (moins de 15 mètres) peuvent tout de même être difficiles à voir clairement.
\nTout ce qui ressemble à un navire sur les images satellites n’en est pas forcément un. Pour aider à éliminer les fausses détections (comme les bouées, les plateformes offshore, la glace de mer ou les nuages), nous soumettons chaque détection à un modèle de classification secondaire. Ce classificateur est un modèle d'apprentissage machine qui utilise à la fois la vignette de l'image et d’autres données relatives à la détection (telles que la distance par rapport à la côte, la profondeur locale et la densité des navires à proximité) pour décider si l'objet est susceptible d'être un navire. Nous signalons également les détections qui sont proches d’infrastructures fixes connues ou dans des zones où il y a une présence importante de glace de mer ou d’icebergs.
\nSi une détection est classée comme étant probablement non liée à un navire ou signalée comme étant potentiellement une infrastructure ou de la glace, nous la supprimons de la couche cartographique afin que seules les détections à haute confiance soient incluses. Nous découpons également les empreintes satellites (affichées sur le calque cartographique) pour exclure les zones couvertes par le masque des zones glacées. Toutefois, nous fournissons tous les faux résultats positifs avec des étiquettes via le portail de téléchargement de données pour les parties prenantes qui ont besoin d'un ensemble de données plus complet.
\nLes données AIS peuvent révéler l’identité des navires, de leurs propriétaires et de leurs sociétés, ainsi que l’activité de pêche. Cependant, tous les navires ne sont pas tenus d’utiliser des dispositifs AIS, car les réglementations varient selon le pays, la taille du navire et l’activité. Les navires engagés dans des activités illicites peuvent également potentiellement désactiver leurs transpondeurs AIS ou manipuler les positions qu’ils diffusent. De plus, d’importantes « zones d’ombre » le long des eaux côtières résultent des pays qui restreignent l’accès aux données AIS capturées par des récepteurs terrestres au lieu de satellites ou d’une mauvaise réception due à une forte densité de navires et à des dispositifs AIS de mauvaise qualité. Les détections par imagerie sans correspondance fournissent donc les informations manquantes sur le trafic maritime dans l’océan.
\nLa correspondance des détections par imagerie avec les coordonnées GPS des navires provenant de l’AIS est un défi, car l’horodatage des images et des archives AIS ne coïncide pas, et une identité AIS distincte peut potentiellement correspondre à plusieurs navires apparaissant sur l’image, et vice versa. Pour déterminer la probabilité qu'un navire diffusant sur AIS corresponde à une détection spécifique, nous avons développé une approche de correspondance basée sur des rasters de probabilité de l'endroit où un navire est susceptible de se trouver quelques minutes avant et après l'enregistrement d'une position AIS. Ces rasters ont été produits à partir d'une année de données AIS mondiales provenant du flux de données Global Fishing Watch, qui utilise des données satellites fournies par Spire Global et Orbcomm. Ces rasters de probabilité sont basés sur environ 10 milliards de positions de navires, et ils sont calculés pour six classes de navires différentes, en tenant compte de six vitesses différentes et de 36 intervalles de temps. Nous obtenons ainsi la position probable d'un navire qui pourrait correspondre à une détection en fonction de la classe du navire, de la vitesse et de l'intervalle de temps. En plus de la correspondance spatiotemporelle, nous prenons en compte la similitude entre la longueur du navire déduite du modèle et la longueur des données d'identité AIS pour éviter les correspondances (probablement incorrectes) avec de grandes différences de taille, par exemple, l'AIS d’un remorqueur et la détection d'un grand navire se trouvant derrière lui.
\nPour aider les utilisateurs à comprendre où les détections ont été possibles, nous affichons les « empreintes » de détection sur la carte. Ces polygones sont les portions des images satellites qui couvrent l’océan et qui ont été utilisées pour la détection. Ainsi, si vous voyez une empreinte, mais aucune détection, cela signifie qu'aucun navire n'a été détecté dans cette zone. S'il n'y a pas d'empreinte, aucune image n’a été traitée pour cet emplacement et cette heure.
\nNotre système de détection et de correspondance est exécuté automatiquement chaque jour. Le système vérifie régulièrement la publication de nouvelles images Sentinel-2 sur Google Cloud et traite celles qui répondent à nos critères de qualité. Les nouvelles détections sont généralement disponibles dans un délai de 1 à 2 jours après la capture de l’image par le satellite. La chaîne de traitement automatisée revérifie également toutes les images publiées tardivement pour garantir que toutes les lacunes de données sont comblées.
\nToutes les données sur les navires sont disponibles gratuitement via le portail de données Global Fishing Watch à l'adresse https://globalfishingwatch.org/data-download/.
\nUsage non commercial uniquement. Le Site et les Services sont fournis pour une utilisation non commerciale uniquement conformément à la licence CC BY-NC 4.0. Si vous souhaitez utiliser le Site et/ou les Services à des fins commerciales, veuillez nous contacter.
", "schema": { "length": { "keyword": "Longueur du navire", "enum": { "<20": "<20", "20-60": "20-60", "60-100": "60-100", ">100": ">100" } }, "matched": { "keyword": "Correspondance", "enum": { "true": "Correspondance AIS", "false": "Sans correspondance AIS" } }, "shiptype": { "keyword": "Type de navire", "enum": { "carrier": "Transporteur", "seismic_vessel": "Navire d’étude sismique", "passenger": "Passager", "other": "Autres", "support": "Soutien", "bunker": "Navire ravitailleur", "gear": "Engin", "cargo": "Fret", "fishing": "Pêche", "discrepancy": "Discordance" } } } }, "public-global-skylight-viirs": { "name": "VIIRS (Skylight)", "description": "The United Nations Convention on the Law of the Sea describes the high seas as ‘all parts of the sea that are not included in the exclusive economic zone, in the territorial sea or in the internal waters of a State, or in the archipelagic waters of an archipelagic State.’ High Seas pockets are areas totally enclosed by EEZs. These pockets can be hard to distinguish from the multiple EEZ jurisdictions that surround them, thus, we have a layer that highlights them. Citation: Flanders Marine Institute (2024). Maritime Boundaries Geodatabase: High Seas, version 2. Available online at https://www.marineregions.org/.
" }, "public-immas": { "name": "Important Marine Mammal Areas (IMMA)", "description": "Important Marine Mammal Areas (IMMAs) are defined as discrete portions of habitat, important to marine mammal species, that have the potential to be delineated and managed for conservation.
\nIMMAs are not marine protected areas (MPAs). IMMAs are identified based on scientific expert knowledge, along with peer review, in order to prioritise their consideration for conservation measures by governments, intergovernmental organisations, conservation groups, industry or business, and the general public.
\nThe IMMA spatial layer aims to attract the attention of policy- and decision-makers to the opportunity, as well as to the need, to ensure the favourable conservation status of marine mammals in specific areas through the implementation of the most appropriate management measures. This can include an MPA designation, shipping or fishing regulations, and/or monitoring. However, IMMAs per se are a scientific knowledge product totally devoid of management implications.
\nPlease note the following:
\n| Contractor ID | Preferred Contractor Name | Nationality |
|---|---|---|
| BGRPMN1 | Federal Institute for Geosciences and Natural Resources of Germany - PMN | Germany |
| BGRPMS1 | Federal Institute for Geosciences and Natural Resources of Germany - PMS | Germany |
| BMJPMN1 | Blue Minerals Jamaica Limited (BMJ) - PMN | Jamaica |
| BPHDCPMN1 | Beijing Pioneer Hi-Tech Development Corporation - PMN | China |
| BrazilCRFC1 | Companhia de Pesquisa de Recursos Minerais S.A. - CRFC | Brazil |
| CIICPMN1 | Cook Islands Investment Corporation - PMN | Cook Islands |
| CMMPMN1 | China Minmetals Corporation - PMN | China |
| COMRACRFC1 | China Ocean Mineral Resources Research and Development Association - CRFC | China |
| COMRAPMN1 | China Ocean Mineral Resources Research and Development Association - PMN | China |
| COMRAPMS1 | China Ocean Mineral Resources Research and Development Association - PMS | China |
| DORDPMN1 | Deep Ocean Resources Development Co. Ltd. - PMN | Japan |
| GSRPMN1 | Global Sea Mineral Resources NV - PMN | Belgium |
| IFREMERPMN1 | Institut français de recherche pour l'exploitation de la mer - PMN | France |
| IFREMERPMS1 | Institut français de recherche pour l'exploitation de la mer - PMS | France |
| IndiaPMN1 | Government of India - PMN | India |
| IndiaPMS1 | Government of India - PMS | India |
| IOMPMN1 | Interoceanmetal Joint Organization - PMN | Poland |
| KOREACRFC1 | Government of the Republic of Korea - CRFC | Korea |
| KOREAPMN1 | Government of the Republic of Korea - PMN | Korea |
| KOREAPMS1 | Government of the Republic of Korea - PMS | Korea |
| MARAWAPMN1 | Marawa Research and Exploration Ltd. - PMN | Kiribati |
| NORIPMN1 | Nauru Ocean Resources Inc. - PMN | Nauru |
| OMSPMN1 | Ocean Mineral Singapore Pte. Ltd. - PMN | Singapore |
| POLPMS1 | Government of the Republic of Poland - PMS | Poland |
| RUSFEDPMS1 | Government of the Russian Federation - PMS | Russia |
| RUSMNRCRFC1 | Ministry of Natural resources and environment of the russian federation - CRFC | Russia |
| TOMLPMN1 | Tonga Offshore Mining Limited - PMN | Tonga |
| UKSRLPMN1 | UK Seabed Resources Ltd. - I - PMN | UK |
| UKSRLPMN2 | UK Seabed Resources Ltd. - II - PMN | UK |
| YUZHPMN1 | Yuzhmorgeologiya - PMN | Russia |
The MPA Guide is intended to fill a gap in existing MPA classification and assessment tools to help determine how likely MPAs are to deliver the desired conservation outcomes. Over the past few years, the MPAtlas team and key collaborators have applied The MPA Guide framework to MPAs around the world to develop a clearer picture of global marine protection, which includes a recent study establishing a baseline for global \"30x30\" targets - Publication: Ocean Protection Quality is Lagging Behind Quantity. MPAtlas is the online repository for MPA Guide assessments and associated data. Stage of Establishment represents where the MPA is in its process of being an MPA. Proposed/Committed: The intent to create an MPA is made public. Designated: MPA is established/recognized through legal means or other authoritative rulemaking. Implemented: MPA is acknowledged to be operation ‘in the water’ with plans for management activated. Actively managed: MPA management is ongoing, with monitoring, periodic review and adjustments made as needed to achieve biodiversity conservation and other ecological and social goals. Level of Protection represents the extent to which the MPA protected from seven main types of human activities and is likely to generate positive biodiversity outcomes. Fully Protected: No impact from extractive or destructive activities is allowed, and all abatable impacts are minimized. Highly Protected: Only light extractive activities are allowed that have low total impact, and all other abatable impacts are minimized. Lightly Protected: Some protection of biodiversity exists, but extractive or destructive activities that can have moderate to significant impact are allowed. Minimally Protected: Extensive extraction and other activities with high total impact are allowed, but the site can still be considered an MPA under the IUCN protected area definition and provides some conservation benefit. Some areas allow activities that have an impact so large that they are incompatible with the conservation of biodiversity, as defined by the IUCN. For more information, please visit https://mpatlas.org/. Each assessed MPA has a score card that describes its stage of establishment and level of protection, as well as more details about the components that contributed to these assessments. Note: The MPAtlas dataset does not contain boundaries for all global MPAs, only those assessed against MPA quality frameworks.
", "schema": { "establishment_stage": { "keyword": "establishment_stage", "enum": { "proposed/committed": "proposed/committed", "designated": "designated", "actively managed": "actively managed", "implemented": "implemented", "unknown": "unknown" } }, "mpaguide_protection_level": { "keyword": "mpaguide_protection_level", "enum": { "unknown": "unknown", "light": "light", "full": "full", "high": "high", "incompatible": "incompatible", "minimal": "minimal" } } } }, "public-mpa-all": { "name": "AMPs (WDPA)", "description": "Marine protected areas (MPAs) are areas of the ocean set aside for long-term conservation. These can have different levels of protection, and the range of activities allowed or prohibited within their boundaries varies considerably. Source: World Database on Protected Areas. Last updated: November 2022. See more detailed metadata information for this layer." }, "public-mpa-no-take": { "name": "MPAs - No take", "description": "The term Marine Protected Areas include marine reserves, fully protected marine areas, no-take zones, marine sanctuaries, ocean sanctuaries, marine parks, locally managed marine areas, to name a few. Many of these have quite different levels of protection, and the range of activities allowed or prohibited within their boundaries varies considerably too. No Take layer was created using the data available from the Marine Protected Planet WDPA using the filter NO_TAKE = 'All'. Source: World Database on Protected Areas (WDPA)" }, "public-mpa-no-take-partial": { "name": "MPAs - No take Partial", "description": "The term Marine Protected Areas include marine reserves, fully protected marine areas, no-take zones, marine sanctuaries, ocean sanctuaries, marine parks, locally managed marine areas, to name a few. Many of these have quite different levels of protection, and the range of activities allowed or prohibited within their boundaries varies considerably too. Source: World Database on Protected Areas (WDPA)" }, "public-no-take-zone-1618836692786": { "name": "Marine Protection Zone", "description": "90% of EEZ" }, "public-northwest-pacific-isa-claim-areas": { "name": "Northwest Pacific ISA License Areas", "description": "This layer depicts the ISA license areas for seabed mining in the Northwestern Pacific, which primarily contain resources from cobalt-rich ferromanganese crusts and polymetallic nodules. Several countries hold exploration leases in this region including China, Japan, Russia, and South Korea." }, "public-norway-fishing-effort": { "name": "Norway VMS", "description": "Les données du système de surveillance des navires (VMS) sont fournies par la Direction norvégienne des pêches. Les données sont collectées par le système norvégien de surveillance des navires via des satellites, sont publiées dans un délai de trois jours et contiennent des informations sur la localisation, la vitesse, la trajectoire et le mouvement des navires. Global Fishing Watch analyse ces données en utilisant les mêmes algorithmes que ceux développés pour les systèmes d'identification automatique (AIS) afin d'identifier les activités et les comportements de pêche. L'algorithme classe chaque point de données diffusé par les navires comme étant apparemment en train de pêcher ou non et affiche le premier sur la carte thermique de l'activité de pêche de Global Fishing Watch. Le VMS diffuse des données différentes de celles de l'AIS et peut donner des mesures différentes en exhaustivité, précision et qualité. Global Fishing Watch améliore continuellement ses algorithmes pour tous les formats de données diffusées afin d'identifier de manière algorithmique les \\\"activités de pêche apparentes\\\". Il est possible qu'une partie de l'activité de pêche ne soit pas identifiée ou que la carte thermique montre une activité de pêche apparente alors que la pêche n'a pas réellement lieu. Pour ces raisons, Global Fishing Watch utilise les termes \\\"activité de pêche\\\", \\\"pêche\\\" ou \\\"effort de pêche\\\" apparents plutôt que certains. Toutes les informations de Global Fishing Watch concernant \\\"l'activité de pêche apparente\\\" doivent être considérées comme une estimation et doivent être utilisées à la seule discrétion de l'utilisateur. Les algorithmes de détection de pêche de Global Fishing Watch sont développés et testés à partir de données d'événements de pêche réels collectés par des observateurs et sont combinés à une analyse experte des données de mouvement des navires AIS, ce qui permet de classer manuellement des milliers d'événements de pêche connus. Global Fishing Watch collabore également de manière intensive avec des chercheurs universitaires par le biais de notre programme de recherche afin de partager les données de classification des activités de pêche et d'améliorer les techniques de classification automatisée." }, "public-norway-presence": { "name": "VMS Norvège", "description": "Les données du système de surveillance des navires (VMS) sont fournies par la direction norvégienne des pêches. Les données sont collectées à l'aide du système de surveillance des navires par satellite de la Norvège et sont publiées avec un délai de trois jours. Ces données contiennent des informations sur la localisation, la vitesse, le cap et les mouvements des navires. Global Fishing Watch analyse ces données à l'aide des mêmes algorithmes développés pour le système d'identification automatique (AIS) afin d'identifier l'activité et les comportements de pêche. L'algorithme classe chaque point de données diffusé par les navires comme étant apparemment en train de pêcher ou non et affiche la pêche sur la carte thermique des activités de pêche de Global Fishing Watch. Le VMS diffuse les données différemment de l'AIS et peut donner des mesures différentes d'exhaustivité, de précision et de qualité. Global Fishing Watch améliore continuellement ses algorithmes dans tous les formats de données diffusés pour identifier de manière algorithmique « l'activité de pêche apparente ». Il est possible que certaines activités de pêche ne soient pas identifiées ou que la carte thermique montre une activité de pêche apparente alors qu'il n'y a pas réellement de pêche. Pour ces raisons, Global Fishing Watch qualifie les termes « activité de pêche », « pêche » ou « effort de pêche » d'apparents plutôt que certains. Toutes les informations de Global Fishing Watch sur les « activités de pêche apparentes » doivent être considérées comme des estimations et doivent être utilisées à la seule discrétion de l’utilisateur. Les algorithmes de présence de pêche de Global Fishing Watch sont développés et testés à l’aide de données réelles sur les événements de pêche collectées par des observateurs et sont combinés à une analyse experte des données de mouvement des navires AIS, ce qui permet la classification manuelle de milliers d’événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager les données de classification des activités de pêche et pour améliorer les techniques de classification automatisée.", "schema": { "vessel_type": { "keyword": "vessel_type", "enum": { "fishing": "fishing", "research": "research", "kelp trawler": "kelp trawler", "other": "other" } } } }, "public-norway-vessel-identity-fishing": { "name": "VMS Norvège (navires de pêche)", "description": "Jeu de données pour VMS Norvège (public)", "schema": { "selfReportedInfo.geartypes.name": { "keyword": "geartypes", "enum": { "DREDGE_FISHING": "DREDGE_FISHING", "DRIFTING_LONGLINES": "DRIFTING_LONGLINES", "FISHING": "FISHING", "FIXED_GEAR": "FIXED_GEAR", "POLE_AND_LINE": "POLE_AND_LINE", "POTS_AND_TRAPS": "POTS_AND_TRAPS", "PURSE_SEINES": "PURSE_SEINES", "SEINERS": "SEINERS", "SET_GILLNETS": "SET_GILLNETS", "SET_LONGLINES": "SET_LONGLINES", "TRAWLERS": "TRAWLERS", "TROLLERS": "TROLLERS" } } } }, "public-norway-vessel-identity-non-fishing": { "name": "VMS Norvège (navires non pêche)", "description": "Jeu de données pour VMS Norvège (public)", "schema": { "selfReportedInfo.geartypes.name": { "keyword": "geartypes", "enum": { "DREDGE_FISHING": "DREDGE_FISHING", "DRIFTING_LONGLINES": "DRIFTING_LONGLINES", "FISHING": "FISHING", "FIXED_GEAR": "FIXED_GEAR", "POLE_AND_LINE": "POLE_AND_LINE", "POTS_AND_TRAPS": "POTS_AND_TRAPS", "PURSE_SEINES": "PURSE_SEINES", "SEINERS": "SEINERS", "SET_GILLNETS": "SET_GILLNETS", "SET_LONGLINES": "SET_LONGLINES", "TRAWLERS": "TRAWLERS", "TROLLERS": "TROLLERS" } } } }, "public-paa-duke": { "name": "PAAS", "description": "This global Preferential Access Area (PAA) database was built with data for 44 countries identified by the Illuminating Hidden Harvests (IHH) initiative following Basurto et al. (2023) and the FAOLEX database (https://www.fao.org/faolex/en/). The total resulting PAAs identified in this study (n = 63) in 44 countries may be considered a lower bound and not comprehensive, as governments can also establish PAAs via laws or regulations either: (i) not relating to the fisheries sector and categorized elsewhere in the FAOLEX database and hence not searched, or (ii) not reported or captured in it. The most recent review of FAOLEX to identify PAAs was conducted in 2022. For mapping and spatial analysis of the PAAs, a geodatabase of PAA boundaries was created using definition parameters for each PAA (i.e., distance from shoreline or the baseline, depth, or a given set of coordinates or buffered distances around undersea features). Baselines were extracted from Flanders Marine Institute’s (2023) version 12 global EEZ database, defined by ‘Straight Baseline’ features. The shoreline dataset was ESRI’s 2014 global shoreline, the same shoreline dataset as the Flanders Marine Institute global EEZ database. Depth data was extracted from the GEBCO 2023 global relief dataset. When possible, Duke reached out to local experts to review the boundaries for confirmation that our interpretation of FAOLEX and the relevant law or regulation matches what is being used by local fishers. If you have feedback on the PAA boundaries, information regarding PAAs that are not reflected here, or other questions, please reach out to ssf-paa-info@duke.edu. For more information on PAAs and how they are managed, please see Duke’s publication by Basurto et al. (2024) here: https://doi.org/10.1038/s44183-024-00096-0. Please note that there is no singular definition of a PAA, therefore each country will decide what activities, vessels, gear types, etc. are prohibited or restricted in the PAA. For more information of the specific designation of each PAA, please see the law or regulation in FAOLex. Citation: DeLand, S., Vegh, T., Cleary, J., Basurto, X., Virdin, J., & Halpin, P. N. (2025). A global dataset of preferential access areas for small-scale fishing. Duke Research Data Repository. https://doi.org/10.7924/r40s01h5j
" }, "public-panama-fishing-effort": { "name": "VMS Panama", "description": "Données du système de surveillance des navires (VMS) fournies par la Aquatic Resources Authority of Panama (ARAP). Les données sont reçues par le système VMS du Panama via satellite et contiennent les identités des navires, le type d'engin, la localisation, la vitesse, le cap et plus encore. Les données des navires de transport du Panama sont également disponibles ici. Chaque point du calque de données des navires de transport représente une position des navires de transport, mais toutes les positions ne sont pas affichées. Les positions des navires de transport sont affichées une fois par jour. À l'avenir, nous espérons pouvoir afficher davantage de positions. Cliquez sur la position d'un navire de transport pour afficher le tracé complet du navire. Global Fishing Watch analyse ces données à l'aide des mêmes algorithmes que ceux que nous avons développés pour les données du système d'identification automatique (AIS) afin d'identifier l'activité et les comportements de pêche. L'algorithme classe chaque point de données de transmission des navires comme étant apparemment en train de pêcher ou non et affiche la pêche sur la carte thermique des activités de pêche de Global Fishing Watch. Le VMS diffuse les données de manière assez différente de l'AIS et peut donner des mesures différentes de l'exhaustivité, de la précision et de la qualité. Au fil du temps, nos algorithmes s'amélioreront dans tous nos formats de données de transmission. L’algorithme de présence de pêche de Global Fishing Watch pour le VMS, comme pour l'AIS, est un effort optimal pour identifier algorithmiquement « l’activité de pêche apparente ». Il est possible que certaines activités de pêche ne soient pas identifiées ou que la carte thermique montre une activité de pêche apparente alors qu’il n’y a pas réellement de pêche. Pour ces raisons, Global Fishing Watch qualifie les termes « activité de pêche », « pêche » et « effort de pêche » d’« apparents » plutôt que certains. Toutes les informations de Global Fishing Watch sur « l’activité de pêche apparente » doivent être considérées comme une estimation et vous devez vous y fier uniquement à vos propres risques. Les algorithmes de présence de pêche de Global Fishing Watch sont développés et testés à l’aide de données réelles sur les événements de pêche collectées par des observateurs, combinées à une analyse par des experts en données de mouvement des navires AIS, ce qui donne lieu à la classification manuelle de milliers d’événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager des données de classification des activités de pêche et une classification automatisée." }, "public-panama-vessel-identity-fishing": { "name": "VMS Panama (public, navires de pêche)", "description": "Jeu de données pour VMS Panama (public)", "schema": { "selfReportedInfo.imo": { "keyword": "imo" }, "selfReportedInfo.nationalRegisterNumber": { "keyword": "nationalRegisterNumber" }, "selfReportedInfo.ssvid": { "keyword": "ssvid" } } }, "public-panama-vessel-identity-non-fishing": { "name": "VMS Panama (public, navires non pêche)", "description": "Jeu de données pour VMS Panama (public, navires de transport)", "schema": { "selfReportedInfo.imo": { "keyword": "imo" }, "selfReportedInfo.nationalRegisterNumber": { "keyword": "nationalRegisterNumber" }, "selfReportedInfo.ssvid": { "keyword": "ssvid" } } }, "public-peru-fishing-effort": { "name": "VMS Pérou", "description": "Données du système de surveillance des navires (VMS) fournies par le ministère de la Production, secteur de la pêche (PRODUCE) du gouvernement péruvien. L'autorisation d'inclure les données péruviennes a nécessité la mise en œuvre d'un délai de publication de 10 jours. Les données sont collectées à l'aide de leur système de surveillance des navires (VMS) via des satellites et des récepteurs terrestres, et contiennent l'identité du navire, le type d'engin, la localisation, la vitesse, le cap et plus encore. Global Fishing Watch analyse ces données en utilisant les mêmes algorithmes développés pour les données du système d'identification automatique (AIS) afin d'identifier l'activité et les comportements de pêche. L'algorithme classe chaque point de données de diffusion pour ces navires comme étant apparemment en train de pêcher ou non et affiche la pêche sur la carte thermique des activités de pêche de Global Fishing Watch. Le VMS diffuse les données de manière assez différente de l'AIS et peut donner des mesures différentes d'exhaustivité, de précision et de qualité. Au fil du temps, nos algorithmes s'amélioreront dans tous nos formats de données de diffusion. L'algorithme de présence de pêche de Global Fishing Watch pour le VMS, comme pour l'AIS, est un effort optimal pour identifier algorithmiquement « l'activité de pêche apparente ». Il est possible que certaines activités de pêche ne soient pas identifiées ou que la carte thermique montre une activité de pêche apparente alors qu'il n'y a pas réellement de pêche. Pour ces raisons, Global Fishing Watch qualifie les termes « activité de pêche », « pêche » ou « effort de pêche » d'« apparents » plutôt que certains. Toutes les informations de Global Fishing Watch sur « l'activité de pêche apparente » doivent être considérées comme une estimation et vous devez vous y fier uniquement à vos propres risques. Les algorithmes de présence de pêche de Global Fishing Watch sont développés et testés à l'aide de données réelles sur les événements de pêche collectées par des observateurs, combinées à une analyse d'experts en données de mouvement des navires AIS, ce qui permet la classification manuelle de milliers d'événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager des données de classification des activités de pêche et des techniques de classification automatisée.", "schema": { "fleet": { "keyword": "flotte", "enum": { "industrial": "industrielle", "artisanal": "artisanale", "small-scale": "à petite échelle", "not defined": "non définie" } }, "origin": { "keyword": "origin", "enum": { "PER": "PER", "Foreign": "Étranger" } } } }, "public-peru-presence": { "name": "Présence VMS Pérou", "description": "Vessel monitoring system (VMS) data provided by the Peruvian Government’s Ministry of Production, Fisheries Sector (PRODUCE). Permission to include Peruvian Data required that a 10 day delay to publishing was implemented. Data is collected using their vessel monitoring system (VMS) via satellites and terrestrial receivers, and contains a vessel’s identity gear type, location, speed, direction and more. Global Fishing Watch analyzes this data using the same algorithms developed for automatic identification system (AIS) data to identify fishing activity and behaviors. The algorithm classifies each broadcast data point for these vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. VMS broadcasts data quite differently from AIS and may give different measures of completeness, accuracy and quality. Over time our algorithms will improve across all our broadcast data formats. Global Fishing Watch’s fishing presence algorithm for VMS, as for AIS, is a best effort to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified, or that the heat map may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing” or “fishing effort,” as “apparent,” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch fishing presence algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of AIS vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification techniques.", "schema": { "fleet": { "keyword": "flotte", "enum": { "industrial": "industrielle", "artisanal": "artisanale", "small-scale": "à petite échelle", "not defined": "non définie" } }, "origin": { "keyword": "origine", "enum": { "PER": "PER", "Foreign": "Étranger" } } } }, "public-peru-vessel-identity-fishing": { "name": "VMS Pérou (navires de pêche)", "description": "Jeu de données pour VMS Pérou (public)", "schema": { "selfReportedInfo.casco": { "keyword": "casco", "enum": { "ACERO NAVAL": "ACERO NAVAL", "MADERA": "MADERA", "N/E": "N/E", "NONE": "NONE", "FIBRA DE VIDRIO": "FIBRA DE VIDRIO" } }, "selfReportedInfo.externalId": { "keyword": "externalId" }, "selfReportedInfo.fleet": { "keyword": "fleet", "enum": { "industrial": "industrial", "artisanal": "artisanal", "not defined": "not defined" } }, "selfReportedInfo.origin": { "keyword": "origin", "enum": { "Peru": "Peru", "Foreign": "Foreign" } } } }, "public-pmn-exploration-areas-individual": { "name": "PMN Exploration Areas", "description": "Polymetallic nodules occur across abyssal plains. These nodules can be found at depths from 3000 meters to 6500 meters with high abundance in the Pacific Ocean and the Central Indian Ocean Basin. Nodules form at a rate of 1-3 millimeters per million years as metals from the surrounding water precipitate onto small particles, such as a grain of sand or a fragment of a shell, forming habitat for unique and poorly understood biodiversity. They are primarily composed of manganese, nickel, cobalt, copper, and rare earth elements. Exploration Areas under the International Seabed Authority are areas licensed for exploration of mineral resources to particular States and associated contractors. 75,000 square kilometers are allocated to each contractor for polymetallic nodule Exploration Areas.", "schema": { "act_date": { "keyword": "act_date", "enum": { "985816800000": "985816800000", "1717970400000": "1717970400000" } }, "area_key": { "keyword": "area_key" }, "contract_id": { "keyword": "contract_id", "enum": { "KOREAPMN1": "KOREAPMN1", "IOMPMN1": "IOMPMN1", "DORDPMN1": "DORDPMN1", "BMJPMN1": "BMJPMN1", "IndiaPMN1": "IndiaPMN1", "TOMLPMN1": "TOMLPMN1", "IFREMERPMN1": "IFREMERPMN1", "BGRPMN1": "BGRPMN1", "BPHDCPMN1": "BPHDCPMN1", "UKSRLPMN2": "UKSRLPMN2", "UKSRLPMN1": "UKSRLPMN1", "YUZHPMN1": "YUZHPMN1", "CIICPMN1": "CIICPMN1", "OMSPMN1": "OMSPMN1", "GSRPMN1": "GSRPMN1", "MARAWAPMN1": "MARAWAPMN1", "CMMPMN1": "CMMPMN1", "NORIPMN1": "NORIPMN1", "COMRAPMN1": "COMRAPMN1" } } } }, "public-pmn-reserved-areas-individual": { "name": "PMN Reserved Areas", "description": "Polymetallic nodules occur across abyssal plains. These nodules can be found at depths from 3000 meters to 6500 meters with high abundance in the Pacific Ocean and the Central Indian Ocean Basin. Nodules form at a rate of 1-3 millimeters per million years as metals from the surrounding water precipitate onto small particles, such as a grain of sand or a fragment of a shell, forming habitat for unique and poorly understood biodiversity. They are primarily composed of manganese, nickel, cobalt, copper, and rare earth elements. Reserved Areas under the International Seabed Authority are a critical mechanism to ensure developing countries have access to deep-sea mineral resources in the future. These areas are typically contributed by developed States when they apply for exploration rights.", "schema": { "act_date": { "keyword": "act_date", "enum": { "988322400000": "988322400000", "1617487200000": "1617487200000" } }, "area_key": { "keyword": "area_key" }, "contract_id": { "keyword": "contract_id", "enum": { "BPHDCPMN1": "BPHDCPMN1", "PMNReserved": "PMNReserved" } } } }, "public-pms-exploration-areas-individual": { "name": "PMS Exploration Areas", "description": "Polymetallic sulphides, or seafloor massive sulphides, are formed at hydrothermal vents near mid-ocean ridges and back-arc basins between approximately 1,000 and 4,000 meters in depth. They are formed when superheated, mineral-rich fluids from the Earth’s mantle are rapidly cooled by deep water. Rapid cooling results in dissolved metals in the fluid precipitating as metal sulfides. These sulfides and surrounding polymetallic muds can contain copper, zinc, silver, and gold. For polymetallic sulphides, the exploration area allocated to each contractor is 10,000 square kilometres and consists of 100 blocks. Each block is no greater than 100 square kilometres.", "schema": { "act_date": { "keyword": "act_date", "enum": { "1474840800000": "1474840800000", "1698098400000": "1698098400000" } }, "area_key": { "keyword": "area_key" }, "contract_id": { "keyword": "contract_id", "enum": { "KOREAPMS1": "KOREAPMS1", "COMRAPMS1": "COMRAPMS1", "IFREMERPMS1": "IFREMERPMS1", "POLPMS1": "POLPMS1", "RUSFEDPMS1": "RUSFEDPMS1", "BGRPMS1": "BGRPMS1", "IndiaPMS1": "IndiaPMS1" } } } }, "public-png-fishing-effort": { "name": "VMS Papouasie Nouvelle-Guinée", "description": "Les données du système de surveillance des navires (VMS) sont fournies par l'Autorité nationale des pêches de Papouasie-Nouvelle-Guinée. Les données sont collectées à l'aide du système de surveillance des navires (VMS) par satellite de Papouasie-Nouvelle-Guinée, qui contient des informations d'identification et de localisation des navires, et sont publiées avec un délai de cinq jours. Global Fishing Watch déduit la vitesse et le cap de chaque localisation de navire et analyse ces données à l'aide des mêmes algorithmes développés pour le système d'identification automatique (AIS) afin d'identifier l'activité et les comportements de pêche. L'algorithme classe chaque point de données transmis par les navires comme étant apparemment en train de pêcher ou non et affiche la pêche sur la carte thermique des activités de pêche de Global Fishing Watch. Le VMS diffuse les données différemment de l'AIS et peut donner des mesures différentes d'exhaustivité, de précision et de qualité. Global Fishing Watch améliore continuellement ses algorithmes dans tous les formats de données diffusés pour identifier de manière algorithmique « l'activité de pêche apparente ». Il est possible qu'une certaine activité de pêche ne soit pas identifiée ou que la carte thermique montre une activité de pêche apparente alors qu'il n'y a pas réellement de pêche. Pour ces raisons, Global Fishing Watch qualifie les termes « activité de pêche », « pêche » ou « effort de pêche » d’apparents plutôt que certains. Toutes les informations de Global Fishing Watch sur « l’activité de pêche apparente » doivent être considérées comme une estimation et doivent être utilisées uniquement à la discrétion de l’utilisateur. Les algorithmes de détection de pêche de Global Fishing Watch sont développés et testés à l’aide de données réelles sur les événements de pêche collectées par des observateurs et sont combinés à une analyse d'experts en données de mouvement des navires AIS, ce qui permet la classification manuelle de milliers d’événements de pêche connus. Global Fishing Watch collabore également étroitement avec des chercheurs universitaires dans le cadre de notre programme de recherche pour partager les données de classification des activités de pêche et pour améliorer les techniques de classification automatisée." }, "public-png-presence": { "name": "Papua New Guinea VMS", "description": "Les données du système de surveillance des navires (VMS) sont fournies par l'Autorité nationale des pêches de Papouasie-Nouvelle-Guinée. Les données sont collectées à l'aide du VMS national de Papouasie-Nouvelle-Guinée fourni par le Système d'information et de gestion des pêches (FIMS). Les données VMS incluent les identifiants et l'emplacement des navires, et sont publiées avec un délai de cinq jours.\n\nLa couche d'activité affiche une carte thermique de la présence des navires. La présence est déterminée en prenant deux positions par heure et par navire à partir des positions transmises par le VMS du navire." }, "public-png-vessel-identity-fishing": { "name": "Papua New Guinea VMS (Fishing Vessels)", "description": "Dataset for VMS Papua New Guinea (Public) " }, "public-ports-v1": { "name": "Portes", "description": "Named ports v1" }, "public-protectedseas": { "name": "AMPs (ProtectedSeas)", "description": "Les aires marines protégées (AMP) sont des zones océaniques réservées à la conservation à long terme. Celles-ci peuvent avoir différents niveaux de protection et l'éventail des activités autorisées ou interdites à l'intérieur de leurs limites varie considérablement. Source : Navigateur ProtectedSeas. ProtectedSeas attribue un niveau de protection de la pêche (LFP) à chaque zone sur la base d'une analyse des restrictions à l'extraction de la vie marine. Vous pouvez utiliser l'icône de filtre pour explorer les différents scores LFP, qui sont, Le moins restrictif : Aucune restriction de pêche connue ; Moins restrictif : peu de restrictions spécifiques à l'espèce ou à l'engin s'appliquent ; Modérément restrictif : plusieurs restrictions spécifiques à l'espèce ou à l'engin s'appliquent; Fortement restrictif : la pêche est généralement interdite, à quelques exceptions près ; Le plus restrictif : La pêche est interdite. Voir des informations plus détaillées pour cette couche.", "schema": { "removal_of": { "keyword": "Niveau de protection de la pêche", "enum": { "1": "1. Le moins restrictif", "2": "2. Moins restrictif", "3": "3. Modérément restrictif", "4": "4. Fortement restrictif", "5": "5. Le plus restrictif" } } } }, "public-protectedseas-all": { "name": "Protected Seas all", "description": "Protected seas all", "schema": { "category_name": { "keyword": "category_name", "enum": { "IUCN MPA": "IUCN MPA", "Other": "Autres", "Jurisdictional Authority Area": "Jurisdictional Authority Area", "TBD": "TBD", "Fisheries Management Area": "Fisheries Management Area", "Recreational Area": "Recreational Area", "OECM": "OECM", "Vessel Restricted Area": "Vessel Restricted Area", "Voluntary Conservation Measure Area": "Voluntary Conservation Measure Area", "Vessel Reporting Area": "Vessel Reporting Area", "Water Quality/Human Health Area": "Water Quality/Human Health Area" } }, "removal_of_marine_life_is_prohibited": { "keyword": "removal_of_marine_life_is_prohibited", "enum": { "1": "1", "2": "2", "3": "3", "4": "4. Fortement restrictif", "5": "5" } } } }, "public-rfmo": { "name": "RFMO", "description": "Regional fisheries management organizations (RFMOs) are international bodies formed by countries with a shared interest in managing or conserving fish stocks in a particular region. Some manage all the fish stocks found in a given area, while others focus on specific highly migratory species, notably tuna. The regional fisheries management organization on the Global Fishing Watch map currently includes the five tuna regional fisheries management organizations. See more detailed metadata information for this layer.", "schema": { "ID": { "keyword": "ID", "enum": { "APFIC": "APFIC", "BOBP-IGO": "BOBP-IGO", "CCAMLR": "CCAMLR", "CCBSP": "CCBSP", "CCSBT": "CCSBT", "CCSBT Primary Area": "CCSBT Primary Area", "COREP": "COREP", "CPPS": "CPPS", "CRFM": "CRFM", "CTMFM": "CTMFM", "FCWC": "FCWC", "FFA": "FFA", "GFCM": "GFCM", "IATTC": "IATTC", "ICCAT": "ICCAT", "ICES": "ICES", "IOTC": "IOTC", "IPHC": "IPHC", "LTA": "LTA", "NAFO": "NAFO", "NAMMCO": "NAMMCO", "NASCO": "NASCO", "NEAFC": "NEAFC", "NPAFC": "NPAFC", "NPFC": "NPFC", "OSPESCA": "OSPESCA", "PERSGA": "PERSGA", "PICES": "PICES", "RECOFI": "RECOFI", "SEAFDEC": "SEAFDEC", "SIOFA": "SIOFA", "SPC": "SPC", "SPRFMO": "SPRFMO", "SRFC": "SRFC", "SWIOFC": "SWIOFC", "WCPFC": "WCPFC" } } } }, "public-seagrasses": { "name": "Herbiers marins", "description": "Vessel Monitoring System (VMS) data for Belize is provided by the Belize High Seas Fisheries Unit (BHSFU). This data is collected via satellite through Belize's national VMS and includes information on vessels' location, speed, course, and movement. The data is published with a 3-day delay, and historical data is available from 2021 onwards. Due to a degradation in data quality for the Belize vessel feed - specifically, we are no longer receiving vessel shiptype information - we are unable to run our Fishing Effort model on this dataset. Should we be able to re-establish the minimum data requirements (shiptype), we will republish fishing effort in the future.
Public users can view vessel tracks for Belize VMS data, but cannot download them. Vessel names and certain identity information are not available to public users. If you are a member of the Belize government, please contact our support team to request access to a private workspace at support@globalfishingwatch.org. If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please don't hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "public-vms-blz-tracks": { "name": "Belize VMS", "description": "Tracks dataset for VMS Belize (Public)" }, "public-vms-blz-vessel-identity": { "name": "VMS Belize", "description": "Vessels (VMS Belize)" }, "public-vms-bra-fishing-effort": { "name": "VMS Brazil", "description": "Vessel Monitoring System (VMS) data for Brazil is collected via satellite and provided through a partnership with Brazil's Ministry of Fisheries and Aquaculture (MPA). The data is published with a 3-day delay, and historical data is available from 2016 onward. The polling rate depends on vessel type: drifting longline vessels report approximately every 20 minutes, while other vessels report about once per hour.
Please note that given the lower polling rates of some vessel types compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
In our Brazil VMS dataset, you can filter vessels by various gear types as well as by their target species.
Vessel names are visible to public users, and vessel tracks can be viewed but not downloaded. If you require data access beyond what is publicly available, please contact our support team to request access to a private workspace at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "license_category": { "keyword": "license_category", "enum": { "": "", "1.1 - Espinhel horizontal (superfície)": "1.1 - Espinhel horizontal (superfície)", "1.10 - Espinhel vertical/Covos": "1.10 - Espinhel vertical/Covos", "1.11 - Espinhel vertical": "1.11 - Espinhel vertical", "1.12 - Linha de mão (fundo)": "1.12 - Linha de mão (fundo)", "1.13 - Linha/vara - com isca viva": "1.13 - Linha/vara - com isca viva", "1.14 - Linha de mão (fundo)": "1.14 - Linha de mão (fundo)", "1.15 - Linha de mão (superfície)": "1.15 - Linha de mão (superfície)", "1.17 - Cardume associado": "1.17 - Cardume associado", "1.18 - Cardume associado": "1.18 - Cardume associado", "1.2 - Espinhel horizontal (superfície)": "1.2 - Espinhel horizontal (superfície)", "1.3 - Espinhel horizontal (superfície) - com isca-viva": "1.3 - Espinhel horizontal (superfície) - com isca-viva", "1.4 - Espinhel horizontal (superfície)": "1.4 - Espinhel horizontal (superfície)", "1.5 - Espinhel horizontal (fundo)": "1.5 - Espinhel horizontal (fundo)", "1.6 - Espinhel horizontal (fundo)": "1.6 - Espinhel horizontal (fundo)", "1.7 - Espinhel horizontal (fundo)": "1.7 - Espinhel horizontal (fundo)", "1.8 - Espinhel vertical/covos": "1.8 - Espinhel vertical/covos", "1.9 - Espinhel vertical/Covos": "1.9 - Espinhel vertical/Covos", "2.10 - Emalhe costeiro (fundo)": "2.10 - Emalhe costeiro (fundo)", "2.11 - Emalhe costeiro (fundo)": "2.11 - Emalhe costeiro (fundo)", "2.12 - Emalhe costeiro (fundo)": "2.12 - Emalhe costeiro (fundo)", "2.13 - Emalhe Costeiro Diversificado": "2.13 - Emalhe Costeiro Diversificado", "2.2 - Emalhe costeiro (superfície) ": "2.2 - Emalhe costeiro (superfície) ", "2.3 - Emalhe oceânico (fundo)": "2.3 - Emalhe oceânico (fundo)", "2.4 - Emalhe costeiro (fundo)": "2.4 - Emalhe costeiro (fundo)", "2.5 - Emalhe costeiro (superfície)": "2.5 - Emalhe costeiro (superfície)", "2.6 - Emalhe costeiro (superfície)": "2.6 - Emalhe costeiro (superfície)", "2.7 - Emalhe costeiro (superfície)": "2.7 - Emalhe costeiro (superfície)", "2.8 - Emalhe costeiro (superfície)": "2.8 - Emalhe costeiro (superfície)", "3.1 - Arrasto (fundo) parelha ou trilheira (*)": "3.1 - Arrasto (fundo) parelha ou trilheira (*)", "3.10 - Arrasto costeiro (fundo) - duplo": "3.10 - Arrasto costeiro (fundo) - duplo", "3.11 - Arrasto costeiro (fundo simples e parelha": "3.11 - Arrasto costeiro (fundo simples e parelha", "3.12 - Arrasto oceânico (fundo) – simples e duplo": "3.12 - Arrasto oceânico (fundo) – simples e duplo", "3.13 - Arrasto oceânico (fundo) – simples e duplo": "3.13 - Arrasto oceânico (fundo) – simples e duplo", "3.14 - Arrasto (meia água)": "3.14 - Arrasto (meia água)", "3.2 - Arrasto (fundo) – Simples ou parelha": "3.2 - Arrasto (fundo) – Simples ou parelha", "3.3 - Arrasto (fundo) - duplo ou simples (**)": "3.3 - Arrasto (fundo) - duplo ou simples (**)", "3.4 - Arrasto (fundo) - duplo ou simples": "3.4 - Arrasto (fundo) - duplo ou simples", "3.5 - Arrasto (fundo) - duplo ou simples": "3.5 - Arrasto (fundo) - duplo ou simples", "3.6 - Arrasto (fundo) - duplo": "3.6 - Arrasto (fundo) - duplo", "3.7 - Arrasto (fundo)– duplo": "3.7 - Arrasto (fundo)– duplo", "3.8 - Arrasto (fundo) - duplo ou simples": "3.8 - Arrasto (fundo) - duplo ou simples", "3.9 - Arrasto (fundo) - duplo ou simples": "3.9 - Arrasto (fundo) - duplo ou simples", "4.1 - Cerco": "4.1 - Cerco", "4.2 - Cerco": "4.2 - Cerco", "4.3 - Cerco": "4.3 - Cerco", "4.4 - Cerco": "4.4 - Cerco", "4.6 - Cerco": "4.6 - Cerco", "5.1 - Covos": "5.1 - Covos", "5.10 - Potes": "5.10 - Potes", "5.11 - Potes": "5.11 - Potes", "5.12 - Potes": "5.12 - Potes", "5.2 - Covos": "5.2 - Covos", "5.3 - Covos": "5.3 - Covos", "5.4 - Covos": "5.4 - Covos", "5.5 - Covos": "5.5 - Covos", "5.6 - Covos": "5.6 - Covos", "5.9 - Covos": "5.9 - Covos", "Sem código IN - Covos": "Sem código IN - Covos" } }, "target_species": { "keyword": "target_species", "enum": { "": "", "Agulha": "Agulha", "Albacora laje (Thunnus albacares), Albacora bandolim (Thunnus obesus) e Bonito listrado (Katsuwonus pelamis).": "Albacora laje (Thunnus albacares), Albacora bandolim (Thunnus obesus) e Bonito listrado (Katsuwonus pelamis).", "Anchova (Pomatomus saltatrix), corvina (Micropogonias furnieri), pescada (Cynoscion guatucupa), castanha (Umbrina canosai), abrótea (Urophycis brasiliensis) e fauna acompanhante": "Anchova (Pomatomus saltatrix), corvina (Micropogonias furnieri), pescada (Cynoscion guatucupa), castanha (Umbrina canosai), abrótea (Urophycis brasiliensis) e fauna acompanhante", "Anchova, tainha e sororoca": "Anchova, tainha e sororoca", "Anchoíta, galo, calamar": "Anchoíta, galo, calamar", "Atuns (albacora laje, albacora branca e albacora bandolim)": "Atuns (albacora laje, albacora branca e albacora bandolim)", "Bagres (Ariidae), dourada e pescada branca, arraia, pescada amarela, pescada gó, corvina, tainha.": "Bagres (Ariidae), dourada e pescada branca, arraia, pescada amarela, pescada gó, corvina, tainha.", "Batata, Abrótea de profundidade, Namorado, Garoupa,Bagre e cherne verdadeiro": "Batata, Abrótea de profundidade, Namorado, Garoupa,Bagre e cherne verdadeiro", "Bonito listrado": "Bonito listrado", "Camarão rosa (santana e barba ruça)": "Camarão rosa (santana e barba ruça)", "Camarão rosa, sete- barbas e branco": "Camarão rosa, sete- barbas e branco", "Camarão santana e barba ruça": "Camarão santana e barba ruça", "Camarão sete barbas (Santana e barba ruça)": "Camarão sete barbas (Santana e barba ruça)", "Camarões (sete- barbas, branco, rosa)": "Camarões (sete- barbas, branco, rosa)", "Camarões de profundidade": "Camarões de profundidade", "Caranguejo de profundidade (Chaceon spp.)": "Caranguejo de profundidade (Chaceon spp.)", "Caranguejo vermelho (Chaceon notialis)": "Caranguejo vermelho (Chaceon notialis)", "Cavalas, Albacorinhas": "Cavalas, Albacorinhas", "Corvina, castanha, pescada e pescadinha real": "Corvina, castanha, pescada e pescadinha real", "Corvina, castanha, pescada e pescadinha real, linguado, abrotea, cabrinha.": "Corvina, castanha, pescada e pescadinha real, linguado, abrotea, cabrinha.", "Corvina, pescada, castanha, abrótea": "Corvina, pescada, castanha, abrótea", "Dourada, Piramutaba e Gurijuba": "Dourada, Piramutaba e Gurijuba", "Dourado": "Dourado", "Espadarte": "Espadarte", "Galo-de-fundo, abrótea-de-fundo, merluza": "Galo-de-fundo, abrótea-de-fundo, merluza", "Lagosta verde e lagosta vermelha": "Lagosta verde e lagosta vermelha", "Pargo": "Pargo", "Pargo rosa": "Pargo rosa", "Peixe sapo": "Peixe sapo", "Peroá, Garoupa e Corvina": "Peroá, Garoupa e Corvina", "Pescada amarela gurijuba e camurim": "Pescada amarela gurijuba e camurim", "Pescada gó, camurim e corvina": "Pescada gó, camurim e corvina", "Piramutaba": "Piramutaba", "Piramutaba e dourada": "Piramutaba e dourada", "Polvo": "Polvo", "Saramunete": "Saramunete", "Sardinha lage, savelha, galo, sardinha-cascuda, peixe-porco, sardinha-boca-torta, xaréu, guaivira, palombeta e cavalinha ": "Sardinha lage, savelha, galo, sardinha-cascuda, peixe-porco, sardinha-boca-torta, xaréu, guaivira, palombeta e cavalinha ", "Sardinha verdadeira": "Sardinha verdadeira", "Sardinha-lage": "Sardinha-lage", "Scombridae, Lutjanidae, Serranidae e Caranjidae (a definir) e Vermelhos (cioba, dentão, guaíuba, ariacó)": "Scombridae, Lutjanidae, Serranidae e Caranjidae (a definir) e Vermelhos (cioba, dentão, guaíuba, ariacó)", "Serra": "Serra", "Serranidae e caranjidae (detalhar)": "Serranidae e caranjidae (detalhar)", "Tainha": "Tainha", "Vermelhos (especificar)": "Vermelhos (especificar)" } } } }, "public-vms-bra-presence": { "name": "VMS Brazil Presence", "description": "Global Fishing Watch uses data about a vessels identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as carriers. The activity layer displays a heatmap of vessel presence. The presence is determined by taking one position per day per vessel from the positions transmitted by the vessels AIS.", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "Vessel Monitoring System (VMS) data is provided by the Chilean government's fisheries and aquaculture regulator (SERNAPESCA). The data includes information on vessels' location, speed, course, and movement, and is published with a 3-day delay. Historical VMS data is available from 2019 onward.
Users can filter Chile's VMS data by fleet, distinguishing between small-scale fishing vessels (18 meters) and industrial fishing vessels (>18 meters). In addition to fishing vessels, SERNAPESCA also tracks aquaculture vessels and actively uses this map to monitor vessel activity across its fleet.
The polling rate depends on the fishery, with positions reported approximately every 8 to 15 minutes.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are available to public users, and tracks can be viewed and downloaded.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "INDUSTRY": "INDUSTRY", "SMALL_FISHERIES": "SMALL_FISHERIES" } } } }, "public-vms-chl-presence": { "name": "VMS Chile Presence", "description": "Vessel Monitoring System (VMS) data is provided by the Chilean government's fisheries and aquaculture regulator (SERNAPESCA). The data includes information on vessels' location, speed, course, and movement, and is published with a 3-day delay. Historical VMS data is available from 2019 onward.
Users can filter Chile's VMS data by fleet, distinguishing between small-scale fishing vessels (18 meters) and industrial fishing vessels (>18 meters). In addition to fishing vessels, SERNAPESCA also tracks aquaculture vessels and actively uses this map to monitor vessel activity across its fleet.
The polling rate depends on the fishery, with positions reported approximately every 8 to 15 minutes.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are available to public users, and tracks can be viewed and downloaded.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "source_fleet": { "keyword": "source_fleet", "enum": { "AQUACULTURE": "AQUACULTURE", "INDUSTRY": "INDUSTRY", "SMALL_FISHERIES": "SMALL_FISHERIES", "TRANSPORT": "TRANSPORT" } }, "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "public-vms-chl-tracks": { "name": "CHILE VMS", "description": "Tracks dataset for VMS CHILE (Public)" }, "public-vms-chl-vessel-identity": { "name": "VMS Chile", "description": "Vessels (VMS Chile)" }, "public-vms-cri-fishing-effort": { "name": "VMS Costa Rica", "description": "Vessel Monitoring System (VMS) data is provided by the Costa Rican Fisheries and Aquaculture Institute, with CLS as the data provider. The data includes information on vessels' location, speed, course, and movement, and is published with a 3-day delay. Historical VMS data is available from 2021 onward. The polling rate is about once per hour. We publish data for the Tuna fleet, Industrial longline fleet, and sardine fleet.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names are not visible to public users. Vessel tracks can be viewed but cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team to request access to a private workspace at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "ATUNEROS": "ATUNEROS", "AVANZADOS": "AVANZADOS", "SARDINEROS": "SARDINEROS" } } } }, "public-vms-cri-presence": { "name": "VMS Costa Rica Presence", "description": "Vessel Monitoring System (VMS) data is provided by the Costa Rican Fisheries and Aquaculture Institute, with CLS as the data provider. The data includes information on vessels' location, speed, course, and movement, and is published with a 3-day delay. Historical VMS data is available from 2021 onward. The polling rate is about once per hour. We publish data for the Tuna fleet, Industrial longline fleet, and sardine fleet.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names are not visible to public users. Vessel tracks can be viewed but cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team to request access to a private workspace at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "source_fleet": { "keyword": "source_fleet", "enum": { "ATUNEROS": "ATUNEROS", "AVANZADOS": "AVANZADOS", "SARDINEROS": "SARDINEROS" } }, "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "public-vms-cri-tracks": { "name": "Costa Rica VMS", "description": "Tracks dataset for VMS Costa Rica (Public)" }, "public-vms-cri-vessel-identity": { "name": "VMS Costa Rica", "description": "Vessels (VMS Costa Rica)", "schema": { "selfReportedInfo.source_fleet": { "keyword": "source_fleet", "enum": { "ATUNEROS": "ATUNEROS", "AVANZADOS": "AVANZADOS", "SARDINEROS": "SARDINEROS" } } } }, "public-vms-ecu-fishing-effort": { "name": "VMS Ecuador", "description": "Vessel Monitoring System (VMS) data is provided by the National Directorate of Aquatic Spaces of the Ecuadorian Navy. The data is collected via satellite through Ecuador's national VMS and includes information on vessels' identity, location, speed, course, and movement. It is published with a 7-day delay, and historical data is available from 2020 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "public-vms-ecu-presence": { "name": "VMS Ecuador Presence", "description": "Global Fishing Watch uses data about a vessels identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as carriers. The activity layer displays a heatmap of vessel presence. The presence is determined by taking one position per day per vessel from the positions transmitted by the vessels AIS.", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "": "", "SUPPORT": "SUPPORT", "NON-FISHING": "NON-FISHING", "FISHING": "FISHING" } } } }, "public-vms-ecu-tracks": { "name": "Ecuador VMS", "description": "Tracks dataset for VMS Ecuador (Public)" }, "public-vms-ecu-vessel-identity": { "name": "VMS Ecuador", "description": "Vessels (VMS Ecuador)", "schema": { "selfReportedInfo.registryNumber": { "keyword": "registryNumber" } } }, "public-vms-nor-fishing-effort": { "name": "VMS Norway", "description": "Vessel Monitoring System (VMS) data for Norway is provided by the Norwegian Directorate of Fisheries. The data is collected via satellite and includes information on vessels' identity, location, speed, course, and movement. It is published with a 3-day delay, and historical data is available from 2015 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "public-vms-nor-presence": { "name": "VMS Norway Presence", "description": "Vessel Monitoring System (VMS) data for Norway is provided by the Norwegian Directorate of Fisheries. The data is collected via satellite and includes information on vessels' identity, location, speed, course, and movement. It is published with a 3-day delay, and historical data is available from 2015 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "public-vms-nor-tracks": { "name": "Norway VMS", "description": "Tracks dataset for VMS Norway (Public)" }, "public-vms-nor-vessel-identity": { "name": "VMS Norway", "description": "Vessels (VMS Norway)" }, "public-vms-pan-fishing-effort": { "name": "VMS Panama", "description": "Vessel Monitoring System (VMS) data is provided by the Panama Aquatic Resources Authority (ARAP). The data is collected via satellite through Panama's national VMS and includes information on vessels' identity, location, speed, course, and movement. It is published with a 3-day delay, and historical data is available from 2012 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
For the international fleet, vessel identity information is available to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "INTERNATIONAL": "INTERNATIONAL" } } } }, "public-vms-pan-presence": { "name": "VMS Panama Presence", "description": "Vessel Monitoring System (VMS) data is provided by the Panama Aquatic Resources Authority (ARAP). The data is collected via satellite through Panama's national VMS and includes information on vessels' identity, location, speed, course, and movement. It is published with a 3-day delay, and historical data is available from 2012 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
For the international fleet, vessel identity information is available to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, again, please do not hesitate to reach out to our support email.
", "schema": { "source_fleet": { "keyword": "source_fleet", "enum": { "INTERNATIONAL": "INTERNATIONAL" } }, "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "public-vms-pan-tracks": { "name": "PANAMA VMS", "description": "Tracks dataset for VMS PANAMA (Public)" }, "public-vms-pan-vessel-identity": { "name": "VMS Panama", "description": "Vessels (VMS Panama)", "schema": { "selfReportedInfo.externalId": { "keyword": "externalId" }, "selfReportedInfo.imo": { "keyword": "imo" }, "selfReportedInfo.ssvid": { "keyword": "ssvid" } } }, "public-vms-per-fishing-effort": { "name": "VMS Peru", "description": "Global Fishing Watch uses data about a vessel’s identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as known or possible commercial fishing vessels, and applies a fishing presence algorithm to determine “apparent fishing activity” based on changes in vessel speed and direction. The algorithm classifies each AIS broadcast data point for these vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. AIS data as broadcast may vary in completeness, accuracy and quality. Also, data collection by satellite or terrestrial receivers may introduce errors through missing or inaccurate data. Global Fishing Watch’s fishing presence algorithm is a best effort mathematically to identify “apparent fishing activity.” As a result, it is possible that some fishing activity is not identified as such by Global Fishing Watch; conversely, Global Fishing Watch may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies designations of vessel fishing activity, including synonyms of the term “fishing activity,” such as “fishing” or “fishing effort,” as “apparent,” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch is taking steps to make sure fishing activity designations are as accurate as possible. Global Fishing Watch fishing presence algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification techniques.", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } }, "origin": { "keyword": "origin", "enum": { "Foreign": "Foreign", "PER": "PER", "": "" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "": "", "SMALL-SCALE": "SMALL-SCALE", "INDUSTRIAL": "INDUSTRIAL", "ARTISANAL": "ARTISANAL" } } } }, "public-vms-per-presence": { "name": "VMS Peru Presence", "description": "Global Fishing Watch uses data about a vessels identity, type, location, speed, direction and more that is broadcast using the Automatic Identification System (AIS) and collected via satellites and terrestrial receivers. AIS was developed for safety/collision-avoidance. Global Fishing Watch analyzes AIS data collected from vessels that our research has identified as carriers. The activity layer displays a heatmap of vessel presence. The presence is determined by taking one position per day per vessel from the positions transmitted by the vessels AIS.", "schema": { "origin": { "keyword": "origin", "enum": { "Foreign": "Foreign", "PER": "PER", "": "" } }, "source_fleet": { "keyword": "source_fleet", "enum": { "INDUSTRIAL": "INDUSTRIAL", "SMALL-SCALE": "SMALL-SCALE", "ARTISANAL": "ARTISANAL", "": "" } }, "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } } } }, "public-vms-per-tracks": { "name": "PERU VMS", "description": "Tracks dataset for VMS PERU (public)" }, "public-vms-per-vessel-identity": { "name": "VMS Peru", "description": "Vessels (VMS Peru)", "schema": { "selfReportedInfo.externalId": { "keyword": "externalId" }, "selfReportedInfo.hull": { "keyword": "hull", "enum": { "ACERO NAVAL": "ACERO NAVAL", "MADERA": "MADERA", "N/E": "N/E", "NONE": "NONE", "FIBRA DE VIDRIO": "FIBRA DE VIDRIO" } }, "selfReportedInfo.origin": { "keyword": "origin", "enum": { "PERU": "PERU", "FOREIGN": "FOREIGN" } }, "selfReportedInfo.sourceFleet": { "keyword": "sourceFleet", "enum": { "": "", "ARTISANAL": "ARTISANAL", "INDUSTRIAL": "INDUSTRIAL", "SMALL-SCALE": "SMALL-SCALE" } } } }, "public-vms-plw-fishing-effort": { "name": "VMS Palau", "description": "Vessel Monitoring System (VMS) data for Palau is provided by the Palau National Marine Sanctuary. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 3-day delay, and historical data is available from 2021 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "public-vms-plw-presence": { "name": "VMS Palau Presence", "description": "Vessel Monitoring System (VMS) data for Palau is provided by the Palau National Marine Sanctuary. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 3-day delay, and historical data is available from 2021 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "public-vms-plw-tracks": { "name": "Palau VMS", "description": "Tracks dataset for VMS Palau (Public)" }, "public-vms-plw-vessel-identity": { "name": "VMS Palau", "description": "Vessels (VMS Palau)", "schema": { "selfReportedInfo.imo": { "keyword": "imo" } } }, "public-vms-png-fishing-effort": { "name": "VMS Papua New Guinea", "description": "Vessel Monitoring System (VMS) data for Papua New Guinea is provided by the National Fisheries Authority of Papua New Guinea. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 5-day delay, and historical data is available from 2023 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "distance_from_port_km": { "keyword": "distance_from_port_km", "enum": { "0": "0", "1": "1", "2": "2", "3": "3", "4": "4", "5": "5" } } } }, "public-vms-png-presence": { "name": "VMS Papua New Guinea Presence", "description": "Vessel Monitoring System (VMS) data for Papua New Guinea is provided by the National Fisheries Authority of Papua New Guinea. The data is collected via satellite and includes information on vessels' identity, location, speed, and course. It is published with a 5-day delay, and historical data is available from 2023 onward.
Please note that given the lower polling rates of VMS compared to AIS, estimates for apparent fishing activity may be less accurate. We are currently improving our fishing models to be better suited to VMS data.
Vessel names and tracks are visible to public users, but tracks cannot be downloaded. If you require data access beyond what is publicly available, please contact our support team at support@globalfishingwatch.org.
If you notice missing data on the map, it may be due to a VMS data outage. We are currently working on better ways to communicate these outages clearly within the platform. If you have any questions regarding gaps in data, please do not hesitate to reach out to our support email.
", "schema": { "speed": { "keyword": "speed", "enum": { "<2": "<2", "2-4": "2-4", "4-6": "4-6", "6-10": "6-10", "10-15": "10-15", "15-25": "15-25", ">25": ">25" } }, "vessel_type": { "keyword": "vessel_type", "enum": { "FISHING": "FISHING", "NON_FISHING": "NON_FISHING", "SUPPORT": "SUPPORT", "CARRIER": "CARRIER", "RESEARCH": "RESEARCH", "": "" } } } }, "public-vms-png-tracks": { "name": "Papua New Guinea VMS", "description": "Tracks dataset for VMS Papua New Guinea (Public)" }, "public-vms-png-vessel-identity": { "name": "VMS Papua New Guinea", "description": "Vessels (VMS Papua New Guinea)" }, "public-wpp-nri": { "name": "WPP NRI", "description": "The WPP-NRI (Wilayah Pengelolaan Perikanan Negara Republik Indonesia) are fisheries management areas for fishing, conservation, research and fisheries development which cover inland waters, archipelagic waters, and territorial seas within and outside the exclusive economic zone of Indonesia." } }