<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6618.4">
<TITLE>RE: [fdo-internals] Feature with multiple geometries</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">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.</FONT></SPAN></P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">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</FONT><FONT SIZE=2 FACE="Arial">::GetGeometryProperty(). Your provider should make a best effort to identify this when reverse-engineering a schema.</FONT></SPAN></P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">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.</FONT></SPAN></P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Gavin</FONT></SPAN>
</P>
<BR>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">-----Original Message-----</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">From: fdo-internals-bounces@lists.osgeo.org [</FONT></SPAN><A HREF="mailto:fdo-internals-bounces@lists.osgeo.org"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">mailto:fdo-internals-bounces@lists.osgeo.org</FONT></U></SPAN></A><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">] On Behalf Of Mateusz Loskot</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Sent: Wednesday, March 07, 2007 3:04 PM</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">To: fdo-internals</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Subject: [fdo-internals] Feature with multiple geometries</FONT></SPAN>
</P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Hi,</FONT></SPAN>
</P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">In PostGIS, it is possible that a table has more than one geometry</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">columns, so it defines a feature (row) with more than one geometry.</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Is it possible to model this case in FDO?</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">If it is possible, could anyone point classes/interfaces that can be</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">used to to define such feature in FDO ?</FONT></SPAN>
</P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Cheers</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">-- </FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Mateusz Loskot</FONT></SPAN>
<BR><SPAN LANG="en-us"></SPAN><A HREF="http://mateusz.loskot.net"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://mateusz.loskot.net</FONT></U></SPAN></A><SPAN LANG="en-us"></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">_______________________________________________</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">fdo-internals mailing list</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">fdo-internals@lists.osgeo.org</FONT></SPAN>
<BR><SPAN LANG="en-us"></SPAN><A HREF="http://lists.osgeo.org/mailman/listinfo/fdo-internals"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://lists.osgeo.org/mailman/listinfo/fdo-internals</FONT></U></SPAN></A><SPAN LANG="en-us"></SPAN>
</P>
</BODY>
</HTML>