Data & API Requests

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
0
Tracking Albatross-Vessel Interactions in Scientific Research
Feedback: • Fishing Effort Data Access and Analysis: I was able to use the API again to look at encounters of boats and see if our birds were associated with boats that have fishing effort data. It’s been eye-opening. The ability to see a vessel track in tandem with an albatross track allows for so many questions to be answered from a perspective that wasn’t available before. • Real-Time Data Visualization: I think it’s worth mentioning that while the portal has a delay in real-time data (around five days), it’s still incredibly useful for rolling through time series and visualizing interactions. The improvements to the map, along with the API, have been really helpful. • GFW Map and API Improvements: I really like the brighter colors, as the previous lighter colors were a bit of a strain on the eyes. I was happy to see I could upload bird tracks as points rather than tracks, which was especially useful for visualizing radar pings. I made the radar points larger to indicate when a bird was near a boat, and that was really cool to see in real-time. Lastly, I’d say that without the API and portal, it would be impossible for us to visualize and interact with this level of vessel and bird data. Global Fishing Watch has built a tool we couldn’t replicate on our own, and it’s been invaluable for our research • Educational Use Cases: I’ve also been using the portal to set up another professor with albatross data for a lecture and lab format at San Jose State University. Product Requests and Other: • Inclusion of Non-Fishing Vessel Data: One thing I’d like to see in the API is access to vessel density, not just fishing effort. I’d be interested in something similar to the density layer for container ship traffic or general vessel density, not limited to actively fishing boats. It would be helpful to have access to composite densities for all AIS data, in line with what your portal offers. • Handling International Date Line Crossings: One thing I’ve noticed is that when birds cross the International Date Line, it causes issues if the tracks are uploaded as lines, but uploading them as points works fine. For a recent assignment, I provided my students with two example tracks with clear radar hits associated with vessels and four tracks with radar hits that didn’t have an associated vessel. Their task was to use the portal to investigate whether those hits were truly unmatched or if they could identify vessels with gaps in AIS transmissions.
0