Merge pull request #1601 from cityofaustin/19633-jc-eaz-layer

Create equity action zones layer

database/metadata/databases/default/tables/geo_equity_action_zones.yaml

@@ -0,0 +1,3 @@
+table:
+  name: equity_action_zones
+  schema: geo

database/metadata/databases/default/tables/tables.yaml

@@ -2,6 +2,7 @@
 - "!include geo_atd_jurisdictions.yaml"
 - "!include geo_council_districts.yaml"
 - "!include geo_engineering_areas.yaml"
+- "!include geo_equity_action_zones.yaml"
 - "!include geo_non_coa_roadways.yaml"
 - "!include geo_signal_engineer_areas.yaml"
 - "!include geo_zip_codes.yaml"

database/migrations/default/1731432466891_create_equity_action_zones_layer/down.sql

@@ -0,0 +1 @@
+drop table "geo"."equity_action_zones";

database/migrations/default/1731432466891_create_equity_action_zones_layer/up.sql

@@ -0,0 +1,13 @@
+create table "geo"."equity_action_zones" (
+    geoid text primary key,
+    indxd_v numeric,
+    eaz_type text,
+    geometry public.geometry (multipolygon, 4326) not null,
+    created_at timestamptz default now() not null
+);
+
+create index on "geo"."equity_action_zones" using gist (geometry);
+
+comment on column geo.equity_action_zones.geoid is 'The US census geoid of the census tract that matches this feature';
+comment on column geo.equity_action_zones.indxd_v is 'Vulnerability index on a scale of 0-100';
+comment on column geo.equity_action_zones.eaz_type is 'Description of the level of vulnerability';

toolbox/load_agol_layer/README.md

@@ -31,7 +31,7 @@ node --env-file=local.env src/load_agol_layer.js --layer signal_engineer_areas
 
 Each layer must be configured in the `LAYERS` object in [`settings.js`](/toolbox/load_agol_layer/src/settings.js). See the docstring in the settings file for specifics.
 
-When creating a new database table to hold feature data, polygon geometries should always be stored in a `Multipolygon` column type to avoid future issues. As well, any columns that will be populated with AGOL feature attribute data should exactly match the column names used in AGOL, except they should be lowercase.
+When creating a new database table to hold feature data, polygon geometries should always be stored in a `Multipolygon` column type called `geometry` to avoid future issues. As well, any columns that will be populated with AGOL feature attribute data should exactly match the column names used in AGOL, except they should be lowercase.
 
 See the [database documentation](/database#geospatial-layers) about geospatial layers for additional details.
 

toolbox/load_agol_layer/src/settings.js

@@ -74,6 +74,13 @@ const LAYERS = {
     fields: ["ZIPCODE"],
     tableName: "zip_codes",
   },
+  equity_action_zones: {
+    service_name: "Equity_Analysis_Zones_2021",
+    layer_id: 0,
+    query_params: { ...DEFAULT_ESRI_QUERY_PARAMS },
+    fields: ["GEOID", "indxd_v", "EAZ_Type"],
+    tableName: "equity_action_zones",
+  },
 };
 
 module.exports = {