Skip to content

agrc/deq-enviro

Folders and files

NameName
Last commit message
Last commit date

Latest commit

6a663d3 Â· Dec 15, 2023
Dec 8, 2023
Dec 14, 2023
Oct 16, 2023
Dec 12, 2023
Mar 20, 2023
Oct 16, 2023
Oct 16, 2023
Dec 15, 2023
Dec 15, 2023
Nov 4, 2022
May 4, 2023
Mar 21, 2023
Dec 14, 2023
Dec 12, 2023
Mar 21, 2023
Dec 12, 2023
Oct 19, 2023
Mar 22, 2023
May 16, 2023
Oct 19, 2023
Dec 15, 2023
Mar 21, 2023
Sep 7, 2023
Dec 12, 2023
Sep 18, 2023
Dec 15, 2023
Dec 15, 2023
Sep 18, 2023
Dec 8, 2023
Sep 22, 2023
Sep 22, 2023
Sep 22, 2023

Repository files navigation

deq-enviro Build Status

DEQ Environmental Data Viewer

Generic application for searching, viewing and downloading DEQ GIS data and related tables.

Production Config Spreadsheet

Staging Config Spreadsheet

Stage - enviro.dev.utah.gov

Production - enviro.deq.utah.gov

Analytics Dashboard

Query Layers

Requirements

In order for a dataset to be used as a query layer within the application, it must satisfy all of the following requirements:

  • Hosted in ArcGIS Online or ArcGIS Portal
  • "Export Data" enabled

Field Aliases

These are managed via the "Data" tab of the AGOL item. Any changes should immediately be reflected in the application.

Symbology

This is managed via the "Visualization" tab of the AGOL item. Any changes should immediately be reflected in the application. If there is no specific symbology defined, the app has some reasonable defaults that look better than the AGOL defaults.

Map Labels

These are also managed via the "Visualization" tab of the AGOL item. Any changes should immediately be reflected in the application.

Links (Identify Panel)

The links in the "Links" tab in the identify panel are controlled via the corresponding columns in the config spreadsheet. If you want to append the feature's attributes to the URL, use the following syntax: https://example.com?param1={field1}&param2={field2}.

Data Schema Changes

Most updates are taken care of via the config spreadsheet.

Adding a New Query Layer

  1. Add the new row in the config spreadsheet
  2. Deploy changes

Deploy Steps

  1. Publish ExportWebMap service to the DEQEnviro folder using maps/PrintTemplates/Portrait.mxd as the default template.
    • Make sure that the server can resolve the domain name that the app is hosted on (e.g. test.mapserv.utah.gov). If it can't you will need to edit the hosts file. This is required for the ExportWebMap service.
    • synchronous
  2. Add repo to forklift.
    1. Copy scripts/nightly/databases & scripts/nightly/settings/__init__.py from old server.
    2. Download and install the latest oracle instant client.
    3. From within the forklift environment: pip install -r .\scripts\nightly\requirements.txt

Local Development

updateRemoteConfigFromSheets Function

You will need to copy the functions-key-dev.json key file from the terraform project to the functions directory in order to have permissions to hit the staging config spreadsheet.

Config Spreadsheet Deploy Addon

This is accomplished via Google Apps Scripts. An example script and json config can be found in the src/apps-script directory.

Note that the Apps Scripts GCP project needs to be pointed at the same GCP project as the hosting project.