[193008] in North American Network Operators' Group
Re: SNMP syslocation field for GPS coordinates,
daemon@ATHENA.MIT.EDU (Peter Beckman)
Mon Dec 12 12:36:36 2016
X-Original-To: nanog@nanog.org
Date: Mon, 12 Dec 2016 12:36:31 -0500
From: Peter Beckman <beckman@angryox.com>
To: Eric Kuhnke <eric.kuhnke@gmail.com>
In-Reply-To: <CAB69EHgvrtmGehwimwR1hSPTz8kL=trAfe2MfjVudP-zpxLNsQ@mail.gmail.com>
Cc: "nanog@nanog.org list" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Since we all live on standards, I can suggest RFC7946, GeoJSON
(https://tools.ietf.org/html/rfc7946) for all of your location specification
needs:
{
"type" : "Point",
"coordinates" : [
-121.556359,
39.5137752
]
}
or one line (55 characters, no spaces, hopefully short enough):
{"type":"Point","coordinates":[-121.556359,39.5137752]}
GeoJSON supports "properties" which you can define how you like:
{
"type" : "Point",
"coordinates" : [
-121.556359,
39.5137752
],
"properties" : {
"address" : "121 Gigawatts Ave, Springfield, OH 45501 US",
"hardware" : "Cisco 2924",
"elevation" : "124m"
}
}
Note that many formats now list Longitude first, Latitude second.
http://www.macwright.org/lonlat/
I tend to try to offer/use machine-readable formats first, then human-readable,
because I live for automation. GeoJSON benefits from being both.
Beckman
On Fri, 9 Dec 2016, Eric Kuhnke wrote:
> Yes, that's along the lines of what I was thinking. Pre-define a certain
> number of columns of data that will fit in the snmp syslocation field in
> most devices (some vendors have surprisingly short string length limits,
> grrrrrr). And use something like a pipe delimited CSV format in that field,
> so it has the comma separated decimal degrees lat/long in one column, and
> human readable street address in another.
>
> Also worth noting that many recent SNMP-enabled, high capacity point to
> point microwave radios have built in GPS receivers for timing and location
> purposes, which gather elevation data (in meters above MSL usually).
> Perhaps a column for elevation in meters MSL. The sort of data that is
> useful for a mobile network operator with thousands of point to point RF
> links on rooftops and towers, for auditing and compliance purposes.
>
> On Fri, Dec 9, 2016 at 2:09 PM, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
>
>> Yes. But don’t just put in coordinates... Put in other details and use a
>> standard separator 😊
>>
>>
>>
>>
>>
>> alan
>>
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman@angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
