Opened 8 years ago

Last modified 5 years ago

#3050 new enhancement

Set size in d.northarrow

Reported by: wenzeslaus Owned by: grass-dev@…
Priority: minor Milestone: 7.6.2
Component: Display Version: svn-trunk
Keywords: d.northarrow, cartography, gsoc2016 Cc:
CPU: Unspecified Platform: Unspecified

Description

Size of the north arrow cannot be changed. All symbols are scaled to one common size, that's good, but this size should be further rescaled by a value of a size option.

Change History (10)

in reply to:  description ; comment:1 by lazaa, 8 years ago

Replying to wenzeslaus:

Size of the north arrow cannot be changed. All symbols are scaled to one common size, that's good, but this size should be further rescaled by a value of a size option.

The size of symbol is manually tuned and for each symbol is quite different. I would add size option. If user doesn't use size manually tuned size will be used. But if user writes size=25 for some symbols it will have increasing size effect and for others decreasing size effect. Is it OK? User would have to find right size for a symbol and after that if he changed mind and wanted use another symbol he would have to find the right size one more time.

    /* sizes manually tuned */
    switch (n_arrow_num[0]) {
    case '7':
        symbol_size = 23.;
        break;
    case '8':
    case '9':
        symbol_size = 17.;
        break;
    case 'b':
        symbol_size = 80.;
        break;
    case 'f':
        symbol_size = 100.;
        break;

in reply to:  1 comment:2 by wenzeslaus, 8 years ago

Replying to lazaa:

Replying to wenzeslaus:

All symbols are scaled to one common size, that's good, but this size should be further rescaled by a value of a size option.

If user doesn't use size manually tuned size will be used. But if user writes size=25 for some symbols it will have increasing size effect and for others decreasing size effect.

I don't know what is better if to scale, as I suggested, which is different behavior from all the other modules (so it might be better to call it scale), or if it is better to overwrite the size, as you suggest and consequently make it potentially harder for the user (symbols in d.vect behave the same but they have more similar sizes).

For now, I suggest to skip this issue.

comment:3 by martinl, 8 years ago

Milestone: 7.3.07.4.0

Milestone renamed

comment:4 by neteler, 6 years ago

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:5 by martinl, 6 years ago

Can we close the issue?

comment:6 by annakrat, 6 years ago

No, it's still valid problem. But I am not sure which is the right solution at this point.

comment:7 by neteler, 6 years ago

Milestone: 7.4.17.4.2

comment:8 by martinl, 6 years ago

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:9 by martinl, 5 years ago

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:10 by martinl, 5 years ago

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.