Skip to content

Commit

Permalink
doc updates for changing UI
Browse files Browse the repository at this point in the history
  • Loading branch information
nreese committed Dec 10, 2019
1 parent b635c45 commit e6be3e4
Show file tree
Hide file tree
Showing 4 changed files with 13 additions and 11 deletions.
Binary file added docs/maps/images/top_hits.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
5 changes: 0 additions & 5 deletions docs/maps/indexing-geojson-data-tutorial.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -101,11 +101,6 @@ aggregation.
The remaining default settings are good, but there are a couple of
settings that you might want to change.

. Under *Source settings* > *Grid resolution*, select from the different heat map resolutions.
+
The default "Coarse" looks
good, but feel free to select a different resolution.

. Play around with the *Layer Style* >
*Color range* setting.
+
Expand Down
17 changes: 12 additions & 5 deletions docs/maps/maps-aggregations.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -34,18 +34,25 @@ The point location is the weighted centroid for all geo-points in the gridded ce

[role="xpack"]
[[maps-top-hits-aggregation]]
=== Most recent entities
=== Most relevant entities

Most recent entities uses {es} {ref}/search-aggregations-bucket-terms-aggregation.html[terms aggregation] to group your documents by entity.
Then, {ref}/search-aggregations-metrics-top-hits-aggregation.html[top hits metric aggregation] accumulates the most recent documents for each entry.
Use most relevent entities to display documents per entity.
For example, you can use most relevent entities to show the most recent GPS tracks per flight callsign.

Most recent entities is available for <<vector-layer, vector layers>> with *Documents* source.
To enable most recent entities, click "Show most recent documents by entity" and configure the following:
Most relevant entities uses {es} {ref}/search-aggregations-bucket-terms-aggregation.html[terms aggregation] to group your documents by entity.
Then, {ref}/search-aggregations-metrics-top-hits-aggregation.html[top hits metric aggregation] accumulates the most relevant documents for each entry.

Most relevant entities is available for <<vector-layer, vector layers>> with *Documents* source.
To enable most relevant entities:

. In *Sorting*, check the *Show documents per entity* checkbox.
. Set *Entity* to the field that identifies entities in your documents.
This field will be used in the terms aggregation to group your documents into entity buckets.
. Set *Documents per entity* to configure the maximum number of documents accumulated per entity.

[role="screenshot"]
image::maps/images/top_hits.gif[]

[role="xpack"]
[[point-to-point]]
=== Point to point
Expand Down
2 changes: 1 addition & 1 deletion docs/maps/search.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ The most common cause for empty layers are searches for a field that exists in o

You can prevent the search bar from applying search context to a layer by configuring the following:

* In *Source settings*, clear the *Apply global filter to source* checkbox to turn off the global search context for the layer source.
* In *Filtering*, clear the *Apply global filter to layer data* checkbox to turn off the global search context for the layer source.

* In *Term joins*, clear the *Apply global filter to join* checkbox to turn off the global search context for the <<terms-join, term join>>.

Expand Down

0 comments on commit e6be3e4

Please sign in to comment.