# 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:** 2

<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, 8:18pm UTC](https://discuss.elastic.co/t/location-mapping/193615/2 "2019-08-02T20:18:45Z")

</div>

Hi @aaditya_alekar,

It looks like that data set you linked to includes `location` data with a `lat` and `long`, so you should be able to ingest that as a `geo_point` fairly easily. There are [several different formats](https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-point.html) that will work with Elasticsearch (object, string, geohash, array).

You'll need to use logstash or [ingest pipeline](https://www.elastic.co/guide/en/elasticsearch/reference/master/pipeline.html) to make sure the `lat` and `long` are changed to the `geo_point` shape at ingest time. See this thread for an example of how that works: [Problem converting latitude and longitude into a geo point for Kibana](https://discuss.elastic.co/t/problem-converting-latitude-and-longitude-into-a-geo-point-for-kibana/52856/12)

---

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