Skip to main content

Data Delivery

Maritime Sentry Application (MSA)​

All delivered vessel detects are available in the Vantor-hosted, browser-based application. Full strip deliveries do not appear in MSA and only exist in S3.

Standard S3 Delivery​

Data is always delivered to the Vantor-hosted S3 bucket: cni-delivery-prod-us-east-1

Delivery Details​

ContentS3 Path
Callback payloads/customers/<customer_name>/callbacks/...
Delivery manifests/customers/<customer_name>/deliveryManifests/...
EO vessel detect products/<inventory_id>/<inventory_id>-<uuid>_detections.zip
EO image chip †<YYYY-MM-DD>/<inventory_id>/<chip_index>_<G8|G16|B8|B16>_<uuid>.<tif|jpg>
Full strip — GeoTIFF tile/<inventory_id>/full_strip_<uuid>/granule_<inventory_id>_R<row_index>_C<column_index>.tif
Full strip — metadata/<inventory_id>/full_strip_<uuid>/strip.geojson
SAR/RF detect products/<scene_name>/<scene_name>_<uuid>_detections.zip
SAR image chip †<YYYY-MM-DD>/<scene_name>/<chip_index>_<S|OILSPILL>_<uuid>.<png|jpg>
EO tipped HTML alert/customers/<customer_name>/htmlAlerts/<inventory_id>_<tip_id>_<uuid>_context_graphic.html
EO watchbox HTML alert/customers/<customer_name>/htmlAlerts/<inventory_id>_<watchbox_name>_<uuid>_context_graphic.html
SAR/RF HTML alert/customers/<customer_name>/htmlAlerts/<scene_name>_<uuid>_context_graphic.html
EO Summary HTML alert/customers/<customer_name>/summaryAlerts/<mission>_<spacecraft>_<datetime>_<uuid>_summary_graphic.html
Updated EO Summary HTML alert/customers/<customer_name>/summaryAlerts/<mission>_<spacecraft>_<datetime>_update_<updateNumber>_<uuid>_summary_graphic.html

† Image chips are stored in the Vantor-hosted S3 bucket cni-chips-prod-us-east-1 and are referenced from detected_vessels.geojson via CloudFront URLs (imageChipUrlTif, imageChipUrlJpg). The purpose segment encodes chip type and bit depth: G8/G16 = general (as collected) 8-bit/16-bit; B8/B16 = bow-up (cropped and rotated) 8-bit/16-bit. For SAR detects, S = vessel, OILSPILL = oil spill.

Custom S3 Delivery​

Vantor can push data directly into a customer-owned bucket.

  • Customer provides S3 bucket name and optional base prefix
  • Configuration can be set at the customer, mission, and/or product levels
  • Customer grants write permissions to the following AWS IAM role:
    • arn:aws:iam::612258578450:role/cni/cni-prod-us-east-1-customer-s3-delivery
  • With custom s3, there is no CloudFront in use so callbacks and delivery manifests point to relative S3 paths instead of URLs.
  • Image chips are delivered as part of the zip file, but are not separately hosted in the custom S3 bucket. They are still hosted in cni-chips-prod-us-east-1.

Delivery Details​

ContentPath
Callback payloads<customer-prefix>/callbacks/...
Delivery manifests<customer-prefix>/deliveryManifests/...
EO vessel detect products<customer-prefix>/products/<inventory_id>/<inventory_id>-<uuid>_detections.zip
Full strip — GeoTIFF tile<customer-prefix>/products/<inventory_id>/full_strip_<uuid>/granule_<inventory_id>_R<row_index>_C<column_index>.tif
Full strip — metadata<customer-prefix>/products/<inventory_id>/full_strip_<uuid>/strip.geojson
SAR/RF detect products<customer-prefix>/products/<scene_name>/<scene_name>_<uuid>_detections.zip
EO tipped HTML alert<customer-prefix>/htmlAlerts/<inventory_id>_<tip_id>_<uuid>_context_graphic.html
EO watchbox HTML alert<customer-prefix>/htmlAlerts/<inventory_id>_<watchbox_name>_<uuid>_context_graphic.html
SAR/RF HTML alert<customer-prefix>/htmlAlerts/<scene_name>_<uuid>_context_graphic.html
EO Summary HTML alert<customer-prefix>/summaryAlerts/<mission>_<spacecraft>_<datetime>_<uuid>_summary_graphic.html
Updated EO Summary HTML alert<customer-prefix>/summaryAlerts/<mission>_<spacecraft>_<datetime>_update_<updateNumber>_<uuid>_summary_graphic.html

Bespoke Delivery Options​

In certain circumstances, Vantor can also push data directly into customer-owned platforms. Contact Vantor to discuss integration options.