Sort by proximity, add another proximity calculated field even if already present

I have a view which displays distances from geolocated field in my user to a location passed as contextual filter.

My view is made this way:

- Contextual filter: geolocation proximy (latitude/longitude + radius)
- Display fields: a calculated field geolocation proximity for each results
- Sort: proximity of my contextual filter ASC

As soon as I add the sort by proximity, it adds in the SQL query another time the same calculated field already available.
So this field is added and calculated twice for nothing.