[26406] in North American Network Operators' Group
Re: lata maps
daemon@ATHENA.MIT.EDU (Forrest W. Christian)
Fri Dec 31 04:15:51 1999
Date: Fri, 31 Dec 1999 02:09:05 -0700 (MST)
From: "Forrest W. Christian" <forrestc@iMach.com>
To: Jeremy Porter <jerry@fc.net>
Cc: Nathan Stratton <nathan@robotics.net>,
Andrew Brown <atatat@atatdot.net>,
"Damon M. Conway" <damon@chiba.3jane.net>, nanog@merit.edu
In-Reply-To: <199912310658.AAA99604@freeside.fc.net>
Message-ID: <Pine.BSF.3.96.991231020130.21523E-100000@workhorse.iMach.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
> It would be nice to have in a vector based format, either in lat/lon or
> offset, say dxf or even better in DLG/SDTS format. It would be even better
> with NPA/NXX info also plotted, but that might be asking to much, but
> since we're asking. Anyone know of such a thing?
I would LOVE something like this.
However, it gets A LOT more difficult, especially in rural US than you'd
expect.
In Montana, noone knows where exactly the lata line is. The reason is
that the only thing defining the lata line is which NPA NXX'es are where.
So, when you get "close" you have to actually call someone up with a clue
and ask. And sometimes, you find that some physical locations are either
in NEITHER lata or effectively in EITHER (depends on which telco you can
convince to drag you the line). Of course, the only locations in either
are so remote that they are useless for playing cross-lata games.
I personally would like to shoot whichever idiot thought up the brilliant
idea of cutting our state of less than a million people in half by that
(@#*$@# lata line. Shure would make my life easier.
- Forrest W. Christian (forrestc@imach.com) KD7EHZ
----------------------------------------------------------------------
iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com
Solutions for your high-tech problems. (406)-442-6648
----------------------------------------------------------------------
