search

opengeospatial / HY_Features

http://opengeospatial.github.io/HY_Features/
Other
8 stars 1 forks source link

Look at cardinality on reservoir and and waterbody. #228

Closed dblodgett-usgs closed 7 years ago

IrinaDornblut commented 7 years ago

idea behind the cardinality of reservoir <> water body relationship: Cardinality on ‘reservoir.storedWaterBody’ is set 0..1 to describe the (managed) water body, cardinality of ‘waterBody.storage’ is set 0..* to describe separately the different demands/characteristics determined by multiple reservoir purposes. If required, an implementation may limit this to only one reservoir.

dblodgett-usgs commented 7 years ago

How would we model multi water body reservoirs? Such as a flow age with multiple named lakes.

On May 26, 2017 1:41:36 AM CDT, Irina Dornblut notifications@github.com wrote:

idea behind the cardinality of reservoir <> water body relationship: Cardinality on ‘reservoir.storedWaterBody’ is set 0..1 to describe storage characteristics of the (managed) water body, cardinality of ‘waterBody.storage’ is set 0..* to describe separately the different demands/characteristics determined by multiple reservoir purposes. If required, an implementation may limit this to only one reservoir.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/opengeospatial/HY_Features/issues/228#issuecomment-304205050

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

dblodgett-usgs commented 7 years ago

Would it be ok to make the cardinality on the "storedWaterbody" relationship 0..* ? image

IrinaDornblut commented 7 years ago

OK, done. -

grafik

IrinaDornblut commented 7 years ago

figure 44 in spec doc replaced with update

dblodgett-usgs commented 7 years ago

Great. Thanks!