Opened 11 years ago

Last modified 9 months ago

#320 new enhancement

the ``default region'' term is somewhat misleading

Reported by: 1gray Owned by: grass-dev@…
Priority: minor Milestone: 7.6.2
Component: Default Version: svn-trunk
Keywords: region Cc:
CPU: All Platform: All

Description

The region that's currently named ``default'' is, actually, never used by default -- it's the ``current'' region that is.

It seems that the ``default'' region is accessed only in the following cases:

  • it's always used when creating a mapset;
  • it's used with g.region when explicitly requested by -d.

Doesn't it therefore make sense to retitle ``default region'' to, say, ``initial region'' in GRASS 7?

Change History (11)

comment:1 Changed 10 years ago by nikos

see also (to add more confusion :-p): http://trac.osgeo.org/grass/ticket/323

Nikos

comment:2 Changed 10 years ago by hamish

CPU: UnspecifiedAll
Keywords: region added
Platform: UnspecifiedAll
Version: unspecifiedsvn-trunk

it is the default region when creating new mapsets. thus it is the fall-back region setting. (if we really want to get into it, native French speakers can expand on the root of the word; but see closing comments below...)

-> where in the code or docs do you find it to be confusing? The description for 'g.region -d' could certainly be improved to explain this better, tooltips added etc if you like.

I don't think this is important enough to change the DEFAULT_WIND file name, or to break consistency when referencing that file. The WINDow half of the filename has already been abandoned as far as the user interface is concerned.

as with #323, I think most semantic debates are best dealt with by honing the documentation and being consistent in the descriptions.

Hamish

comment:3 in reply to:  2 Changed 10 years ago by nikos

Replying to hamish:

it is the default region when creating new mapsets. thus it is the fall-back region setting. (if we really want to get into it, native French speakers can expand on the root of the word; but see closing comments below...)

-> where in the code or docs do you find it to be confusing? The description for 'g.region -d' could certainly be improved to explain this better, tooltips added etc if you like.

I don't think this is important enough to change the DEFAULT_WIND file name, or to break consistency when referencing that file. The WINDow half of the filename has already been abandoned as far as the user interface is concerned.

as with #323, I think most semantic debates are best dealt with by honing the documentation and being consistent in the descriptions.

agreed, Nikos

comment:4 Changed 4 years ago by martinl

Milestone: 7.0.07.0.5

comment:5 Changed 3 years ago by martinl

Milestone: 7.0.57.3.0

comment:6 Changed 3 years ago by martinl

Milestone: 7.3.07.4.0

Milestone renamed

comment:7 Changed 23 months ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:8 Changed 18 months ago by neteler

Milestone: 7.4.17.4.2

comment:9 Changed 15 months ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:10 Changed 11 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:11 Changed 9 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.