## Signup

To get access to Custom Satellite Embeddings, first express interest with this form:
[Signup](https://mapsplatform.google.com/lp/geospatial-analytics-signup).

## Prerequisites

To access the Custom Satellite Embeddings data, you must:

1. Have a [Google Cloud](https://cloud.google.com/) 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:

   [Get Started](https://console.cloud.google.com/google/maps-apis/start?utm_source=Docs_GS_Button&ref=https://developers.google.com/maps/&utm_content=Docs_Central)
2. Have a [Google Cloud project](https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects).

3. Have a [Google Cloud Storage (GCS)](https://cloud.google.com/storage)
   bucket to write data to. See
   [About Cloud Storage buckets](https://docs.cloud.google.com/storage/docs/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:

```bash
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](https://developers.google.com/earth-engine/guides/custom_embedding_samples_on_gcs_readme.md.txt)
for more details on the COGs and the directory to which the COGs are delivered.

## What's next

- [Read samples](https://developers.google.com/maps/documentation/custom-satellite-embeddings/samples.md.txt)
- [Read reference docs](https://developers.google.com/maps/documentation/custom-satellite-embeddings/reference.md.txt)