Opened 9 years ago
Last modified 7 years ago
#3247 new enhancement
Bring in additional faces columns
| Reported by: | mattybe | Owned by: | robe |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Fund Me |
| Component: | tiger geocoder | Version: | master |
| Keywords: | Cc: | mattybe |
Description (last modified by )
As noted in #3227 by mattybe
Could the columns in tiger.faces be updated with this? I still see cd108fp, cd111fp, statefp00, etc. Some columns missing from current faces files are cd114fp, statefp10, blkgrpce10, etc. Details of the current columns are on page 3-66 here: http://www2.census.gov/geo/pdfs/maps-data/data/tiger/tgrshp2015/TGRSHP2015_TechDoc.pdf
Regina's note I'm hesitant to do this because it requires extra maintainance each year, and it's not used by the geocoder.
Attachments (1)
Change History (8)
comment:1 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Reporter: | changed from to |
comment:2 by , 9 years ago
comment:3 by , 9 years ago
| Cc: | added |
|---|
comment:5 by , 9 years ago
mattybe,
I see you caught some changes I missed on upgrade_geocode script.
Unfortunately, like I said this will need to wait. The problem with changing the lookup tables, is I don't currently upgrade them during extension upgrade, and since people data inherits these tables, any upgrade they do will destroy their existing data.
The only way I can think of to not make upgrade a nightmare would be to have existing obsolete table columns renamed (to their equivalent new) and add additional columns that are missing.
Anyway still too late for PostGIS 2.2 round.
Thanks, Regina
comment:6 by , 9 years ago
Count me in as a +1 for updating the FACES table for census work.
The 'new' column names appear to be consistent to the 2014 data which remained unfixed (I thought waiting for this 2015 release) from ticket #2915.
The 2013 set appears to be the last version that provides the needed census lookup information.
I hope it will be maintained since the changes are well documented and there are many uses for having the census data loaded. But if the team's not committed to staying consistent with the TIGER data it would probably be best to just drop all the old columns, since now there are just a bunch of nonsense columns full of NULLs taking up space.