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

Implement Dataset Refs #164

Open
3 tasks
philipbaileynar opened this issue Sep 8, 2021 · 1 comment
Open
3 tasks

Implement Dataset Refs #164

philipbaileynar opened this issue Sep 8, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@philipbaileynar
Copy link
Contributor

philipbaileynar commented Sep 8, 2021

When business logic refers to data that has a ref attribute, ArcRAVE needs the ability to go find that referenced dataset elsewhere in the project. (QRAVE already does this.)

In python we do it this way:

https://github.com/Riverscapes/QRAVEPlugin/blob/dev/src/classes/project.py#L304-L361

Update:

I had to create a sample test project and business logic to test this

It's in nardata at the path nardata/Matt/RefProject.zip (80 Mb)

Two things to check:

  • regular nodes without ref= still load normally
  • Nodes with ref= get the right lookup and appear in the tree
  • Metadata values show correctly for nodes with ref=
@philipbaileynar philipbaileynar added the enhancement New feature or request label Sep 8, 2021
@philipbaileynar philipbaileynar self-assigned this Sep 8, 2021
@MattReimer MattReimer added this to the ArcRAVE 2.2 milestone Sep 8, 2021
@philipbaileynar
Copy link
Contributor Author

  1. Can nodes have both ref and xpath? If so what takes precedence?
  2. Can any node type have ref, or just GIS datasets?
  3. Does a business logic node that has an xpathlabel and that refers to a project node with a ref, does the xpathlabel refer to the project node or the referenced node?

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

No branches or pull requests

3 participants