Team Meeting Agenda - NWFWMD-IT/Hydrologic-Monitoring-Project GitHub Wiki

Every Meeting

  • Review issues with Done status
    • Close and move to Reviewed (assuming no follow-up work discovered during review)
  • Review issues with Blocked status

Meeting: 2025-01-06

  • Export district monitoring data from Aquarius > import to hydro geodatabase (#188)

    • Michael: Send Craig list of attributes
    • Craig: Export to file geodatabase
    • Michael: Import to hydro geodatabase
  • Update Sensor / Data Logger domain values (#203; Katie, Craig)

  • Aquarius source data

    • Measuring Point datums (#82; Katie)
    • Photos (#82; Katie, Steve)
  • Aquarius integration update (Craig, Katie)

    • Need to update field names / column aliases (#178)
  • District Monitoring migration status (#188; Katie)

Tasks to Get to Production

  • Deploy Survey123 to field devices
    • Upgrade field laptops to Windows 11
      • Complete except for one machine that doesn't support Windows 11
        • Running Windows 10
        • Meets the current business need, because we're no longer using Windows Subsystem for Android
  • Update data in Aquarius > import to geodatabase:
    • Measuring Points (target last week December)
      • Incorrect vertical datum
      • Missing from some Locations
    • Photos (2024-12-02 112 of ~700 remaining; target last week of December)
    • New equipment / serial numbers
      • Several dozen items in coming month(s)
        • Equipment has arrived
        • Needs to be installed
      • Ideally, update District Monitoring spreadsheet > import to clean geodatabase before production
        • Being rolled out gradually
  • Procedure for propagating Aquarius changes to geodatabase
    • Photos
      • Have loader that handles incremental changes
    • New information migrated to Aquarius from District Monitoring spreadsheet
      • Manually update Aquarius + geodatabase with changes (e.g. serial#) until or unless that becomes more burdensome than writing an incremental data loader / sync tool
  • Procedure for propagating survey data from geodatabase to Aquarius
    • Review surveys before sending to Aquarius
      • Discharges / ADVM need to be reviewed in other software first
        • Possibly edited
        • Cannot be edited once it's loaded to Aquarius
        • Notify Katie that new discharge / ADVM is available for review
          • Research solutions (#186)
          • Implement solution (#191 pending Enterprise upgrade)
  • Move District Monitoring spreadsheet to geodatabase (#178, 188)
    • Data mostly migrated (pending project number, #188)
    • Need dashboard for end-user interface (#202)
      • Workforce excluded because need for mobile device
  • Training
    • Slow rollout?
  • See Future section below for survey update related questions

On Hold

  • #96 Continue reviewing as a group
    • Workflow diagram annotated with where we left off

Future

Production Updates to Survey / Data

  • Continue discussion about workflow / automation for "republishing" survey when something changes:
    • Survey will need to be modified by GIS staff and republished from Survey123 Connect application under these circumstances
      • New field added to database
      • Domain updated in the database
      • Question in the survey needs to be reworded or modified
    • When a new location gets added or modified in the database the following changes will need to occur:
      • Measuring Point (CSV) to be updated via a manual upload or updated with a script
      • Photos for the location to be added manually via a survey or copied over with a script