Content

• Each row represents a Location that humans visit

  • E.g. Locations with logger, or that require manual measurement
  • Does not include fully-automated locations
  • Visited by NWFWMD staff or contractor (purple highlight)

• Project numbers, for billing

• Monitoring type

  • Type of sensor(s) deployed

• Telemetry

  • Identifies whether access is inside/outside NWFWMD firewall
    • Other agencies need access to some data, but don't have LAN access

• Various equipment columns

• Priorities

  • Mostly issues with locations
    • Different than Survey123 LocationIssue
  • Can move to location notes in Aquarius

Need to Add

• Phone number
  • Per Steve
  • For device? contact person?

Structure

• Station ID is unique
  • Also called "NWFID", "Unique ID"
• Names help users who don't have station IDs memorized

Migration

• Aquarius reports require development in C# or Java

To Aquarius

• We can store information in:
  • Built-in Aquarius attributes
  • Extended attributes
    • Only for Locations
      • Not attachments, etc.
    • Custom
    • Available through APIs
  • Tags
    • 1:M
    • Stored in separate table when ETLed to SQL Server
    • Allows filtering in API queries
      • Queries returning too much data tend to fail
    • Structured management in Aquarius
      • Have to be preconfigured
      • Get to choose what type of information tag applies to
    • Can run report on tags
      • Not able to run report on extended attribute
  • Notes
    • 1:M Location:Notes
    • Notes can have from/to dates indicating when they apply
  • Attachments
    • Have:
      • Tags
      • Comments
        • MP photo links stored here because we can't create extended attributes for attachments

Sensors

• Already place to hold sensor/gauge details

Locations

• Location Details tab
• Visit frequency
  • Expected to be queried
  • E.g. user will want to see all locations assigned to them and what the visit frequency is so they can plan visits
  • Probably requires tag
    • Alternatively, query / report in ArcGIS
    • Aquarius remains system-of-record > synced to geodatabase
• Collection interval
  • Probably not queried on, so suitable for location notes

Priorities

• Suitable for Aquarius location notes
• Different than geodatabase LocationIssue

Needs a Home

• Who is location assigned to

  • Possible Aquarius extended attribute or tag
  • Steve manages this content, but does not have edit permissions in Aquarius

• Last Visit / who visited last

  • Can derive from geodatabase LocationVisit
  • May need to sync to Aquarius, so available in one system
  • Aquarius already shows list of visits for each location
    • Can sort by date
    • Does this solve the problem?
    • Aquarius APIs would allow us to:
      • Read list of visits
      • Find most recent
      • Read write last visit date to extended attribute
      • Run report showing all locations + last visit date
        • See notes above about difficulty of Aquarius report development

Decisions

• Use Aquarius when we can

  • Many existing places to put information
  • Many options for adding custom information (e.g. tags, extended attributes, location notes, comments)

• Will need second system (e.g. ArcGIS) to meet some requirements

  • General reporting
    • Too difficult in Aquarius
  • Notifications
    • E.g. location issues highlighted in dashboard, webhook email sent

Requirements

Field User

"My Locations"

• Report of all locations for a user
  • Assigned to
  • Last visit date
    • Link to details?
  • Last visit staff
    • May be different than assigned staff
  • Visit frequency
  • Location notes
    • E.g. Location access instructions

Back Office

Location Issues

• Dashboard / notification / etc.

Survey with Discharge

• Need specific awareness when survey with discharge has been submitted
  • Requires manual review/processing

Integration

Aquarius > Geodatabase Sync

• E.g. update geodatabase copies of Aquarius information (e.g. location assignee, photo, serial #) when changed in Aquarius

• Daily sync likely sufficient

  • Ideally, on-demand sync option, too

• Will need to store more asset/config information in the geodatabase than we currently are

  • E.g. location notes
  • To do:
    • Update data model
    • Build sync solution

Geodatabase > Aquarius sync

• Interval
  • Automatically daily (overnight) sync
  • Require on-demand sync option, as well
    • Need more than one person to be able to do this
    • Craig/GIS/IT should all be able to do this
      • Need to know how