Hi,
does anyone know if its possible to use geodetic (projected) locations in Splunk.
As update to this issue:
At the moment there is no functionality to work in meters within the mapping apps. I got round this problem by using the following calculation which anyone wanting to convert from meters to decimal degrees in the rijksdriehoekstel (Nederlands/dutch) format can use.
| eval x={your X in meters}, y={your Y in meters}
| where y > 0 AND x > 0
| eval dX = round((('x' - 155000) * 0.00001),5), dY = round((('y' - 463000) * 0.00001),5)
| eval SomN = (3235.65389 * dY) + (-32.58297 * pow(dX,2)) + (-0.2475 * pow(dY,2)) + (-0.84978 * pow(dX,2) * dY) + (-0.0655 * pow(dY,3)) + (-0.01709 * pow(dX,2) * pow(dY,2)) + (-0.00738 * dX) + (0.0053 * pow(dX,4)) + (-0.00039 * pow(dX,2) * pow(dY,3)) + (0.00033 * pow(dX,4) * dY) + (-0.00012 * dX * dY), SomE = (5260.52916 * dX) + (105.94684 * dX * dY) + (2.45656 * dX * pow(dY,2)) + (-0.81885 * pow(dX,3)) + (0.05594 * dX * pow(dY,3)) + (-0.05607 * pow(dX,3) * dY) + (0.01199 * dY) + (-0.00256 * pow(dX,3) * pow(dY,2)) + (0.00128 * dX * pow(dY,4)) + (0.00022 * pow(dY,2)) + (-0.00022 * pow(dX,2)) + (0.00026 * pow(dX,5))
| eval latitude = 52.15517 + (SomN / 3600), longitude = 5.387206 + (SomE / 3600)
The end result is a latitude and longitude field in decimal degrees that can be used in all the mapping apps.
As update to this issue:
At the moment there is no functionality to work in meters within the mapping apps. I got round this problem by using the following calculation which anyone wanting to convert from meters to decimal degrees in the rijksdriehoekstel (Nederlands/dutch) format can use.
| eval x={your X in meters}, y={your Y in meters}
| where y > 0 AND x > 0
| eval dX = round((('x' - 155000) * 0.00001),5), dY = round((('y' - 463000) * 0.00001),5)
| eval SomN = (3235.65389 * dY) + (-32.58297 * pow(dX,2)) + (-0.2475 * pow(dY,2)) + (-0.84978 * pow(dX,2) * dY) + (-0.0655 * pow(dY,3)) + (-0.01709 * pow(dX,2) * pow(dY,2)) + (-0.00738 * dX) + (0.0053 * pow(dX,4)) + (-0.00039 * pow(dX,2) * pow(dY,3)) + (0.00033 * pow(dX,4) * dY) + (-0.00012 * dX * dY), SomE = (5260.52916 * dX) + (105.94684 * dX * dY) + (2.45656 * dX * pow(dY,2)) + (-0.81885 * pow(dX,3)) + (0.05594 * dX * pow(dY,3)) + (-0.05607 * pow(dX,3) * dY) + (0.01199 * dY) + (-0.00256 * pow(dX,3) * pow(dY,2)) + (0.00128 * dX * pow(dY,4)) + (0.00022 * pow(dY,2)) + (-0.00022 * pow(dX,2)) + (0.00026 * pow(dX,5))
| eval latitude = 52.15517 + (SomN / 3600), longitude = 5.387206 + (SomE / 3600)
The end result is a latitude and longitude field in decimal degrees that can be used in all the mapping apps.
From which system? Basic latitude and longitude (ie GPS) are accommodated in splunk geomaps.
On the other hand, I actually don't know if splunk accommodates Cartesian coordinates...which, for the general public, is the less-accurate, map-based, somewhat old-fashioned opposite of "geodetic".
What other features do you need, for what application? Are you needing altitude as well?
I mean, is there a way to show geodetic RDS co-ordinates (meters) as opposed to the WGS84 lat, long that the mapping tools are using.
What I would like to do is import transport data directly from a source without having to first convert the x,y to lat long in a GIS.