[Maps] [Meta] Add .mvt vector tile support

[thomasneirynck]

Introducing vector tiles in Maps (experimental feature).

(unrelated to EMS base-layer support. This is for custom sources, ultimately backed by Kibana index patterns).

An initial POC here: #57248

Version label is subject to change.

---

1. Preliminary PRs. These are chores that have no end-user impact

• ensure ordinal numerical data is not scaled. It is no longer necessary since styles have access to field-meta. ([Maps] Remove client-side scaling of ordinal values #58528)
• ensure raw mb-feature properties are passed to the filterTooltip* methods. This way, Maps can read out the properties from non-geojson data. ([Maps] Add styling and tooltip support to mapbox mvt vector tile sources #64488)
• expecting to introduce new modules that extend the existing object model. Get some of the core TypeScript boilerplate out of the way, iso introducing boilerplate + new extensions in single PR ([Maps] Add XYZTMSSource unit test #58567)

2 Support generic vector tile source with XYZ pattern. While we're unsure yet if Maps should support this, it will help condense the final PR, allowing us to split up PRs for the browser-code from the PRs for the server-side tile-generation code.

• add client-side support for vector tile sources: [Maps] Add 3rd party vector tile support #62084
  • generic vector-tile source, requiring an XYZ pattern and a URL layer-name (similar to WMS sources).
  • a tiled-vector layer, requiring a vector-tile source
  • questions:
    • enable/disable dynamic styling (?)
    • enable/disable TileJson metadata (?)
  • looking to dial in functionality in following order
    • support for 3rd party service (as YXZ layer) with static styling only
    • add feature identification (ie. tooltips) ([Maps] Add styling and tooltip support to mapbox mvt vector tile sources #64488)
    • add dynamic styling support ([Maps] Add styling and tooltip support to mapbox mvt vector tile sources #64488)
    • 3rd party x/y/z service ([Maps] Support custom vector tiles defined by user #46409)

3. Add backend routes for tiling of ES-results and corresponding source on the client

• mvt search source ([Maps] Add mvt support for ES doc sources  #75698)
• mvt grid source [Maps] Add super-fine option to grid/cluster layer #78201

4. Add metadata parsing for well known specs

• TileJson ([Maps] Support TileJson spec #70146)
• EMS tiles manifest shortcut

5. Dangling issues

• custom size-ranges [Maps] Should allow custom min-max data ranges for ordinal styling of sizes #62867
• legend and preview icon [Maps] Show legend preview icon for vector tile scaling #76549
• enable heatmaps with vector tile backend [Maps] Add super fine option to heatmap layers #78311
• optimize tile-requests across layers in mb (ie. if multiple kibana layers hit the same tile-service, they should reuse the same mb-source). ([Maps] Optimize tile-requests for mvt sources #70369)

[elasticmachine]

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

[thomasneirynck]

Closing as the core refactors and additions have been made. Outstanding enhancements are tracked separately.

[florinvirdol]

Hi again, @thomasneirynck !
When you have some time, I have some questions, please.

As a bit of context, for my web app, on the Angular frontend, on top of Google Maps APIs, i'm using Uber's deck.gl library for better rendering geo-spatial data (GeoJson layers and MVT layers).
For the deck.gl MVT layers I was using PostgreSQL PostGIS as Vector tile server.

Now, I migrated away from PostGIS and I'm storing the geo-spatial data (collection of shapes and points) in ElasticSearch for faster indexing and querying.

I was wondering if with this initiative or in the near future, am I able to use ElasticSearch or Kibana as a Vector tile server in order to get geo-spatial data (normal for shapes and clustered for points) only for the current map viewport (based on zoom and pan / drag on the map) and in the Mapbox .mvt / pbf formats?

I saw you guys did a wonderful job of implementing something similar into Kibana Maps (serving as Vector Tiles geo-spatial data from ElasticSearch: normal shapes and clustered points).

I'm looking forward to your response!
Thank you very much!

[nickpeihl]

I was wondering if with this initiative or in the near future, am I able to use ElasticSearch or Kibana as a Vector tile server in order to get geo-spatial data (normal for shapes and clustered for points) only for the current map viewport (based on zoom and drag on the map) and in the Mapbox .mvt / pbf formats?

Hi @florinvirdol. It sounds like getting vector tiles directly from Elasticsearch is the best option for you. Would you mind expressing your need in this issue? I think that would help the Elasticsearch team understand and prioritize this effort.

[Zoefrost1312]

#100974