-
-
Notifications
You must be signed in to change notification settings - Fork 808
Add docs for identify tool for mesh layer #10252
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
base: master
Are you sure you want to change the base?
Conversation
.. _exploring_mesh: | ||
|
||
Exploring mesh datasets | ||
======================== | ||
|
||
Using the identify tools | ||
------------------------ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason to have two levels of title here? And there is only one child section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure though, probably just in case we have other ways other than identify tools to explore mesh dataset in the future? @DelazJ
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably... But I don't see what other ways we have today so would rather stick to a single level that we could adjust when the features are made available.
|
||
* **Dataset values** for the clicked element: | ||
|
||
* The active dataset groups (scalar and, if available, vector) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* The active dataset groups (scalar and, if available, vector) | |
* The active dataset groups (scalar and/or vector) |
You get info on the groups you made active and nothing prevents you from only enabling the vector one and deactivating the scalar
When the map canvas is non-temporal (temporal navigation disabled), | ||
the results only contain values from the static dataset groups defined | ||
in the mesh layer properties. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this block belongs to the "Dataset values|groups" item. The "geometry information" and some of the returned properties are available in all cases, regardless of temporal controller, and it looks unclear to me how these outputs relate to each other.
As far as I understand the results, you get either:
- TC is off: only the selected dataset groups with the value configured for their static state. Source is displayed for each. And x/y component for the vector dataset group.
- TC is on: all available groups with their value "corresponding" to the current time. Source is displayed for each. And x/y component for the vector dataset group. And an additional field showing the actual time step value.
- in both cases, Geometry information
* Center of a snapped edge (if the click was snapped to an edge). | ||
|
||
When the map canvas is non-temporal (temporal navigation disabled), | ||
the results only contain values from the static dataset groups defined |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add a link to guide people to what we are talking about (I couldn't find a closer anchor)
the results only contain values from the static dataset groups defined | |
the results only contain values from the :ref:`static dataset groups <meshsource>` defined |
Sorry @hefniraera I do not understand your latest changes. Geometry information is mentioned twice, and nothing indicates that inactive dataset groups are shown only in TC on context. |
Sorry about that, I guess I wasn’t focused enough. Let me fix that. |
Fixes #5894
Goal:
Ticket(s): #