# Unable to select correct Index in map visualisation

**URL:** https://discuss.elastic.co/t/unable-to-select-correct-index-in-map-visualisation/228466
**Category:** Kibana
**Tags:** maps
**Created:** [April 17, 2020, 7:58am UTC](https://discuss.elastic.co/t/unable-to-select-correct-index-in-map-visualisation/228466 "2020-04-17T07:58:32Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)
#### Post date: [April 17, 2020, 10:07am UTC](https://discuss.elastic.co/t/unable-to-select-correct-index-in-map-visualisation/228466/4 "2020-04-17T10:07:34Z")

</div>

Objects are one of the supported types for geo\_point, there's plenty of posts on this topic here at discuss, I've found this one [where a colleague suggests to refresh the index pattern in Kibana](https://discuss.elastic.co/t/unable-to-get-geoip-location-to-a-geo-point-in-es/107252/6?).

What do you see on your index pattern?

Another thing to try is to do a simple geospatial query against your index to confirm your data is stored as geometries, for example:

```auto
GET bitvise-geo/_search
{
  "query": {
    "bool": {
      "must": [{ "match_all": {} }],
      "filter": {
        "geo_bounding_box": {
          "geoip.location": {
            "top_left": { "lat": 90, "lon": -120 },
            "bottom_right": { "lat": -90, "lon": 120}
          } } } } } }

```

---

_[View the full topic](https://discuss.elastic.co/t/unable-to-select-correct-index-in-map-visualisation/228466)._