mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
[DOCS] Updates titles in Maps docs (#68703)
* [DOCS] Updates titles in Maps docs * [DOCS] Changes Elastic Maps to Maps to match the UI * [DOCS] Fixes titles Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This commit is contained in:
parent
208b580061
commit
e04624ace0
15 changed files with 67 additions and 49 deletions
|
@ -1,17 +1,17 @@
|
|||
[role="xpack"]
|
||||
[[maps-connect-to-ems]]
|
||||
== Connecting to Elastic Maps Service
|
||||
== Connect to Elastic Maps Service
|
||||
|
||||
https://www.elastic.co/elastic-maps-service[Elastic Maps Service (EMS)] is a service that hosts
|
||||
tile layers and vector shapes of administrative boundaries.
|
||||
If you are using Kibana's out-of-the-box settings, **Elastic Maps** is already configured to use EMS.
|
||||
If you are using Kibana's out-of-the-box settings, Maps is already configured to use EMS.
|
||||
|
||||
EMS requests are made to the following domains:
|
||||
|
||||
* tiles.maps.elastic.co
|
||||
* vector.maps.elastic.co
|
||||
|
||||
**Elastic Maps** makes requests directly from the browser to EMS.
|
||||
Maps makes requests directly from the browser to EMS.
|
||||
|
||||
[float]
|
||||
=== Connect to Elastic Maps Service from an internal network
|
||||
|
@ -33,5 +33,5 @@ behind a firewall. If this happens, you can disable the EMS connection to avoid
|
|||
To disable EMS, change your <<settings, kibana.yml>> file.
|
||||
|
||||
. Set `map.includeElasticMapsService` to `false` to turn off the EMS connection.
|
||||
. Set `map.tilemap.url` to the URL of your tile server. This configures the default tile layer of **Elastic Maps**.
|
||||
. Set `map.tilemap.url` to the URL of your tile server. This configures the default tile layer of Maps.
|
||||
. (Optional) Set `map.regionmap` to the vector shapes of the administrative boundaries that you want to use.
|
||||
|
|
|
@ -1,11 +1,13 @@
|
|||
[role="xpack"]
|
||||
[[geojson-upload]]
|
||||
== Upload GeoJSON data
|
||||
*Elastic Maps* makes it easy to import geospatial data into the Elastic Stack.
|
||||
Using the *GeoJSON Upload* feature, you can drag and drop your point and shape
|
||||
|
||||
Maps makes it easy to import geospatial data into the Elastic Stack.
|
||||
Using the GeoJSON Upload feature, you can drag and drop your point and shape
|
||||
data files directly into {es}, and then use them as layers
|
||||
in the map. You can also use the GeoJSON data in the broader Kibana ecosystem,
|
||||
for example, in visualizations and Canvas workpads.
|
||||
|
||||
[float]
|
||||
=== Why GeoJSON?
|
||||
GeoJSON is an open-standard file format for storing geospatial vector data.
|
||||
|
@ -17,7 +19,7 @@ GeoJSON is the most commonly used and flexible option.
|
|||
Follow these instructions to upload a GeoJSON data file, or try the
|
||||
<<indexing-geojson-data-tutorial, end-to-end integrated example>>.
|
||||
|
||||
. Open the menu, go to *Elastic Maps*, and then click *Add layer*.
|
||||
. Open the menu, go to *Maps*, and then click *Add layer*.
|
||||
. Click *Uploaded GeoJSON*.
|
||||
+
|
||||
[role="screenshot"]
|
||||
|
|
|
@ -1,13 +1,13 @@
|
|||
[role="xpack"]
|
||||
[[maps]]
|
||||
= Elastic Maps
|
||||
= Maps
|
||||
|
||||
[partintro]
|
||||
--
|
||||
|
||||
*Elastic Maps* enables you to parse through your geographical data at scale, with speed, and in real time. With features like multiple layers and indices in a map, plotting of raw documents, dynamic client-side styling, and global search across multiple layers, you can understand and monitor your data with ease.
|
||||
Maps enables you to parse through your geographical data at scale, with speed, and in real time. With features like multiple layers and indices in a map, plotting of raw documents, dynamic client-side styling, and global search across multiple layers, you can understand and monitor your data with ease.
|
||||
|
||||
With *Elastic Maps*, you can:
|
||||
With Maps, you can:
|
||||
|
||||
* Create maps with multiple layers and indices.
|
||||
* Upload GeoJSON files into Elasticsearch.
|
||||
|
@ -15,7 +15,7 @@ With *Elastic Maps*, you can:
|
|||
* Symbolize features using data values.
|
||||
* Focus in on just the data you want.
|
||||
|
||||
*Ready to get started?* Start your tour of *Elastic Maps* with the <<maps-getting-started, getting started tutorial>>.
|
||||
*Ready to get started?* Start your tour of Maps with the <<maps-getting-started, getting started tutorial>>.
|
||||
|
||||
[float]
|
||||
=== Create maps with multiple layers and indices
|
||||
|
@ -26,7 +26,7 @@ image::maps/images/sample_data_ecommerce.png[]
|
|||
|
||||
[float]
|
||||
=== Upload GeoJSON files into Elasticsearch
|
||||
Elastic Maps makes it easy to import geospatial data into the Elastic Stack. Using the GeoJSON Upload feature, you can drag and drop your point and shape data files directly into Elasticsearch, and then use them as layers in the map.
|
||||
Maps makes it easy to import geospatial data into the Elastic Stack. Using the GeoJSON Upload feature, you can drag and drop your point and shape data files directly into Elasticsearch, and then use them as layers in the map.
|
||||
|
||||
[float]
|
||||
=== Embed your map in dashboards
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
[role="xpack"]
|
||||
[[indexing-geojson-data-tutorial]]
|
||||
== Indexing GeoJSON data tutorial
|
||||
=== Tutorial: Index GeoJSON data
|
||||
|
||||
In this tutorial, you'll build a customized map that shows the flight path between
|
||||
two airports, and the lightning hot spots on that route. You'll learn to:
|
||||
|
@ -15,7 +15,7 @@ two airports, and the lightning hot spots on that route. You'll learn to:
|
|||
This tutorial requires you to download the following GeoJSON sample data files.
|
||||
These files are good examples of the types
|
||||
of vector data that you can upload to Kibana and index in
|
||||
Elasticsearch for display in *Elastic Maps*.
|
||||
Elasticsearch for display in Maps.
|
||||
|
||||
* https://raw.githubusercontent.com/elastic/examples/master/Maps/Getting%20Started%20Examples/geojson_upload_and_styling/logan_international_airport.geojson[Logan International Airport]
|
||||
* https://raw.githubusercontent.com/elastic/examples/master/Maps/Getting%20Started%20Examples/geojson_upload_and_styling/bangor_international_airport.geojson[Bangor International Airport]
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
[role="xpack"]
|
||||
[[maps-settings]]
|
||||
== Map settings
|
||||
== Configure map settings
|
||||
|
||||
Elastic Maps offers settings that let you configure how a map is displayed.
|
||||
Maps offers settings that let you configure how a map is displayed.
|
||||
To access these settings, click *Map settings* in the application toolbar.
|
||||
|
||||
[float]
|
||||
|
|
|
@ -2,6 +2,11 @@
|
|||
[[maps-aggregations]]
|
||||
== Plot big data without plotting too much data
|
||||
|
||||
++++
|
||||
<titleabbrev>Plot big data</titleabbrev>
|
||||
++++
|
||||
|
||||
|
||||
Use {ref}/search-aggregations.html[aggregations] to plot large data sets without overwhelming your network or your browser.
|
||||
When using aggregations, the documents stay in Elasticsearch and only the calculated values for each group are returned to your computer.
|
||||
|
||||
|
@ -37,7 +42,7 @@ image::maps/images/grid_to_docs.gif[]
|
|||
[[maps-grid-aggregation]]
|
||||
=== Grid aggregation
|
||||
|
||||
*Grid aggregation* layers use {ref}/search-aggregations-bucket-geotilegrid-aggregation.html[GeoTile grid aggregation] to group your documents into grids. You can calculate metrics for each gridded cell.
|
||||
Grid aggregation layers use {ref}/search-aggregations-bucket-geotilegrid-aggregation.html[GeoTile grid aggregation] to group your documents into grids. You can calculate metrics for each gridded cell.
|
||||
|
||||
Symbolize grid aggregation metrics as:
|
||||
|
||||
|
@ -213,7 +218,7 @@ The following shows an example terms aggregation response. Note the *key* proper
|
|||
}
|
||||
--------------------------------------------------
|
||||
|
||||
==== Augmenting the left source with metrics from the right source
|
||||
==== Augment the left source with metrics from the right source
|
||||
|
||||
The join adds metrics for each terms aggregation bucket to the world country feature with the corresponding ISO 3166-1 alpha-2 code. Features that do not have a corresponding terms aggregation bucket are not visible on the map.
|
||||
|
||||
|
|
|
@ -1,8 +1,14 @@
|
|||
[role="xpack"]
|
||||
[[maps-getting-started]]
|
||||
== Getting started with Elastic Maps
|
||||
== Get started with Maps
|
||||
|
||||
You work with *Elastic Maps* by adding layers. The data for a layer can come from
|
||||
++++
|
||||
<titleabbrev>Get started</titleabbrev>
|
||||
++++
|
||||
|
||||
|
||||
|
||||
You work with Maps by adding layers. The data for a layer can come from
|
||||
sources such as {es} documents, vector sources, tile map services, web map
|
||||
services, and more. You can symbolize the data in different ways.
|
||||
For example, you might show which airports have the longest flight
|
||||
|
@ -25,7 +31,7 @@ image::maps/images/read-only-badge.png[Example of Maps' read only access indicat
|
|||
[float]
|
||||
=== Prerequisites
|
||||
Before you start this tutorial, <<add-sample-data, add the web logs sample data set>>. Each
|
||||
sample data set includes a map to go along with the data. Once you've added the data, open *Elastic Maps* and
|
||||
sample data set includes a map to go along with the data. Once you've added the data, open Maps and
|
||||
explore the different layers of the *[Logs] Total Requests and Bytes* map.
|
||||
You'll re-create this map in this tutorial.
|
||||
|
||||
|
@ -40,7 +46,7 @@ In this tutorial, you'll learn to:
|
|||
|
||||
[role="xpack"]
|
||||
[[maps-create]]
|
||||
=== Creating a new map
|
||||
=== Create a map
|
||||
|
||||
The first thing to do is to create a new map.
|
||||
|
||||
|
@ -55,7 +61,7 @@ image::maps/images/gs_create_new_map.png[]
|
|||
|
||||
[role="xpack"]
|
||||
[[maps-add-choropleth-layer]]
|
||||
=== Adding a choropleth layer
|
||||
=== Add a choropleth layer
|
||||
|
||||
Now that you have a map, you'll want to add layers to it.
|
||||
The first layer you'll add is a choropleth layer to shade world countries
|
||||
|
@ -106,7 +112,7 @@ image::maps/images/gs_add_cloropeth_layer.png[]
|
|||
|
||||
[role="xpack"]
|
||||
[[maps-add-elasticsearch-layer]]
|
||||
=== Adding layers for {es} data
|
||||
=== Add layers for the {es} data
|
||||
|
||||
To avoid overwhelming the user with too much data at once, you'll add two layers for {es} data.
|
||||
|
||||
|
@ -183,7 +189,7 @@ image::maps/images/sample_data_web_logs.png[]
|
|||
|
||||
[role="xpack"]
|
||||
[[maps-save]]
|
||||
=== Saving the map
|
||||
=== Save the map
|
||||
Now that your map is complete, you'll want to save it so others can use it.
|
||||
|
||||
. In the application toolbar, click *Save*.
|
||||
|
@ -202,7 +208,7 @@ You have completed the steps for re-creating the sample data map.
|
|||
|
||||
[role="xpack"]
|
||||
[[maps-embedding]]
|
||||
=== Adding the map to a dashboard
|
||||
=== Add the map to a dashboard
|
||||
You can add your saved map to a {kibana-ref}/dashboard.html[dashboard] and view your geospatial data alongside bar charts, pie charts, and other visualizations.
|
||||
|
||||
. Open the menu, then go to *Dashboard*.
|
||||
|
@ -224,7 +230,7 @@ Your dashboard should look like this:
|
|||
[role="screenshot"]
|
||||
image::maps/images/gs_dashboard_with_map.png[]
|
||||
|
||||
==== Exploring your data using filters
|
||||
==== Explore your data using filters
|
||||
|
||||
You can apply filters to your dashboard to hone in on the data that you are most interested in.
|
||||
The dashboard is interactive--you can quickly create filters by clicking on the desired data in the map and visualizations.
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
[role="xpack"]
|
||||
[[maps-search]]
|
||||
== Searching your data
|
||||
== Search geographic data
|
||||
|
||||
**Elastic Maps** embeds the search bar for real-time search.
|
||||
Maps embeds the search bar for real-time search.
|
||||
Only layers requesting data from {es} are filtered when you submit a search request.
|
||||
Layers narrowed by the search context contain the filter icon image:maps/images/filter_icon.png[] next to the layer name in the legend.
|
||||
|
||||
|
@ -23,7 +23,7 @@ image::maps/images/global_search_bar.png[]
|
|||
|
||||
[role="xpack"]
|
||||
[[maps-create-filter-from-map]]
|
||||
=== Creating filters from your map
|
||||
=== Create filters from a map
|
||||
|
||||
You can create two types of filters by interacting with your map:
|
||||
|
||||
|
@ -62,7 +62,7 @@ image::maps/images/create_phrase_filter.png[]
|
|||
|
||||
[role="xpack"]
|
||||
[[maps-layer-based-filtering]]
|
||||
=== Filtering a single layer
|
||||
=== Filter a single layer
|
||||
|
||||
You can apply a search request to individual layers by setting `Filters` in the layer details panel.
|
||||
Click the *Add filter* button to add a filter to a layer.
|
||||
|
@ -74,7 +74,7 @@ image::maps/images/layer_search.png[]
|
|||
|
||||
[role="xpack"]
|
||||
[[maps-search-across-multiple-indices]]
|
||||
=== Searching across multiple indices
|
||||
=== Search across multiple indices
|
||||
|
||||
Your map might contain multiple {es} indices.
|
||||
This can occur when your map contains two or more layers with {es} sources from different indices.
|
||||
|
@ -85,7 +85,7 @@ The most common cause for empty layers are searches for a field that exists in o
|
|||
|
||||
[float]
|
||||
[[maps-disable-search-for-layer]]
|
||||
==== Disable search for layer
|
||||
==== Disable search for a layer
|
||||
|
||||
You can prevent the search bar from applying search context to a layer by configuring the following:
|
||||
|
||||
|
@ -95,7 +95,7 @@ You can prevent the search bar from applying search context to a layer by config
|
|||
|
||||
[float]
|
||||
[[maps-add-index-search]]
|
||||
==== Use _index in your search
|
||||
==== Use _index in a search
|
||||
|
||||
Add {ref}/mapping-index-field.html[_index] to your search to include documents from indices that do not contain a search field.
|
||||
|
||||
|
|
|
@ -1,13 +1,18 @@
|
|||
[role="xpack"]
|
||||
[[maps-troubleshooting]]
|
||||
== Elastic Maps troubleshooting
|
||||
== Troubleshoot Maps
|
||||
|
||||
++++
|
||||
<titleabbrev>Troubleshoot</titleabbrev>
|
||||
++++
|
||||
|
||||
|
||||
Use the information in this section to inspect Elasticsearch requests and find solutions to common problems.
|
||||
|
||||
[float]
|
||||
=== Inspect Elasticsearch requests
|
||||
|
||||
*Elastic Maps* uses the {ref}/search-search.html[{es} search API] to get documents and aggregation results from {es}. To troubleshoot these requests, open the Inspector, which shows the most recent requests for each layer. You can switch between different requests using the *Request* dropdown.
|
||||
Maps uses the {ref}/search-search.html[{es} search API] to get documents and aggregation results from {es}. To troubleshoot these requests, open the Inspector, which shows the most recent requests for each layer. You can switch between different requests using the *Request* dropdown.
|
||||
|
||||
[role="screenshot"]
|
||||
image::maps/images/inspector.png[]
|
||||
|
@ -33,6 +38,6 @@ image::maps/images/inspector.png[]
|
|||
[float]
|
||||
==== Coordinate and region map visualizations not available in New Visualization menu
|
||||
|
||||
Kibana’s out-of-the-box settings no longer offers coordinate and region maps as a choice in the New Visualization menu because you can create these maps in *Elastic Maps*.
|
||||
Kibana’s out-of-the-box settings no longer offers coordinate and region maps as a
|
||||
choice in the New Visualization menu because you can create these maps in the Maps app.
|
||||
If you want to create new coordinate and region map visualizations, set `xpack.maps.showMapVisualizationTypes` to `true`.
|
||||
|
||||
|
|
|
@ -15,7 +15,7 @@ image::maps/images/multifeature_tooltip.png[]
|
|||
[float]
|
||||
[[maps-vector-tooltip-formatting]]
|
||||
|
||||
==== Formatting tooltips
|
||||
==== Format tooltips
|
||||
|
||||
You can format the attributes in a tooltip by adding <<managing-fields, field formatters>> to your
|
||||
Kibana index pattern. You can use field formatters to round numbers, provide units,
|
||||
|
@ -23,7 +23,7 @@ and even display images in your tooltip.
|
|||
|
||||
[float]
|
||||
[[maps-vector-tooltip-locking]]
|
||||
==== Locking a tooltip at the current location
|
||||
==== Lock a tooltip at the current location
|
||||
You can lock a tooltip in place by clicking a location on the map.
|
||||
With locked tooltips you can:
|
||||
|
||||
|
|
|
@ -40,7 +40,7 @@ repeated production process, but rather for the initial exploration of your data
|
|||
=== Upload geospatial data
|
||||
|
||||
To visualize geospatial data in a point or shape file, you can upload it using the <<geojson-upload, GeoJSON Upload>>
|
||||
feature in *Elastic Maps*, and then use that data as a layer in a map.
|
||||
feature in Maps, and then use that data as a layer in a map.
|
||||
The data is also available for use in the broader Kibana ecosystem, for example,
|
||||
in visualizations and Canvas workpads.
|
||||
With GeoJSON Upload, you can upload a file up to 50 MB.
|
||||
|
|
|
@ -66,7 +66,7 @@ image:images/Dashboard_add_new_visualization.png[Example add new visualization t
|
|||
+
|
||||
For information on how to create visualizations, see <<visualize,Visualize>>.
|
||||
+
|
||||
For information on how to create Maps, see <<maps,Elastic Maps>>.
|
||||
For information on how to create maps, see <<maps,Maps>>.
|
||||
|
||||
To add an existing element:
|
||||
|
||||
|
|
|
@ -85,16 +85,16 @@ image::images/intro-dashboard.png[]
|
|||
|
||||
* <<visualize, Visualize>> allows you to display your data in
|
||||
line charts, bar graphs, pie charts, histograms, and tables
|
||||
(just to name a few). It's also home to *Lens*, the drag-and-drop interface.
|
||||
*Visualize* supports the ability to add interactive
|
||||
(just to name a few). It's also home to Lens, the drag-and-drop interface.
|
||||
Visualize supports the ability to add interactive
|
||||
controls to your dashboard, and filter dashboard content in real time.
|
||||
|
||||
* <<canvas, Canvas>> gives you the ability to present your data in a
|
||||
visually compelling, pixel-perfect report. Give your data the “wow” factor
|
||||
needed to impress your CEO or to captivate people with a big-screen display.
|
||||
|
||||
* <<maps, Elastic Maps>> enables you to ask (and answer) meaningful
|
||||
questions of your location-based data. *Elastic Maps* supports multiple
|
||||
* <<maps, Maps>> enables you to ask (and answer) meaningful
|
||||
questions of your location-based data. Maps supports multiple
|
||||
layers and data sources, mapping of individual geo points and shapes,
|
||||
and dynamic client-side styling.
|
||||
|
||||
|
|
|
@ -38,7 +38,7 @@ Quickly build several types of basic visualizations by simply dragging and dropp
|
|||
data sets.
|
||||
|
||||
<<visualize-maps, Maps>>::
|
||||
* *<<maps,Elastic Maps>>* — Displays geospatial data in {kib}.
|
||||
* *<<maps,Maps>>* — Displays geospatial data in {kib}.
|
||||
|
||||
* <<heat-map,Heat map>>:: Display shaded cells within a matrix.
|
||||
|
||||
|
|
|
@ -213,7 +213,7 @@ url: {
|
|||
format: {property: "features"}
|
||||
----
|
||||
|
||||
To enable Elastic Maps, the graph must specify `type=map` in the host
|
||||
To enable Maps, the graph must specify `type=map` in the host
|
||||
configuration:
|
||||
|
||||
[source,yaml]
|
||||
|
@ -306,7 +306,7 @@ to your kibana.yml file.
|
|||
[[vega-useful-links]]
|
||||
=== Resources and examples
|
||||
|
||||
experimental[] To learn more about Vega and Vega-List, refer to the resources and examples.
|
||||
experimental[] To learn more about Vega and Vega-List, refer to the resources and examples.
|
||||
|
||||
==== Vega editor
|
||||
The https://vega.github.io/editor/[Vega Editor] includes examples for Vega & Vega-Lite, but does not support any
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue