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
Arc layers draw an arc between two points. They’re useful for visualizing the distance between two points as well as comparing distances in 3D. Note that arc layers don’t show routes between points, but simply the distance between the two points. The tallest arc represents the greatest distance.
16
18
@@ -20,90 +22,94 @@ Layer Attributes: Color/ Color Based On, Opacity, Stroke Width/ Stroke Based On,
Line layers are the 2D version of arc layers. Both draw a line between two points to represent distance, but in a line layer, the drawing lies flat on the map.
26
28
27
29
Layer Attributes: Color, Stroke, High Precision Rendering
Hexbin aggregates points into hexagons. The counts can be represented through color and/or height.
34
36
35
37
Layer Attributes: Color/ Color Based On, Filter by Count Percentile, Opacity, Hexagon Radius (km), Coverage (Radius), Enable Height, Elevation Scale/ Height Based On, High Precision Rendering
Icon layers are a type of point layer. They allow you to differentiate between points by assigning icons to points based on a field. For example, you might use icons to differentiate between types of venues and points of interest.
58
60
59
61
Layer Attributes: Color, Radius, Label, High Precision Rendering
60
62
61
63
To see the icon menu, create a new icon layer and click how to draw an icon layer:
62
64
63
-
![How to Draw Icon Layer](https://d1a3f4spazzrp4.cloudfront.net/kepler.gl/documentation/image38.png"How to Draw Icon Layer")
65
+
Grids layers are similar to heatmaps. They show the density of points. They provide visual discrepancy in a map where multiple heatmap-style layers are present.
71
73
72
74
Layer Attributes: Color, Radius, Height, High Precision Rendering
GeoJSON layers can display either paths, polygons or points. For example, a path GeoJSON layer can display data like trip routes. A polygon GeoJSON layer is essentially a [choropleth](https://en.wikipedia.org/wiki/Choropleth_map) layer and works best for rendering geofences. To add a GeoJSON layer, your dataset must contain geometry data.
H3 layers visualize spatial data using [H3 Hexagonal Hierarchical Spatial Index](https://eng.uber.com/h3/).
86
88
87
89
To use H3 layer, you need a `hex_id` in your dataset, which can be generated using [h3-js](https://github.com/uber/h3-js) from latitude, longitude and resolution.
Vector Tile Layer makes it possible to visualize very large datasets through MVTs (Mapbox Vector Tiles). To optimize performance, the layer only loads and renders tiles containing features that are visible within the current viewport.
Raster layers are used to show satellite and aerial imagery. They allow you to work interactively directly with massive, image collections stored in .pmtiles (in raster format) or Cloud Optimized GeoTIFF format.
109
115
@@ -112,7 +118,41 @@ Supported URL templates:
112
118
- Users can reference remote **.pmtiles files in raster format** for raster layers by supplying a direct link to the file.
113
119
114
120
-**Cloud-Optimized GeoTIFFs (COG)** can also be used in raster layers by providing standardized Spatio-Temporal Asset Catalog (STAC) metadata.
115
-
- The metadata file must be a valid *STAC Item* or *STAC Collection*, version 1.0.0 or higher.
116
-
- Raster data referenced in STAC assets should be Cloud-Optimized GeoTIFFs and need to be publicly accessible via HTTPS.
117
-
- STAC item and collections *must have Electro-Optical and Raster extensions*, and at least one asset must have both eo:bands and raster:bands information. common_name must be provided in eo:bands and data_type must be provided in raster:bands.
118
-
- Users must use their own instances of raster tile servers, such as Titiler. [TODO: add instructions]
121
+
122
+
- The metadata file must be a valid _STAC Item_ or _STAC Collection_, version 1.0.0 or higher.
123
+
- Raster data referenced in STAC assets should be Cloud-Optimized GeoTIFFs and need to be publicly accessible via HTTPS.
124
+
- STAC item and collections _must have Electro-Optical and Raster extensions_, and at least one asset must have both eo:bands and raster:bands information. common_name must be provided in eo:bands and data_type must be provided in raster:bands.
125
+
- To use COGs with STAC metadata, you must run your own raster tile server (e.g., TiTiler). Example implementation: [kepler-raster-server](https://github.com/igorDykhta/kepler-raster-server).
- Web Map Service (WMS) layers render raster tiles from OGC WMS servers.
146
+
- This feature is experimental and disabled by default. To try it, enable `enableWMSLayer: true` in the application configuration.
147
+
- When enabled, add a WMS service via the Tilesets modal by providing the service URL and selecting a named layer. Feature info on click is supported for queryable layers.
Currently trip layer support a special `geoJSON` format where the coordinate `linestring` has a 4th element denoting timestamp.
11
11
12
-
In order to animate the path, the `geoJSON` data needs to contain `LineString` in its features' geometry, and the coordinates in the `LineString` need to have 4 elements in the format of `[longitude, latitude, altitude, timestamp]`, with the last element being a timestamp. Valid timestamp formats include unix in seconds such as `1564184363` or in milliseconds such as `1564184363000`.
12
+
In order to animate the path, the `geoJSON` data needs to contain `LineString` in its features' geometry, and the coordinates in the `LineString` need to have 4 elements in the format of `[longitude, latitude, altitude, timestamp]`, with the last element being a timestamp. Valid timestamp formats include unix in seconds such as `1564184363` or in milliseconds such as `1564184363000`.
Use Raster Tile layer to visualize satellite/aerial imagery from raster pmtiles or COGs via STAC metadata.
4
+
5
+
1. Open Add Data → Tilesets.
6
+
2. Select Raster Tile tileset type.
7
+
3. Paste URL to the tileset:
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).
10
+
4. Click Add.
11
+
5. Style band selection and opacity as needed in Layers panel.
12
+
13
+
Important notes for COGs via STAC:
14
+
15
+
- The STAC Item/Collection must include EO and Raster extensions with `eo:bands` and `raster:bands` .
16
+
- COG assets must be publicly accessible over HTTPS.
17
+
- 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
+
19
+
# Elevation
20
+
21
+
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.
22
+
23
+
- For STAC Items/Collections: compatible raster tile servers are required.
24
+
- For raster .pmtiles: raster tile servers are optional for imagery, but required if you plan to use elevation.
25
+
- The server must expose COGs as XYZ tiles and support elevation/DEM tiles. Example implementation: [kepler-raster-server](https://github.com/igorDykhta/kepler-raster-server) (TiTiler-based).
26
+
27
+
Example Raster .pmtiles:
28
+
29
+
- Mount Whitney - https://pmtiles.io/usgs-mt-whitney-8-15-webp-512.pmtiles
0 commit comments