mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
* [skip-ci][Maps] Point to point source docs * review feedback
This commit is contained in:
parent
659f711569
commit
5161203529
4 changed files with 18 additions and 3 deletions
BIN
docs/maps/images/point_to_point.png
Normal file
BIN
docs/maps/images/point_to_point.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 1,006 KiB |
|
@ -40,6 +40,18 @@ This field will be used in the terms aggregation to group your documents into en
|
|||
This field will be used to sort your documents in the top hits aggregation.
|
||||
. Set *Documents per entity* to configure the maximum number of documents accumulated per entity.
|
||||
|
||||
[role="xpack"]
|
||||
[[point-to-point]]
|
||||
=== Point to point
|
||||
|
||||
A point-to-point connection plots aggregated data paths between the source and the destination.
|
||||
Thicker, darker lines symbolize more connections between a source and destination, and thinner, lighter lines symbolize less connections.
|
||||
|
||||
Point to point uses an {es} {ref}/search-aggregations-bucket-terms-aggregation.html[terms aggregation] to group your documents by destination.
|
||||
Then, a nested {ref}/search-aggregations-bucket-geotilegrid-aggregation.html[GeoTile grid aggregation] groups sources for each destination into grids.
|
||||
A line connects each source grid centroid to each destination.
|
||||
|
||||
image::maps/images/point_to_point.png[]
|
||||
|
||||
[role="xpack"]
|
||||
[[terms-join]]
|
||||
|
@ -49,9 +61,9 @@ Use term joins to augment vector features with properties for <<maps-vector-styl
|
|||
|
||||
Term joins are available for <<vector-layer, vector layers>> with the following sources:
|
||||
|
||||
* Custom vector shapes
|
||||
* Configured GeoJSON
|
||||
* Documents
|
||||
* Vector shapes
|
||||
* EMS Boundaries
|
||||
|
||||
==== Example term join
|
||||
|
||||
|
|
|
@ -34,7 +34,7 @@ You can create two types of filters by interacting with your map:
|
|||
[[maps-spatial-filters]]
|
||||
==== Spatial filters
|
||||
|
||||
A spatial filter narrow searchs results to documents that either intersect with, are within, or do not intersect with the specified geometry.
|
||||
A spatial filter narrows search results to documents that either intersect with, are within, or do not intersect with the specified geometry.
|
||||
|
||||
You can create spatial filters in two ways:
|
||||
|
||||
|
|
|
@ -24,5 +24,8 @@ The index must contain at least one field mapped as {ref}/geo-point.html[geo_poi
|
|||
|
||||
*EMS Boundaries*:: Administrative boundaries from https://www.elastic.co/elastic-maps-service[Elastic Maps Service].
|
||||
|
||||
*Point to point*:: Aggregated data paths between the source and destination.
|
||||
The index must contain at least 2 fields mapped as {ref}/geo-point.html[geo_point], source and destination.
|
||||
|
||||
include::vector-style.asciidoc[]
|
||||
include::vector-style-properties.asciidoc[]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue