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
Permits need the ability to track where they have been derived from other permits [0..n].
This is particularly useful for tracking the progress from exploration through to production AND for reconciling reserves and production statistics. @LizDerrington@DavidCrosswellGSQ
e.g.
ATP123 is converted to PL987
PL456 and PL 654 merge to PL1010
ATP123 has an associated PCA4 overlaying
ATP314 splits into ATP 312 and ATP 316
Part of ATP 333 is carved off to create PL33 whilst leaving a remnant ATP333
The text was updated successfully, but these errors were encountered:
How are you modelling permits? AFAICT they are they grant certain rights and obligations related to a specified geographic area in a specified time-span. Very similar to cadastre. Can you borrow from cadastral models?
Each permit will be linked to a time interval, and a set of geometries. The permit type will define what set of rights are bestowed upon the permit. Each geometry will also require its own independent time interval to reflect common occurrences during life-of-tenure over a permit that change the shape i.e. partial relinquishments and surrenders.
@DavidCrosswellGSQ our data profile diagram does need some updating to reflect the changes discussed since the last revision.
Permits need the ability to track where they have been derived from other permits [0..n].
This is particularly useful for tracking the progress from exploration through to production AND for reconciling reserves and production statistics. @LizDerrington @DavidCrosswellGSQ
e.g.
The text was updated successfully, but these errors were encountered: