BAGIS V3

Key Features

Support Web Services in BASIN Creation

• • DEM

  • PRISM precipitation

  • USGS gauge stations

  • SNOTEL/Snow course sites

  • Reference layers

  • Other participating layers

Figure 1: BAGIS V3 Settings form

Updating the Default Layer Locations and Reference Layer .lyr file on the server

• • Secure a remote desktop connection to the server hosting the web services for the .json or .lyr file. For example: basins

  • Both files are located in the C:\ebagis folder

  • Overwrite the JSON in the YAML file or overwrite the .lyr file and save. The web service will automatically serve the latest data

  • Colons with spaces around them ( : ) are a reserved character and will break the web service

  • BAGIS - V3

    • These settings are at the top of the file and do not have a heading

    • Sample url for REST service that lists the BAGIS V3 data sources: https://test.ebagis.geog.pdx.edu/api/rest/desktop/settings/

    • These data sources are used when populating the BAGIS V3 settings screen

    • Example url for downloading reference .lyr file: https://test.ebagis.geog.pdx.edu/api/rest/desktop/lyr/

  • BAGIS - P

    • This section is headed by bagis-p:

    • Sample url for REST service that lists the BAGIS-P data sources: https://ebagis.geog.pdx.edu/api/rest/desktop/settings/bagis-p/

    • Sample entry in YAML file. These entries are children of the datasources tag. The id is the key and needs to be unique

      • - id: 4

      • name: JH_Coef_Aug_Tmax

      • source: http://bagis.geog.pdx.edu/arcgis/services/BAGIS_Databin/PRISM_1981_2010_tmax_august/ImageServer

      • description: August Max Temperature for JH_Coef estimation

      • jhCoeff: JH_Coef_Aug_Tmax

  • BAGIS-PRO

    • This section is headed by bagis-pro:

  • Sample url for REST service that lists the BAGIS-PRO data sources metadata: https://ebagis.geog.pdx.edu/api/rest/desktop/settings/bagis-p/

  • Sample entry in YAML file. These entries are children of the datasources tag. The layerType is the key and needs to be unique

    • • - layerType: Snotel SWE

      • description: SWE Data Source - Averaged daily SNOw Data Assimilation System (SNODAS) Snow Water Equivalent (SWE) from 2004 to 2019 data

      • source: http://bagis.geog.pdx.edu/arcgis/services/DAILY_SWE_NORMALS/

Reference Layers

• • Form fields: Terrain Ref, Drainage Ref, Watershed Ref

  • Data source(s): File system or map service

  • Function: Load into ArcMap when user selects 'Add Ref Layers' menu item, OR 'Add Ref. Layers to Map' button on settings form; Load into ArcMap when user selects 'Set DEM Extent' tool

Analysis Layers (feature class)

• • Form fields: Gauge stations, SNOTEL, Snow Course

  • Data source: feature access service

  • Function: Snotel and Snow Course Clip to AOI boundary in Create AOI tool, Re-Clip BAGIS Layers tool, Create AOI from Shapefile tool

  • Function: Query feature access service for attribute field names to populate Name and Area fields for Gauge Stations; Elevation and Name fields for SNOTEL and Snow Course layers

  • Function: Spatial query/Attribute query for Pour Points tool to retrieve names of gauge stations within basin boundary; The gauge station names are added to user list

  • Function: Set selected features when user selects a gauge name from the list, this gauge is selected on the feature access service layer in the display

Analysis Layers (raster)

• • Form fields: 10 Meters DEM, 30 Meters DEM, Precipitation

  • Data source: image service; PRISM points to parent folder

  • Function: Clip DEM with 'Clip DEM Tool'

  • Function: Clip DEM (Create AOI from Shapefile tool only) and all PRISM layers to AOI boundary in Create AOI tool, Re-Clip BAGIS Layers tool, Create AOI from Shapefile tool

  • PRISM layers are clipped at the AOI creation, not at Basin creation so they won't be local until that point

Updates to settings form appearance

• • Add button called "Default Settings" above Save Settings button for setting the default web services for each data layer. These settings will be delivered as a json package from a REST webservice so that they can be changed without recompiling the AddIn.

Notes/Questions

• • Basins and AOIs may be created from a file system OR from the web services or a combination

  • The 'Add new Layer to AOI' tool and 'Other Participating Layers' list do NOT support feature access or image services.

  • Gauge stations are NOT clipped to the Basin or AOI.when they are created. The station locations are used as a reference for selecting the pourpoint of the AOI. Some attributes of the stations are copied to the pourpoint layer when the AOI is created.

  • We will determine if the data source is a web service or on the file system by searching for ImageServer/FeatureServer in the data source name.

  • For all types of layers, BAGIS should check to make sure the services are accessible as it does today with the file system. Show an error if any of the required layers are missing.

  • Buttons for all form fields must allow the user to select the appropriate web service from the IGXCatalog control. The 3 point layers (gauge stations, snotel, and snow course) must be feature access services. We need to warn users of this requirement if they want to use web services other than what are on our ArcGIS servers (e.g., Atlas).

  • We distribute a .lyr file via the file system that points at a map service and this layer will be added to the map when it is loaded. This layer will be downloaded from a REST webservice so we can swap it out without recompiling the AddIn.

  • Where do we get the location of the "default web services". Is it possible to run some sort of query against a service? This way the default web services locations could be changed from the server side without recompiling the client.

Services available as of January 1, 2020