Gleipnir/nidus-sync
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

fix up instructions on district import

Browse source 
After doing it in prod.
This commit is contained in:
Eli Ribble 2026-01-22 04:50:20 +00:00
parent f38381eaf0
commit 56e1e51279
No known key found for this signature in database
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -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