Refine your search:

Our Web App already returns the lat and long on the Payload XML. On the response you see something like this: ***<x>-115.37517777777778</x><y>36.542195555555555</y>***

I successfully extracted fields with that and named them 'Latitude' and 'Longitude' but the Google Map app cannot see it (even though the fields populated with data on the left side of the screen)

Has anybody been successful plotting Lat and Long directly from the XML response? Thanks!!

asked 27 Apr '11, 14:28

DotTest37's gravatar image

DotTest37
123
accept rate: 0%


One Answer:

Yep. I did this on an app I developed for one of my customers not long ago. We wanted to use the GoogleMaps module but we already had latitude and longitude in the events so we didnt need the lookup.

You may be tripped up by the same thing I was, which is that while the lookup outputs lots of fields, the only fields the GoogleMaps module looks for are "_lat" and "_lng".

(Note the underscores and also note especially the lack of "o" in "_lng". )

Feed this to the GoogleMaps module and it should work.

<your search> | eval _lat=Latitude | eval _lng=Longitude
link

answered 27 Apr '11, 18:15

nick's gravatar image

nick ♦
14.2k1318
accept rate: 47%

edited 27 Apr '11, 18:16

Thanks for assisting me Nick! Your suggestion worked perfect.

(27 Apr '11, 21:50) DotTest37

Please note: In the new version you have to use the _geo field with the combined lat/lng value:

<your search> | eval _geo=Latitude+","+Longitude
(24 Jun '11, 04:05) ziegfried ♦
Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions

RSS:

Answers

Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

Asked: 27 Apr '11, 14:28

Seen: 772 times

Last updated: 24 Jun '11, 04:05

Copyright © 2005-2012 Splunk, Inc. All rights reserved.