Hi Bob,
hi all,
thanks for your contribution: i.target with parser support.
I have fixed a few traps (checks which cmd line parameters
are allowed) and uploaded to CVS.
the original INTER version lives in i.target/inter now and
is in use for the inter mode (due to GRASS front.end).
i.target help
Description:
This program targets an imagery group to a GRASS location and mapset
Usage:
i.target [-c] group=name [location=name] [mapset=name]
Flags:
-c Set current location and mapset as target for of imagery group
Parameters:
group Name of imagery group
location Name of imagery target location
mapset Name of target mapset
The HTML page is also updated.
Next to come: i.rectify... (and i.group)
Then geo-rectification can be done scripted.
Best regards
Markus
Markus and others,
I found some inconsistencies in manual with the current code which
suggest that
some code merging might be useful (and hopefully not difficult.):
we have d.what.vect which according to the manual works only on lines,
however it also outputs this:
601442.22222222(E) 4924546.66666667(N)
soils.acidic in helena Line - Category <not tagged>
Area - Category 54 Wb
Size - Sq Meters: 689050.000 Hectares: 68.905
Acres: 170.264 Sq Miles: 0.2660
so the manual should be updated
We also have v.area which outputs everything that d.what.vect does plus
perimeter, area centroid and island info (and the "mouse clicking" is
different -
that is one standard that needs to be set for 5.1)
Point at cross hairs: 4918382.22 (N) 602540.00 (E)
Getting value 0 with opflag 0
Islands flag is 0
Area index number: 79
Perimeter: 8613.35 meters 28258.68 feet 5.352 miles
Area: 2557050.00 sq meters 255.71 hectares
631.845 acres 0.9873 sq miles
Area centroid: 4918410.00 (N) 602490.00 (E)
cat#= 9, label= <CBE>
and then we also have d.area for which the manual says:
Obtains area/perimeter information on vector polygons, which it is not
doing?
but it has the capability to display areas as filled areas that the
previous
two do not have.
So for 5.0 the manual entries for d.area and d.what.area should be
updated and
for 5.1 the best thing probably would be to merge v.area with
d.vect.area and I believe
that it should be called d.vect.area. d.area should be probably kept
separate.
If I have missed something that was already discussed here, I
appologize,
Helena
On Fri, Oct 26, 2001 at 08:58:39AM -0500, Helena wrote:
Markus and others,
I found some inconsistencies in manual with the current code which
suggest that
some code merging might be useful (and hopefully not difficult.):
we have d.what.vect which according to the manual works only on lines,
however it also outputs this:
601442.22222222(E) 4924546.66666667(N)
soils.acidic in helena Line - Category <not tagged>
Area - Category 54 Wb
Size - Sq Meters: 689050.000 Hectares: 68.905
Acres: 170.264 Sq Miles: 0.2660
so the manual should be updated
done.
We also have v.area which outputs everything that d.what.vect does plus
perimeter, area centroid and island info (and the "mouse clicking" is
different - that is one standard that needs to be set for 5.1)
Point at cross hairs: 4918382.22 (N) 602540.00 (E)
Getting value 0 with opflag 0
Islands flag is 0
Area index number: 79
Perimeter: 8613.35 meters 28258.68 feet 5.352 miles
Area: 2557050.00 sq meters 255.71 hectares
631.845 acres 0.9873 sq miles
Area centroid: 4918410.00 (N) 602490.00 (E)
cat#= 9, label= <CBE>
and then we also have d.area for which the manual says: Obtains
area/perimeter information on vector polygons, which it is not doing? but
it has the capability to display areas as filled areas that the previous
two do not have.
I agree, that's a sort of confusing.
So for 5.0 the manual entries for d.area and d.what.area should be updated
d.what.vect...
and for 5.1 the best thing probably would be to merge v.area with
d.vect.area and I believe that it should be called d.vect.area. d.area
should be probably kept separate.
Mhh, I think that the idea of [rsv].what is to provide a tool to
query maps non-interactively in contrast to d.*
This feature should be kept, but all tools synchronised.
If I have missed something that was already discussed here, I
appologize,
Helena
Markus
On Wed, 31 Oct 2001 18:50:46 +0100, Markus Neteler <neteler@itc.it> wrote:
[snip]
> We also have v.area which outputs everything that d.what.vect does plus
> perimeter, area centroid and island info (and the "mouse clicking" is
> different - that is one standard that needs to be set for 5.1)
>
> Point at cross hairs: 4918382.22 (N) 602540.00 (E)
> Getting value 0 with opflag 0
> Islands flag is 0
> Area index number: 79
> Perimeter: 8613.35 meters 28258.68 feet 5.352 miles
> Area: 2557050.00 sq meters 255.71 hectares
> 631.845 acres 0.9873 sq miles
> Area centroid: 4918410.00 (N) 602490.00 (E)
> cat#= 9, label= <CBE>
>
> and then we also have d.area for which the manual says: Obtains
> area/perimeter information on vector polygons, which it is not doing? but
> it has the capability to display areas as filled areas that the previous
> two do not have.
I agree, that's a sort of confusing.
The man page and description for d.area have been fixed. Note, v.area does
filled polygons using the '-f' flag upon selection -- but it doesn't handle
islands or clipping correctly (similar polygon clipping problem that d.area
has).
--
Eric G. Miller <egm2@jps.net>