Hi Andrea; I am afraid you missed the part we needed your help on - 
choose between these code examples.

- 
http://docs.codehaus.org/display/GEOTDOC/02+Measurement+Example+with+getGeometry
Here is an example of what we are having trouble with:
> String sitename = (String) feature.getAttribute( "sitename" );
> Point location = (Point) feature.getGeometry();
> Propety sitenameProperty = feature.getProperty( "sitename" );
> String sitename = (String) sitenameProperty.getValue();
>
> GeometryAttribute geometry  = feature.getGeoemtryProperty();
> CoordianteReferenceSystem crs = geometry.getCRS();
> Point location = (Point) geometry.getValue();
>   

- 
http://docs.codehaus.org/display/GEOTDOC/03+Measurement+Example+with+getDefaultGeometry
And the other way:
> String sitename = (String) feature.getAttribute( "sitename" );
> Point location = (Point) feature.getDefaultGeometry();
> Propety sitenameProperty = feature.getProperty( "sitename" );
> String sitename = (String) sitenameProperty.getValue();
>
> GeometryAttribute defaultGeometry  = feature.getDefaultGeoemtryProperty();
> CoordianteReferenceSystem crs = defaultGeometry.getCRS();
> Point location = (Point) defaultGeometry.getValue();
>
>   
Please see the page for the complete context; do just look at this email.
Jody
> About Jody featureland and wiki code examples
> --------------------------------------------------------------
>
> * Success table:
>   provide operations so we can smoothly integrate with Coverage? Hmm...
>   you mean, thinking about coverage as an n-dimensional function?
Basically the "Operations" we have in the feature model should match up 
what they have in the Coverge. I think the use of an opeation to sample 
the coverage is the motivation  - but I have been ignoring the details.

Um so for someone who knows the details now is a good time ;-)
> * builder examples in the wiki.
>   FeatureType does not have a CRS
>   (it's a derived attribute, as stated by the javadoc), but the
>   geometry attribute should instead.
Right; it is a builder so it is stateful - the setting of a CRS is used 
by the geometry( "location", Point.class ) line.
>   I fail to see the need to explicitly cast in 2.6. Can't we just
>   deprecate geotools features and eventually remove them from the
>   API instead?
It is not needed, is it however a good idea?
- http://docs.codehaus.org/display/GEOTDOC/10+Migration+Guide

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to