ToDo SWMM

This is a list of notes that are being observed while working on SWMM.

1. Scenario Name is being hardcoded somewhere as the value is not changing when I press on the other rows. List of my current Open tickets in order ish.

SWMM

Frontend

1. Sensor Data - I am fixing the API Query now.
2. Review React Cesium Code
3. Do some testing and make sure we are not hardcoding anything. See list above.
4. Look into 3D mapping and SWMM Low Priority.

API

1. Test API Methods.
2. Look at Storage with an eye to redoing it. Low Priority. (Make Sure as is is documented)

Stormwater

API

1. Review common Data access
2. See if I can find out why Swagger is not working in Stormwater.
3. Test The API.
4. Soil Data always could be better.
5. Look at Storage with an eye to redoing it. Low Priority. (Make Sure as is is documented)

Front End

1. Soil Data EPA vs GQC
2. Compare EPA SWC and GQC SWC
   1. Write up a memo on what EPA has that we do not and how we could improve GQC.
3. Modify Transparency of map overlays
4. Code Cleanup
   1. Add Comments
   2. Remove unused packages and libs.
   3. Update Readme
   4. Find and Document Unused code.
   5. Linting

HydroTrek

What projects are we going to be using in the future.

EX TL RM SV EPANET

1. Get all projects working On msi-laptop 2
   1. Cleanup Nuget Packages.
   2. Check for Doxygen comments and Run Doxygen
   3. Publish and test installation versions
   4. Check naming is consistent (TL)
2. MSX version validation and verification
   1. Start with GUI 32 bit version and Caleb's 64 bit version.
3. MSX difference between GQC vs EPA version.
4. TL Proper storing and use of volume curve
5. Are we still going to use RM or is EPANET Console Core replacing it?
6. SV create a cross-reference table using EPANET
7. Is SV getting reworked into React?
8. Insert SCADA Summary in TL
9. Implement Link Results
10. Refresh where we are in Power BI
11. WNTR
12. Create a Metric for PDA DDA 32 and 64 bit versions 2.2 and 2.3