[FEAT-API]: Create Hydrograph Manipulation table and handlers for basic input

[martyheynbah]

Create the Hydrograph Manipulation table and add foreign keys to existing tables. Below are possible columns, constraints. and relationships, please confirm all with @trietmnj:

• hydrograph manipulation columns
  • name: string not null
  • description: string
  • start_date: date
  • end_date: date
  • tides: float
  • depth_limiations: float
  • alpha: float
  • beta: float
• h5 table columns (many to 1 relationship with hydrograph table)
  • file_type: enum ('water_level', 'wave')
  • filename: string
  • reach: foreign _key (maybe in H5 table instead as all reaches required)
  • savepoint: foreign_key (maybe in H5 table instead)
• each savepoint will need 2 h5 attached. 1 water level h5 file and 1 waves h5 file

• @trietmnj what output data from the hydrograph run will we need to store. Based off this we can think about if this is stored in this table or a separate table

Create handlers to:

• GET list all hydrographs
• POST create hydrographs
• PUT update hydrographs
• DELETE remove hydrographs

[martyheynbah]

@Cheng-Kevin2 as I promised in the sprint planning meeting... half baked table schema sketches:

[trietmnj]

Here is an example of the data generated from the Hydrograph Manipulator.

EventDate_LC.zip