Data & API Requests

4wings report API - return vessel record id

Does anyone know why, when I pull the squid jigger data for the IATTC area, I get different values than those shown on the map? For example, for 2011 in the IATTC area, the map shows 210 vessels, while gfwR ( gfw_ais_fishing_hours ) results 197 unique vessels. Here are the < https://globalfishingwatch.org/map/fishing-activity/default-public/report/public-rfmo/IATTC?_gl=1%2A1hg2zn9%2A_gcl_au%2AMTgxODMyMDk4LjE3NTU3OTQyMjU.%2A_ga%2AMjI4MjQyODM3LjE3NTU3OTQyMjU.%2A_ga_5W83X3EYGW%2AczE3NTkzMjM0NDEkbzUyJGcwJHQxNzU5MzIzNDQxJGo2MCRsMCRoNDY0Nzg1MDI4%2A_ga_M5J2ZHDZMV%2AczE3NTkzMjM0NDEkbzE5JGcwJHQxNzU5MzIzNDQxJGo2MCRsMCRoOTI5MDUzOTM3&longitude=-110.02665&latitude=0&zoom=1.92618414&dvIn[0][id]=context-layer-rfmo&dvIn[0][cfg][vis]=true&dvIn[1][id]=vms&dvIn[1][cfg][vis]=false&dvIn[2][id]=ais&dvIn[2][cfg][vis]=true&dvIn[2][cfg][filters][geartype][0]=squid_jigger&bDV&start=2021-01-01T00%3A00%3A00.000Z&end=2022-01-01T00%3A00%3A00.000Z&lTD=&fTD=&trackCorrectionId=&aVM=heatmap|dynamic report> and code. ```code_rfmo <- gfw_region_id(region_name = "IATTC", region_source = "RFMO") fh2025 <- gfw_ais_fishing_hours( spatial_resolution = "HIGH", temporal_resolution = "DAILY", group_by = "VESSEL_ID", start_date = "2021-01-01", end_date = "2021-12-31", region = gfw_region_id(region_name = "IATTC", region_source = "RFMO")$id[1], region_source = "RFMO") fh_squid_2025 <- fh2025 %>% filter( Gear Type %in% c("SQUID_JIGGER")) length(unique(fh_squid_2025$ Vessel ID ))```

Angola EEZ - Transshipment Detection

ORG : MareDatum | BGAPP Angola TOKEN : 3273 DATASET : public-global-transshipment:latest NEED : At-sea transfer activities detection in Angola waters USE : Illegal transshipment detection & enforcement DEADLINE : Dec 2025 NON-COMMERCIAL | Academic/Gov Research Detect illegal transshipment activities in Angolan waters

Angola EEZ - Carrier Vessel Supply Chain

ORG : MareDatum | BGAPP Angola TOKEN : 3273 DATASET : public-global-carrier-vessels:latest NEED : Transport & supply vessel tracking in Angola EEZ USE : Supply chain monitoring & maritime logistics DEADLINE : Dec 2025 NON-COMMERCIAL | Academic/Gov Research Track support vessels and supply chains

Angola EEZ - Fishing Activity Monitoring

ORG : MareDatum | BGAPP Angola TOKEN : 3273 | ERROR : 404 Not Found DATASET : public-global-fishing-activity:v20241201 NEED : Fishing patterns & intensity per location in Angola waters USE : Marine protected area monitoring & IUU fishing detection DEADLINE : Dec 2025 NON-COMMERCIAL | Academic/Gov Research Monitor fishing pressure in Angolan marine protected areas

Angola EEZ - Vessel Identification System

ORG : MareDatum | BGAPP Angola TOKEN : 3273 DATASET : public-global-vessel-identity:latest NEED : IMO, callsign, flag state data for Angola EEZ vessels USE : Vessel compliance & registry verification DEADLINE : Dec 2025 NON-COMMERCIAL | Academic/Gov Research Vessel identification and compliance monitoring

Angola EEZ - Vessel Presence Tracking

