#562: patch proposal: do not show delimiters for empty labels in case of multiple
cats per feature
-------------------------+--------------------------------------------------
Reporter: mlennert | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: default | Version: svn-trunk
Keywords: | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
The attached patch (against svn7) slightly modifies d.vect in that it only
displays delimiters ("/") for those category values where label values
actually exist. I attache two screenshots to make clearer what the patch
does.
I would just submit the patch without posting, but I'm not sure if some
people find it important to see the existance of null values for some
categories. However, if no one objects, I'll commit.
#562: patch proposal: do not show delimiters for empty labels in case of multiple
cats per feature
--------------------------+-------------------------------------------------
Reporter: mlennert | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: default | Version: svn-trunk
Resolution: | Keywords:
Platform: Unspecified | Cpu: Unspecified
--------------------------+-------------------------------------------------
Comment (by hamish):
what's the command line option to do that? I'm not sure I know what that
does.
my gut feeling is that those empty delimiters actually do show
information: positional. if you remove them and only one field has a
value, which field did it come from, a, b, or c?
#562: patch proposal: do not show delimiters for empty labels in case of multiple
cats per feature
--------------------------+-------------------------------------------------
Reporter: mlennert | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: default | Version: svn-trunk
Resolution: | Keywords:
Platform: Unspecified | Cpu: Unspecified
--------------------------+-------------------------------------------------
Comment (by dersh):
I think that it really depends on the data.
For example, if you were doing samples at several locations once a month,
but a few of the actual samples got lost in processing, then I would say
that you are correct that missing data should be shown.
On the other hand if the data is "missing" because it is the result of a
query, ("select where value > 10" or "select where date < 2007-01-01")
then you intentionally don't want to show some data, and having those
slashes doesn't show any useful information.
I would argue that if you actually are missing data, then it should be
entered into the database as missing (-999, "M" whatever is appropriate
for the type of data), rather then just leaving it blank.
Perhaps the best answer would be to a flag for which behavior is desired.
I would also propose that the user should be able to select what delimiter
is used. "/" is not a bad choice for the default, but perhaps the user
wants "\n" instead? That way the labels are not a cluttered in some cases.
Another flag for d.vect?