[GRASS-dev] [GRASS GIS] #2382: d.legend: integer map legends should not be flipped upside-down
GRASS GIS
trac at osgeo.org
Wed Jul 30 09:57:42 PDT 2014
#2382: d.legend: integer map legends should not be flipped upside-down
-------------------------+--------------------------------------------------
Reporter: neteler | Owner: hamish
Type: defect | Status: assigned
Priority: normal | Milestone: 7.0.0
Component: Display | Version: svn-releasebranch70
Keywords: d.legend | Platform: All
Cpu: Unspecified |
-------------------------+--------------------------------------------------
Comment(by wenzeslaus):
Replying to [comment:1 hamish]:
>
> In the NC08 dataset consider: `d.legend towns`
> (see attached screenshot)
>
> I think we can all agree that counting from category 1 (smallest value)
at the top is how we would like that to be.
>
Sorry, I cannot agree entirely. I don't see the reason to have numbers
there when labels are the only important thing in case of of towns. Then
of course the order (order according category) is not important. Although
I agree that we might suppose some ordering imprinted in categories, e.g.
in case of labels for slope.
> note I built in two handy tricks to get the flip to happen without the
-f flag: in GRASS 6 (and with at= in G7) when drawing the box with the
mouse draw from bottom up instead of top down, and another way is to
reverse the order of values in the range= option.
>
I generally agree with introducing these tricks (clever decision making,
heuristics). However, in this case it is questionable if it creates more
confusion then convenient/handy behavior. Perhaps option
`order=ascending`, `order=descending` and `order=auto` would improve the
situation by making things explicit. `order=auto` can be the default.
`order=ascending` and `order=descending` would disable any handy tricks.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2382#comment:5>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list