Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permits need Origin Story #1

Open
KellyVance opened this issue Oct 30, 2019 · 2 comments
Open

Permits need Origin Story #1

KellyVance opened this issue Oct 30, 2019 · 2 comments

Comments

@KellyVance
Copy link
Contributor

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
@dr-shorthair
Copy link

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?

@KellyVance
Copy link
Contributor Author

KellyVance commented Oct 30, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants