#5603 closed defect (fixed)
TIGER 2023 support
| Reported by: | robe | Owned by: | robe |
|---|---|---|---|
| Priority: | blocker | Milestone: | PostGIS 3.4.1 |
| Component: | tiger geocoder | Version: | 3.4.x |
| Keywords: | Cc: |
Description
Looks like tiger 2023 is out and they changed their naming structure, so probably more work to do than past years
https://www2.census.gov/geo/tiger/TIGER_RD18/LAYER/
I'm not exactly sure why the folder name is RD18 and why the change in files to be prefixed with tl_rd22 instead of just https://www2.census.gov/geo/tiger/TIGER2022/ (tl_)
But anyrate I suspect things have changed enough that I might not be able to backport this to 3.4.1, and just slate this for 3.5.0.
Change History (4)
comment:1 by , 12 months ago
| Milestone: | PostGIS 3.5.0 → PostGIS 3.4.1 |
|---|
Version 0, edited 12 months ago by (next)
Note:
See TracTickets
for help on using tickets.
Okay this is not as much of a change as I feared. Seems changing loader_variables table is sufficient to make this work
is sufficient to make it work. That said I think I can backport this to 3.4.1 without issue.
I'm doing some tests on demo.postgis.net I have tiger_2022 loaded, not loading tiger_2023 with the changes to see if any issues before I push these.
So far so good. DC seems to have loaded fine and in middle of loading MA.
I guess Connecticut underwent some changes. We have one county less and 8 new Connecticut counties not in 2022 set.