From 56e1e5127917ac2da981421d093d76f1e3fb11ea Mon Sep 17 00:00:00 2001 From: Eli Ribble Date: Thu, 22 Jan 2026 04:50:20 +0000 Subject: [PATCH] fix up instructions on district import After doing it in prod. --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b10a53ba..936e7461 100644 --- a/README.md +++ b/README.md @@ -33,12 +33,14 @@ You'll need a number of environment variables for configuring things; ### Districts -There's a table containing district information in the database, `public.district`. It was created with: +There's a table containing district information in the database, `import.district`. It was created with: ``` -shp2pgsql -s 3857 -c -D -I CA_districts.shp public.district | psql -d nidus-sync psql -ALTER TABLE district ADD COLUMN geom_4326 geometry(MultiPolygon,4326) GENERATED ALWAYS AS (ST_Transform(geom, 4326)) STORED; +CREATE SCHEMA import; +shp2pgsql -s 3857 -c -D -I CA_districts.shp import.district | psql -d nidus-sync +psql +ALTER TABLE import.district ADD COLUMN geom_4326 geometry(MultiPolygon,4326) GENERATED ALWAYS AS (ST_Transform(geom, 4326)) STORED; ``` ## Hacking