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: Indonesia Pelagic", "description": "Aruna Presence" }, "private-indonesia-aruna-vessel-identity": { "name": "Indonesia Aruna (Vessels)", "description": "Vessels (Indonesia Aruna)" }, "private-indonesia-fishing-effort": { "name": "VMS de Indonesia", "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: Indonesia Pelagic", "description": "AP2HI-IPNLF Presence" }, "private-indonesia-ipnlf-vessel-identity": { "name": "Indonesia AP2HI-IPNLF (Vessels)", "description": "Vessels (Indonesia AP2HI-IPNLF)" }, "private-indonesia-pelagic-fishing-effort": { "name": "Indonesia Pelagic (Pilot)", "description": "Indonesia Pelagic Fishing Effort Private Data" }, "private-indonesia-pelagic-presence": { "name": "Indonesia Pelagic (Pilot)", "description": "Pelagic Presence" }, "private-indonesia-pelagic-vessel-identity": { "name": "Indonesia Pelagic (Vessels)", "description": "Vessels (Indonesia Pelagic)" }, "private-indonesia-presence": { "name": "VMS de Indonesia", "description": "Presencia" }, "private-indonesia-rare-fishing-effort": { "name": "Rare: Indonesia Pelagic", "description": "Indonesia Rare Fishing Effort" }, "private-indonesia-rare-presence": { "name": "Rare: Indonesia Pelagic", "description": "Rare Presence" }, "private-indonesia-rare-vessel-identity": { "name": "Indonesia Rare (Embarcaciones)", "description": "Embarcaciones (Indonesia Rare)" }, "private-indonesia-zebrax-presence": { "name": "Indonesia Zebrax (Private)", "description": "Esta capa de Global Fishing Watch utiliza datos proporcionados por Rare, Aruna y AP2HI. Los datos se recopilan mediante distintos dispositivos que rastrean la ubicación y la velocidad. La información mostrada representa la presencia de la embarcación. La presencia se determina tomando todas las posiciones transmitidas por el dispositivo de la embarcación." }, "private-indonesia-zebrax-vessel-identity": { "name": "Embarcaciones", "description": "Embarcaciones" }, "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": "VMS de Panamá", "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": "shiptype", "enum": { "carrier": "carrier", "fishing": "fishing", "oil_tanker": "oil_tanker" } } } }, "private-panama-vessel-identity-fishing": { "name": "VMS Privado de Panamá (Pesqueros Privados)", "description": "Esta capa utiliza los datos del Sistema de Seguimiento de Buques (VMS) proporcionados por la Autoridad Panamana de Recursos Acuáticos (ARAP). Los datos son recibidos por el sistema VMS de Panama vía satélite y contienen identidades de buques, tipo de engranaje, ubicación, velocidad, dirección y más. Los datos del buque portador de Panama también están disponibles aquí. Cada punto en la capa de datos del buque de transporte representa una posición de los transportistas, pero no todas las posiciones se muestran. Las posiciones del buque portador se muestran una vez al día. En el futuro, esperamos poder mostrar más posiciones. Haga clic en la posición del transportista para ver el camino completo de la compañía. Global Fishing Watch analiza estos datos utilizando los mismos algoritmos que desarrollamos para los datos AIS para identificar la actividad y el comportamiento de la pesca. El algoritmo clasifica cada punto de datos de emisión de los buques como pesca aparente o sin actividad pesquera y muestra el primero en el mapa de calor de la actividad pesquera del Observatorio Mundial de Pesca. El VMS transmite datos de forma muy diferente al AIS y puede exhibir diferentes medidas de integridad, precisión y calidad. Con el tiempo, nuestros algoritmos mejorarán a través de todos nuestros formatos de datos de difusión. El algoritmo de detección de pesca de Global Fishing Watch para VMS, como para AIS, es un mejor esfuerzo para identificar algorítmicamente “aparente actividad pesquera”. Es posible que no se identifique alguna actividad pesquera, o que el mapa de calor pueda mostrar una actividad pesquera aparente donde la pesca no se está llevando a cabo. Por estas razones, Global Fishing Watch califica los términos “actividad pesquera”, “pesca” y “esfuerzo pesquero” como “aparente” en lugar de brindar certeza sobre esa actividad. En un todo o en parte, la información de Global Fishing Watch sobre “actividad pesqura aparente” debe ser considerada una estimación y debe ser confiada únicamente bajo su propio riesgo. Los algoritmos de detección de pesca Global Fishing Watch son desarrollados y probados usando datos reales de eventos de pesca recopilados por observadores, combinado con el análisis experto de los datos del movimiento de los buques AIS resultando en la clasificación manual de miles de eventos de pesca conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de actividades pesqueras y clasificación automatizada.", "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": "Esta capa utiliza los datos del Sistema de Seguimiento de Buques (VMS) proporcionados por la Autoridad Panamana de Recursos Acuáticos (ARAP). Los datos son recibidos por el sistema VMS de Panama vía satélite y contienen identidades de buques, tipo de engranaje, ubicación, velocidad, dirección y más. Los datos del buque portador de Panama también están disponibles aquí. Cada punto en la capa de datos del buque de transporte representa una posición de los transportistas, pero no todas las posiciones se muestran. Las posiciones del buque portador se muestran una vez al día. En el futuro, esperamos poder mostrar más posiciones. Haga clic en la posición del transportista para ver el camino completo de la compañía. Global Fishing Watch analiza estos datos utilizando los mismos algoritmos que desarrollamos para los datos AIS para identificar la actividad y el comportamiento de la pesca. El algoritmo clasifica cada punto de datos de emisión de los buques como pesca aparente o sin actividad pesquera y muestra el primero en el mapa de calor de la actividad pesquera del Observatorio Mundial de Pesca. El VMS transmite datos de forma muy diferente al AIS y puede exhibir diferentes medidas de integridad, precisión y calidad. Con el tiempo, nuestros algoritmos mejorarán a través de todos nuestros formatos de datos de difusión. El algoritmo de detección de pesca de Global Fishing Watch para VMS, como para AIS, es un mejor esfuerzo para identificar algorítmicamente “aparente actividad pesquera”. Es posible que no se identifique alguna actividad pesquera, o que el mapa de calor pueda mostrar una actividad pesquera aparente donde la pesca no se está llevando a cabo. Por estas razones, Global Fishing Watch califica los términos “actividad pesquera”, “pesca” y “esfuerzo pesquero” como “aparente” en lugar de brindar certeza sobre esa actividad. En un todo o en parte, la información de Global Fishing Watch sobre “actividad pesqura aparente” debe ser considerada una estimación y debe ser confiada únicamente bajo su propio riesgo. Los algoritmos de detección de pesca Global Fishing Watch son desarrollados y probados usando datos reales de eventos de pesca recopilados por observadores, combinado con el análisis experto de los datos del movimiento de los buques AIS resultando en la clasificación manual de miles de eventos de pesca conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de actividades pesqueras y clasificación automatizada.", "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": "Flota", "enum": { "industrial": "industrial", "artisanal": "Artesanal", "small-scale": "small-scale", "not defined": "not defined" } }, "origin": { "keyword": "origin", "enum": { "PER": "Peru", "Foreign": "Foreign" } } } }, "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": "Flota", "enum": { "industrial": "industrial", "artisanal": "Artesanal", "small-scale": "small-scale", "not defined": "not defined" } }, "origin": { "keyword": "origin", "enum": { "PER": "Peru", "Foreign": "Foreign" } } } }, "private-peru-vessel-identity-fishing": { "name": "VMS de Peru (Buques de pesca)", "description": "Conjunto de Datos VMS de Perú (Privado)", "schema": { "selfReportedInfo.nationalId": { "keyword": "nationalId" } } }, "private-png-fishing-effort": { "name": "VMS de Papúa Nueva Guinea", "description": "Los datos del sistema de seguimiento de embarcaciones (VMS) son proporcionados por la Autoridad Nacional de Pesca de Papúa Nueva Guinea. Los datos se recopilan utilizando el VMS nacional de Papúa Nueva Guinea proporcionado por el Sistema de Gestión e Información Pesquera (FIMS, por sus siglas en inglés). Los datos VMS incluyen los identificadores y la ubicación de las embarcaciones, y se publican con un retraso de cinco días. Global Fishing Watch infiere la velocidad y el rumbo para la ubicación de cada barco y analiza estos datos utilizando los mismos algoritmos desarrollados para el sistema de identificación automática (AIS) para identificar la actividad y los comportamientos de pesca. El algoritmo clasifica cada punto de datos de transmisión de las embarcaciones como pesca aparente o no pesca y muestra el primero en el mapa de actividad pesquera de Global Fishing Watch. VMS transmite datos de manera diferente a AIS y puede brindar diferentes medidas de integridad, precisión y calidad. Global Fishing Watch mejora continuamente sus algoritmos en todos los formatos de datos de transmisión para identificar algorítmicamente la \"actividad de pesca aparente\". Es posible que no se identifique alguna actividad pesquera o que el mapa de calor muestre actividad pesquera aparente cuando en realidad no se está pescando. Por estas razones, Global Fishing Watch califica los términos “actividad pesquera”, “pesca” o “esfuerzo pesquero” como aparentes en lugar de ciertos. Cualquier y toda la información de Global Fishing Watch sobre la \"actividad de pesca aparente\" debe considerarse una estimación y debe confiarse únicamente en la discreción del usuario. Los algoritmos de detección de pesca de Global Fishing Watch se desarrollan y prueban utilizando datos de eventos de pesca reales recopilados por observadores y se combinan con análisis expertos de datos de movimiento de embarcaciones AIS, lo que da como resultado la clasificación manual de miles de eventos de pesca conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de actividades pesqueras y mejorar las técnicas de clasificación automatizadas" }, "private-png-fishing-identity-vessels": { "name": "VMS de Papúa Nueva Guinea (Buques de pesca)", "description": "VMS de Papúa Nueva Guinea (Buques de pesca)" }, "private-png-presence": { "name": "VMS de Papúa Nueva Guinea", "description": "Los datos del sistema de seguimiento de embarcaciones (VMS) son proporcionados por la Autoridad Nacional de Pesca de Papúa Nueva Guinea. Los datos se recopilan utilizando el VMS nacional de Papúa Nueva Guinea proporcionado por el Sistema de gestión e información pesqueras (FIMS, por sus siglas en inglés). Los datos de VMS incluyen los identificadores y la ubicación de las embarcaciones, y se publican con un retraso de cinco días.\n\nLa capa de actividad muestra un mapa de calor de presencia de embarcaciones. La presencia se determina tomando dos posiciones por hora por embarcación a partir de las posiciones transmitidas por el VMS de la embarcación." }, "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 - Encounter Events of 30min. (AIS)", "description": "The dataset contains encounter events of 30min for AIS. [Fishing-Carriers, Carriers-Fishing, Support-Fishing, Fishing-Support]", "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": "VMS de Belice", "description": "Los datos del sistema de monitoreo de embarcaciones (VMS) son proporcionados por la Unidad de Pesca en Alta Mar de Belice (BHSFU). Los datos se recopilan mediante el sistema de seguimiento de embarcaciones de Belice a través de satélites y se publican con un retraso de tres días brindando información sobre la ubicación, la velocidad, el rumbo y el movimiento de las embarcaciones. Global Fishing Watch analiza estos datos utilizando los mismos algoritmos desarrollados para el sistema de identificación automática (AIS) con el fin de identificar la actividad y los comportamientos pesqueros. El algoritmo clasifica cada punto de los datos transmitidos por las embarcaciones como \"pesca aparente\" o \"no pesca\" y muestra el primero en el mapa de calor de la actividad pesquera de Global Fishing Watch. El VMS transmite los datos de manera diferente al AIS y puede ofrecer diferentes medidas de integridad, precisión y calidad. Global Fishing Watch mejora continuamente sus algoritmos en todos los formatos de datos transmitidos para identificar algorítmicamente la \"actividad pesquera aparente\". Es posible que no se identifique alguna actividad pesquera o que el mapa de calor pueda mostrar una actividad pesquera aparente cuando en realidad no se está pescando. Por estas razones, Global Fishing Watch califica los términos \"actividad pesquera\", \"pesca\" o \"esfuerzo pesquero\" como aparentes en lugar de ciertos. Toda la información de Global Fishing Watch sobre “actividad pesquera aparente” debe considerarse una estimación y el usuario debe confiar únicamente en ella a su entera discreción. Los algoritmos de presencia pesquera de Global Fishing Watch se desarrollan y prueban utilizando datos reales de eventos pesqueros recopilados por observadores y se combinan con un análisis experto de los datos de movimiento de embarcaciones AIS, lo que da como resultado la clasificación manual de miles de eventos pesqueros conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de la actividad pesquera y mejorar las técnicas de clasificación automatizada." }, "public-belize-vessel-identity-fishing": { "name": "VMS de Belice", "description": "Identidad de la embarcación (VMS Belice)" }, "public-bra-onyxsat-fishing-effort": { "name": "VMS de Brasil", "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": { "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 de Brasil (Pesqueros)", "description": "Pesqueros (VMS Brasil)", "schema": { "selfReportedInfo.targetSpecies": { "keyword": "targetSpecies" }, "targetSpecies": { "keyword": "targetSpecies" } } }, "public-brazil-opentuna-presence": { "name": "Brazil Open Tuna VMS", "description": "Esta capa de Global Fishing Watch utiliza datos proporcionados por ATLANTIC'S ALLIANCE FOR SOSTENIBLE TUNA, un grupo de empresas atuneras privadas brasileñas que decidieron ser transparentes, más información aquí. Los datos se recopilan utilizando su Sistema de Monitoreo de Embarcaciones (VMS) a través de satélites, incluida la identificación, ubicación, velocidad y rumbo de la embarcación. La información que se muestra representa la presencia del barco." }, "public-brazil-opentuna-vessel-identity-fishing": { "name": "VMS de Brasil Open Tuna (Pesqueros)", "description": "Conjunto de Datos VMS Brasil (Público)", "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": "VMS de Chile", "description": "Datos del sistema de monitoreo de embarcaciones (VMS) proporcionados por el regulador de pesca y acuicultura del gobierno de Chile (SERNAPESCA). Es posible filtrar los datos VMS de Chile para pesqueros de pequeña escala (<18 metros) y pesqueros industriales (>18 metros). Tenga en cuenta que algunas embarcaciones tienen <18 metros, pero se consideran industriales porque se registraron en la captura de cuotas industriales. SERNAPESCA también está utilizando nuestro mapa para visualizar y rastrear las posiciones de los buques de su flota, incluidos los buques involucrados en la acuicultura. Los datos se recopilan utilizando el VMS de Chile a través de satélites y receptores terrestres y contienen identidades de los buques, tipo de arte, ubicación, velocidad, dirección y más. Global Fishing Watch analiza estos datos utilizando los mismos algoritmos que desarrollamos para los datos del sistema de identificación automática (AIS) para identificar la actividad y los comportamientos pesqueros. El algoritmo clasifica cada punto de datos transmitido por las embarcaciones como \"aparentemente pescando\" o \"no pescando\" y muestra el primero en el mapa de Global Fishing Watch. El VMS transmite datos de manera bastante diferente al AIS y puede brindar diferentes medidas de integridad, precisión y calidad. Con el tiempo, nuestros algoritmos mejorarán en todos nuestros formatos de datos de transmisión. El algoritmo de presencia de pesca de Global Fishing Watch para VMS, al igual que para AIS, es un esfuerzo máximo para identificar algorítmicamente la \"actividad pesquera aparente\". Es posible que no se identifique alguna actividad pesquera o que el mapa de calor pueda mostrar una actividad pesquera aparente cuando en realidad no se está pescando. Por este motivo, Global Fishing Watch califica los términos \"actividad pesquera\", \"pesca\" y \"esfuerzo pesquero\" como \"aparentes\" en lugar de ciertos. Toda la información de Global Fishing Watch sobre la \"actividad pesquera aparente\" debe considerarse una estimación y debe confiar en ella únicamente bajo su propio riesgo. Los algoritmos de presencia de pesca de Global Fishing Watch se desarrollan y prueban utilizando datos reales de eventos pesqueros recopilados por observadores, combinados con un análisis experto de los datos de movimiento de embarcaciones AIS, lo que da como resultado la clasificación manual de miles de eventos pesqueros conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de su programa de investigación para compartir datos de clasificación de la actividad pesquera y clasificación automatizada.", "schema": { "fleet": { "keyword": "Flota", "enum": { "chile_vms_small_fisheries": "Artesanal", "chile_vms_industry": "Industrial" } } } }, "public-chile-presence": { "name": "VMS de Chile", "description": "Datos del sistema de monitoreo de embarcaciones (VMS) proporcionados por el regulador de pesca y acuicultura del gobierno de Chile (SERNAPESCA). Es posible filtrar los datos VMS de Chile para pesqueros de pequeña escala (<18 metros) y pesqueros industriales (>18 metros). Tenga en cuenta que algunas embarcaciones tienen <18 metros, pero se consideran industriales porque se registraron en la captura de cuotas industriales. SERNAPESCA también está utilizando nuestro mapa para visualizar y rastrear las posiciones de los buques de su flota, incluidos los buques involucrados en la acuicultura. Los datos se recopilan utilizando el VMS de Chile a través de satélites y receptores terrestres y contienen identidades de los buques, tipo de arte, ubicación, velocidad, dirección y más. Global Fishing Watch analiza estos datos utilizando los mismos algoritmos que desarrollamos para los datos del sistema de identificación automática (AIS) con el fin de identificar la actividad y los comportamientos pesqueros. El algoritmo clasifica cada punto de datos transmitidos por los buques como \"aparentemente pescando\" o \"no pescando\" y muestra el primero en el mapa de Global Fishing Watch. El VMS transmite datos de manera bastante diferente al AIS y puede brindar diferentes medidas de integridad, precisión y calidad. Con el tiempo, nuestros algoritmos mejorarán en todos nuestros formatos de datos de transmisión. El algoritmo de presencia de pesca de Global Fishing Watch para VMS, al igual que para AIS, es un esfuerzo máximo para identificar algorítmicamente la \"actividad pesquera aparente\". Es posible que no se identifique alguna actividad pesquera o que el mapa de calor pueda mostrar una actividad pesquera aparente cuando en realidad no se está pescando. Por estos motivos, Global Fishing Watch califica los términos \"actividad pesquera\", \"pesca\" y \"esfuerzo pesquero\" como \"aparentes\" en lugar de ciertos. Toda la información de Global Fishing Watch sobre la \"actividad pesquera aparente\" debe considerarse una estimación y debe confiar en ella únicamente bajo su propio riesgo. Los algoritmos de presencia de pesca de Global Fishing Watch se desarrollan y prueban utilizando datos reales de eventos pesqueros recopilados por observadores, combinados con un análisis experto de los datos de movimiento de embarcaciones AIS, lo que da como resultado la clasificación manual de miles de eventos pesqueros conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de su programa de investigación para compartir datos de clasificación de la actividad pesquera y la clasificación automatizada.", "schema": { "fleet": { "keyword": "Flota", "enum": { "chile_vms_small_fisheries": "Artesanal", "chile_vms_industry": "Industrial", "chile_vms_aquaculture": "Acuicultura", "chile_vms_transport": "Transporte" } } } }, "public-chile-vessel-identity-fishing": { "name": "Chile VMS (Fishing Vessels)", "description": "Conjunto de datos para VMS Chile (Público)" }, "public-chile-vessel-identity-non-fishing": { "name": "VMS de Chile (No Pesqueros)", "description": "Conjunto de datos para VMS Chile (Público)" }, "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": "Arrecifes de coral", "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\nOffshore fixed infrastructure is a global dataset that uses AI and machine learning to detect and classify structures throughout the world’s oceans.
Classification labels (oil, wind, and unknown) are provided, as well as confidence levels (high, medium, or low) reflecting our certainty in the assigned label. Detections can be filtered and colored on the map using both label and confidence level.The data is updated on a monthly basis, and new classified detections are added at the beginning of every month. Viewing change using the timebar is simple, and allows anyone to recognize the rapid industrialization of the world’s oceans. For example, you can easily observe the expansion of wind farms in the North and East China Seas, or changes in oil infrastructure in the Gulf of Mexico or Persian Gulf.
By overlaying the existing map layers, you can explore how vessels interact with oil and wind structures, visualise the density of synthetic aperture radar (SAR) and Visible Infrared Imaging Radiometer Suite (VIIRS) vessel detections around infrastructure, or determine which marine protected areas (MPAs) contain wind, oil, or other infrastructure types. These are only examples of the types of questions we can now ask. Offshore fixed infrastructure is a first of its kind dataset that not only brings to light the extensive industrialization of our oceans, but enables users across industries to use this information in research, monitoring and management.
We use SAR imagery from the Copernicus Sentinel-1 mission of the European Space Agency (ESA) [1]. The images are sourced from two satellites (S1A and S1B up until December 2021 when S1B stopped operating, and S1A only from 2022 onward) that orbit 180 degrees out of phase with each other in a polar, sun-synchronous orbit. Each satellite has a repeat-cycle of 12 days, so that together they provide a global mapping of coastal waters around the world approximately every six days for the period that both were operating. The number of images per location, however, varies greatly depending on mission priorities, latitude, and degree of overlap between adjacent satellite passes. Spatial coverage also varies over time [2]. Our data consist of dual-polarization images (VH and VV) from the Interferometric Wide (IW) swath mode, with a resolution of about 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
Detecting infrastructure with SAR is based on the widely used Constant False Alarm Rate (CFAR) algorithm, an anomaly detection method conceived for detecting ships in synthetic aperture radar images, that has been modified to remove non-stationary objects. This algorithm is designed to search for pixel values that are unusually bright (the targets) compared to those in the surrounding area (the sea clutter). This method sets a threshold based on the pixel values of the local background (within a window), scanning the whole image pixel-by-pixel. Pixel values above the threshold constitute an anomaly and are likely to be samples from a target.
To classify every detected offshore infrastructure, we used deep learning and designed a ConvNet based on the ConvNeXt architecture. A novel aspect of our deep learning classification approach is the combination of SAR imagery from Sentinel-1 with optical imagery from Sentinel-2. From six-month composites of dual-band SAR (VH and VV) and four-band optical (RGB and NIR) images, we extracted small tiles for every detected fixed infrastructure, with the respective objects at the center of the tile. A single model output includes the probabilities for the specified classes: wind, oil, unknown, lake maracaibo, and noise.
GFW post-processed the classified SAR detections to reduce noise (false positives), remove vessels, exclude areas with sea ice at high latitudes, and incorporate expert feedback. We used a clustering approach to identify detections across time (within a 50 m radius) that were likely the same structure but their coordinates differed slightly, and assigned them the greatest average predicted label of the cluster. We also filled in gaps for fixed structures that were missing in one timestep but detected in the previous and following timesteps, and dropped detections appearing in a single timestep. Finally, the dataset underwent extensive manual review and editing by researchers and industry experts in order to refine the final product, and provide the most accurate dataset possible.
Each detection has a unique individual identifier (detection_id). A six-month image composite is used in the classification, therefore the detection_date represents the middle of the six month period. This helps to remove non-stationary objects (i.e. vessels), and avoid confusion in the model if a structure is being built, or there isn’t adequate imagery available. structure_id allows you to track a structure through time. There are therefore many detection_id (one for each month the structure is detected) for each structure_id. Labels of wind and oil represent any wind or oil related structure respectively. Unknown represents a structure that is not oil or wind related, such as bridges or navigational buoys.
Label confidence levels of ‘High’. ‘Medium’ and ‘Low’ are assigned to each structure, and are conditional on where the detections fell in relation to the boundaries of manually developed wind and oil polygons, and whether the label has changed from the previous month. The label_confidence field can be used to filter analysis.
Two repos are used in the automation process, both of which are private, and should not be shared publicly.
Detection and classification: https://github.com/GlobalFishingWatch/sentinel-1-ee/tree/master
Clustering and reclassification: https://github.com/GlobalFishingWatch/infrastructure-post-processing
All code developed for the paper, Paolo, F.S., Kroodsma, D., Raynor, J. et al. Satellite mapping reveals extensive industrial activity at sea. Nature 625, 85–91 (2024). https://doi.org/10.1038/s41586-023-06825-8, including SAR detection, deep learning models, and analyses is open source and freely available at https://github.com/GlobalFishingWatch/paper-industrial-activity.
Copernicus Sentinel data 2017-current
Lujala, Päivi; Jan Ketil Rød & Nadia Thieme, 2007. 'Fighting over Oil: Introducing A New Dataset', 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, T.J., Justman, D., Miller III, R., Rose, K., and 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
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.
Infrastructure development methods should reference the paper:
Paolo, F.S., Kroodsma, D., Raynor, J. et al. Satellite mapping reveals extensive industrial activity at sea. Nature 625, 85–91 (2024). https://doi.org/10.1038/s41586-023-06825-8
All code developed for the paper, including SAR detection, deep learning models, and analyses is open source and freely available at https://github.com/GlobalFishingWatch/paper-industrial-activity. All the data generated and used by these scripts can reference the following data repos:
Analysis and Figures: https://doi.org/10.6084/m9.figshare.24309475
Training and Evaluation: 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": "high", "medium": "medium", "low": "low" } }, "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": "Trayectorias", "description": "The dataset contains the tracks from all vessels (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": "Batimetría", "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": "Tipo de embarcaciones", "enum": { "CARRIER-FISHING": "Embarcación de transporte <> Pesca", "SUPPORT-FISHING": "Soporte <> Pesca", "FISHING-CARRIER": "Pesca <> Embarcación de transporte", "FISHING-BUNKER": "Pesca <> Aprovisionamiento", "FISHING-FISHING": "Pesca <> Pesca", "CARRIER-BUNKER": "Embarcación de transporte <> Aprovisionamiento", "FISHING-SUPPORT": "Fishing <> Soporte" } } } }, "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 utiliza datos sobre la identidad, el tipo, la ubicación, la velocidad, y otros datos que son emitidos a través del Sistema de Identificación Automática (AIS) y recolectados a través de satélites y receptores terrestres. El AIS fue desarrollado para la prevención de colisión/esquivación. Global Fishing Watch analiza los datos AIS recopilados de los buques que nuestra investigación ha identificado como conocidos o posibles buques pesqueros comerciales, y aplica un algoritmo de detección de pesca para determinar una “aparente actividad pesquera” basado en cambios en la velocidad y dirección de los buques. El algoritmo clasifica cada punto de datos para estos buques como pesca aparente o sin actividad pesquera y muestra el primero en el mapa de calor de la actividad pesquera de Global Fishing Watch. Los datos AIS pueden variar en integridad, precisión y calidad. Además, la recolección de datos por parte de receptores satelitales o terrestres, puede introducir errores a través de datos faltantes o inexactos. El algoritmo de detección de pesca de Global Fishing Watch representa un esfuerzo matemático para identificar una “aparente actividad pesquera”. Como resultado, es posible que algunas actividades pesqueras no sean identificadas como tales por Global Fishing Watch. Por el contrario, Global Fishing Watch puede mostrar una actividad pesquera aparente en la que la pesca no se está llevando a cabo. Por estas razones, Global Fishing Watch califica “actividad pesquera”,“pesca” o “esfuerzo pesquero” como “aparente”, en lugar de brindar certeza sobre la actividad. En todo o en parte, la información de Global Fishing Watch sobre “aparente actividad de pesca” debe ser considerada una estimación y debe ser confiada únicamente bajo su propio riesgo. Global Fishing Watch está tomando medidas para asegurar que la identificación del comportamiento de la actividad pesquera sea lo más exacta posible. Los algoritmos de detección de pesca de Global Fishing Watch son desarrollados y probados usando datos reales de eventos de pesca recopilados por observadores, combinado con el análisis experto de los datos del movimiento de buques que dan lugar a la clasificación manual de miles de eventos de pesca conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de actividades pesqueras y técnicas de clasificación automatizadas.", "schema": { "distance_from_port_km": { "keyword": "Búfer del puerto", "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": "A la deriva (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": "Tipo de embarcaciones", "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": "Concentración de nitrato (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": "Tipo de embarcaciones", "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 utiliza datos sobre la identidad, el tipo, la ubicación, la velocidad, y otros datos que son emitidos a través del Sistema de Identificación Automática (AIS) y recolectados a través de satélites y receptores terrestres. El AIS fue desarrollado para la prevención de colisión/esquivación. La capa de actividad muestra un mapa de calor de la presencia de buques. La presencia se determina tomando una posición al hora por buque a partir de las posiciones transmitidas por el AIS de la buque.", "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": { "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": "Salinidad", "description": "
Satellite synthetic aperture radar (SAR) is a spaceborne radar imaging system that can detect at-sea vessels and structures in any weather conditions. Microwave pulses are transmitted by a satellite-based antenna towards the Earth surface. The microwave energy scattered back to the spacecraft is then measured and integrated to form a “backscatter” image. The SAR image contains rich information about the different objects on the water, such as their size, orientation and texture. SAR imaging systems overcome most weather conditions and illumination levels, including clouds or rain due to the cloud penetrating property of microwaves, and daylight or darkness due to radar being an “active” sensor (it shoots and records back its own energy). SAR gives an advantage over some other “passive” satellite sensors, such as electro-optical imagery, consisting of a satellite-based camera recording the sunlight/infrared radiation reflected from/emitted by objects on the ground. This latter method can be confounded by cloud cover, haze, weather events and seasonal darkness at high latitudes.
\nWe use SAR imagery from the Copernicus Sentinel-1 mission of the European Space Agency (ESA) [1]. The images are sourced from two satellites (S1A and S1B up until December 2021 when S1B stopped operating, and S1A only from 2022 onward) that orbit 180 degrees out of phase with each other in a polar, sun-synchronous orbit. Each satellite has a repeat-cycle of 12 days, so that together they provide a global mapping of coastal waters around the world approximately every six days for the period that both were operating. The number of images per location, however, varies greatly depending on mission priorities, latitude, and degree of overlap between adjacent satellite passes. Spatial coverage also varies over time [2]. Our data consist of dual-polarization images (VH and VV) from the Interferometric Wide (IW) swath mode, with a resolution of about 20 m.
\n[1]\n \n https://sedas.satapps.org/wp-content/uploads/2015/07/Sentinel-1_User_Handbook.pdf\n \n
\n[2]\n \n https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1/observation-scenario\n \n
\nDetection footprints are areas within each satellite scan (or scene) that our system uses to perform detections. These filters help to keep relevant detections and exclude data that may be inaccurate. Detection footprints are smaller than the total scene as they exclude any land areas and islands, and exclude a 500 meter buffer from the boundaries of the scene and a 1 kilometer buffer from shorelines.
\nGFW has post-processed the SAR detections to reduce noise (false positives), remove offshore infrastructure from this layer focused on vessels, and exclude areas with sea ice at high latitudes.
\nDetecting vessels with SAR is based on an known as Constant False Alarm Rate (CFAR), a threshold algorithm used for anomaly detection in radar imagery. This algorithm is designed to search for pixel values that are unusually bright (the targets) compared to those in the surrounding area (the sea clutter). This method sets a threshold based on the pixel values of the local background (within a window), scanning the whole image pixel-by-pixel. Pixel values above the threshold constitute an anomaly and are likely to be samples from a target, and therefore are included as a detection.
\nTo estimate the length of every detected object and also to identify when our CFAR algorithm made false detections, we designed a deep convolutional neural network (ConvNet) based on the modern ResNet (Residual Networks) architecture. This single-input/multi-output ConvNet takes dual-band SAR image tiles of 80 by 80 pixels as input, and outputs the probability of object presence (known as a “binary classification task”) and the estimated length of the object (known as a “regression task”).
\nTo identify whether a detected vessel was a fishing or non-fishing vessel we use a machine learning model. For this classification task we used a ConvNeXt architecture modified to process the following two inputs: the estimated length of the vessel from SAR (a scalar quantity) and a stack of environmental rasters centered at the vessel’s location (a multi-channel image). This multi-input-mixed-data/single-output model passes the raster stack (11 channels) through a series of convolutional layers and combines the resulting feature maps with the vessel length value to perform a binary classification: fishing or non-fishing.
\nThe environmental layers used to differentiate between fishing and non-fishing include:
\nAIS 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 SAR detections therefore provide the missing information about vessel traffic in the ocean.
\nMatching SAR detections to vessels’ GPS coordinates (from the automatic identification system (AIS) is challenging because the timestamp of the SAR images and AIS records do not coincide, and a single AIS message 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 SAR detection, we followed 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 developed from one year of global AIS data from the Global Fishing Watch pipeline which uses Spire Global and Orbcomm sources of satellite data, including roughly 10 billion vessel positions, and 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 SAR detection based on the vessel class, speed and time interval.
\nAutomatic identification system (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 SAR detections therefore provide the missing information about vessel traffic in the ocean.
\nAll code developed in this study for SAR detection, deep learning models, and analyses is open source and freely available at\n \n https://github.com/GlobalFishingWatch/paper-industrial-activity\n .\n
\nAll vessel data are freely available through the Global Fishing Watch data portal at\n \n https://globalfishingwatch.org\n . All data to reproduce our supporting scientific paper can be downloaded from\n \n https://doi.org/10.6084/m9.figshare.24309475\n \n (statistical analyses and figures) and\n \n https://doi.org/10.6084/m9.figshare.24309469\n \n (model training and evaluation).\n
\nNon-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": { "matched": { "keyword": "Coincidencia con AIS vessels", "enum": { "true": "Coincidencia con AIS", "false": "Sin coincidencia con AIS" } }, "neural_vessel_type": { "keyword": "neural_vessel_type", "enum": { "Likely non-fishing": "Likely non-fishing", "Likely Fishing": "Likely Fishing", "Unknown": "Desconocido" } }, "shiptype": { "keyword": "shiptype", "enum": { "carrier": "carrier", "seismic_vessel": "seismic_vessel", "passenger": "passenger", "other": "other", "support": "support", "bunker": "bunker", "gear": "Arte", "cargo": "cargo", "fishing": "fishing", "discrepancy": "discrepancy" } } } }, "public-global-sentinel2-footprints": { "name": "Zonas de detección", "description": "Zonas de detección" }, "public-global-sentinel2-presence": { "name": "Detecciones de imágenes (Ópticas)", "description": "
Esta capa muestra embarcaciones detectadas mediante imágenes satelitales ópticas recopiladas por los satélites Sentinel-2 de la Agencia Espacial Europea. Las imágenes ópticas son similares a fotografías aéreas de alta calidad tomadas desde el espacio, utilizando la luz solar reflejada en longitudes de onda visibles y del infrarrojo cercano. Este tipo de imágenes ofrece un nivel de detalle de alta resolución que permite identificar embarcaciones pequeñas, observar patrones en la estela de la embarcación, así como comprender mejor la actividad cercana a la costa.
\nGlobal Fishing Watch utiliza un modelo de aprendizaje automático que procesa cada imagen para identificar embarcaciones y estimar su longitud, orientación y velocidad a partir de las características de su estela. Luego, las detecciones se filtran mediante una clasificación secundaria que elimina elementos que no corresponden a embarcaciones, como nubes, rocas o icebergs. Cada detección está vinculada a una imagen recortada (o miniatura) para que los usuarios puedan inspeccionar visualmente lo que el modelo ha identificado.
\nDado que los satélites ópticos dependen de la luz solar y del cielo despejado, las detecciones solo son posibles durante el día y cuando el área no está cubierta por nubes o neblina. A pesar de estas limitaciones, las detecciones con imágenes ópticas son especialmente útiles para identificar embarcaciones pequeñas y no rastreadas que podrían no aparecer en otros sistemas de seguimiento.
\nMonitorear la presencia de embarcaciones (tanto pesqueras como no pesqueras) en zonas de interés como Áreas Marinas Protegidas (AMP), Zonas Económicas Exclusivas (ZEE), zonas de exclusión costera (IEZ, por sus siglas en inglés) y organizaciones regionales de ordenación pesquera (OROP). En algunos casos, actividades como la pesca de arrastre de fondo pueden ser identificadas por la alteración de los sedimentos del lecho marino.
\nEvaluar la presencia de embarcaciones que no aparecen en sistemas de seguimiento cooperativo —incluidos el sistema de identificación automática (AIS) y el sistema de monitoreo de embarcaciones (VMS)— cerca de ecosistemas marinos vulnerables y hábitats esenciales para peces.
\nApoyar el análisis de la pesca en pequeña escala. Aunque la resolución de 10 metros aún es demasiado baja para cartografiar completamente esta actividad, las detecciones del Sentinel-2 se han integrado en varios análisis regionales y han demostrado su potencial como un valioso complemento a los limitados datos disponibles sobre el seguimiento de embarcaciones.
\nDetecciones de embarcaciones mediante imágenes ópticas requieren luz diurna y cielos despejados.\n
\nA diferencia del radar, los satélites ópticos no pueden atravesar nubes, niebla o bruma. Las detecciones solo son posibles durante las horas de luz solar y cuando la visibilidad no está obstruida.\n
\nLa cobertura geográfica no es uniforme.\n
\nLa cobertura del Sentinel-2 se limita principalmente a aguas costeras. Revisa la mayoría de las zonas cada cinco días, pero la disponibilidad de las imágenes depende de las condiciones meteorológicas. Las regiones con nubosidad o bruma frecuentes son visitadas con menor frecuencias que aquellas con mejor clima.\n
\nLas detecciones pueden incluir falsos positivos\n
\nA pesar del posprocesamiento, el modelo puede generar detecciones erróneas ocasionales, como boyas, residuos, infraestructura fija o artefactos de imagen. Estos falsos positivos se reducen mediante un clasificador secundario, pero no serán eliminados por completo\n
\nIncertidumbre sobre algunas características de las embarcaciones\n
\nLas embarcaciones más pequeñas o de movimiento lento pueden no dejar una estela visible, lo que dificulta estimar su velocidad o rumbo. Por lo tanto, estos valores podrían ser imprecisos en el caso de las embarcaciones pequeñas.\n
\nNo todas las detecciones sin coincidencia con AIS son a embarcaciones no rastreadas\n
\nLas detecciones incluyen tanto embarcaciones con AIS como sin él. Se intenta cotejar las detecciones con trayectorias AIS, pero esto no siempre es posible debido a grandes intervalos entre posiciones AIS o a la alta densidad de embarcaciones detectadas.\n
\nEsta capa se basa en imágenes de los satélites Sentinel-2, operados por la Agencia Espacial Europea (ESA). Estos satélites capturan imágenes del océano con resolución media (10 metros por píxel), utilizando luz visible y del infrarrojo cercano, entre otras bandas. En conjunto, los satélites cubren la mayoría de las aguas costeras y ciertas zonas del mar abierto aproximadamente cada cinco días. Las imágenes están disponibles de forma gratuita a través de la ESA.
\nUtilizamos imágenes preprocesadas de Sentinel-2 que han sido corregidas debido a distorsiones geométricas y alineadas con la superficie terrestre. Estas imágenes se dividen en recuadros manejables y hemos elegido los recuadros que cubren únicamente zonas oceánicas (se excluyen áreas terrestres). Utilizamos cuatro bandas espectrales: rojo, verde, azul (RGB) y el infrarrojo cercano (NIR), todas con una resolución de 10 metros. Estas bandas nos proporcionan el detalle y contraste necesarios para detectar y clasificar embarcaciones.
\nNuestro modelo de aprendizaje automático escanea cada recuadro con el objetivo de detectar embarcaciones. Ha sido entrenado para buscar características como la forma, el brillo y la estela de una embarcación. Cuando encuentra un candidato probable, el modelo estima una puntuación de presencia del buque junto con estimaciones de su ubicación, tamaño, orientación y velocidad.
\nEl modelo fue entrenado utilizando más de 11.000 ejemplos de embarcaciones revisados manualmente en miles de escenas Sentinel-2. Este entrenamiento incluyó muchas embarcaciones pequeñas y escenas de todo el mundo, lo que le permite desempeñarse bien en distintos entornos y con diversos tipos de buques.
\nCada detección incluye una pequeña “muestra visual” con la embarcación detectada en el centro. Estas miniaturas están disponibles en dos formatos: una versión en color basada en las bandas RGB, y una versión en escala de grises basada en la banda del infrarrojo cercano. Cada muestra visual cubre un área de 1 km². Estas miniaturas son útiles para confirmar visualmente una detección o comprender su contexto. Sin embargo, en el caso de embarcaciones muy pequeñas (menores a 15 metros), es posible que sea difícil verlas con claridad.
\nNo todo lo que parece una embarcación en una imagen satelital realmente lo es. Para ayudar a eliminar detecciones erróneas (como boyas, plataformas marinas, hielo marino o nubes), cada detección pasa por un clasificador secundario. Este clasificador —también basado en aprendizaje automático— utiliza tanto la miniatura de la imagen como información adicional sobre la detección (como, por ejemplo, la distancia de la costa, profundidad local y densidad de embarcaciones cercanas) para evaluar si el objeto probablemente es una embarcación.
\nAdemás, marcamos las detecciones que se encuentren cerca de infraestructuras fijas conocidas o en zonas con presencia significativa de hielo marino o icebergs. Si una detección se clasifica como “probablemente no embarcación” o se marca como posible infraestructura o hielo, se elimina de la capa del mapa, de modo que solo incluye detecciones con alta probabilidad. Asimismo, recortamos los límites de las escenas satelitales mostradas en el mapa para excluir las áreas cubiertas por la máscara de regiones heladas.
\nSin embargo, todos los falsos positivos se proporcionan con etiquetas a través del portal de descarga de datos, para los usuarios que necesiten conjuntos de datos más completos.
\nLos datos del sistema AIS pueden revelar la identidad de una embarcación, sus propietarios, operadores y su actividad pesquera. Sin embargo, no todas las embarcaciones están obligadas a usar dispositivos AIS, ya que las regulaciones varían según el país, el tamaño del buque y su actividad. Además, embarcaciones involucradas en actividades ilícitas pueden apagar sus transpondedores AIS o manipular las ubicaciones que transmiten.
\nTambién existen grandes “zonas ciegas” en aguas costeras, debido a países que restringen el acceso a los datos AIS captados por receptores terrestres (en lugar de satelitales), o a una mala recepción provocada por alta densidad de embarcaciones o equipos de baja calidad. Por este motivo, las detecciones no cotejadas con AIS ofrecen la información faltante del tráfico marítimo.
\nCotejar las detecciones con coordenadas GPS del AIS es un desafío, ya que las marcas de tiempo de las imágenes y de los registros AIS no coinciden, y una sola identidad AIS puede corresponder a múltiples embarcaciones visibles en una imagen, o viceversa. Para determinar la probabilidad de que una embarcación con señal AIS coincida con una detección específica, hemos desarrollado un enfoque basado en rásters de probabilidad que indica dónde es probable que se encuentre una embarcación minutos antes y después de una posición AIS registrada.
\nEstos rásters fueron producidos a partir de un año de datos globales AIS en el flujo de datos de Global Fishing Watch, que obtiene datos satelitales de Spire Global y Orbcomm. Los rásters de probabilidad se basan en aproximadamente 10.000 millones de posiciones de embarcaciones y se calculan para seis clases de buques, considerando seis velocidades distintas y 36 intervalos de tiempo. Esto permite estimar la posición probable de una embarcación que podría coincidir con una detección, en función de su clase, velocidad e intervalo temporal.
\nAdemás del cotejamiento espaciotemporal, también se toma en cuenta la similitud entre la eslora inferida por el modelo y la eslora reportada en el AIS, con el fin de evitar coincidencias (probablemente erróneas) con grandes diferencias de tamaño, como asociar el AIS de un remolcador con la detección de un buque grande que le sigue.
\nPara ayudar a los usuarios a entender dónde eran posibles las detecciones, mostramos las “huellas de detección” en el mapa. Estos polígonos corresponden a las porciones de las imágenes satelitales que cubren zonas oceánicas y que se utilizan para detección. Por lo tanto, si encuentra una huella sin detecciones, significa que no se detectaron embarcaciones en esa área. Si no hay huella, no se procesó ninguna imagen para ese lugar y momento.
\nNuestro sistema de detección y cotejamiento funciona de forma automatizada cada día. Verifica si hay nuevas imágenes Sentinel-2 publicadas en Google Cloud y procesa las que cumplan con nuestros criterios de calidad. Las nuevas detecciones suelen estar disponibles entre 1 y 2 días después de que el satélite captura la imagen. El flujo automático también vuelve a revisar cualquier imagen publicadas con retraso, para asegurar que cualquier brecha en los datos sea completada.
\nTodos los datos de embarcaciones están disponibles gratuitamente a través del portal de datos de Global Fishing Watch https://globalfishingwatch.org/data-download.
\nUso no comercial únicamente. El Sitio y los Servicios se proporcionan exclusivamente para uso no comercial de acuerdo con la licencia CC BY-NC 4.0. Si desea utilizar el Sitio o los Servicios con fines comerciales, póngase en contacto con nosotros.
", "schema": { "length": { "keyword": "Longitud de la embarcación", "enum": { "<20": "<20", "20-60": "20-60", "60-100": "60-100", ">100": ">100" } }, "matched": { "keyword": "Coincidencia con AIS", "enum": { "true": "Coincidencia con AIS", "false": "Sin coincidencia con AIS" } }, "shiptype": { "keyword": "Tipos de Embarcaciones", "enum": { "carrier": "Embarcación de transporte", "seismic_vessel": "Buque sismológico", "passenger": "Pasajeros", "other": "Otro", "support": "Soporte", "bunker": "Aprovisionamiento", "gear": "Arte de pesca", "cargo": "Mercancía", "fishing": "Pesca", "discrepancy": "Discrepancia" } } } }, "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": "AMP (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": "El término Áreas Marinas Protegidas incluye, por ejemplo, reservas marinas, áreas marinas totalmente protegidas, zonas sin tomar santuarios marinos, santuarios oceánicos, parques marinos y áreas marinas administradas localmente. Muchos de ellos tienen diferentes niveles de protección y el abanico de actividades permitidas o prohibidas dentro de sus límites también varía considerablemente. La capa de áreas sin actividad pesquera se creó utilizando los datos disponibles en el Planeta Marino Protegido WDPA usando el filtro NO_TAKE = 'Todos'. Fuente: Base de datos mundial sobre áreas protegidas (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": "VMS de Noruega", "description": "Los datos del sistema de monitoreo de embarcaciones (VMS) son proporcionados por la Dirección de Pesca de Noruega. Los datos se recopilan utilizando el sistema de seguimiento de embarcaciones de Noruega a través de satélites y se publican con un retraso de tres días que contienen información sobre la ubicación, velocidad, rumbo y movimiento de las embarcaciones. Global Fishing Watch analiza estos datos utilizando los mismos algoritmos desarrollados para el sistema de identificación automática (AIS) para identificar la actividad y los comportamientos de pesca. El algoritmo clasifica cada punto de datos de transmisión de los barcos como pesca aparente o no, y muestra el primero en el mapa de actividad pesquera de Global Fishing Watch. El VMS transmite datos de manera diferente al AIS y puede brindar diferentes medidas de integridad, precisión y calidad. Global Fishing Watch mejora continuamente sus algoritmos en todos los formatos de datos de transmisión para identificar algorítmicamente la \"actividad de pesca aparente\". Es posible que no se identifique alguna actividad pesquera o que el mapa de calor muestre actividad pesquera aparente cuando en realidad no se está pescando. Por estas razones, Global Fishing Watch califica los términos “actividad pesquera”, “pesca” o “esfuerzo pesquero” como aparentes en lugar de confirmados. Toda la información de Global Fishing Watch sobre la \"actividad de pesca aparente\" debe considerarse una estimación y debe confiarse únicamente en la discreción del usuario. Los algoritmos de detección de pesca de Global Fishing Watch se desarrollan y prueban utilizando datos de eventos de pesca reales recopilados por observadores y se combinan con análisis expertos de datos de movimiento de embarcaciones AIS, lo que da como resultado la clasificación manual de miles de eventos de pesca conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de actividades pesqueras y mejorar las técnicas de clasificación automatizadas" }, "public-norway-presence": { "name": "VMS de Noruega", "description": "Esta capa utiliza los datos del sistema de monitoreo de embarcaciones (VMS) proporcionados por la Dirección de Pesca de Noruega. Los datos son recibidos por el sistema VMS de Noruega vía satélite y se publican con un retraso de tres días conteniendo información sobre la ubicación, velocidad, rumbo y movimiento de las embarcaciones. La capa de actividad muestra un mapa de calor de la presencia de embarcaciones. Cada punto en la capa de presencia representa una posición de las embarcaciones, sin embargo no son mostradas todas las posiciones. Las posiciones de las embarcaciones se muestran una vez por hora. Haga clic en la posición de un barco para ver la ruta completa de la embarcación.", "schema": { "vessel_type": { "keyword": "vessel_type", "enum": { "fishing": "fishing", "research": "research", "kelp trawler": "kelp trawler", "other": "other" } } } }, "public-norway-vessel-identity-fishing": { "name": "Norway VMS (Fishing Vessels)", "description": "Dataset for VMS Norway (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": "Norway VMS (Non Fishing Vessels)", "description": "Dataset for VMS Norway (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 de Panamá", "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 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,” 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 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." }, "public-panama-vessel-identity-fishing": { "name": "Panama VMS (Public Fishing Vessels)", "description": "Dataset for VMS Panama (Public)", "schema": { "selfReportedInfo.imo": { "keyword": "imo" }, "selfReportedInfo.nationalRegisterNumber": { "keyword": "nationalRegisterNumber" }, "selfReportedInfo.ssvid": { "keyword": "ssvid" } } }, "public-panama-vessel-identity-non-fishing": { "name": "Panama VMS (Public Non fishing vessels)", "description": "Dataset for VMS Panama - Carriers (Public)", "schema": { "selfReportedInfo.imo": { "keyword": "imo" }, "selfReportedInfo.nationalRegisterNumber": { "keyword": "nationalRegisterNumber" }, "selfReportedInfo.ssvid": { "keyword": "ssvid" } } }, "public-peru-fishing-effort": { "name": "VMS de Perú", "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": "Flota", "enum": { "industrial": "industrial", "artisanal": "Artesanal", "small-scale": "small-scale", "not defined": "not defined" } }, "origin": { "keyword": "origin", "enum": { "PER": "Peru", "Foreign": "Foreign" } } } }, "public-peru-presence": { "name": "VMS de Perú", "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": "Flota", "enum": { "industrial": "industrial", "artisanal": "Artesanal", "small-scale": "small-scale", "not defined": "not defined" } }, "origin": { "keyword": "origin", "enum": { "PER": "Peru", "Foreign": "Foreign" } } } }, "public-peru-vessel-identity-fishing": { "name": "VMS de Perú (Embarcaciones de pesca)", "description": "Conjunto de Datos VMS Perú (Público)", "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 de Papúa Nueva Guinea", "description": "Los datos del sistema de seguimiento de embarcaciones (VMS) son proporcionados por la Autoridad Nacional de Pesca de Papúa Nueva Guinea. Los datos se recopilan utilizando el VMS nacional de Papúa Nueva Guinea proporcionado por el Sistema de Gestión e Información Pesquera (FIMS, por sus siglas en inglés). Los datos VMS incluyen los identificadores y la ubicación de las embarcaciones, y se publican con un retraso de cinco días. Global Fishing Watch infiere la velocidad y el rumbo para la ubicación de cada barco y analiza estos datos utilizando los mismos algoritmos desarrollados para el sistema de identificación automática (AIS) para identificar la actividad y los comportamientos de pesca. El algoritmo clasifica cada punto de datos de transmisión de las embarcaciones como pesca aparente o no pesca y muestra el primero en el mapa de actividad pesquera de Global Fishing Watch. VMS transmite datos de manera diferente a AIS y puede brindar diferentes medidas de integridad, precisión y calidad. Global Fishing Watch mejora continuamente sus algoritmos en todos los formatos de datos de transmisión para identificar algorítmicamente la \"actividad de pesca aparente\". Es posible que no se identifique alguna actividad pesquera o que el mapa de calor muestre actividad pesquera aparente cuando en realidad no se está pescando. Por estas razones, Global Fishing Watch califica los términos “actividad pesquera”, “pesca” o “esfuerzo pesquero” como aparentes en lugar de ciertos. Cualquier y toda la información de Global Fishing Watch sobre la \"actividad de pesca aparente\" debe considerarse una estimación y debe confiarse únicamente en la discreción del usuario. Los algoritmos de detección de pesca de Global Fishing Watch se desarrollan y prueban utilizando datos de eventos de pesca reales recopilados por observadores y se combinan con análisis expertos de datos de movimiento de embarcaciones AIS, lo que da como resultado la clasificación manual de miles de eventos de pesca conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de actividades pesqueras y mejorar las técnicas de clasificación automatizadas" }, "public-png-presence": { "name": "VMS de Papúa Nueva Guinea", "description": "Los datos del sistema de seguimiento de embarcaciones (VMS) son proporcionados por la Autoridad Nacional de Pesca de Papúa Nueva Guinea. Los datos se recopilan utilizando el VMS nacional de Papúa Nueva Guinea proporcionado por el Sistema de gestión e información pesqueras (FIMS, por sus siglas en inglés). Los datos de VMS incluyen los identificadores y la ubicación de las embarcaciones, y se publican con un retraso de cinco días.\n\nLa capa de actividad muestra un mapa de calor de presencia de embarcaciones. La presencia se determina tomando dos posiciones por hora por embarcación a partir de las posiciones transmitidas por el VMS de la embarcación." }, "public-png-vessel-identity-fishing": { "name": "VMS de Papúa Nueva Guinea (Buques de pesca)", "description": "Dataset for VMS Papua New Guinea (Public) " }, "public-ports-v1": { "name": "Puertos", "description": "Named ports v1" }, "public-protectedseas": { "name": "AMP (ProtectedSeas)", "description": "Las áreas marinas protegidas (AMP) son áreas del océano reservadas para la conservación a largo plazo. Estas pueden tener diferentes niveles de protección, y la gama de actividades permitidas o prohibidas dentro de sus límites varía considerablemente. Fuente: ProtectedSeas Navigator. ProtectedSeas asigna una puntuación de nivel de protección pesquera (LFP) a cada área en función de un análisis de las restricciones a la extracción de vida marina. Puede usar el ícono de filtro para explorar los diferentes puntajes LFP, que son, El menos restrictivo: Sin restricciones de pesca conocidas; Menos restrictivo: se aplican pocas restricciones específicas de especies o artes; Moderadamente restrictivo: se aplican varias restricciones específicas de especies o artes; Muy restrictivo: la pesca está prohibida en su mayoría, con pocas excepciones; El más restrictivo: La pesca está prohibida. Ver información más detallada para esta capa.", "schema": { "removal_of": { "keyword": "Nivel de protección de la pesca", "enum": { "1": "1. El menos restrictivo", "2": "2. Menos restrictivo", "3": "3. Moderadamente restrictivo", "4": "4. Muy restrictivo", "5": "5. El más restrictivo" } } } }, "public-protectedseas-all": { "name": "Protected Seas all", "description": "Protected seas all", "schema": { "category_name": { "keyword": "category_name", "enum": { "IUCN MPA": "IUCN MPA", "Other": "Otro", "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. El menos restrictivo", "2": "2. Menos restrictivo", "3": "3. Moderadamente restrictivo", "4": "4. Muy restrictivo", "5": "5. El más restrictivo" } } } }, "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": "Praderas marinas", "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." } }