You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/planetary-computer/service-usage-meters.md
+25-16Lines changed: 25 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,49 +5,53 @@ author: prasadko
5
5
ms.author: prasadkomma
6
6
ms.service: planetary-computer-pro
7
7
ms.topic: article
8
-
ms.date: 10/13/2024
8
+
ms.date: 02/11/2026
9
9
#customer intent: As a user, I want to understand the service usage meter structure for Microsoft Planetary Computer Pro so I can estimate usage.
10
10
---
11
11
12
12
# Microsoft Planetary Computer Pro service usage meters
13
13
14
-
Microsoft Planetary Computer Pro offers a pay-as-you-go usage model. You're charged for the resources you consume, providing flexibility and control over your spending. This article details the usage meters for the different components of the service.
14
+
Microsoft Planetary Computer Pro uses a pay-as-you-go pricing model. You pay for the resources you use, so you have flexibility and control over your spending. This article describes the usage meters for the different components of the service.
15
15
16
16
## Access usage metrics through the Azure portal
17
17
18
-
Detailed information about the utilization of your GeoCatalog resource is available in the Azure portal under **Monitoring**>**Metrics** in the resource view.
18
+
You can find detailed information about the utilization of your GeoCatalog resource in the Azure portal under **Monitoring** > **Metrics** in the resource view.
19
19
20
20
[](./media/service-usage-metrics.png#lightbox)
21
21
22
22
## Service usage meters
23
23
24
-
Usage of the service is measured with the following dimensions:
24
+
The service measures usage by using the following dimensions:
|**Geospatial Data Operations**| 10K operations | Storage read and metadata retrieval operations, such as search, list, and item or asset metadata access. |
30
30
|**Ingestion & Transformation**| vCPU-hour | Compute consumed transforming data into cloud-optimized formats (for example COG generation) and ingesting data into GeoCatalog. |
31
31
|**Bandwidth**| GiB | Data transferred out of the Azure region hosting the GeoCatalog resource. |
32
32
33
-
All meters are calculated using binary gigabytes (GiB), where 1 GiB equals 1,073,741,824 bytes.
33
+
All meters use binary gigabytes (GiB), where 1 GiB equals 1,073,741,824 bytes.
34
34
35
35
### Geospatial Storage
36
36
37
-
Measured in GiB-month of data stored in your GeoCatalog (original plus derived / optimized forms). Includes any cloud-optimized representations generated by the platform.
37
+
The service measures GiB-month of data stored in your GeoCatalog, including original data and derived or optimized forms. This measurement includes any cloud-optimized representations that the platform generates.
38
38
39
-
### Geospatial Data Operations
39
+
Geospatial storage metrics can take up to six hours to reflect additions or deletions to stored data.
40
40
41
-
Operations are read operations for data that is stored in the managed storage inside a GeoCatalog resource. Common patterns include:
41
+
### Geospatial data operations
42
+
43
+
These operations are read operations for data that the managed storage inside a GeoCatalog resource stores. Common patterns include:
42
44
* Use the SAS API to read stored assets.
43
45
* Use the Data API to render a tile based on managed data.
46
+
*[Ingest new data](./ingestion-overview.md) into a GeoCatalog (this operation happens once).
44
47
45
-
Use of the [STAC API](./stac-overview.md) for querying or searching a catalog isn't considered a read operation.
48
+
Use of the [STAC API](./stac-overview.md) for querying or searching a catalog isn't a read operation.
46
49
50
+
It can take up to two hours for geospatial data operations metrics to reflect new operations.
47
51
48
-
### Ingestion & Transformation
52
+
### Ingestion and transformation
49
53
50
-
A virtual CPU (vCPU) hour reflects how much processing power the service spent on your ingestion job. While data is being ingested and transformed, Microsoft Planetary Computer Pro tracks the CPU time consumed by the workers that run your job inside its managed environment. It adds up every second of CPU usage from those workers, converts the total into hours, and reports that number as vCPU-hours for billing.
54
+
A virtual CPU (vCPU) hour reflects how much processing power the service spends on your ingestion job. While the service ingests and transforms data, Microsoft Planetary Computer Pro tracks the CPU time the workers consume as they run your job inside its managed environment. The service adds up every second of CPU usage from those workers, converts the total into hours, and reports that number as vCPU-hours for billing.
51
55
52
56
To estimate your vCPU-hours, choose a data type similar to the one you plan to ingest:
53
57
@@ -58,20 +62,25 @@ To estimate your vCPU-hours, choose a data type similar to the one you plan to i
58
62
| Aerial Orthomosaic | Non-COG | Orthorectified GeoTIFF mosaic; Three bands (RGB); large tiles | 0.20 |
To estimate your vCPU-hours, select a data type that's similar to the one you plan on ingesting, and multiply the **Representative vCPU-hours/GiB** value by the number of gigabytes of data you intend to ingest.
65
+
To estimate your vCPU-hours, select a data type that's similar to the one you plan to ingest, and multiply the **Representative vCPU-hours/GiB** value by the number of gigabytes of data you intend to ingest.
62
66
63
-
**Example:** Suppose you're ingesting 250 GiB of [National Aerial Imagery Program](./data-visualization-samples.md#the-national-agriculture-imagery-program-collection-configuration) (NAIP) data already in Cloud Optimized GeoTIFF (COG) format. Using the representative value of 0.030 vCPU/GiB from the table:
67
+
**Example:** Suppose you're ingesting 250 GiB of [National Aerial Imagery Program](./data-visualization-samples.md#the-national-agriculture-imagery-program-collection-configuration) (NAIP) data already in Cloud Optimized GeoTIFF (COG) format. Use the representative value of 0.030 vCPU/GiB from the table:
64
68
65
69
250 GiB × 0.030 vCPU/GiB = 7.5 vCPU-hours
66
70
71
+
The ingestion and transformation metric can take up to 2 hours to reflect new activity from ingestion.
67
72
68
73
### Bandwidth
69
74
70
-
Bandwidth is measured in GiB of data that leave the GeoCatalog’s Azure region. This meter increments alongside read [operations](#geospatial-data-operations) whenever data moves to another Azure region or outside of Azure.
75
+
You measure bandwidth in GiB of data that leave the GeoCatalog’s Azure region. This meter increments alongside read [operations](#geospatial-data-operations) whenever data moves to another Azure region or outside of Azure when using the SAS API to read data directly from GeoCatalog managed storage.
76
+
77
+
> [!NOTE]
78
+
> Use of the Data/Tiler API doesn't result in any bandwidth usage.
79
+
71
80
72
81
## Cost management
73
82
74
-
Azure provides tools to help you monitor and manage your spending. You can use[Microsoft Cost Management and Billing](/azure/cost-management-billing/cost-management-billing-overview) to track your Microsoft Planetary Computer Pro usage and costs, set budgets, and receive alerts.
83
+
Azure provides tools to help you monitor and manage your spending. Use[Microsoft Cost Management and Billing](/azure/cost-management-billing/cost-management-billing-overview) to track your Microsoft Planetary Computer Pro usage and costs, set budgets, and receive alerts.
0 commit comments