Skip to content

Commit 3430529

Browse files
committed
post learn review updates to bulk-ingestion-api.md
1 parent 5c54368 commit 3430529

File tree

2 files changed

+16
-15
lines changed

2 files changed

+16
-15
lines changed

articles/planetary-computer/bulk-ingestion-api.md

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -13,24 +13,24 @@ ms.date: 04/18/2024
1313

1414
This article shows you how to ingest many geospatial data assets at once into a GeoCatalog using the Bulk Ingestion API. First, we create and configure a GeoCatalog Ingestion Source. Creating an Ingestion Source establishes a secure connection between a GeoCatalog resource and the storage location for your existing geospatial data. Next, we create a SpatioTemporal Access Catalog (STAC) Collection within your GeoCatalog resource to store the data being ingested. Finally, we use the Bulk Ingestion API to initiate the ingestion workflow. When you're finished completing these steps, your geospatial data is ingested and accessible from the GeoCatalog UIs and APIs.
1515

16-
:::image type="content" source="media/static_catalog_import.png" alt-text="Diagram illustrating the static catalog import process for GeoCatalog, showing data flow from storage to GeoCatalog via the Bulk Ingestion API.":::
16+
:::image type="content" source="media/static-catalog-import.png" alt-text="Diagram illustrating the static catalog import process for GeoCatalog, showing data flow from storage to GeoCatalog via the Bulk Ingestion API.":::
1717

1818
## Prerequisites
1919

2020
In your Azure subscription:
21-
1. [GeoCatalog](./deploy-geocatalog-resource.md)
22-
1. [Azure Storage Account](/azure/storage/common/storage-account-create?tabs=azure-portal)
21+
- [GeoCatalog](./deploy-geocatalog-resource.md)
22+
- [Azure Storage Account](/azure/storage/common/storage-account-create?tabs=azure-portal)
2323

2424
A geospatial dataset in your storage account blob container:
25-
1. Geospatial data assets (for example, GeoTIFF files)
26-
1. The associated STAC Items [Create STAC Items](./create-stac-item.md) for these assets.
27-
1. A STAC Collection JSON that references all the STAC Items and geospatial data assets.
25+
- Geospatial data assets (for example, GeoTIFF files)
26+
- The associated STAC Items [Create STAC Items](./create-stac-item.md) for these assets.
27+
- A STAC Collection JSON that references all the STAC Items and geospatial data assets.
2828

2929
In your local / development environment:
3030

31-
1. A Python environment running Python 3.8, or later.
32-
1. [Azure CLI](/cli/azure/install-azure-cli)
33-
1. You're [signed in to Azure](/cli/azure/authenticate-azure-cli-interactively)
31+
- A Python environment running Python 3.8, or later.
32+
- [Azure CLI](/cli/azure/install-azure-cli)
33+
- You're [signed in to Azure](/cli/azure/authenticate-azure-cli-interactively)
3434

3535
Microsoft Planetary Computer Pro must have access to the Azure Blob Storage container. In this article, we create and use a temporary SAS token credential to grant this access. Alternatively, you can use these guides to set up Managed Identity or hard-coded SAS Tokens.
3636

@@ -148,10 +148,10 @@ Creating an ingestion source defines for GeoCatalog which source to ingest geosp
148148
```
149149
> [!NOTE]
150150
> Running these steps more than once back-to-back results in a 409 response:
151-
152-
```Container url <container uri> already contains a SAS token ingestion source with id <sas token id>```
153-
154-
The ingestion source API doesn't allow you to create more than one ingestion source for the same container URL. To avoid conflicts, ensure you clean up any existing ingestion sources before creating a new one. For details, see [Clean up resources](#clean-up-resources).
151+
>
152+
> ```Container url <container uri> already contains a SAS token ingestion source with id <sas token id>```
153+
>
154+
> The ingestion source API doesn't allow you to create more than one ingestion source for the same container URL. To avoid conflicts, ensure you clean up any existing ingestion sources before creating a new one. For details, see [Clean up resources](#clean-up-resources).
155155
156156
## Create Collection
157157
@@ -202,8 +202,9 @@ A STAC collection is the high-level container for STAC Items and their associate
202202
"msft:short_description": "An example collection",
203203
}
204204
```
205+
205206
> [!NOTE]
206-
> This sample collection specification is a basic example of a collection. For more information on STAC collections and the STAC open standard, see the [STAC overview](./stac-overview.md). For a guide creating a complete STAC collection, see [Create STAC Collection](./create-stac-collection.md).
207+
> This sample collection specification is a basic example of a collection. For more information on STAC collections and the STAC open standard, see the [STAC overview](./stac-overview.md). For more information about creating a complete STAC collection, see [Create STAC Collection](./create-stac-collection.md).
207208
208209
1. Create the new collection with the Collection API
209210
@@ -316,7 +317,7 @@ Once the workflow is complete, you can query, retrieve, or visualize your geospa
316317
317318
## Clean up resources
318319
319-
1. Delete ingestion source
320+
- Delete ingestion source
320321
321322
```python
322323
del_is_endpoint = f"{GEOCATALOG_URI}/inma/ingestion-sources/{ingestion_source_id}"

0 commit comments

Comments
 (0)