OUTFLOW.DAT - Githubissues

erpas commented 8 years ago

OUTFLOW.DAT information goes into the following GeoPackage tables:

outflow
outflow_cells*
outflow_chan_elems
outflow_hydrographs
time_series (the same we use for inflow data)
time_series_data (the same we use for inflow data)
qh_params

*we will use grid element and cell interchangeably.

gpkg table: outflow (contains general info about each outflow)

"fid" INTEGER NOT NULL PRIMARY KEY,
"name" TEXT, -- name of outflow
"time_series_fid" INTEGER REFERENCES time_series(fid), -- id of time series used for outflow
"ident" TEXT, -- OUTCHAR, identifier of inflow element type K for channel, N for floodplain (Outflow hydrographs O for floodplain elements go to separate table outflow_hydrographs)
"nostacfp" INTEGER, -- NOSTACFP, outflow element type 0 for floodplain, 1 for channel
"qh_params_fid" INTEGER, -- if OUTCHAR = H take stage-discharge relation parameters from table qh_params
"geom" POLYGON, -- area of outflow. In case of translating from DAT: it could be a part of the grid cell interior where the outflow is located in or a part of channel (grid_fid = NOSTA when ident = K and elem_id = KOUT when ident = K). When users modify the geometry automatic geoprocessing triggers will find grid cells or channel elements affected -> table outflow_cells or outflow_chan_elems.
"note" TEXT

gpkg table: qh_params (stage-discharge reletionship parameters)

"fid" INTEGER NOT NULL PRIMARY KEY,
"hmax" REAL, -- HOUT(J,1)
"coef" REAL, -- HOUT(J,2)
"exponent" REAL, -- HOUT(J,3)

gpkg table: outflow_cells (cells being affected by an outflow)

"fid" INTEGER NOT NULL PRIMARY KEY,
"outflow_fid" INTEGER NOT NULL REFERENCES outflow(fid), -- outflow id
"grid_fid" INTEGER NOT NULL REFERENCES grid(fid) -- NOSTA - grid element id affected by an outflow

gpkg table: outflow_chan_elems (channel elements being affected by an outflow)

"fid" INTEGER NOT NULL PRIMARY KEY,
"outflow_fid" INTEGER NOT NULL REFERENCES outflow(fid), -- outflow id
"elem_fid" INTEGER NOT NULL REFERENCES grid(fid) -- KOUT - grid element id affected by an outflow

gpkg table: time_series (named time series)

"fid" INTEGER NOT NULL PRIMARY KEY,
"name" TEXT, -- name of time series
"type" TEXT, -- type of data
"hourdaily" INTEGER -- IHOURDAILY - is time given in hours (0) or days (1)

gpkg table: time_series_data (time series data)

"fid" INTEGER NOT NULL PRIMARY KEY,
"series_fid" INTEGER NOT NULL REFERENCES time_series(fid), -- fid of time series the data pair belongs to
"time" REAL NOT NULL, -- time
"value" REAL NOT NULL -- value1
"value2" REAL -- value2
"value3" REAL -- value3

gpkg table: outflow_hydrographs (cells that should produce outflow hydrographs)

"fid" INTEGER NOT NULL PRIMARY KEY,
"hydro_fid" INTEGER NOT NULL, -- OUTCHAR, O-O9 - number of outflow hydrograph to be created
"grid_fid" INTEGER NOT NULL REFERENCES grid(fid) -- grid element id being a part of an outflow hydro_id

erpas commented 8 years ago

Jim, Karen, Naomi,

Do channel elements have the same number (KOUT) that the grid element they are located in (NOSTA)? Thanks!

FLO-2DJim commented 8 years ago

Rado: Yes...all grid element number is the same for channels, streets, outflow and inflow nodes. Internally in the FLO-2D code, channels, streets and other components have unique numbers starting with 1, but the user only sees the grid element number in the data files.

Jim

On Thu, Sep 8, 2016 at 7:19 AM, Radosław Pasiok notifications@github.com wrote:

Jim, Karen, Naomi,

Do channel elements have the same number (KOUT) that the grid element they are located in (NOSTA)? Thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lutraconsulting/qgis-flo-2d-plugin/issues/46#issuecomment-245567458, or mute the thread https://github.com/notifications/unsubscribe-auth/ATenh_sikjrcpI54LEr_1k5pxDZX2Tb2ks5qn-8qgaJpZM4J34HX .

Jimmy S. O'Brien FLO-2D Software, Inc./Riada Engineering (928) 339 1935

FLO-2DKaren commented 8 years ago

Hi Radoslaw,

The K line for a channel ouflow node is assigned to the left bank channel node. You can see an example in lesson 15 outflow.out.

Karen

