we had an initial discussion about the opportunity
to have all GRASS commands know a description of their
own.
The aspired benefit is to
- have the short description when issuing <command> -help
- ultimately get rid of tcl-list based command definitions
in src/tcltkgrass/module
- provide valuable information to other programs such
as OSSIM through the xml-based interface description
I have extended the GRASS parser to allow to
G_define_module() and also checked in a example:
GRASS:~ > r.basins.fill -help
Description:
Generates a raster map layer showing watershed subbasins.
Parameters:
number Number of passes through the dataset
c_map Coded stream network file name
t_map Thinned ridge network file name
result Name for the resultant watershed partition file
Now it's time to add the short description to all commands.
As a selection for the commands it seems to be a good idea
to take all that is installed to the GRASS bin directory.
Later on any module that is added to the install routine
must be provided with the internal short description first.
As the source for short description, the html documents seems
to be the best choice.
I will start with this (somewhat unamusing) job for the raster commands
right now ...
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
today I got an announcement of TERRA/NASA data distribution.
Most of these data are distributed in HDF format (some of
them for free like the hyperspectral MODIS).
The letter stated that ENVI would be one of the few
packages to support HDF format.
Of course I remembered GRASS 4.2.1 and the src.garden/grass.hdf/
tree in GRASS 5. I feel we should get HDF active. This would
mean that the r.[in|out].hdf needs an upgrade to HDF 5:
We are all overwhelmed with other stuff, but is anyone willing
to do the job ?
Unfortunately the HDF5 lib would be another 8MB of source code.
But the current src.garden/grass.hdf consumes 27MB.
So a general upgrade would save space. Using my scripts I could
easily remove the old hdf stuff from CVS and check in the new HDF5
libraries. Just let me know. A license file I could find there,
seems to be public domain.
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Tue, Nov 21, 2000 at 05:36:09PM -0500, Frank Warmerdam wrote:
Markus Neteler wrote:
>
> Hi all,
>
> today I got an announcement of TERRA/NASA data distribution.
> Most of these data are distributed in HDF format (some of
> them for free like the hyperspectral MODIS).
> The letter stated that ENVI would be one of the few
> packages to support HDF format.
>
> Of course I remembered GRASS 4.2.1 and the src.garden/grass.hdf/
> tree in GRASS 5. I feel we should get HDF active. This would
> mean that the r.[in|out].hdf needs an upgrade to HDF 5:
>
> http://hdf.ncsa.uiuc.edu/HDF5/
> ftp://ftp.ncsa.uiuc.edu/HDF/HDF5/hdf5-1.2.2/src/
>
> We are all overwhelmed with other stuff, but is anyone willing
> to do the job ?
>
> Unfortunately the HDF5 lib would be another 8MB of source code.
> But the current src.garden/grass.hdf consumes 27MB.
>
> So a general upgrade would save space. Using my scripts I could
> easily remove the old hdf stuff from CVS and check in the new HDF5
> libraries. Just let me know. A license file I could find there,
> seems to be public domain.
Markus,
I have been kicking around the idea of adding HDF support to GDAL. Would
you be satisified if r.in.gdal could support HDF? HDF is very complicated,
and therefore I think it might be desirable to avoid re-implementing it in too
many places. I would like to see libgdal.1.1.so included with some of the
binary builds of GRASS.
Hi Frank,
this would be the best! Generally a powerful *single* module to
import various formats is most convenient.
BTW: What is the reason that some (interesting) formats are restricted
in GDAL?
Thanks for your reply,
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
this would be the best! Generally a powerful *single* module to
import various formats is most convenient.
BTW: What is the reason that some (interesting) formats are restricted
in GDAL?
Markus,
How do you mean restricted?
Best regards,
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerda
and watch the world go round - Rush | Geospatial Programmer for Rent
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Wed, Nov 22, 2000 at 08:46:18AM -0500, Frank Warmerdam wrote:
Markus Neteler wrote:
> Hi Frank,
>
> this would be the best! Generally a powerful *single* module to
> import various formats is most convenient.
>
> BTW: What is the reason that some (interesting) formats are restricted
> in GDAL?
Markus,
How do you mean restricted?
Mhhh, I am sure there have been restrictions for SPOT at least
on this page:
So it's not an issue any more!
Sorry for this confusion.
Just curious: Will you add LANDSAT 7 as well in future?
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
?