Skip to content

Commit 6e8306c

Browse files
author
pcoma55
committed
commitring most recent updates
1 parent eaedcc0 commit 6e8306c

File tree

1 file changed

+20
-17
lines changed

1 file changed

+20
-17
lines changed

articles/planetary-computer/data-visualization-samples.md

Lines changed: 20 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,14 @@ ms.custom:
1414

1515
This gallery provides ready-to-use configuration examples for visualizing common geospatial data types in Microsoft Planetary Computer Pro. Each example includes comprehensive JSON configurations for mosaics, render options, tile settings, and STAC collection metadata that you can adapt for your own datasets.
1616

17+
## Table of Contents
18+
19+
- [Prerequisites](#prerequisites)
20+
- [How to use these examples](#how-to-use-these-examples)
21+
- [Sentinel-2-l2a Multi-Spectral Imagery](#sentinel-2-l2a-collection-configuration)
22+
- [The National Agriculture Imagery Program Aerial Imagery](#the-national-agriculture-imagery-program-collection-configuration)
23+
- [Umbra Synthetic Aperture Radar Imagery](#umbra-sar-imagery-collection-configuration)
24+
1725
## Prerequisites
1826

1927
Before using these examples, you should have:
@@ -36,11 +44,11 @@ Each example in this gallery includes:
3644

3745
To apply these examples to your own data:
3846

39-
1. Create a new collection in your GeoCatalog
40-
2. Navigate to the collection's configuration page
47+
1. [Create a new collection](./create-collection-web-interface.md) in your GeoCatalog
48+
2. Navigate to the [collection's configuration](./configure-collection-web-interface.md) page
4149
3. Modify the example JSON to match your dataset's specific bands, assets, and properties
4250
4. Apply the configurations to your collection
43-
5. View the results in the Explorer
51+
5. View the results in the [Explorer](./use-explorer.md)
4452

4553
## Sentinel-2-l2a Collection Configuration
4654

@@ -179,7 +187,7 @@ The `options` string specifies how to visualize the data:
179187

180188
## Tile Settings Configuration
181189

182-
The tile settings configuration defines how data is tiled and displayed at different zoom levels.
190+
The tile settings configuration defines how data is tiled and displayed at different zoom levels. For Sentinel-2 data with its 10-60m ground sample distance (GSD), the `minZoom: 8` setting allows the imagery to become visible at moderate zoom levels, which is appropriate since Sentinel-2's resolution (10m for most bands, 20m for some bands, 60m for atmospheric bands) provides useful detail starting around zoom levels 8-12. Unlike sub-meter imagery that requires higher zoom levels for effective viewing, Sentinel-2's moderate resolution makes it suitable for regional to local-scale analysis. The `maxItemsPerTile: 35` parameter controls how many individual Sentinel-2 scenes are composited together in each tile, balancing performance with temporal coverage completeness.
183191

184192
```json
185193
{
@@ -748,21 +756,19 @@ The render configuration directly references these asset keys to create differen
748756
---
749757

750758

751-
## naip-airports Collection Configuration
752-
753-
[Collection description to be added here]
759+
## The National Agriculture Imagery Program Collection Configuration
754760

755-
[ ![Screenshot of naip-airports data visualization](media/naip-imagery.png) ](media/naip-imagery.png#lightbox)
761+
[ ![Screenshot of The National Agriculture Imagery Program data visualization](media/naip-imagery.png) ](media/naip-imagery.png#lightbox)
756762

757-
[Description of data source and link to where to get the data]
763+
The National Agriculture Imagery Program (NAIP) provides high-resolution aerial imagery captured by the USDA Farm Service Agency at least every three years across the United States. NAIP data consists of 4-band imagery stored in cloud-optimized GeoTIFF format with spatial resolutions ranging from 0.3 to 1 meter per pixel. Each image contains Red, Green, Blue, and Near-Infrared (NIR) bands stored as a single multi-band asset, enabling natural color visualization (RGB bands 1-3), color infrared analysis for vegetation health (NIR-Red-Green), and calculated indices like NDVI using the formula (NIR-Red)/(NIR+Red) to assess vegetation density and health.
758764

759765
## Configuration details
760766

761767
# [Mosaic](#tab/naip-airports-mosaics)
762768

763769
## Mosaic Configuration
764770

765-
The mosaic configuration defines how images are combined when displayed in the Explorer.
771+
The mosaic configuration defines how images are combined when displayed in the Explorer, this collection uses the default settings.
766772

767773
```json
768774
[
@@ -779,7 +785,7 @@ The mosaic configuration defines how images are combined when displayed in the E
779785

780786
## Render Options Configuration
781787

782-
This render configuration offers three different ways to visualize the National Agriculture Imagery Program (NAIP) data. NAIP imagery contains four spectral bands stored in a single multi-band asset called "image":
788+
This render configuration offers three different ways to visualize the NAIP data. NAIP imagery contains four spectral bands stored in a single multi-band asset called "image":
783789

784790
1. **Band 1**: Red
785791
2. **Band 2**: Green
@@ -844,8 +850,8 @@ Each visualization option uses these bands differently:
844850
# [Tile Settings](#tab/naip-airports-tile-settings)
845851

846852
## Tile Settings Configuration
853+
The tile settings configuration defines how data is tiled and displayed at different zoom levels. For high-resolution imagery like NAIP (0.3-1m GSD), appropriate zoom level settings are critical for performance and visual quality. Generally, imagery should become visible around zoom level 12-14 for meter-class data, with sub-meter imagery like NAIP (0.3-0.6m GSD) becoming useful at zoom levels 15-18. The `minZoom: 4` setting here allows the data to be visible at very low zoom levels, while `maxItemsPerTile: 35` controls how many image tiles are composited together, balancing performance with coverage completeness.
847854

848-
The tile settings configuration defines how data is tiled and displayed at different zoom levels.
849855

850856
```json
851857
{
@@ -1070,11 +1076,9 @@ The STAC Collection configuration defines the core metadata for this collection.
10701076

10711077
## Umbra SAR Imagery Collection Configuration
10721078

1073-
[Collection description to be added here]
1074-
10751079
[ ![Screenshot of Umbra SAR Imagery data visualization](media/umbra-sar-imagery.png) ](media/umbra-sar-imagery.png#lightbox)
10761080

1077-
[Description of data source and link to where to get the data]
1081+
[Umbra's Synthetic Aperture Radar (SAR) imagery](https://umbra.space/open-data/) uses radar signals transmitted from satellites to create high-resolution images of the Earth's surface, capable of seeing through clouds, darkness, and weather conditions that would block traditional optical satellites. This technology is particularly valuable for monitoring infrastructure, detecting changes in urban areas, tracking ships and vehicles, and assessing damage after natural disasters, as it can capture detailed images at any time of day or night regardless of weather conditions.
10781082

10791083
## Configuration details
10801084

@@ -1136,8 +1140,7 @@ This configuration creates a grayscale visualization where brighter areas repres
11361140
# [Tile Settings](#tab/umbra-sar-tile-settings)
11371141

11381142
## Tile Settings Configuration
1139-
1140-
The tile settings configuration defines how data is tiled and displayed at different zoom levels.
1143+
The tile settings configuration defines how data is tiled and displayed at different zoom levels. For SAR imagery like Umbra's sub-meter resolution data (approximately 0.48m GSD), the `minZoom: 12` setting reflects the high-resolution nature of this dataset. SAR data at this resolution provides extremely detailed views of surface features, making it most useful at higher zoom levels where individual buildings, vehicles, and infrastructure elements become clearly distinguishable. The higher minimum zoom level ensures optimal performance and prevents unnecessary processing of very detailed data at zoom levels where the resolution advantage wouldn't be apparent to users.
11411144

11421145
```json
11431146
{

0 commit comments

Comments
 (0)