PostGIS includes Tiger/LINE data

[lukehutch]

Hi, I see you made some effort to reduce the layer size in your Docker image. However, you are depending upon the postgis image, not the postgres image. The postgis image includes the Tiger/LINE data, which is large. Wouldn't it be better to base your image on postgres, and just install the postgis extension?

[joshuasundance-swca]

Great point! Thank you for pointing this out. I will check it out this week-- or you could submit a pull request. 😀

Thanks again.

[lukehutch]

Thanks -- in the end I decided to go with a different Docker image though, because your image is based on Postgres 13, and I was looking for a Docker image based on Postgres 16.

However, in case it helps, here are the tables that are set up by the postgis/postgis image that your image is based on:

# \dt
                   List of relations
  Schema  |           Name           | Type  |  Owner   
----------+--------------------------+-------+----------
 public   | spatial_ref_sys          | table | postgres
 tiger    | addr                     | table | postgres
 tiger    | addrfeat                 | table | postgres
 tiger    | bg                       | table | postgres
 tiger    | county                   | table | postgres
 tiger    | county_lookup            | table | postgres
 tiger    | countysub_lookup         | table | postgres
 tiger    | cousub                   | table | postgres
 tiger    | direction_lookup         | table | postgres
 tiger    | edges                    | table | postgres
 tiger    | faces                    | table | postgres
 tiger    | featnames                | table | postgres
 tiger    | geocode_settings         | table | postgres
 tiger    | geocode_settings_default | table | postgres
 tiger    | loader_lookuptables      | table | postgres
 tiger    | loader_platform          | table | postgres
 tiger    | loader_variables         | table | postgres
 tiger    | pagc_gaz                 | table | postgres
 tiger    | pagc_lex                 | table | postgres
 tiger    | pagc_rules               | table | postgres
 tiger    | place                    | table | postgres
 tiger    | place_lookup             | table | postgres
 tiger    | secondary_unit_lookup    | table | postgres
 tiger    | state                    | table | postgres
 tiger    | state_lookup             | table | postgres
 tiger    | street_type_lookup       | table | postgres
 tiger    | tabblock                 | table | postgres
 tiger    | tabblock20               | table | postgres
 tiger    | tract                    | table | postgres
 tiger    | zcta5                    | table | postgres
 tiger    | zip_lookup               | table | postgres
 tiger    | zip_lookup_all           | table | postgres
 tiger    | zip_lookup_base          | table | postgres
 tiger    | zip_state                | table | postgres
 tiger    | zip_state_loc            | table | postgres
 topology | layer                    | table | postgres
 topology | topology                 | table | postgres
(37 rows)
```console

[lukehutch]

Oh, I just looked in these tables and they are empty! I thought it was a complete release of Tiger/LINE (which is a lot of data). These are just placeholders. Probably one of the postgis extensions needs these, but I doubt postgis itself needs them. Anyway, this is not such a big deal if the data is not installed in the default database.

[joshuasundance-swca]

I don't remember exactly why I used postgres 13. I think it may have been because that's what the pgvector installation notes said to use... or something like that. There was definitely a reason. 😅

I like the idea of updating it though. I'll see if I can get it all fixed up.