# Parsing Geo Data from text documents **URL:** \ **Category:** Elasticsearch\ **Created:** [July 18, 2017, 6:37am UTC](https://discuss.elastic.co/t/parsing-geo-data-from-text-documents/93507 "2017-07-18T06:37:53Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![antman1p](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@antman1p](https://discuss.elastic.co/u/antman1p)\ **Post date:** [July 18, 2017, 6:37am UTC](https://discuss.elastic.co/t/parsing-geo-data-from-text-documents/93507/1 "2017-07-18T06:37:53Z")
I am currently have a python script that watches a directory and every time a new file shows up, it calls Apache Tika to parse the file. I am parsing a WIDE variety of document types and the script posts the parsed data to the appropriate type in an elastic search index. My question is: Is there a way for Elastic search to recognize various geo-coordinates from the parsed text of the various document types and possibly automatically pin them on the Kibana map? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 18, 2017, 6:55am UTC](https://discuss.elastic.co/t/parsing-geo-data-from-text-documents/93507/2 "2017-07-18T06:55:20Z")
If the coordinates are in a specific field and you use a template/mapping for that field, then yes. ---
**Author:** ![antman1p](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@antman1p](https://discuss.elastic.co/u/antman1p)\ **Post date:** [July 19, 2017, 12:43am UTC](https://discuss.elastic.co/t/parsing-geo-data-from-text-documents/93507/3 "2017-07-19T00:43:48Z")
What if they're not? Is there a plugin or anything that could search all of the parsed text for strings that look like geocoords and tag them in a way that they can be recognized as such? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 19, 2017, 1:13am UTC](https://discuss.elastic.co/t/parsing-geo-data-from-text-documents/93507/4 "2017-07-19T01:13:55Z")
You could try [https://github.com/spinscale/elasticsearch-ingest-opennlp](https://github.com/spinscale/elasticsearch-ingest-opennlp) ---
**Author:** ![antman1p](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@antman1p](https://discuss.elastic.co/u/antman1p)\ **Post date:** [July 19, 2017, 6:18am UTC](https://discuss.elastic.co/t/parsing-geo-data-from-text-documents/93507/5 "2017-07-19T06:18:13Z")
I read the documentation for the repo you linked, but am confused as to what exactly it does. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 19, 2017, 6:29am UTC](https://discuss.elastic.co/t/parsing-geo-data-from-text-documents/93507/6 "2017-07-19T06:29:27Z")
It uses natural language processing to do entity extraction, an entity in this instance could be a location. I guess the simple way of putting this is there isn't a really easy way to do this at the moment, unless you want to spend $$$ on a off the shelf solution or spend some time to build something out of base technology like OpenNLP. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 16, 2017, 6:29am UTC](https://discuss.elastic.co/t/parsing-geo-data-from-text-documents/93507/7 "2017-08-16T06:29:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.