[GRASS5] small bug in d.site.labels

GRASS GRASS developer
1

Hi,

i found a small bug in d.site.labels. The font in the monitor is not
reset to default after running d.site.labels, e. g. if running d.zoom.sh
the yes/no is displayed in the same font than selected for output with
d.site.labels.

Apart from that it works, many thanks.

Could we standardize on the user interface for this?
(attr=string, cat, double, coords, dim; index=number, ignored if
attr=cat or attr=coords). This should be the same for all modules that
convert sites data to raster/vector, if applicable.

I think that for the user interface of the modules some more
standardization is needed, e. g. the modules use file= map= sites= vect=
raster= and so on, but there was IMHO the standard to use map= if only
one type of data is to be displayed, input=/output= if data is imported
or exported or shuffeled around in grass mapsets/locations.

Where is this standard/convention explained? Can't remember.

cu,

Andreas

--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange@Rhein-Main.de - A.C.Lange@GMX.net

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

2

On Sun, Oct 15, 2000 at 06:09:06PM +0200, Andreas Lange wrote:
[...]

Could we standardize on the user interface for this?
(attr=string, cat, double, coords, dim; index=number, ignored if
attr=cat or attr=coords). This should be the same for all modules that
convert sites data to raster/vector, if applicable.

I think that for the user interface of the modules some more
standardization is needed, e. g. the modules use file= map= sites= vect=
raster= and so on, but there was IMHO the standard to use map= if only
one type of data is to be displayed, input=/output= if data is imported
or exported or shuffeled around in grass mapsets/locations.

Where is this standard/convention explained? Can't remember.

Thanks Andreas for this point. Actually I can't remember, too.
But we need some standard:

Import/Export modules:
  s.in.ascii sites=name [input=name]
    * reads from stdin

  r.in.ascii input=name output=name
  i.in.erdas input=name output=name

-> the raster/imagery modules have input=,
    but the s.in.ascii sites=
=> not consistent (I propose a change in s.in.ascii)

  v.in.shape in=name
-> v.in.shape should use "input" as well

  v.in.arc vector_out=name lines_in=name [points_in=name] [text_in=name]
-> again another name (vector_out): should be "output"

  v.out.arc vect=name arc_prefix=name
-> again another name (vect): should be "input="

etc. It should be less complex than now.

We should remove this confusion, I am willing to help (the related HTML
pages needs to me updated, too).

But we need to agree first. Do we need a full list of options?

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

3

Hello all

Markus Neteler wrote:

<option examples snipped>

But we need to agree first. Do we need a full list of options?

I would say yes and for all commands to ensure that they are all
consistant. I also think this should wait for 5.1.

--
Sincerely,

Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand

People who think they know everything are very irritating to those
of us who do. ---Anonymous

Jazz and Trek Rule!!!

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

4

Hi Markus,

i would propose not to change any module that was introduced before
GRASS5.0, because older scripts might no longer run in that case. We
could discuss those changes for 5.1 again.

All new modules should use a standardized scheme.
e. g. Import/Export: input=name output=name for all raster, sites and
vector modules.
e. g. display modules: map= for all raster and vector modules, file=name
for modules that can read from stdin in the "easting northing label"
format.

For the shape/arc converters i personally think that it would be better
to explicitly give a name for the resulting vector file and to default
to the shapefile name if it is not used.

I'll prepare a summary/proposal and check this in under the documents
section in CVS.

cu,

Andreas

Markus Neteler wrote:

Thanks Andreas for this point. Actually I can't remember, too.
But we need some standard:

Import/Export modules:
  s.in.ascii sites=name [input=name]
    * reads from stdin

  r.in.ascii input=name output=name
  i.in.erdas input=name output=name

-> the raster/imagery modules have input=,
    but the s.in.ascii sites=
=> not consistent (I propose a change in s.in.ascii)

  v.in.shape in=name
-> v.in.shape should use "input" as well

  v.in.arc vector_out=name lines_in=name [points_in=name] [text_in=name]
-> again another name (vector_out): should be "output"

  v.out.arc vect=name arc_prefix=name
-> again another name (vect): should be "input="

etc. It should be less complex than now.

We should remove this confusion, I am willing to help (the related HTML
pages needs to me updated, too).

But we need to agree first. Do we need a full list of options?

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange@Rhein-Main.de - A.C.Lange@GMX.net

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

5

On Tue, Oct 17, 2000 at 07:37:03PM +0200, Andreas Lange wrote:

Hi Markus,

i would propose not to change any module that was introduced before
GRASS5.0, because older scripts might no longer run in that case. We
could discuss those changes for 5.1 again.

Hi Andreas,

yes, we should keep it until 5.1 (even inconsistencies) except modules
recently introduced. I have added a small proposal

documents/parameter_proposal.txt:

Please modify/update etc. this file.

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'