DEQ Environmental Data Viewer
Generic application for searching, viewing and downloading DEQ GIS data and related tables.
Production - enviro.deq.utah.gov
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
These are managed via the "Data" tab of the AGOL item. Any changes should immediately be reflected in the application.
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.
These are also managed via the "Visualization" tab of the AGOL item. Any changes should immediately be reflected in the application.
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}¶m2={field2}
.
Most updates are taken care of via the config spreadsheet.
- Add the new row in the config spreadsheet
- Deploy changes
- Publish ExportWebMap service to the
DEQEnviro
folder usingmaps/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
- 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
- Add repo to forklift.
- Copy
scripts/nightly/databases
&scripts/nightly/settings/__init__.py
from old server. - Download and install the latest oracle instant client.
- From within the forklift environment:
pip install -r .\scripts\nightly\requirements.txt
- Copy
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.
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.