Re: [Geotools-gt2-users] Should I use a Polygon or a Mark?

[jv <cib...@gm...>]

That's exactly what I'm looking for :-) And it's nice to know you're also in
the same field... my boss has some millions of citations in a database and
we're trying to publish that information in several ways. The first (in
theory) little project we want to write with gt is to migrate our tiny wms
server to this platform.
The second  (and by far more interesting) project will be to create a
multimedia-gps-based guide. That's why we need the power of gt: we don't
know how to correctly work with several projections on our own.
Now I realise that polygons are more convenient in order to surround an area
of the map, not to place marks on a determined spot. But I still don't know
how to do it. If I understand you correctly the steps are something like
this:
- create a single featuretype with the "schema" of the information of a bio
citation (at least name, x,y, status)
- instantiate several features of that featureType, one for each citation.
- create as many styles as status values.
- link every kind of style with the set of features that share the matching
status.
- create a layer from all those features.
The main problem is still I don't know how to express the coordinates as
 attributes of a featuretype... perhaps is enough to add them with a
particular name? And I'm also not  sure how to link the styles with the
features.
You're being really patient. I promise I'll try to write a short tutorial
about all of this once I feel more comfortable with the library. And of
course both Jody and you have as many beers paid as you want if you come to
Barcelona ;-)
jv

On Wed, Sep 9, 2009 at 12:27 PM, Michael Bedward
<mic...@gm...>wrote:

> Hi jv,
>
> I just had a look at your code - only very quickly so correct me if I
> things wrong below...
>
> Firstly, always pleased to see someone using GeoTools for species
> conservation apps :-)  That's my area as well.
>
> Rather than creating a feature type for each of your status categories
> (Fiability enum ?) it would be more convenient for you to have a
> single feature type, with attributes for species, position, status...
> Then, when rendering the features, have a Style that links the symbol
> / color / fill to the status value.
>
> Is that the sort of thing you're after ?
>
> Michael
>



-- 
=======================================================
Javier Moreno
www.imaginafoto.com
=======================================================