[Breaking change] Remove Coordinate map and region map visualizations

[nreese]

Change description

Which release will ship the breaking change?

8.0

Describe the change. How will it manifest to users?

tile_map, region_map, and maps_legacy plugins will be removed from the kibana baseline. This will remove Coordinate map and region map visualizations from Kibana visualize library.

How many users will be affected?

What can users do to address the change manually?

Starting in 7.10, coordinate map and region map contain a View in maps button that will migrate their coordinate map or region map configuration to the Maps application (#77683). This provides users with the ability to test out the migration in 7.x releases prior to 8.0

How could we make migration easier with the Upgrade Assistant?

The upgrade assistant should convert all tile_map and region_map visualization saved objects to map saved objects. The upgrade assistant will also have to update any dashboard or canvas that embeds these migrated visualizations.

Are there any edge cases?

• Coordinate map and region map embedded in dashboard
• Coordinate map and region map embedded in dashboard canvas
• Region map using map.regionmap vector layer. [Breaking change] Remove map.regionmap.* kibana.yml settings #81704

Test Data

Manually creating coordinate map and region map visualizations

1. To show coordinate map and region map visualizations in "Create new" menu, add xpack.maps.showMapVisualizationTypes: true to kibana.dev.yml
2. Then, create coordinate map and region map visualizations just like any other "Aggregation based" visualization. Open "visualize" and click "Create visualization", Select "Aggregation based", finally select "Coordinate map" or "Region map".

Coordinate map configuration for kibana_sample_data_logs

Region map configuration for kibana_sample_data_logs

Manually creating region map visualization using map.regionmap vector layer.

1. Add the following to kibana.dev.yml

   map.regionmap:
    layers:
     - attribution: "EMS"
       name: "My copy of world countries"
       url: "https://vector.maps.elastic.co/files/world_countries_v7.geo.json?elastic_tile_service_tos=agree&my_app_name=ems-landing-page&my_app_version=7.10.0&license=643c1faf-80fc-4ab0-9323-4d9bd11f4bbc"
       fields:
        - name: "name"
          description: "Name"
        - name: "iso2"
          description: "iso2"
   

2. Create region map as described above

3. Configure region map to use world countries layer defined in map.regionmap by opening "Options" tag and using the configuraitons below
   

Import pre-made saved objects for kibana_sample_data_logs that include edge cases

TBD

Cross links

None

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[alisonelizabeth]

@nreese would you mind adding details to the Test Data section? I think providing steps or pointing to docs on the best way to set up coordinate map and region map visualizations would be helpful.

[nreese]

would you mind adding details to the Test Data section?

I added some details for creating region map and coordinate map visualizations. I will update with an example with map.regionmap configuration later today and with a exported saved object ndjson file in a few weeks once we start to think about the upgrade assistent and the test cases we want for that.

[kobelb]

@nreese do we have any idea how may users are likely to hit this breaking change?

[alisonelizabeth]

I'm going to remove the Elasticsearch UI team label. This deprecation should be registered by the plugin owner via the core deprecations service (#94845). All registered deprecations will be displayed in the Upgrade Assistant (to be implemented via #97159). Feel free to reach out to myself or the core team with any questions!

[thomasneirynck]

support of equivalent to min_doc_count should be introduced in Maps.

[nreese]

closed by #105326

[cjcenizal]

Thanks for updating this @nreese! Could you please update #109166?