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
Usability improvement: Multipolygon vertex table: make affiliation/membership of points and of polygon contained in a Multipolygon transparent to the user
#41621
Open
tschmetzer opened this issue
Feb 17, 2021
· 0 comments
Multipolygon vertex table: make affiliation/membership of points and of polygon contained in a Multipolygon transparent to the user. Based on the table it is barely not determinable what points belong to what polygon and how many polygons there are. Currently the multipolygon has only a "flattened" representation in the user interface. The current representation does not support a python script writer looking for understanding his data.
Of course we would first need to create and agree on a concept how to cleverly visualize a multipolygon's structure (exterior and multiple interior rings) and its coordinates.
What about this proposal to start with:
What does "r" mean by the way? I am only aware of Z and M values for each vertex...
The text was updated successfully, but these errors were encountered:
Multipolygon vertex table: make affiliation/membership of points and of polygon contained in a Multipolygon transparent to the user. Based on the table it is barely not determinable what points belong to what polygon and how many polygons there are. Currently the multipolygon has only a "flattened" representation in the user interface. The current representation does not support a python script writer looking for understanding his data.
Of course we would first need to create and agree on a concept how to cleverly visualize a multipolygon's structure (exterior and multiple interior rings) and its coordinates.
What about this proposal to start with:
What does "r" mean by the way? I am only aware of Z and M values for each vertex...
The text was updated successfully, but these errors were encountered: