# Location Mapping

**URL:** <https://discuss.elastic.co/t/location-mapping/193615>\
**Category:** Logstash\
**Created:** [August 2, 2019, 7:34pm UTC](https://discuss.elastic.co/t/location-mapping/193615 "2019-08-02T19:34:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lukeelmers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukeelmers/32/35230_2.png) [@lukeelmers](https://discuss.elastic.co/u/lukeelmers)\
**Post date:** [August 2, 2019, 10:09pm UTC](https://discuss.elastic.co/t/location-mapping/193615/4 "2019-08-02T22:09:57Z")

</div>

You may want to start with the [configuring logstash](https://www.elastic.co/guide/en/logstash/current/configuration.html) docs to get an idea as to how this process looks. It involves creating a `.conf` file, which you can do from the command line.

Also for your case, perhaps this thread, though old, would be even more useful: [How to process "Lat" & "Long" fields using default Logstash config and mapping to use in Kibana 4 tile map](https://discuss.elastic.co/t/how-to-process-lat-long-fields-using-default-logstash-config-and-mapping-to-use-in-kibana-4-tile-map/23398/8)

It includes a link to [this blog post](http://david.pilato.fr/blog/2015/04/28/exploring-capitaine-train-dataset/) which gives some concrete examples of using `mutate` to turn separate `latitude` and `longitude` values into a geo\_point `location`.

(I'm going to re-categorize this discussion under Logstash since it's more relevant to ingesting data... hope that's okay!) 🙂

---

_[View the full topic](https://discuss.elastic.co/t/location-mapping/193615)._