# How to dynamically recognize points via HTTPS ingestion?

**URL:** <https://discuss.elastic.co/t/how-to-dynamically-recognize-points-via-https-ingestion/296346>\
**Category:** Logstash\
**Created:** [February 4, 2022, 9:44pm UTC](https://discuss.elastic.co/t/how-to-dynamically-recognize-points-via-https-ingestion/296346 "2022-02-04T21:44:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![HC\_LW](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hc_lw/32/101399_2.png) [@HC\_LW](https://discuss.elastic.co/u/HC_LW)\
**Post date:** [February 4, 2022, 9:44pm UTC](https://discuss.elastic.co/t/how-to-dynamically-recognize-points-via-https-ingestion/296346/1 "2022-02-04T21:44:57Z")

</div>

We are sending https requests to ingest data. How can the request be formatted so that Elastic dynamically maps the 'geo\_point' field as type:point and not text or number? Thank you!

```auto
curl -X POST "https://in-https.URL" -H 'Content-Type: application/json' -d'
{
    "geo_point": -71.34, 41.12
}
'

```

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [February 4, 2022, 10:03pm UTC](https://discuss.elastic.co/t/how-to-dynamically-recognize-points-via-https-ingestion/296346/2 "2022-02-04T22:03:46Z")

</div>

I suggest you read [this thread](https://discuss.elastic.co/t/logstash-geojson-and-kibana/277450/5).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 4, 2022, 10:04pm UTC](https://discuss.elastic.co/t/how-to-dynamically-recognize-points-via-https-ingestion/296346/3 "2022-03-04T22:04:36Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.