diff --git a/docs/maps/connect-to-ems.asciidoc b/docs/maps/connect-to-ems.asciidoc index 75018e6dd4d97..6b4eb9928cea0 100644 --- a/docs/maps/connect-to-ems.asciidoc +++ b/docs/maps/connect-to-ems.asciidoc @@ -4,9 +4,9 @@ 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, the **Maps** application is already configured to use EMS. +If you are using Kibana's out-of-the-box settings, **Elastic Maps** is already configured to use EMS. -The **Maps** application makes requests directly from the browser to EMS. +**Elastic Maps** makes requests directly from the browser to EMS. To proxy EMS requests through the Kibana server, set `map.proxyElasticMapsServiceInMaps` to `true` in your <> file. @@ -19,5 +19,5 @@ behind a firewall. If this happens, you can disable the EMS connection to avoid To disable EMS, change your <> 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 **Maps** default tile layer. +. Set `map.tilemap.url` to the URL of your tile server. This configures the default tile layer of **Elastic Maps**. . (Optional) Set `map.regionmap` to the vector shapes of the administrative boundaries that you want to use. diff --git a/docs/maps/index.asciidoc b/docs/maps/index.asciidoc index cb7ddd62d6c47..bb569a11ed874 100644 --- a/docs/maps/index.asciidoc +++ b/docs/maps/index.asciidoc @@ -1,11 +1,23 @@ [role="xpack"] [[maps]] -= Maps += Elastic Maps [partintro] -- -The **Maps** application 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. +*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. + +With *Elastic Maps*, you can: + +* Create maps with multiple layers and indices. +* Upload GeoJSON files into Elasticsearch. +* Embed your map in Dashboards. +* Plot individual documents or use aggregations to plot any data set, no matter how large. +* Create choropleth maps. +* Use data driven styling to symbolize features from property values. +* Focus the data you want to display with searches. + +Start your tour of *Elastic Maps* with the <>. [role="screenshot"] image::maps/images/sample_data_ecommerce.png[] diff --git a/docs/maps/maps-getting-started.asciidoc b/docs/maps/maps-getting-started.asciidoc index 68163f5e88a0e..f6db2f0fff219 100644 --- a/docs/maps/maps-getting-started.asciidoc +++ b/docs/maps/maps-getting-started.asciidoc @@ -1,8 +1,8 @@ [role="xpack"] [[maps-getting-started]] -== Getting started with Maps +== Getting started with Elastic Maps -You work with *Maps* by adding layers. The data for a layer can come from +You work with *Elastic 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 @@ -14,7 +14,7 @@ light to dark. image::maps/images/sample_data_web_logs.png[] [[maps-read-only-access]] -NOTE: If you have insufficient privileges to create or save maps, a read-only icon +NOTE: If you have insufficient privileges to create or save maps, a read-only icon appears in the application header. The buttons to create new maps or edit existing maps won't be visible. For more information on granting access to Kibana see <>. @@ -25,7 +25,7 @@ image::maps/images/read-only-badge.png[Example of Maps' read only access indicat [float] === Prerequisites Before you start this tutorial, <>. Each -sample data set includes a map to go along with the data. Once you've added the data, open *Maps* and +sample data set includes a map to go along with the data. Once you've added the data, open *Elastic Maps* and explore the different layers of the *[Logs] Total Requests and Bytes* map. You'll re-create this map in this tutorial. @@ -44,7 +44,7 @@ In this tutorial, you'll learn to: The first thing to do is to create a new map. -. If you haven't already, open *Maps*. +. If you haven't already, open *Elastic Maps*. . On the maps list page, click *Create map*. . Set the time range to *Last 7 days*. + diff --git a/docs/maps/search.asciidoc b/docs/maps/search.asciidoc index 33a8ba15113d8..3830ecdcbc1f0 100644 --- a/docs/maps/search.asciidoc +++ b/docs/maps/search.asciidoc @@ -2,7 +2,7 @@ [[maps-search]] == Searching your data -The **Maps** application embeds the query bar for real-time ad hoc search. +**Elastic Maps** embeds the query bar for real-time ad hoc search. Only layers requesting data from {es} are filtered when you submit a search request. You can create a layer that requests data from {es} from the following: diff --git a/docs/maps/trouble-shooting.asciidoc b/docs/maps/trouble-shooting.asciidoc index d23bed546a6dc..542138828530b 100644 --- a/docs/maps/trouble-shooting.asciidoc +++ b/docs/maps/trouble-shooting.asciidoc @@ -1,13 +1,13 @@ [role="xpack"] [[maps-troubleshooting]] -== Maps troubleshooting +== Elastic Maps troubleshooting Use the information in this section to inspect Elasticsearch requests and find solutions to common problems. [float] === Inspect Elasticsearch requests -The Maps application 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. +*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. [role="screenshot"] image::maps/images/inspector.png[]