# Query Exception: Geo Points **URL:** \ **Category:** Elasticsearch\ **Created:** [August 20, 2015, 6:52pm UTC](https://discuss.elastic.co/t/query-exception-geo-points/27789 "2015-08-20T18:52:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Jaraxal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaraxal/32/458_2.png) [@Jaraxal](https://discuss.elastic.co/u/Jaraxal)\ **Post date:** [August 20, 2015, 6:52pm UTC](https://discuss.elastic.co/t/query-exception-geo-points/27789/1 "2015-08-20T18:52:32Z")
Typically if you query an index using a fielded query that doesn't exist, Elasticsearch will simply return 0 hits. This is our desired behavior. However this doesn't seem to be the case if your query is a geospatial query. If I try to query against a geo\_point field that doesn't exist, I get a QueryParsingException saying that it failed to find the geo\_point field. Why doesn't this return 0 hits for those indexes without the field like other queries do? Is it a bug or a known issue? ---
**Author:** ![emptyemail](https://avatars.discourse-cdn.com/v4/letter/e/6de8d8/32.png) [@emptyemail](https://discuss.elastic.co/u/emptyemail)\ **Post date:** [August 20, 2015, 6:56pm UTC](https://discuss.elastic.co/t/query-exception-geo-points/27789/2 "2015-08-20T18:56:59Z")
I've seen this behavior for a while, I use an exists filter to make sure the fields exists, it is cached and is much faster than running the geo filters on all the data. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:54pm UTC](https://discuss.elastic.co/t/query-exception-geo-points/27789/3 "2017-07-05T23:54:51Z")