# Geoip\_point can not be used in machine learning detector funktion lat\_long in Kibana 7.5.0 **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-machine-learning\ **Created:** [December 5, 2019, 11:32am UTC](https://discuss.elastic.co/t/geoip-point-can-not-be-used-in-machine-learning-detector-funktion-lat-long-in-kibana-7-5-0/210688 "2019-12-05T11:32:16Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![AndWe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andwe/32/47532_2.png) [@AndWe](https://discuss.elastic.co/u/AndWe)\ **Post date:** [December 5, 2019, 11:32am UTC](https://discuss.elastic.co/t/geoip-point-can-not-be-used-in-machine-learning-detector-funktion-lat-long-in-kibana-7-5-0/210688/1 "2019-12-05T11:32:16Z")
Kibana, Elasticsearch updated to 7.5.0 When I try to setup ML job I cannot select geoip\_point field for lat\_long function. ![12](https://us1.discourse-cdn.com/elastic/original/3X/4/2/42584dbb626f910eecc001577f888f3ee2c7d79c.png) When I type the name of the geoip\_point field other fields stay inactive. This applies also to discovery. Adding filters doesn't work. But using the Search field I'm able to filter. Discover (Add filter) - not working: ![59](https://us1.discourse-cdn.com/elastic/original/3X/1/0/1001561f81c14ade5871979a8ef23c92ecafcaab.png) Discover (Search) - working: ![32](https://us1.discourse-cdn.com/elastic/original/3X/d/e/de8b1819b5fbc21fc04028f10359d1b43e48d7f4.png) ---
**Author:** ![BenTrent](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bentrent/32/33915_2.png) [@BenTrent](https://discuss.elastic.co/u/BenTrent)\ **Post date:** [December 5, 2019, 12:32pm UTC](https://discuss.elastic.co/t/geoip-point-can-not-be-used-in-machine-learning-detector-funktion-lat-long-in-kibana-7-5-0/210688/2 "2019-12-05T12:32:53Z")
@AndWe What is the mapped type of `source.geo.location`? Is it indexed as a `geo_point`? If it is, but it is still not available in the wizard, could double check the kibana index pattern? The ML Job Wizard relies on the discovered mapped types in the index pattern and you may have to refresh the pattern. ---
**Author:** ![James\_Gowdy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_gowdy/32/74175_2.png) [@James\_Gowdy](https://discuss.elastic.co/u/James_Gowdy)\ **Post date:** [December 5, 2019, 12:37pm UTC](https://discuss.elastic.co/t/geoip-point-can-not-be-used-in-machine-learning-detector-funktion-lat-long-in-kibana-7-5-0/210688/3 "2019-12-05T12:37:58Z")
This is a bug that will be fixed in 7.5.1 > ---
**Author:** ![AndWe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andwe/32/47532_2.png) [@AndWe](https://discuss.elastic.co/u/AndWe)\ **Post date:** [December 5, 2019, 1:42pm UTC](https://discuss.elastic.co/t/geoip-point-can-not-be-used-in-machine-learning-detector-funktion-lat-long-in-kibana-7-5-0/210688/4 "2019-12-05T13:42:08Z")
Hi All, Thanks for your quick responses. So I have to wait for 7.5.1. ---
**Author:** ![AndWe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andwe/32/47532_2.png) [@AndWe](https://discuss.elastic.co/u/AndWe)\ **Post date:** [December 5, 2019, 1:44pm UTC](https://discuss.elastic.co/t/geoip-point-can-not-be-used-in-machine-learning-detector-funktion-lat-long-in-kibana-7-5-0/210688/5 "2019-12-05T13:44:33Z")
And what about the filters in Discover? Will this also be fixed? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 2, 2020, 1:44pm UTC](https://discuss.elastic.co/t/geoip-point-can-not-be-used-in-machine-learning-detector-funktion-lat-long-in-kibana-7-5-0/210688/6 "2020-01-02T13:44:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.