You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need an immutable object-identification, because:
We want to be able to link non-hydamo properties to an hydamo-object.
We want to link our modelled objects to HyDAMO. Models last +/- 5 years. After 5 years we still want to be able to link the model to the object so we can e.g. (1) update the modelled object with new parameters, (2) link modelled results to the object
What we see:
globalid is still changing between different table versions supplied by water authorities
nen3610id uses objectid which is the ArcGIS table index. This is quite dangerous as we assume objectid will change when a water authority re-indexes/rebuilds its database
For modelling purposes we propose to use the code column instead to introduce a field model_id to use in models and can be related to objects as long as they have a code:
NL.WBHCODE.{wbhcode}.{layer}.{code}
We'll introduce a method on a HyDAMO layer that will:
Validate if code is filled; return an exception if it is not
populate a column with model_id
add the column to the layer-schema so it is saved when a user writes a geopackage
The text was updated successfully, but these errors were encountered:
Seems waterbeheercode is only available for water authorities. We need codes for rijkswaterstaat, found objects managed by Provinces and can imagine municipalities manage objects as well. A sollution to solve it all is to start using BGT-codes: https://www.kadaster.nl/-/bgt-bronhoudercodes-per-1-1-2022 as they are available for all authorities. Then:
NL.BGTCODE.{bgt_code}.{layer}.{code} would be the format-string-template
We need an immutable object-identification, because:
What we see:
globalid
is still changing between different table versions supplied by water authoritiesnen3610id
usesobjectid
which is the ArcGIS table index. This is quite dangerous as we assumeobjectid
will change when a water authority re-indexes/rebuilds its databaseFor modelling purposes we propose to use the
code
column instead to introduce a fieldmodel_id
to use in models and can be related to objects as long as they have acode
:We'll introduce a method on a HyDAMO layer that will:
code
is filled; return an exception if it is notmodel_id
The text was updated successfully, but these errors were encountered: