You can not configure the lookup through the interface since a geospatial lookup takes 2 inputs (Lat Lon) and the interface only allows for 1.
I tried and confirmed the possibility to add a geospatial lookup in
<yourApp>/local/data/models/<yourDataModel.json>
by adding a calculated field in the calculated fields section of your datamodel like this:
{
"outputFields": [
{
"fieldName": "<FieldName>",
"owner": "<DataModelRoot>",
"type": "string",
"fieldSearch": "",
"required": false,
"multivalue": false,
"hidden": false,
"editable": true,
"displayName": "<FieldName>",
"comment": "",
"lookupOutputFieldName": "featureId"
}
],
"calculationType": "Lookup",
"lookupName": "<NameOfYourLookupAsDefinedInTransforms>",
"comment": "",
"lookupInputs": [
{
"inputField": "gps_latitude",
"lookupField": "latitude"
},
{
"inputField": "gps_longitude",
"lookupField": "longitude"
}
],
"owner": "<DatamodelRoot>",
"calculationID": "<someHash>",
"editable": true
},
This "works"... At least most of the time. We are curently seeing issues that lead to the looked up field sometimes being Null or even more weirdly, containing the name of the lookup instead of any valid output. Right now we have no explanation how this happens.
There seems to be at least one other user that ran into the same problem, as seen in this question:
https://answers.splunk.com/answers/688678/why-does-data-model-show-name-of-lookup-definition.html
So if you try this out, I would very much like to hear what your experience was.
Some kind of official statement regarding this issue would be great too.
... View more