无法创建geo_point字段，求助Kibana坐标地图配置问题

Hey there! I’ve dealt with this exact problem multiple times when bringing MySQL data into Kibana for map visualizations—let’s break down the solutions that work depending on where you are in the process.

1. If You Haven’t Imported the Data Yet (Pre-Import Setup) #

The easiest way is to configure your data pipeline (like Logstash, commonly used for MySQL → Elasticsearch transfers) to create the geo_point field during import.

Example Logstash Config #

Add this filter block to your Logstash configuration to combine your latitude and longitude columns into a proper geo_point field:

filter {
  # Combine lat/lon into a nested location object
  mutate {
    add_field => { "[location][lat]" => "%{latitude}" }
    add_field => { "[location][lon]" => "%{longitude}" }
  }
  # Convert values to floats (critical—geo_point requires numeric data)
  mutate {
    convert => {
      "[location][lat]" => "float"
      "[location][lon]" => "float"
    }
  }
}

In your output block, ensure you’re sending data to Elasticsearch—your location field will automatically map to geo_point if the format is correct.

2. If You Already Imported the Data (Post-Import Fix) #

If your data is already in Elasticsearch but missing the geo_point field, you’ll need to update the index mapping and populate the field retroactively.

Step 1: Update the Index Mapping #

Use Kibana’s Dev Tools to add the geo_point mapping to your index (replace your-mysql-index with your actual index name):

PUT your-mysql-index/_mapping
{
  "properties": {
    "location": {
      "type": "geo_point"
    }
  }
}

Step 2: Populate the location Field #

Run an _update_by_query command to fill the new field with existing latitude/longitude data. Elasticsearch expects geo_point in [longitude, latitude] order for array format:

POST your-mysql-index/_update_by_query
{
  "script": {
    "source": "ctx._source.location = [ctx._source.longitude, ctx._source.latitude]"
  }
}

Step 3: Verify the Mapping #

Double-check that the mapping took effect with:

GET your-mysql-index/_mapping

Look for the location field listed with type geo_point.

3. Critical Checks to Avoid Common Pitfalls #

• Ensure numeric data types: Your latitude and longitude columns in MySQL must be numeric (e.g., FLOAT, DECIMAL), not strings. Text values will fail to convert to geo_point.
• Index template for future imports: If you plan to re-import data later, create an index template to auto-apply the geo_point mapping:

PUT _index_template/mysql-geo-template
{
  "index_patterns": ["your-mysql-index-*"],
  "template": {
    "mappings": {
      "properties": {
        "location": {"type": "geo_point"},
        "latitude": {"type": "float"},
        "longitude": {"type": "float"}
      }
    }
  }
}

Once you’ve completed these steps, head back to Kibana’s Maps app—your location field should now be available for coordinate maps!

内容的提问来源于stack exchange，提问作者Axel Morvan