# Worldmap not working with geopoint field

**URL:** <https://community.graylog.org/t/worldmap-not-working-with-geopoint-field/23366>\
**Category:** Graylog Central (peer support)\
**Created:** [April 12, 2022, 4:46pm UTC](https://community.graylog.org/t/worldmap-not-working-with-geopoint-field/23366 "2022-04-12T16:46:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![manfredw](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/manfredw/32/11426_2.png) [@manfredw](https://community.graylog.org/u/manfredw)\
**Post date:** [April 12, 2022, 4:46pm UTC](https://community.graylog.org/t/worldmap-not-working-with-geopoint-field/23366/1 "2022-04-12T16:46:40Z")

</div>

Hi,  
I’m not able to get the world map widget working (but worked already some years ago with same settings on older Graylog versions), maps stay empty or throw errors that only numeric fields can be visualized.  
A click on the fieldname with the coordinates shows that mapping should be correct  
`compound(geo-point,string)` , values are populated by lookup table (mapping of internal IP addresses to locations).  
The docu I’ve found for [Geolocation](https://docs.graylog.org/docs/geolocation) shows screenshots of very old GUI version.

**My environment**  
Graylog 3.3.16/OpenJDK11 on Linux 5.x  
Elasticsearch 6.8, MongoDB 4.2, all systems clustered

Mapping for location field is geo\_location, format “,” (string notation)

**3. What steps have you already taken to try and solve the problem?**  
No real changes on field format possible - other formats are rejected by ES or I was not able to switch to a different format like array [ES Geopoint Formats](https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-point.html)

**4. How can the community help?**  
Has anybody experiences with this topic?  
Have the settings changed and there is a docu bug?

---

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [April 12, 2022, 5:55pm UTC](https://community.graylog.org/t/worldmap-not-working-with-geopoint-field/23366/2 "2022-04-12T17:55:07Z")

</div>

They way you describe it, you have worked in Elasticsearch to set the field type to “geo\_point” but Graylog doesn’t use that field type, it uses “keyword” with lat/lon data … granted you have an older version of Graylog (You can find archived docs for it [here](https://archivedocs.graylog.org/en/3.2/index.html)) so for instance when I examine some of my data the field will show up like so:

```auto
external_ip_geolocation
37.751,-97.822

```

and if I examine the field type in Elasticsearch it appears as such:

```auto
$ curl -X GET "elastique:9200/tiny_index_72/_mapping/field/external*geo*?pretty"
{
  "tiny_index_72" : {
    "mappings" : {
      "external_ip_geolocation" : {
        "full_name" : "external_ip_geolocation",
        "mapping" : {
          "external_ip_geolocation" : {
            "type" : "keyword"
          }
        }
      }
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![manfredw](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/manfredw/32/11426_2.png) [@manfredw](https://community.graylog.org/u/manfredw)\
**Post date:** [April 12, 2022, 7:48pm UTC](https://community.graylog.org/t/worldmap-not-working-with-geopoint-field/23366/3 "2022-04-12T19:48:31Z")

</div>

Great, this solves my problem, now there is an additional field with string format 😀

I think I’ve changed the mapping from string to geopoint to use the grafana world map plugin.  
Basically it would make sense to use geopoint because you can do geo calculations like distance, boxing… [ES Geo queries](https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-queries.html).

Too bad that the Graylog world map currently does not support such nice features…

---

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [April 12, 2022, 8:03pm UTC](https://community.graylog.org/t/worldmap-not-working-with-geopoint-field/23366/4 "2022-04-12T20:03:57Z")

</div>

I considered adding Grafana into the mix - I would create a [custom index mapping](https://archivedocs.graylog.org/en/3.2/pages/configuration/elasticsearch.html?highlight=custom%20index#custom-index-mappings) for a different field and see if I could get Graylog to copy the keyword field data to the custom geo\_point field I haven’t checked to see if the data would need to change or even if Graylog would allow a field type it doesn’t use… If you go that route, let me know how it goes!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [April 26, 2022, 8:04pm UTC](https://community.graylog.org/t/worldmap-not-working-with-geopoint-field/23366/5 "2022-04-26T20:04:06Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.