Hi list,
Is there any module list that should not be ported to 5.7 from 5.3?
Currently, I can find many modules are missing in 5.7.
Thanks
Huidae Cho
On Mon, Nov 01, 2004 at 01:31:47AM -0600, Huidae Cho wrote:
Hi list,
Is there any module list that should not be ported to 5.7 from 5.3?
Yes,
http://grass.itc.it/grass57/index.html#docs
-> GRASS 5.7 vector modules upgrade status
-> http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass51/doc/vector/v.modules.html
Currently, I can find many modules are missing in 5.7.
Please post a list of module not appearing in above list.
Up to now we only transferred modules of interest to 5.7.
Your list might be helpful to identify further modules needed.
Cheers
Markus
About 8 months ago I did a list of 5.3 modules not in 5.7. At the time, it
looked long, but functionality of many of the missing modules was already
offered in alternate ways. The biggest difference was in the import modules.
5.3 has many format specific modules while 5.7 has much of its import
covered under GDAL and OGR. Because of this, 5.7 will probably import more
formats currently in use than 5.3 in spite of lacking many 5.3 import
modules.
I haven't checked the list in a while but most or all of the remaining
modules have been ported. The last batch was a set of point
analysis/manipulation routines recently ported from 5.3 sites to 5.7
vectors.
Given all the recent activity and impending release of 5.4 it is probably a
good time to review the functional differences between the two versions.
However, I think that 5.7 now all the functionality of 5.3 plus
functionality not in 5.3.
Michael
On 11/1/04 12:31 AM, "Huidae Cho" <grass4u@gmail.com> wrote:
Hi list,
Is there any module list that should not be ported to 5.7 from 5.3?
Currently, I can find many modules are missing in 5.7.Thanks
Huidae Cho
____________________
C. Michael Barton, Professor of Anthropology
School of Human, Cultural, and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA
Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>
I'm attaching a list, so could anyone update this? BTW, it would be
great if things like this can be done in GRASS Wiki. No one uses it?
Thanks,
Huidae Cho
On Mon, 1 Nov 2004 14:46:09 +0100, Markus Neteler <neteler@itc.it> wrote:
On Mon, Nov 01, 2004 at 01:31:47AM -0600, Huidae Cho wrote:
> Hi list,
>
> Is there any module list that should not be ported to 5.7 from 5.3?Yes,
http://grass.itc.it/grass57/index.html#docs
-> GRASS 5.7 vector modules upgrade status
-> http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass51/doc/vector/v.modules.html> Currently, I can find many modules are missing in 5.7.
Please post a list of module not appearing in above list.
Up to now we only transferred modules of interest to 5.7.
Your list might be helpful to identify further modules needed.Cheers
Markus
(attachments)
missing.txt (3.92 KB)
On Mon, Nov 01, 2004 at 11:58:48AM -0600, Huidae Cho wrote:
I'm attaching a list, so could anyone update this? BTW, it would be
great if things like this can be done in GRASS Wiki. No one uses it?
I'm currently migrating texts to a new WIKI. Asap available...
Generally I feel that only useful commands should enter 5.7
(and after code cleanup).
More tomorrow,
Markus
On Mon, 1 Nov 2004 19:11:52 +0100, Markus Neteler <neteler@itc.it> wrote:
On Mon, Nov 01, 2004 at 11:58:48AM -0600, Huidae Cho wrote:
> I'm attaching a list, so could anyone update this? BTW, it would be
> great if things like this can be done in GRASS Wiki. No one uses it?I'm currently migrating texts to a new WIKI. Asap available...
Generally I feel that only useful commands should enter 5.7
(and after code cleanup).
Sure! But sometimes I cannot find equivalent commands even though
it's useful: e.g., d.extend. So i'm asking now because I have no right
to determine which modules should go to 5.7 ;-).
Huidae Cho
More tomorrow,
Markus
Thanks much Huidae. I went through your list adde, organized it into the
type of module and made comments about what has been ported or not, what is
obsolete, and what is covered functionally by another command. I'd be happy
for anyone to make corrections on it. This should make it a bit easier to
see what remains to be ported and decided if it is worth the effort to do
so.
Michael
On 11/1/04 10:58 AM, "Huidae Cho" <grass4u@gmail.com> wrote:
I'm attaching a list, so could anyone update this? BTW, it would be
great if things like this can be done in GRASS Wiki. No one uses it?Thanks,
Huidae ChoOn Mon, 1 Nov 2004 14:46:09 +0100, Markus Neteler <neteler@itc.it> wrote:
On Mon, Nov 01, 2004 at 01:31:47AM -0600, Huidae Cho wrote:
Hi list,
Is there any module list that should not be ported to 5.7 from 5.3?
Yes,
http://grass.itc.it/grass57/index.html#docs
-> GRASS 5.7 vector modules upgrade status
->
FreeGIS.org
s.htmlCurrently, I can find many modules are missing in 5.7.
Please post a list of module not appearing in above list.
Up to now we only transferred modules of interest to 5.7.
Your list might be helpful to identify further modules needed.Cheers
Markus
______________________________
Michael Barton, Professor of Anthropology
School of Human, Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
(attachments)
missing_response.txt (8.29 KB)
Michael Barton wrote:
Thanks much Huidae. I went through your list adde, organized it into the
type of module and made comments about what has been ported or not, what is
obsolete, and what is covered functionally by another command. I'd be happy
for anyone to make corrections on it. This should make it a bit easier to
see what remains to be ported and decided if it is worth the effort to do
so.
Some of the r.in.* modules provide functionality not available through
r.in.gdal (e.g. r.in.png can preserve the original intensity
resolution and gamma).
r.grow2 - this IS ported. But until someone can tell me what it does
or how, I can't make a tcltk menu option
r.grow2 essentially combines functionality from r.grow and r.buffer,
plus some additional functionality. You can use it like r.grow, but
with the ability to grow by more than one cell, or like r.buffer, but
with the option of preserving the original cells (similar to combining
r.buffer and r.patch).
If you know what r.grow and r.buffer do, the options should be mostly
self-explanatory.
--
Glynn Clements <glynn@gclements.plus.com>
Glynn,
Thanks very much for an explanation of this. This sounds like a very nice
enhancement to r.grow. Given this, is there any reason to keep the original
r.grow?
Michael
On 11/1/04 9:37 PM, "Glynn Clements" <glynn@gclements.plus.com> wrote:
r.grow2 essentially combines functionality from r.grow and r.buffer,
plus some additional functionality. You can use it like r.grow, but
with the ability to grow by more than one cell, or like r.buffer, but
with the option of preserving the original cells (similar to combining
r.buffer and r.patch).If you know what r.grow and r.buffer do, the options should be mostly
self-explanatory.
____________________
C. Michael Barton, Professor of Anthropology
School of Human, Cultural, and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA
Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>
On Tuesday 02 November 2004 00:06, Michael Barton wrote:
Thanks much Huidae. I went through your list adde, organized it into the
type of module and made comments about what has been ported or not, what is
obsolete, and what is covered functionally by another command. I'd be happy
for anyone to make corrections on it. This should make it a bit easier to
see what remains to be ported and decided if it is worth the effort to do
so.
Michael, thanks for cleaning up the list. It could be useful to have
a HTML table like we have for vectors/sites.
------ some comments: ---------------
Vector modules
v.mkquads - Not ported
This module is not general enough for standard GRASS distribution, it is specific
for one state only, I think. It should be distributed as additional package.
v.split - what is this?
v.split breaks lines and boundaries to segments. I'll add this functionality
as tool to v.clean.
v.support - not ported
Ported as v.build, but rarely needed .
v.alabel - will be merged by v.category
It is in v.category.
v.prune - this functionality should go to v.clean
It is in v.clean as tool 'prune'
v.reclass.pg - moved to v.reclass?
Yes, *.pg is not used in 5.7 and no *.pg modules will be ported.
v.rmedge - merged to v.clean?
Not directly, I believe that it is not necessary because other cleaning tools
can be used. In any case, the functionality can be reached by v.to.db option=sides
+ v.extract.
v.timestamp- move to v.info?
Missing.
v.to.sites - obsolete (sites replaced by vector points)
There is also v.to.points available.
------------------------------------
'Missing' and missing modules cannot stop 5.8/6.0 release.
For me, it is important to get a short list of modules (functions)
realy missing in 5.7, with an explanation why it should be ported,
rather than a long comparison of bin directories.
Radim
r.grow2 - this IS ported. But until someone can tell me what it does
or how, I can't make a tcltk menu optionr.grow2 essentially combines functionality from r.grow and r.buffer,
plus some additional functionality. You can use it like r.grow, but
with the ability to grow by more than one cell, or like r.buffer, but
with the option of preserving the original cells (similar to combining
r.buffer and r.patch).If you know what r.grow and r.buffer do, the options should be mostly
self-explanatory.
/grass51/raster/r.grow2 is now compiled to r.grow
and /grass51/raster/r.grow was removed.
Radim