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/data-visualization-samples.md
+29-16Lines changed: 29 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.custom:
12
12
13
13
# Microsoft Planetary Computer Pro Data Visualization Gallery
14
14
15
-
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.
15
+
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 SpatioTemporal Asset Catalog (STAC) collection metadata that you can adapt for your own datasets.
16
16
17
17
## Table of Contents
18
18
@@ -62,7 +62,7 @@ To apply these examples to your own data:
62
62
63
63
## Mosaic Configuration
64
64
65
-
The mosaic configuration shown below tells the Explorer to display the most recent Sentinel-2 images from the collection, but only those with cloud cover less than or equal to 40%. The cql (Common Query Language) filter ensures that only relatively clear images are included, making the visualization more useful for most applications. Each mosaic entry can define different criteria for selecting and combining images, and this example uses a single "default" mosaic focused on recent, low-cloud imagery.
65
+
This mosaic configuration tells the Explorer to display the most recent Sentinel-2 images from the collection, but only those images with cloud cover less than or equal to 40%. The cql (Common Query Language) filter ensures that only relatively clear images are included, making the visualization more useful for most applications. Each mosaic entry can define different criteria for selecting and combining images, and this example uses a single "default" mosaic focused on recent, low-cloud imagery.
66
66
67
67
```json
68
68
[
@@ -94,25 +94,25 @@ This render configuration defines several ways to visualize Sentinel-2 satellite
94
94
The `options` string specifies how to visualize the data:
95
95
96
96
-`assets=B04&assets=B03&assets=B02`:
97
-
This tells the system which bands (layers of satellite data) to use for the image. For example, B04 is red, B03 is green, and B02 is blue—together, they make a true-color image.
97
+
This code tells the system which bands (layers of satellite data) to use for the image. For example, B04 is red, B03 is green, and B02 is blue—together, they make a true-color image.
98
98
99
99
-`nodata=0`:
100
100
Any pixel with a value of 0 is treated as missing or transparent.
This applies color corrections to make the image look more natural or visually appealing.
103
+
This code applies color corrections to make the image look more natural or visually appealing.
104
104
-**Gamma** adjusts brightness
105
105
-**Saturation** changes color intensity
106
106
-**Sigmoidal** adjusts contrast
107
107
108
108
-`expression=(B08-B04)/(B08+B04)`:
109
-
For NDVI and NDWI, this calculates a mathematical formula using the bands to create a new image that highlights vegetation or moisture.
109
+
For NDVI and NDWI, this code calculates a mathematical formula using the bands to create a new image that highlights vegetation or moisture.
110
110
111
111
-`rescale=-1,1`:
112
-
This stretches the calculated values to fit a color scale, so the results are easy to interpret.
112
+
This code stretches the calculated values to fit a color scale, so the results are easy to interpret.
113
113
114
114
-`colormap_name=rdylgn`:
115
-
This applies a color palette (red-yellow-green) to the result, making it easier to see differences.
115
+
This code applies a color palette (red-yellow-green) to the result, making it easier to see differences.
116
116
117
117
```json
118
118
[
@@ -187,7 +187,7 @@ The `options` string specifies how to visualize the data:
187
187
188
188
## Tile Settings Configuration
189
189
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.
190
+
The tile settings configuration defines how data is tiled and displayed at different zoom levels. For Sentinel-2 data with its 10-60 meter 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 (10 meter for most bands, 20 meter for some bands, 60 meter 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.
191
191
192
192
```json
193
193
{
@@ -207,7 +207,7 @@ The `item_assets` section in the STAC Collection JSON serves as a critical catal
207
207
208
208
* Asset keys (like "B04", "B03") that are referenced by the render configuration
209
209
Metadata about each band (resolution, data type, roles)
210
-
* Band descriptions that explain what each band represents (e.g., B04 is "red", B08 is "near infrared")
210
+
* Band descriptions that explain what each band represents (B04 is "red", B08 is "near infrared")
211
211
* Wavelength information useful for scientific applications
212
212
213
213
The render configuration directly references these asset keys to create different visualizations. For example, when the render configuration specifies `assets=B04&assets=B03&assets=B02`, it's pulling the red, green, and blue bands defined in item_assets to create a natural color image.
@@ -759,8 +759,21 @@ The render configuration directly references these asset keys to create differen
759
759
## The National Agriculture Imagery Program Collection Configuration
760
760
761
761
[](media/naip-imagery.png#lightbox)
762
+
The National Agriculture Imagery Program (NAIP) provides high-resolution aerial imagery across the United States. The USDA Farm Service Agency captures this imagery at least every three years.
762
763
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.
764
+
NAIP data offers excellent detail with spatial resolutions ranging from 0.3 to 1 meter per pixel. The imagery is stored in cloud-optimized GeoTIFF format for efficient access and processing.
765
+
766
+
Each NAIP image contains four spectral bands:
767
+
- Red
768
+
- Green
769
+
- Blue
770
+
- Near-Infrared (NIR)
771
+
772
+
All four bands are stored together as a single multi-band asset. This structure enables several types of analysis:
773
+
774
+
-**Natural color visualization** uses the RGB bands (1-3) to create images that look similar to what the human eye sees
775
+
-**Color infrared analysis** combines NIR, Red, and Green bands to assess vegetation health
776
+
-**NDVI calculations** use the formula (NIR-Red)/(NIR+Red) to measure vegetation density and health
764
777
765
778
## Configuration details
766
779
@@ -806,7 +819,7 @@ Each visualization option uses these bands differently:
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.
866
+
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 low zoom levels, while `maxItemsPerTile: 35` controls how many image tiles are composited together, balancing performance with coverage completeness.
854
867
855
868
856
869
```json
@@ -1078,7 +1091,7 @@ The STAC Collection configuration defines the core metadata for this collection.
1078
1091
1079
1092
[](media/umbra-sar-imagery.png#lightbox)
1080
1093
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.
1094
+
[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 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.
1082
1095
1083
1096
## Configuration details
1084
1097
@@ -1105,7 +1118,7 @@ This is the default mosaic configuration.
1105
1118
1106
1119
The render configuration works as follows:
1107
1120
1108
-
**VV polarization**: Refers to "Vertical transmit, Vertical receive" radar signals, which are effective for detecting man-made structures and surface roughness
1121
+
**VV polarization**: Refers to "Vertical transmit, Vertical receive" radar signals, which are effective for detecting artificial structures and surface roughness
1109
1122
1110
1123
***Key parameters**:
1111
1124
*`assets=GEC`: Selects the geocoded ellipsoid corrected (GEC) asset from the STAC item
@@ -1140,7 +1153,7 @@ This configuration creates a grayscale visualization where brighter areas repres
1140
1153
# [Tile Settings](#tab/umbra-sar-tile-settings)
1141
1154
1142
1155
## Tile Settings Configuration
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.
1156
+
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.48 meter GSD), the `minZoom: 12` setting reflects the high-resolution nature of this dataset. SAR data at this resolution provides 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 detailed data at zoom levels where the resolution advantage wouldn't be apparent to users.
1144
1157
1145
1158
```json
1146
1159
{
@@ -1163,7 +1176,7 @@ This section tells us:
1163
1176
2.**Data Format**: The asset is a cloud-optimized GeoTIFF, which allows efficient access to portions of the imagery
1164
1177
1165
1178
3.**Radar Properties**:
1166
-
- This is VV polarization data (vertical transmit, vertical receive)
1179
+
- This image contains VV polarization data (vertical transmit, vertical receive)
1167
1180
- Contains terrain-corrected gamma naught values with radiometric correction
0 commit comments