[Maps] Use ES mvt

[thomasneirynck]

Replace Kibana's mvt generation with Elasticsearch ES-mvt generation

---

Vector tile drawing of Elasticsearch data is going GA in Kibana Maps

This PR removes the Kibana implementation of mapbox vector tiles (" mvt") (https://docs.mapbox.com/vector-tiles/reference/), in favor of the mvt-implementation in Elasticsearch( cf. https://www.elastic.co/guide/en/elasticsearch/reference/current/search-vector-tile-api.html)

Since 7.11, the Kibana implementation of mvt was a beta-feature, and being used for:

• vector tile scaling option in document layers
• super-fine grid resolution for cluster layers

With this change to using Elasticsearch, both these capabilities are now going GA.

Increase geo-data volume on screen

This change significantly enhances the amount of geo-data that can be shown on screen.

Displaying more individual documents

Each tile contains up to the max_result_window of features. This is a per-index setting https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules.html. A single view contain will conist of 4-9 tiles.

Displaying clusters at high resolution

The super-fine resolutions displays up to 128x128 cells per tile, creating high-res cluster maps

---

Other changes

The client-side data-mapping is no longer possible for ES document layers

This switch is always on by default for scaling with vector tiles. This means the domain-range (ie. min & max) of a value is determined by querying the min-max of the underlying data in Elasticsearch, and not by only getting the min-max of the features on screen.

top-term aggregation is disabled

Top-terms agg is not supported by the vector tile search API of Elasticsearch.

too many features outline

This PR introduces a orange dotted outline of the bounding-box of the features int he tile. This is only used if the number of features exceeds the maximum allowed number of features per tile.

e.g.: zoomed out, cannot show all features at this scale level. Users would need to filter or zoom-in further to see all data.

Field formatters are not applied on map labels

When using vector tiles, field formatters of the data view are not applied for labeling on the map.

[nreese]

@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[thomasneirynck]

scope exceeds original goals. I'm +1 on this change. thx!

[nreese]

LGTM, code review and tested in chrome. This is such a huge improvement. Elasticsearch MVTs have such an amazing performance boost.

Anything that I am still unhappy with is tracked in #116150 and can be fixed at a later time.

[jsanz]

Tested with Chrome and Firefox and I haven't got a single glitch. I will open a separate issue for removing labels in super-fine grid since they don't make any sense with such small squares but other than that, I've tested medium/large datasets with point, lines, and polygon geometry types and they render fast, panning now around is a great experience. Beautiful job everyone!

[kibanamachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: ddb5d29
• Storybooks Preview

Test Failures

• [job] [logs] Default CI Group #7 / dashboard feature controls dashboard feature controls security no dashboard privileges "before all" hook for "doesn't show dashboard navLink"

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
maps	839	837	-2

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
maps	201	203	+2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
maps	2.7MB	2.7MB	+3.3KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
maps	42.1KB	41.7KB	-470.0B

Unknown metric groups

API count

id	before	after	diff
maps	202	204	+2

References to deprecated APIs

id	before	after	diff
maps	1697	1707	+10

History

• 💚 Build #1217 succeeded 0dc5411
• 💔 Build #1216 failed 2909005
• 💔 Build #1215 failed 01ecad3
• 💔 Build #1209 failed 0e4e68a
• 💚 Build #1170 succeeded a383be1
• 💔 Build #1150 failed bb1448b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 114553 or prevent reminders by adding the backport:skip label.