Skip to content

Commit 33d667a

Browse files
prasadkoprasadko
committed
Improve Build & Use Applications section cohesion
- Restructure anchor article as use-case router with integration path table - Add missing links to build-web-application.md and azure-batch.md - Add Related content back-links to anchor article in child articles - Cross-link GIS tool articles (ArcGIS Pro and QGIS) - Fix authentication article Next steps to point to anchor article - Fix typos and grammar issues
1 parent c287ded commit 33d667a

7 files changed

Lines changed: 83 additions & 42 deletions

‎articles/planetary-computer/azure-batch.md‎

Lines changed: 20 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,19 @@ ms.custom:
1313

1414
# Quickstart: Use Microsoft Planetary Computer Pro GeoCatalog in Azure Batch
1515

16-
In this quickstart, you learn how to use Microsoft Planetary Computer Pro GeoCatalog resource in Azure Batch to process geospatial data. Planetary Computer Pro GeoCatalog is a geospatial data catalog that provides a unified view of your geospatial data assets across your organization. You can use Planetary Computer Pro GeoCatalog to discover, manage, and analyze your geospatial data.
16+
In this quickstart, you learn how to use a Microsoft Planetary Computer Pro GeoCatalog resource in Azure Batch to process geospatial data at scale.
17+
18+
Azure Batch is a cloud-based job scheduling service that enables you to run large-scale parallel and high-performance computing (HPC) workloads. By combining Azure Batch with Microsoft Planetary Computer Pro, you can:
19+
20+
- Process large volumes of geospatial data in parallel across multiple compute nodes
21+
- Authenticate securely to GeoCatalog APIs using managed identities
22+
- Scale processing power up or down based on workload demands
23+
- Automate geospatial data pipelines without managing infrastructure
24+
25+
This quickstart demonstrates how to set up a Batch pool with a user-assigned managed identity, configure permissions to access your GeoCatalog, and run jobs that query the STAC API.
26+
27+
> [!TIP]
28+
> For an overview of application development options with Microsoft Planetary Computer Pro, see [Building applications with Microsoft Planetary Computer Pro](./build-applications-with-planetary-computer-pro.md).
1729
1830
## Prerequisites
1931

@@ -214,6 +226,10 @@ az batch task file download \
214226

215227
- [Building applications with Microsoft Planetary Computer Pro](./build-applications-with-planetary-computer-pro.md)
216228
- [Configure application authentication for Microsoft Planetary Computer Pro](./application-authentication.md)
217-
- For more information about managed identities in batch pools, see [Configure managed identities in Batch pools](/azure/batch/managed-identity-pools) documentation.
218-
219-
- For more information about how to deploy files to your Batch account, see [Copy applications and data to pool nodes](/azure/batch/batch-applications-to-pool-nodes), [Deploy applications to compute nodes with Batch application packages](/azure/batch/batch-application-packages), and [Creating and using resource files](/azure/batch/resource-files).
229+
- [Build a web application with Microsoft Planetary Computer Pro](./build-web-application.md)
230+
- [Use the Microsoft Planetary Computer Pro Explorer](./use-explorer.md)
231+
- [Manage access to Microsoft Planetary Computer Pro](./manage-access.md)
232+
- [Configure managed identities in Batch pools](/azure/batch/managed-identity-pools)
233+
- [Copy applications and data to pool nodes](/azure/batch/batch-applications-to-pool-nodes)
234+
- [Deploy applications to compute nodes with Batch application packages](/azure/batch/batch-application-packages)
235+
- [Creating and using resource files](/azure/batch/resource-files)

‎articles/planetary-computer/build-applications-with-planetary-computer-pro.md‎

Lines changed: 40 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -14,68 +14,76 @@ ms.custom:
1414

1515
# Building applications with Microsoft Planetary Computer Pro
1616

17-
Microsoft Planetary Computer Pro offers APIs and connectors that enable developers to build applications that can access, analyze, and visualize large-scale geospatial datasets. This article provides an overview of the application development options available with Planetary Computer Pro and key concepts for integrating with its services.
17+
Microsoft Planetary Computer Pro offers multiple ways to access, analyze, and visualize large-scale geospatial datasets—from no-code browser experiences to fully custom application development. This article provides an overview of the application development options available with Planetary Computer Pro and guides you to the right approach for your needs.
1818

1919
## Prerequisites
2020

