[178757] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: FCC form 477 geocoding

daemon@ATHENA.MIT.EDU (Jay Hennigan)
Tue Mar 3 20:43:22 2015

X-Original-To: nanog@nanog.org
Date: Tue, 03 Mar 2015 17:43:15 -0800
From: Jay Hennigan <jay@west.net>
To: Sean Donelan <sean@donelan.com>
In-Reply-To: <alpine.BSF.2.11.1503031808390.53304@cnex.qbaryna.pbz>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

On 3/3/15 15:13, Sean Donelan wrote:
> On Tue, 3 Mar 2015, Jay Hennigan wrote:
>>> Well you'll need to translate those into addresses.  That should be easy
>>> with Google or Bing.
>>
>> We have the addresses, need census tract and block.
> 
> For small address batches you can use the Census Geocoder.  The
> documentation is at
> 
> http://www.census.gov/geo/maps-data/data/geocoder.html
> 
> Basically you upload a CSV file addresses and you'll get back FIPS
> codes for state, county, census tract and census block for each address.
> Concatenate the FIPS state+county+censustract code (not the census block).

This turns out to be the least hassle, thanks to all in the group who
replied. Note that although the Census website says that it will handle
a CSV file of up to 1000 addresses, in reality it pukes on anything
greater than about 100 at a time.


-- 
--
Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net
Impulse Internet Service  -  http://www.impulse.net/
Your local telephone and internet company - 805 884-6323 - WB6RDV

home help back first fref pref prev next nref lref last post