Access to public-global-vessel-presence for dark-vessel detection proof-of-concept
A
Abdullah Alshamrani
We're a small satellite-data/AI team building a proof-of-concept that fuses Sentinel-1 SAR ship detection (our own CFAR pipeline, running on sentinel-1-rtc) with GFW's public-global-sar-presence dataset as an independent cross-check -- a vessel flagged by both our detector and GFW's SAR model, with no AIS match, gets treated as a high-confidence dark-vessel alert. The SAR presence cross-check is already working well for us. What we're missing is AIS: we get a 403 ("Insufficient permissions for public-global-vessel-presence:latest") when querying AIS positions ourselves. We'd like this specifically to (1) time-interpolate AIS pings to our SAR scene's exact acquisition timestamp for tighter, more accurate matching than GFW's own internal check alone gives us, and (2) add a third independent confirmation layer on top of the SAR-vs-SAR-vs-AIS agreement we've already built. Scope: testing against small AOIs (10-30km) in the Singapore/Malacca Strait region, a handful of dates so far, non-commercial proof-of-concept -- not yet a production or commercial deployment, and we'll credit GFW if/when this becomes a real product. Query volume is low; this is exploratory work, not a firehose. Happy to share our SAR-presence integration or detection methodology if useful context for reviewing this.