21-
- An Azure account and subscription [Create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
22-
- Access to a Microsoft Planetary Computer Pro [GeoCatalog resource](./deploy-geocatalog-resource.md)
21+
- An Azure account and subscription. [Create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
22+
- Access to a Microsoft Planetary Computer Pro [GeoCatalog resource](./deploy-geocatalog-resource.md).
2323

2424
## Application integration approaches
2525

2626
Planetary Computer Pro supports multiple integration approaches depending on your application's requirements. You can build applications that access Planetary Computer Pro's data and services in several ways:
2727

2828
[ ![Diagram illustrating how to build applications with Microsoft Planetary Computer Pro, showing integration points, APIs, and supported workflows.](media/build-apps-diagram.png) ](media/build-apps-diagram.png#lightbox)
2929

30-
### Direct API integration
30+
### No code: Built-in Explorer
3131

32-
The primary way to integrate with Planetary Computer Pro is through its REST APIs. Planetary Computer Pro provides a comprehensive set of APIs to build applications. These APIs are summarized in the next table:
32+
The fastest way to get started is with the built-in **Explorer** web application. Explorer allows you to visualize and interact with geospatial data directly in your browser—no coding required.
3333

34-
| API Name | Description |
35-
|---------------|----------------------------------------------------------------------------------------------|
36-
| STAC API | Search, discover, and access geospatial data using the SpatioTemporal Asset Catalog (STAC) specification. |
37-
| Tiler API | Serve map tiles and imagery for visualization in web maps and GIS apps. |
38-
| SAS API | Generate secure, time-limited access tokens for sharing geospatial data. |
39-
| Ingestion API | Ingest and transform new geospatial datasets into the GeoCatalog. |
34+
By using Explorer, you can:
35+
- Browse collections and view items on an interactive map
36+
- Apply filters and mosaic definitions to refine your data
37+
- Generate code samples for Python integration
38+
- Create collection thumbnails
4039

41-
These APIs support [standard authentication through Microsoft Entra ID](/entra/architecture/guide-for-independent-software-developers), enabling secure access to your resources. Integrating your application requires the use of [application authentication](./application-authentication.md). Once your app is registered with Microsoft Entra, it can securely use the APIs to access all data inside a GeoCatalog.
40+
Once your data is [configured for visualization](./collection-configuration-concept.md), you can [use the Explorer](./use-explorer.md) immediately. Explorer is ideal for data exploration, quick visualization, and sharing insights with stakeholders.
4241

43-
For a complete walkthrough of building a browser-based application that uses these APIs, see [Build a web application with Microsoft Planetary Computer Pro](./build-web-application.md).
42+
By using [the API services](#custom-development-rest-apis), you can also integrate data in Planetary Computer Pro with Microsoft applications such as [Fabric](/fabric) and [Microsoft Foundry](/azure/ai-foundry/what-is-azure-ai-foundry).
4443

45-
The [REST API is detailed in the API reference](/rest/api/planetarycomputer).
44+
### Desktop GIS applications
4645

47-
### First-party application support
46+
For geospatial professionals who prefer working with desktop GIS tools, Planetary Computer Pro integrates with industry-standard applications:
4847

49-
Planetary Computer Pro has a built-in application called Explorer that allows users to visualize ingested data in a GeoCatalog resource from their browser. Once the data is [configured for visualization](./collection-configuration-concept.md), it can be [used in the Explorer](./use-explorer.md).
48+
**ArcGIS Pro** — Planetary Computer Pro integrates directly with ESRI ArcGIS Pro, providing a seamless workflow for GIS professionals. By connecting Planetary Computer Pro data directly to ArcGIS Pro, users can:
5049

51-
By using [the API services](#direct-api-integration), data in Planetary Computer Pro can be integrated with first-party Microsoft applications such as [Fabric](/fabric) and [Azure Machine Learning](/azure/machine-learning/overview-what-is-azure-machine-learning).
50+
- Access and analyze large-scale, cloud-hosted geospatial datasets without complex data transfers.
51+
- Use ArcGIS Pro's advanced visualization, editing, and analysis capabilities on authoritative data from Planetary Computer Pro.
52+
- Streamline collaboration by combining enterprise GIS workflows with the latest planetary-scale datasets.
53+
- Accelerate decision-making by integrating cloud-based data with local projects, enabling richer insights and more informed outcomes.
5254

53-
### GIS application connectivity
55+
For more information, see [Configure ArcGIS Pro to access a GeoCatalog](./create-connection-arc-gis-pro.md).
5456

55-
Planetary Computer Pro integrates directly with the ESRI ArcGIS Pro desktop GIS application.
57+
**QGIS**: The open-source QGIS desktop application connects via the STAC API for browsing and visualization. QGIS enables direct interaction with STAC collections, so you can visualize, analyze, and style data on the fly. For more information, see [Configure QGIS to access a GeoCatalog resource](./configure-qgis.md).
5658

57-
Integrating Microsoft Planetary Computer Pro with ESRI ArcGIS Pro provides a seamless workflow for geospatial professionals who rely on industry-standard desktop GIS tools. By connecting Planetary Computer Pro data directly to ArcGIS Pro, users can:
59+
### Custom development: REST APIs
5860

59-
- Access and analyze large-scale, cloud-hosted geospatial datasets without complex data transfers.
60-
- Use ArcGIS Pro’s advanced visualization, editing, and analysis capabilities on authoritative data from Planetary Computer Pro.
61-
- Streamline collaboration by combining enterprise GIS workflows with the latest planetary-scale datasets.
62-
- Accelerate decision-making by integrating cloud-based data with local projects, enabling richer insights and more informed outcomes.
61+
For full control over your application's functionality, integrate directly with Planetary Computer Pro's REST APIs. By using these APIs, you can build custom web applications, backend services, and automated pipelines.
62+
63+
| API Name | Description |
64+
|---------------|----------------------------------------------------------------------------------------------|
65+
| STAC API | Search, discover, and access geospatial data using the SpatioTemporal Asset Catalog (STAC) specification. |
66+
| Tiler API | Serve map tiles and imagery for visualization in web maps and GIS apps. |
67+
| SAS API | Generate secure, time-limited access tokens for sharing geospatial data. |
68+
| Ingestion API | Ingest and transform new geospatial datasets into the GeoCatalog. |
6369

64-
For more information on how to connect ArcGIS Pro to a GeoCatalog resource, see the [Configure ArcGIS Pro to access a GeoCatalog](./create-connection-arc-gis-pro.md).
70+
These APIs support [standard authentication through Microsoft Entra ID](/entra/architecture/guide-for-independent-software-developers), enabling secure access to your resources. To integrate your application, use [application authentication](./application-authentication.md). Once you register your app with Microsoft Entra, it can securely use the APIs to access all data inside a GeoCatalog.
6571

66-
Another desktop integration option is [QGIS](./configure-qgis.md), which connects via the STAC API for browsing and visualization.
72+
For a complete walkthrough of building a browser-based application that uses these APIs, see [Build a web application with Microsoft Planetary Computer Pro](./build-web-application.md).
73+
74+
The [REST API is detailed in the API reference](/rest/api/planetarycomputer).
6775

6876
## Authentication and authorization
6977

70-
All applications that interact with Planetary Computer Pro must authenticate properly using Microsoft Entra ID.
78+
All applications that interact with Planetary Computer Pro must authenticate properly by using Microsoft Entra ID.
7179

72-
### Authentication options and recommendations:
80+
### Authentication options and recommendations
7381

7482
| Application Hosting Environment | Access Type Required | Recommended Identity Type | Explanation |
7583
| :------------------------------ | :------------------- | :------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------- |
76-
| **Running on Azure** (VM, App Service, Functions, Container Apps, etc.) | App-Only (Application acts as itself) | Managed Identity (User-assigned recommended) | **Security & Manageability:** Eliminates the need to store and manage credentials (secrets/certificates) in code or configuration. Azure handles credential rotation automatically. User-assigned is preferred for sharing across multiple resources. |
84+
| **Running on Azure** (VM, App Service, Functions, Container Apps, etc.) | App-Only (Application acts as itself) | Managed Identity (User-assigned recommended) | **Security & Manageability:** Eliminates the need to store and manage credentials (secrets or certificates) in code or configuration. Azure handles credential rotation automatically. User-assigned is preferred for sharing across multiple resources. |
7785
| **Running on Azure** (VM, App Service, Functions, Container Apps, etc.) | Delegated (Application acts on behalf of a user) | Managed Identity (User-assigned recommended) | **Leverages Azure Integration:** Combines the security benefits of Managed Identity for the application itself with standard user authentication flows. Simplifies infrastructure setup within Azure. |
78-
| **Running Outside Azure** (On-premises, other cloud, developer machine) | App-Only (Application acts as itself) | Service Principal | **Standard for External Apps:** The established method for non-Azure applications to authenticate with Microsoft Entra ID. Requires managing credentials (secrets/certificates) securely. |
86+
| **Running Outside Azure** (On-premises, other cloud, developer machine) | App-Only (Application acts as itself) | Service Principal | **Standard for External Apps:** The established method for non-Azure applications to authenticate with Microsoft Entra ID. Requires managing credentials (secrets or certificates) securely. |
7987
| **Running Outside Azure** (On-premises, other cloud, developer machine) | Delegated (Application acts on behalf of a user) | Service Principal | **Standard for External Apps:** Enables standard OAuth 2.0 flows for user sign-in and consent for applications outside Azure, using the application's registered identity in Entra ID. |
8088
| **Running Outside Azure (Alternative)** | App-Only or Delegated | Managed Identity | **Brings Azure Benefits:** By hosting the application in an Azure compute service (like a VM or Container App), it can use the enhanced security and manageability of Managed Identities, avoiding credential management even though the *origin* might be considered non-Azure. |
8189

@@ -88,7 +96,7 @@ Select the approach that best fits your use case:
8896
| Use case | Recommended approach | Get started |
8997
|----------|---------------------|-------------|
9098
| **Explore data without coding** | Use the built-in Explorer web application | [Use the Explorer](./use-explorer.md) |
91-
| **Build a custom web application** | Browser-based app with JavaScript/TypeScript using MSAL.js | [Build a web application](./build-web-application.md) |
99+
| **Build a custom web application** | Browser-based app with JavaScript or TypeScript using MSAL.js | [Build a web application](./build-web-application.md) |
92100
| **Desktop GIS with ArcGIS Pro** | Connect ArcGIS Pro directly to GeoCatalog | [Configure ArcGIS Pro](./create-connection-arc-gis-pro.md) |
93101
| **Desktop GIS with QGIS** | Connect QGIS to GeoCatalog via STAC | [Configure QGIS](./configure-qgis.md) |
94102
| **Batch processing on Azure** | Run processing jobs with Azure Batch and managed identity | [Use Azure Batch](./azure-batch.md) |
@@ -101,3 +109,4 @@ Select the approach that best fits your use case:
101109
- [Connect ArcGIS Pro to Microsoft Planetary Computer Pro](./create-connection-arc-gis-pro.md)
102110
- [Configure QGIS to access a GeoCatalog resource](./configure-qgis.md)
103111
- [Manage access to Microsoft Planetary Computer Pro](./manage-access.md)
112+
- [Microsoft Planetary Computer Pro REST API reference](/rest/api/planetarycomputer)

‎articles/planetary-computer/build-web-application.md‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ In this quickstart, you build a web application that displays satellite imagery
2525

2626
The code patterns work with any modern JavaScript framework (React, Vue, Angular) or vanilla JavaScript. GeoCatalog APIs have full CORS support, so you can call them directly from `localhost` during development—no proxy required.
2727

28+
You can download and test this code from the [Microsoft Planetary Computer Pro public GitHub repository](https://github.com/Azure/microsoft-planetary-computer-pro/tree/main/tools/javascript-sample).
29+
2830
## Table of contents
2931

3032
- [Architecture overview](#architecture-overview)
@@ -61,10 +63,10 @@ A typical GeoCatalog web application follows this architecture:
6163

6264
## Register your application in Microsoft Entra ID
6365

64-
Before your web application can authenticate users, you need to register it in Microsoft Entra ID. This quickstart uses a **Single Page Application (SPA)** registration, which is ideal for client-side JavaScript applications and local development. The API integration patterns shown in later steps work with any application type.
66+
Before your web application can authenticate users, register it in Microsoft Entra ID. This quickstart uses a **Single Page Application (SPA)** registration, which is ideal for client-side JavaScript applications and local development. The API integration patterns shown in later steps work with any application type.
6567

6668
> [!NOTE]
67-
> For production applications with a backend server, you might choose a different registration type (Web, Native, etc.). See [Configure application authentication](./application-authentication.md) for guidance on choosing the right approach for your scenario.
69+
> For production applications with a backend server, consider choosing a different registration type (Web, Native, etc.). See [Configure application authentication](./application-authentication.md) for guidance on choosing the right approach for your scenario.
6870
6971
### Register as a single-page application
7072

@@ -286,7 +288,7 @@ const results = await searchItems(token, catalogUrl, {
286288

287289
## Tile URLs: Build URLs for map visualization
288290

289-
The GeoCatalog Tiler API serves raster data as map tiles. You construct tile URLs with the following pattern:
291+
The GeoCatalog Tiler API serves raster data as map tiles. Construct tile URLs with the following pattern:
290292

291293
### Single item tiles
292294

@@ -498,7 +500,7 @@ function buildMosaicTileUrl(catalogUrl, searchId, collectionId, options = {}) {
498500
The SAS API provides time-limited tokens for downloading raw asset files (GeoTIFFs, COGs, and other files) directly from Azure Blob Storage. Use this option when you need the original source files rather than rendered tiles.
499501

500502
> [!IMPORTANT]
501-
> SAS tokens enable **downloads only** in browser applications. Due to Azure Blob Storage CORS policies, browsers can't read blob data via JavaScript `fetch()`. See [Browser limitations](#browser-limitations) section.
503+
> SAS tokens enable **downloads only** in browser applications. Due to Azure Blob Storage CORS policies, browsers can't read blob data via JavaScript `fetch()`. See the [Browser limitations](#browser-limitations) section.
502504
503505
[ ![Screenshot showing how to download assets using a SAS token.](media/download-via-sas-token.gif) ](media/download-via-sas-token.gif#lightbox)
504506

0 commit comments

Comments
 (0)