Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#2413 closed defect (fixed)

Update to support TIGER 2013

Reported by: robe Owned by: robe
Priority: medium Milestone: PostGIS 2.1.1
Component: tiger geocoder Version: master
Keywords: history Cc:

Description (last modified by robe)

According to news on TIGER site, they will be producing the 2013 files this month (August 2013).

http://www.census.gov/geo/maps-data/data/tiger.html

Hope to jump on it as soon as it is available. Hopefully won't require too much (if any changing at all) of our loader scripts.

I'm also going to flatter the extras folder. Right now extras tiger structure looks like

extras\tiger_geocoder\tiger_2011

This is a misnomer since 2011 and 2012 use the same structure and the logic to load 2012 is in tiger_loader_2012.sql file which is the file included for postgis_tiger_geocoder extension.

Change History (6)

comment:1 Changed 6 years ago by robe

Description: modified (diff)

comment:2 Changed 6 years ago by robe

Summary: Update to suport TIGER 2013Update to support TIGER 2013

News Flash: Census just came out with the 2013 tiger data today

http://www.census.gov/geo/maps-data/data/tiger-line.html

comment:3 Changed 6 years ago by robe

Guess have to read this document to make sure no major changes and also to better the approximation of street ranges

http://www.census.gov/geo/maps-data/data/pdfs/tiger/tgrshp2013/TGRSHP2013_TechDoc.pdf

e.g compensate that the range is absolute maximum rather than reality.

comment:4 Changed 6 years ago by robe

Keywords: history added

NAtion script and state scripts seem to be working simply by changing the year in platform. Will close once made this the primary year in extension and tiger scripts after testing a bit more. committed at r11855

comment:5 Changed 6 years ago by robe

Resolution: fixed
Status: newclosed

I'm going to consider this done. I've tested on MA, DC, and testing now on CA and TX

comment:6 Changed 5 years ago by robe

Milestone: PostGIS 2.2.0PostGIS 2.1.1

Hmm I think I had actually shipped this with 2.1 so doesn't belong as a 2.2 item.

Note: See TracTickets for help on using tickets.