[193005] in North American Network Operators' Group
Re: SNMP syslocation field for GPS coordinates, and use with
daemon@ATHENA.MIT.EDU (Eric Kuhnke)
Fri Dec 9 17:46:53 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <78222.1481323210@turing-police.cc.vt.edu>
From: Eric Kuhnke <eric.kuhnke@gmail.com>
Date: Fri, 9 Dec 2016 14:46:27 -0800
To: Valdis.Kletnieks@vt.edu
Cc: "nanog@nanog.org list" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
If you think that's bad, the public copy of the entire Industry Canada
licensed frequency database (for every type of radio system, nationwide)
comes in a giant space delimited text file with many database fields
truncated when they export it from whatever ancient database system they're
using. Nevermind that the owner/control entity fields and many other fields
also contain spaces.
The FCC version which is much more sane and usable is a pipe delimited CSV
format file with no fields cut off.
On Fri, Dec 9, 2016 at 2:40 PM, <Valdis.Kletnieks@vt.edu> wrote:
> On Fri, 09 Dec 2016 22:09:40 +0000, Alan Buxey said:
> > Yes. But don=C3=A2=E2=82=AC=E2=84=A2t just put in coordinates... Put in=
other details and use
> a
> > standard separator
>
> You want to tell that to the creator of some software I recently
> encountered
> that used a non-breaking space rather than a tab, or comma, or other sane
> values? :)
>
>
