Signup
To get access to Custom Satellite Embeddings, first express interest with this form: Signup.
Prerequisites
To access the Custom Satellite Embeddings data, you must:
Have a Google Cloud account.
If you don't have an account, click the Get Started button that links to an interactive setup experience in the Cloud console for new users:
Have a Google Cloud project.
Have a Google Cloud Storage (GCS) bucket to write data to. See About Cloud Storage buckets for instructions on creating and using Cloud Storage buckets.
Access your GCS buckets
The bucket in Google Cloud Storage to which COGs are delivered is owned and
managed by the customer. The delivery location, including the complete path
(e.g. gs://your-bucket/your-folder), is provided at the time of order.
Folder structure
Datasets are delivered with this folder structure:
gs://your-bucket/your-folder/DATASET-NAME/START-DATE_END-DATE/UTM_ZONE/IMAGE-NAME/*
Both START_DATE and END_DATE have date format yyyyMMdd. There may be one
or more START-DATE_END-DATE folders depending on the temporal cadence of your
imagery. There may be one or more IMAGE-NAME folders per
START-DATE_END-DATE folder depending on whether your imagery is stored in
tiles. When a request spans more than five UTM zones but has a total area of
less than 250,000 square kilometers, UTM_ZONE is replaced by global.
Each IMAGE-NAME folder contains:
data.tiff: Cloud-Optimized GeoTIFF file containing the image data.image_manifest.json: Image metadata not stored in the GeoTIFF header.
See the COGs README for more details on the COGs and the directory to which the COGs are delivered.