Stored geo_point field return Lucene interleaved/morton hash?

Greetings,

It appears that all stored geo_point fields (when we're not leveraging _source) actually return the Lucene representation of the lat/long. For those of us not leveraging the Elasticsearch/Lucene libs directly, is there some way to have Elasticsearch split the combined lat/long data back into individual lat/long components for easier consumption?

What was sent in:
"location": {
"lat": 37.65785,
"lon": -122.42313
}

What was returned:
"location": [
2564999456675991600
]

Repro command to be ran in Sense:
DELETE /geotemp

PUT /_template/geotemp
{
"template": "geotemp*",
"mappings": {
"geodatapoint": {
"properties": {
"location": {
"type": "geo_point",
"store": true
}
}
}
}
}

PUT /geotemp/geodatapoint/1
{
"location": {
"lat": 37.65785,
"lon": -122.42313
}
}

GET /geotemp/geodatapoint/_search
{
"query": {
"bool": {
"must": [
{
"match_all": {}
}
]
}
},
"fields": [
"*"
]
}