From: Radosław Pasiok [mailto:notifications@github.com] Sent: Thursday, September 8, 2016 7:19 AM To: lutraconsulting/qgis-flo-2d-plugin Subject: Re: [lutraconsulting/qgis-flo-2d-plugin] OUTFLOW.DAT (#46)

Jim, Karen, Naomi,

Do channel elements have the same number (KOUT) that the grid element they are located in (NOSTA)? Thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lutraconsulting/qgis-flo-2d-plugin/issues/46#issuecomment-245567458, or mute the thread https://github.com/notifications/unsubscribe-auth/ATenDP3PUVmVYeS2ccgCxQybFesd-11tks5qn-8qgaJpZM4J34HX .[image: Image removed by sender.]

erpas commented 8 years ago

Jim, Karen, Naomi,

What is a time unit for stage-time relationships in OUTFLOW.DAT? In INFLOW.DAT it was defined by IHOURDAILY. Thanks!

erpas commented 8 years ago

Jim, Karen, Naomi,

We have two floodplain/channel indicators in OUTFLOW.DAT:

OUTCHAR = N or K
NOSTACFP = 0 or 1.

We understand that if OUTCHAR is N and NOSTACFP = 0 (stage-time relationship is for channel element) then the grid element stage is influenced by the stage from the channel element. Is that correct?

erpas commented 8 years ago

It would be great if you could point us to any example model having grid element with OUTCHAR = N and NOSTACFP = 0. This case is described in the Data Input Manual PRO, but to test the import/export functionality we would need that in a real example model. Thanks!

FLO-2DJim commented 8 years ago

In OUTFLOW.DAT, STA(I,J,1) is in hourly data only.

On Mon, Sep 12, 2016 at 5:29 AM, Radosław Pasiok notifications@github.com wrote:

Jim, Karen, Naomi,

What is a time unit for stage-time relationships in OUTFLOW.DAT? In INFLOW.DAT it was defined by IHOURDAILY. Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/lutraconsulting/qgis-flo-2d-plugin/issues/46#issuecomment-246295258, or mute the thread https://github.com/notifications/unsubscribe-auth/ATenh2X88sJVH8Gxs1bsEV5oEd13oMsBks5qpRt1gaJpZM4J34HX .

Jimmy S. O'Brien FLO-2D Software, Inc./Riada Engineering (928) 339 1935

FLO-2DJim commented 8 years ago

Radoslaw: If OUTCHAR = N and NOSTACFP = 0, the stage time is assigned to the floodplain outflow element.

If OUTCHAR = K and NOSTACFP = 1, the stage time relationship is assigned to the channel outflow element.

Jim

On Mon, Sep 12, 2016 at 5:36 AM, Radosław Pasiok notifications@github.com wrote:

Jim, Karen, Naomi,

We have two floodplain/channel indicators in OUTFLOW.DAT:

OUTCHAR = N or K

NOSTACFP = 0 or 1.

We understand that if OUTCHAR is N and NOSTACFP = 0 (stage-time relationship is for channel element) then the grid element stage is influenced by the stage from the channel element. Is that correct?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/lutraconsulting/qgis-flo-2d-plugin/issues/46#issuecomment-246296987, or mute the thread https://github.com/notifications/unsubscribe-auth/ATenh1_W-Y5s2HSgirK2NQRVE6oLikToks5qpR0agaJpZM4J34HX .

Jimmy S. O'Brien FLO-2D Software, Inc./Riada Engineering (928) 339 1935

FLO-2DJim commented 8 years ago

Karen or Noemi: Do you have an example for Radolaw?

On Mon, Sep 12, 2016 at 5:39 AM, Radosław Pasiok notifications@github.com wrote:

It would be great if you could point us to any example model having grid element with OUTCHAR = N and NOSTACFP = 0. This case is described in the Data Input Manual PRO, but to test the import/export functionality we would need that in a real example model. Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/lutraconsulting/qgis-flo-2d-plugin/issues/46#issuecomment-246297780, or mute the thread https://github.com/notifications/unsubscribe-auth/ATenh6a7oyNgomSDdr0-wRjkJVhQ5xy7ks5qpR3bgaJpZM4J34HX .

Jimmy S. O'Brien FLO-2D Software, Inc./Riada Engineering (928) 339 1935

FLO-2DKaren commented 8 years ago

Here is an example of a simple ouflow.dat Stage Time condition. OUTCHAE = N. This is only one single configuration. Once you understand it, let’s talk about the others.

From: Radosław Pasiok [mailto:notifications@github.com] Sent: Monday, September 12, 2016 5:40 AM To: lutraconsulting/qgis-flo-2d-plugin Cc: FLO-2DKaren; Comment Subject: Re: [lutraconsulting/qgis-flo-2d-plugin] OUTFLOW.DAT (#46)

It would be great if you could point us to any example model having grid element with OUTCHAR = N and NOSTACFP = 0. This case is described in the Data Input Manual PRO, but to test the import/export functionality we would need that in a real example model. Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/lutraconsulting/qgis-flo-2d-plugin/issues/46#issuecomment-246297780, or mute the thread https://github.com/notifications/unsubscribe-auth/ATenDHR38QAuujq0toxryBxPD4aMxEvyks5qpR3agaJpZM4J34HX .[image: Image removed by sender.]

FLO-2DKaren commented 8 years ago

Flume Stage Time.zip

FLO-2DKaren commented 8 years ago

Radek, See my previous post. It has an example of the outchar = N

FLO-2DSoftware / qgis-flo-2d-plugin

OUTFLOW.DAT #46