# Nest cutting off trailing zero

**URL:** <https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264>\
**Category:** Elasticsearch\
**Created:** [August 14, 2019, 8:48pm UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264 "2019-08-14T20:48:29Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![plawler92](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/plawler92/32/61507_2.png) [@plawler92](https://discuss.elastic.co/u/plawler92)\
**Post date:** [August 14, 2019, 8:48pm UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264/1 "2019-08-14T20:48:29Z")

</div>

I have Latitude and Longitude fields in my index stored as double that can contain trailing zero's which we treat as important ex: 37.15580. When I query elasticsearch through curl or kibana this field correctly returns all digits including the trailing zero, however when I query for this document through C# NEST or elasticsearch's python library this trailing zero is removed. Is there any way to change this behavior so the trailing zero's are preserved?

---

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [August 15, 2019, 7:20am UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264/2 "2019-08-15T07:20:02Z")

</div>

> [@plawler92](#):
>
> however when I query for this document through C# NEST or elasticsearch's python library this trailing zero is removed

To clarify, does the JSON response from Elasticsearch contain the trailing zero, but when serializing the `double` again to which the latitude or longitude field is deserialized into, the trailing zero is trimmed?

> [@plawler92](#):
>
> which we treat as important

Why are trailing zeroes important?

---

<div class="post-metadata">

**Author:** ![plawler92](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/plawler92/32/61507_2.png) [@plawler92](https://discuss.elastic.co/u/plawler92)\
**Post date:** [August 15, 2019, 1:23pm UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264/3 "2019-08-15T13:23:03Z")

</div>

The response I am getting is using this Nest code (which cuts off trailing zero before it gets out of what Nest is doing):  
var results = ElasticClient.Search(s =\> s  
.Index(IndexProperties.POSTAL\_INDEX)  
.Size(1)  
.Query(q =\> q  
.Bool(b =\> b  
.Must(mu =\> mu  
.Match(ma =\> ma.Field(f =\> f.CityName).Query(sCityName).MinimumShouldMatch(MinimumShouldMatch.Percentage(100))))  
.Filter(f =\> f  
.Term(t =\> t.Field(fi =\> fi.CountryCode).Value(sCountryCode)) && f  
.Term(t =\> t.Field(fi =\> fi.StateCode).Value(sStateCode)) && f  
.Term(t =\> t.Field(fi =\> fi.PostalCode).Value(sPostalCode))))));

This code using the low level client returns the latitude in the way I want it too:  
var lowlevelClient = new ElasticLowLevelClient();

```
        var searchResponse = lowlevelClient.Search<StringResponse>("mdm_postalgeo", PostData.Serializable(new
        {
            from = 0,
            size = 10,
            query = new
            {
                term = new
                {
                    PostalCode = "24059"
                }
            }
        }));

```

The zeroes are important for us because they are indicating the degree of precision for the given latitude and longitude.

---

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [August 15, 2019, 2:08pm UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264/4 "2019-08-15T14:08:45Z")

</div>

> [@plawler92](#):
>
> The response I am getting is using this Nest code (which cuts off trailing zero before it gets out of what Nest is doing):

Where in the response are you looking at double values? For example, on `results.Documents.Select(d => d.Latitude)`?

> [@plawler92](#):
>
> This code using the low level client returns the latitude in the way I want it too:

That'll be returning the JSON string representation of the numeric value. The same representation will be returned to NEST too, which is why I'd like to understand _where_ you are looking at double values. Would you be able to provide a small code example, or screenshot?

---

<div class="post-metadata">

**Author:** ![plawler92](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/plawler92/32/61507_2.png) [@plawler92](https://discuss.elastic.co/u/plawler92)\
**Post date:** [August 15, 2019, 3:19pm UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264/5 "2019-08-15T15:19:40Z")

</div>

Yes I am seeing is an element under results.Documents.Select. I have also looked under 'Hits' and found it also cut the zero off there. The latitude in the picture is 37.15580 in the actual elastic index.

![ElasticTrailingZero](https://us1.discourse-cdn.com/elastic/original/3X/b/e/be6883e1ed0030e289ae3350ea8b2e7430858e5d.png)

---

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [August 16, 2019, 12:48am UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264/6 "2019-08-16T00:48:01Z")

</div>

This is not a NEST issue, but the way that doubles are handled in C#/CLR, according to [IEEE 754](https://en.wikipedia.org/wiki/IEEE_754); when a string representation of a double value is parsed to a `System.Double` type, trailing fractional zero significant digits are truncated

```auto
void Main()
{

	var value1 = double.Parse("37.1558");

    // could make this 37.1558 followed by any number of trailing zeroes
	var value2 = double.Parse("37.15580");

	Console.WriteLine($"value1: {value1}");
	Console.WriteLine($"value2: {value2}");

    // put aside comparing doubles for equality with == for the moment :)
	Console.WriteLine($"value1 == value2: {value1 == value2}");
}

```

yields

```auto
value1: 37.1558
value2: 37.1558
value1 == value2: True

```

I would expect the same behaviour in other languages that adhere to `IEEE 754`.

Using `System.Decimal` will preserve the precision

```auto
// same code as before, but using Decimal
var value1 = Decimal.Parse("37.1558");
var value2 = Decimal.Parse("37.15580");

```

yields

```auto
value1: 37.1558
value2: 37.15580
value1 == value2: True

```

**However** , Elasticsearch internally will index these values as [`double` numeric types](https://www.elastic.co/guide/en/elasticsearch/reference/current/number.html), and any calculations within Elasticsearch will be performed with this precision.

There are a couple of ways that you may want to retain this information:

1. Create your own `GeoLocation` type that uses `System.Decimal` for latitude and longitude properties, that you can deserialize these values into.
2. Store the precision of the values as a separate field or fields that can be used to inform your usage e.g. when values are `.ToString()`'ed, etc.

---

<div class="post-metadata">

**Author:** ![plawler92](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/plawler92/32/61507_2.png) [@plawler92](https://discuss.elastic.co/u/plawler92)\
**Post date:** [August 16, 2019, 1:35pm UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264/7 "2019-08-16T13:35:28Z")

</div>

Thanks! That was very helpful I'll take a look as those options.

---

<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:** [September 13, 2019, 1:41pm UTC](https://discuss.elastic.co/t/nest-cutting-off-trailing-zero/195264/8 "2019-09-13T13:41:11Z")

</div>

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