ORG : MareDatum | BGAPP Angola ( [ bgapp-admin.pages.dev ]( http://bgapp-admin.pages.dev ) ) TOKEN : 3273 | ERROR : 403 Forbidden DATASET : public-global-ais-vessel-presence:v3.0 NEED : Real-time vessel heatmaps Angola EEZ (11.5°E-17.5°E, -18.5°S to -4.2°S) USE : Gov maritime security & EEZ monitoring DEADLINE : Dec 2025 Gov Presentation NON-COMMERCIAL | Academic/Gov Research Core vessel tracking for Angolan waters

Allow speed to be used as a group-by parameter in AIS Vessel Presence - 4Wings API

Context: "Currently I’m submitting a separate request for each of the different speed category levels in order to get a speed value for each result… it might be nice in the future to allow speed to be one of the ‘group’ options so that this could be done in a single request.” NOAA researcher (via API Support) Adding support for group-by=SPEED in the 4Wings API report endpoint would allow users to generate this data in a single request, improving performance and usability, especially for time- and bandwidth-sensitive analyses.

Gap events - port visited after event

What port a vessel went to after a gap event. Recorded for Joe. Follow up for more info.

Encounters events - AIS-VMS

Stationary facilities with AIS appear as duplicates when combining both the AIS and the Infrastructure APIs

At SkyTruth, we identify sources of marine pollution using both vessel and infrastructure data from GFW (both can cause pollution). When a stationary facility - such as an FPSO or an oil platform - is broadcasting AIS, it will appears on both GFW APIs, resulting as duplicate potential sources of pollution. This is misleading for advocates and journalists investigating the cause of the detected pollution, as it looks like there are 2 possible polluters when actually there is 1 likely culprit. We would prefer to use the AIS version of the two because includes additional metadata about the AIS broadcasting facility (flag, vessel name, etc), however it is generally more accurate to describe these locations as infrastructure and not vessels, so it would be nice to append the Structure ID somehow so we can describe it correctly. (Oil slicks that come from stationary sources also look quite different from oil slicks cause by vessels in motion, so this is also useful for pollution investigators.) Is it possible to cross-reference the lat/lon of known infrastructure with known AIS to de-dupe somehow? Examples (not exhaustive, we see this relatively frequently, especially among FPSOs/FSOs and similar floating infra) -- We also have the S1 scenes for these locations available if helpful for your investigation. Structure ID 239392 & MMSI 309999000 (also shared in screenshot) https://cerulean.skytruth.org/?zoom=13.578009&lng=11.269523&lat=-6.146767&startDate=2024-06-03&endDate=2024-12-03&cls=2_3_4_5_6_7_8&sources=1_2&sourceScore=-1_&sourceLimit=3&imageGamma=2&imageOpacity=1&machine_confidence=0.9&area=5_50&mpa=0&eez=0&iho=0&hitl_cls=&offset=0&limit=100&hitl_rev=0_1&slickId=3573116 Structure IDs 340743 & 88494; MMSI 2320206. https://cerulean.skytruth.org/?zoom=11.435713&lng=1.471807&lat=58.078448&startDate=2024-06-03&endDate=2024-12-03&cls=2_3_4_5_6_7_8&sources=1_2&sourceScore=_&sourceLimit=5&imageGamma=2&imageOpacity=1&machine_confidence=0.9&area=5_50&mpa=0&eez=0&iho=0&hitl_cls=&offset=0&limit=100&hitl_rev=0_1&slickId=3573183 Structure IDs 1040285 & 77739; MMSI 235599000. https://cerulean.skytruth.org/?zoom=11.425581&lng=0.914865&lat=57.087792&startDate=2024-06-03&endDate=2024-12-03&cls=2_3_4_5_6_7_8&sources=1_2&sourceScore=_&sourceLimit=5&imageGamma=2&imageOpacity=1&machine_confidence=0.9&area=5_50&mpa=0&eez=0&iho=0&hitl_cls=&offset=0&limit=100&hitl_rev=0_1&slickId=3573376 Structure IDs 592009 & 457875; MMSI 538003299. https://cerulean.skytruth.org/?zoom=12.915541&lat=28.466801&lng=49.367199&startDate=2000-06-04&endDate=2024-12-04&cls=2_3_4_5_6_7_8&sources=1_2&sourceScore=_&sourceLimit=3&imageGamma=2&imageOpacity=1&machine_confidence=0.5&area=0_&mpa=0&eez=0&iho=0&hitl_cls=&offset=0&limit=100&hitl_rev=0_1&slickId=3558829 --Kris

→