* [Maps] replace coordinate map with Elastic Maps in Kibana getting started docs
* update dashboard getting started page
* update screen shot
* Update docs/getting-started/tutorial-visualizing.asciidoc
Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com>
* review feedback
* update dashboard instructions to include step to set time fitler
* clean up more instances for vector style
* review feedback
* [DOCS] Updates images in Getting Started
* [DOCS] Updates getting started
* [DOCS] Updated gs based on review comments
* [DOCS] Updates links to sample data
* [DOCS] Fixes broken links
* [DOCS] Minor edits to GS
* [DOCS] New tutorial for exploring Kibana with sample data set
* [DOCS] Incorporated review comments into sample tutorial
* [DOCS] GS: Edits for consistency
* [DOCS: Getting Started] Edited text and updated screenshots]
* [DOCS|Getting Started] Edited for consistency in addressing the user
* [DOCS|Getting Started] Incorporated review comments
* [DOCS|GS] Style changes for consistency
* WIP - add shakespeare data for getting started guide
* Refactor of getLineChartData, getBarChartData, getAreaChartData
* Added changing extents and test
* Fix opening axis options
* Change precision from 8 to 7
* lower precision to 6
* Fix index pattern creation
* update from review, remove comments, add others
- Users can now create choropleth maps. This requires configuring an inner join between the results of a term-aggregation and a reference vector layer. This vector layer needs to be in the GeoJson format. By default, Kibana uses vector layers serverd by a data service hosted by Elastic. Users can also bring in their own layers by adding configuration entries in the kibana.yml. These need to point to a CORS-enabled data service that accepts requests from the Kibana application.
- For clarity, the tilemap is renamed to Coordinate Map.
- A new manifest is published by Elastic. this includes metadata for the available tilemap services, as well as metadata for the available vector data layers.
This overhaul of the docs structure puts Kibana's documentation more
inline with the structure that is used in Elasticsearch. This will help
us better organize the docs going forward as more docs are added.
This also includes a few necessary content changes for 5.0.
