(n => n
.Name(nn => nn.Addresses)
.AutoMap()
)
)
)
)
);
```
generates the following create index request
```json
PUT http://localhost:9200/my_index
{
"mappings": {
"product": {
"properties": {
"addresses": {
"type": "nested",
"properties": {
"address": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"latLon": {
"type": "geo_point"
}
}
}
}
}
}
}
```
---
### Author:  [@ivankarpey](https://discuss.elastic.co/u/ivankarpey)
#### Post date: [August 16, 2018, 11:30am UTC](https://discuss.elastic.co/t/nest-c-index-list-of-custom-location-like-objects-how-to-map-it-to-index-properly/144598/3 "2018-08-16T11:30:29Z")
@forloop The problem is that I use **GeoItem** in other places of my code and it's already settled with current structure, so I can't change it to support elastic **GeoLocation** directly. Is there a way to somehow set dynamic conversion from **GeoItem** to **GeoLocation** during the mapping phase (like in automapper for instance) or I need to create separate model?
---
### Author:  [@forloop](https://discuss.elastic.co/u/forloop)
#### Post date: [August 17, 2018, 4:35am UTC](https://discuss.elastic.co/t/nest-c-index-list-of-custom-location-like-objects-how-to-map-it-to-index-properly/144598/4 "2018-08-17T04:35:27Z")
You could write your own [Json.NET](http://Json.NET) `JsonConverter` for `GeoItem` that serializes it to the format expected by Elasticsearch, then use the [Nest.JsonNetSerializer nuget package](https://www.nuget.org/packages/NEST.JsonNetSerializer/) and [hook up the `JsonNetSerializer`](https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/custom-serialization.html#_jsonnetserializer) as the serializer for the client to use
```auto
var pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200"));
var connectionSettings =
new ConnectionSettings(pool, sourceSerializer: JsonNetSerializer.Default);
var client = new ElasticClient(connectionSettings);
```
Alternatively, you could use specific types to represent the documents in Elasticsearch and use `GeoLocation`, then map your domain objects to these POCOs with something like AutoMapper.
---
### Author:  [@ivankarpey](https://discuss.elastic.co/u/ivankarpey)
#### Post date: [August 17, 2018, 8:23am UTC](https://discuss.elastic.co/t/nest-c-index-list-of-custom-location-like-objects-how-to-map-it-to-index-properly/144598/5 "2018-08-17T08:23:33Z")
ok, I decide to proceed with special elasticmodels since there is seems like similar problem with other elastic specific fields like DoubleRange for example. But thanks a lot for your advice
---
### Author:  [@forloop](https://discuss.elastic.co/u/forloop)
#### Post date: [August 17, 2018, 8:35am UTC](https://discuss.elastic.co/t/nest-c-index-list-of-custom-location-like-objects-how-to-map-it-to-index-properly/144598/6 "2018-08-17T08:35:47Z")
> [@ivankarpey](#):
>
> I decide to proceed with special elasticmodels
That's what I would recommend, since it'll allow you to take advantage of Nest specific types on your models
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 14, 2018, 8:36am UTC](https://discuss.elastic.co/t/nest-c-index-list-of-custom-location-like-objects-how-to-map-it-to-index-properly/144598/7 "2018-09-14T08:36:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.