[fdo-internals] Feature with multiple geometries

[Gavin Cramer]

Hi,  Mateusz.  Fdo classes can have whatever number of geometric
properties you like.  In writing a provider, presumeably you have a way
of satisfying a caller's invocation of
FdoClassDefinition::GetProperties().  While this would typically contain
zero or one properties of type FdoGeometricPropertyDefinition, it can
actually contain any number of them.

If the class has multiple geometric properties, but has one "default"
one that a caller would typically use for drawing or filtering, it can
be identifed (for features, not non-feature objects) via
FdoFeatureClass::GetGeometryProperty().  Your provider should make a
best effort to identify this when reverse-engineering a schema.

Geometric properties, even within a class, do not all have to correspond
to the same spatial context.  They can be explicitly related, with the
relationship accessible via
FdoGeometricPropertyDefinition::GetSpatialContextAssociation.

Gavin


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Mateusz
Loskot
Sent: Wednesday, March 07, 2007 3:04 PM
To: fdo-internals
Subject: [fdo-internals] Feature with multiple geometries

Hi,

In PostGIS, it is possible that a table has more than one geometry
columns, so it defines a feature (row) with more than one geometry.
Is it possible to model this case in FDO?
If it is possible, could anyone point classes/interfaces that can be
used to to define such feature in FDO ?

Cheers
-- 
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20070307/bbce05b3/attachment.html