8000 Move the generate centerline tool · Issue #440 · Riverscapes/QRiS · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Move the generate centerline tool #440

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

Closed
Jdgilby opened this issue Jul 10, 2024 · 1 comment
Closed

Move the generate centerline tool #440

Jdgilby opened this issue Jul 10, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Jdgilby
Copy link
Collaborator
Jdgilby commented Jul 10, 2024

Right now the only place you can access the Generate Centerline tool is through polygons features in the Context node. The main purpose of centerline is tracking metrics over riverscape so the riverscape is where it should come form.
Three requests:

  1. Remove access to centerline tool in Context node,
  2. Add the centerline tool to right click in polygons in Riverscapes node.
  3. To properties of saved centerline add the associated Riverscape valley bottom it was generated from.

I think importing a centerline from VBET and promoting will be a non issue because it will have that tracked through metadata.

@Jdgilby Jdgilby added the enhancement New feature or request label Jul 10, 2024
@Jdgilby Jdgilby added this to the 1.0 - Public Release milestone Sep 12, 2024
@KellyMWhitehead
Copy link
Collaborator
KellyMWhitehead commented Sep 14, 2024
8000
  1. Done for v0.9.4
  2. Done for v0.9.4
  3. The centerline tool already does this, however it saves this as 'system metadata' that QRiS does not currently exposed to the user. I should probably expose this to the user as a non-editable table or other format (see Show "System" metadata to the user. #498). Beyond exposing this to the user, we can start doing some 'smart' things with these feature associations in 1.1.

@Jdgilby Jdgilby self-assigned this Sep 17, 2024
@KellyMWhitehead KellyMWhitehead removed their assignment Sep 18, 2024
@Jdgilby Jdgilby closed this as completed Sep 18, 2024
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

2 participants
0