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: docs/user-guides/c-types-of-layers/n-raster-tile-layer.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,16 +6,28 @@ Use Raster Tile layer to visualize satellite/aerial imagery from raster pmtiles
6
6
2. Select Raster Tile tileset type.
7
7
3. Paste URL to the tileset:
8
8
- pmtiles (raster format): provide a direct HTTPS URL to a .pmtiles file containing raster imagery. Raster pmtiles don't require dedicated raster tile servers, unless you want to use elevation meshes.
9
-
- STAC Item/Collection (COGs): provide a HTTPS URL to a STAC Item or Collection (v1.0.0+ with EO + Raster extensions). For this option you need to provide a [compatible raster tile server](https://github.com/igorDykhta/kepler-raster-server).
9
+
- COG (.tif): provide a direct HTTPS URL to a Cloud Optimized GeoTIFF. The public [TiTiler](https://titiler.xyz) service is used automatically for metadata and tile serving. Elevation is not supported in this mode.
10
+
- STAC Item/Collection (COGs): provide a HTTPS URL to a STAC Item or Collection. Both STAC 1.0.x (with EO + Raster extensions) and STAC 1.1.0+ (with core `bands`) are supported. For this option you need to provide a [compatible raster tile server](https://github.com/igorDykhta/kepler-raster-server).
10
11
4. Click Add.
11
12
5. Style band selection and opacity as needed in Layers panel.
12
13
13
14
Important notes for COGs via STAC:
14
15
15
-
- The STAC Item/Collection must include EO and Raster extensions with `eo:bands` and `raster:bands` .
16
+
-**STAC 1.0.x:** The STAC Item/Collection must include EO and Raster extensions with `eo:bands` and `raster:bands`.
17
+
-**STAC 1.1.0+:** Items using the core `bands` field (where band metadata lives directly on each asset instead of separate `eo:bands`/`raster:bands` extensions) are also supported. Each band object should include `data_type` and optionally `eo:common_name` and `statistics`.
18
+
- Both formats can coexist within a single STAC item (some assets using legacy extensions, others using core `bands`).
16
19
- COG assets must be publicly accessible over HTTPS.
17
20
- You must run your own raster tile server (e.g., TiTiler). Example implementation that supports collections and elevations: [kepler-raster-server](https://github.com/igorDykhta/kepler-raster-server).
18
21
22
+
# Loading standalone COG (.tif) files
23
+
24
+
You can load a Cloud Optimized GeoTIFF directly by pasting its URL (ending in `.tif` or `.tiff`) into the "Tileset metadata URL" field. When a COG URL is detected, kepler.gl automatically fetches STAC metadata from the public [TiTiler](https://titiler.xyz) service (`/cog/stac` endpoint) and sets `https://titiler.xyz` as the raster tile server.
25
+
26
+
-**No self-hosted server required** — the public TiTiler instance handles both metadata and tile serving.
27
+
-**Elevation is not available** when using the public TiTiler service.
28
+
- The COG file must be publicly accessible over HTTPS.
29
+
- If the "Raster tile servers" field is empty when you paste a `.tif` URL, it will be auto-filled with `https://titiler.xyz`.
30
+
19
31
# Elevation
20
32
21
33
To enable elevation rendering, you must provide one or more compatible raster tile servers when adding the tileset. Enter them in the "Raster tile servers" field of the Add Tileset form.
0 commit comments