Jody,

Sorry about the confusion my post caused.

Jody wrote: "A feature collection is literally defined
by the association it is representing ....

You may find it easier to think of the Layer owning the Features."

I don't think that this is how JUMP works, at least if I understand it
correctly. In OpenJUMP a FeatureCollection is definitely the primary
container for Features and a Layer just wraps this container with
styling information.

Jody wrote: "You may find it easier to think of the Layer owning the
Features, and
using FeatureCollection as a way of answering questions like "what
features are on the screen", and "what features are new" (ie use feature
collections to express association not ownership)."

It sounds like our implementation of FeatureCollection is much more
concrete and perhaps inflexible than the one in GeoTools.

Jody wrote: "If you look at the ISO FeatureModel the FeatureType of a
FeatureCollection is used to document why the members are gathered
together. We went into the requirements gather exercise with the
restriction of being able to expression spatial, temporal and
containment associations."

Perhaps JUMP deviated from the ISO FeatureModel in this regard? I
don't know for sure. I think we may be getting over my head. :]

The Sunburned Surveyor


On 6/21/07, Jody Garnett <[EMAIL PROTECTED]> wrote:
> Fair enough - we have also had this request (and it would result in a
> nice setup).
>
> However GeoTools developers are getting paid work to chase after GML3
> and the ISO Feature model. As an architect guy I am doing my best to let
> everyone get along; we will see how it goes.
>
> The *biggest* strength of a the JUMP (lets call it *plain*) feature
> model is that it can be quickly implemented by domain objects. At the
> end of the day you are getting very close to a Map with known keys.
>
> Aside: I think we have a bit of confusion in your posting about the
> difference tradeoffs between feature collection and allowing
> associations between features. A feature collection is literally defined
> by the association it is representing ....
>
> You may find it easier to think of the Layer owning the Features, and
> using FeatureCollection as a way of answering questions like "what
> features are on the screen", and "what features are new" (ie use feature
> collections to express association not ownership).
>
> If you look at the ISO FeatureModel the FeatureType of a
> FeatureCollection is used to document why the members are gathered
> together. We went into the requirements gather exercise with the
> restriction of being able to expression spatial, temporal and
> containment associations.
>
> Cheers,
> Jody
>
> Sunburned Surveyor wrote:
> > I put up a recent blog post about what form OpenJUMP's Feature Model
> > will look like in the future. This might be of interest to the
> > GeoTools developers because I am advocating a course that I think
> > differs from the one that GeoTools took. This is basicly enforcement
> > of simplicity at the cost of some functionality.
> >
> > At any rate, some of you might be interested in reading it.
> >
> > http://openjump.blogspot.com/
> >
> > The Sunburned Surveyor
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Geotools-devel mailing list
> > Geotools-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geotools-devel
> >
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to