[fdo-internals] Request review of RFC 28-AddStart/EndExpressionFunctions

[Dan Stoica]

Then you cannot have only X(geometry). In addition a PointN() function is needed as well.

Dan.

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Robert Fortin
Sent: Wednesday, November 05, 2008 11:48 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request review of RFC 28-AddStart/EndExpressionFunctions

Following other functions declaration (RFC-8, RFC-11 and that's what the RFC-28 indicated), it's a property name which in this case has to be a geometry property.

RF

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Dan Stoica
Sent: Wednesday, November 05, 2008 11:14 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request review of RFC 28-AddStart/EndExpressionFunctions

By geometry you mean the geometry column or a geometry value which definitely has to be a point?

Dan.
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Robert Fortin
Sent: Wednesday, November 05, 2008 11:03 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request review of RFC 28-AddStart/EndExpressionFunctions

I'm all for trying to use existing standard and applying to our case.

In order to address my use case which is only concerned with point geometry,  I would have to do and implement the following:

X(geometry)
Y(geometry)
Z(geometry)
(and M(geometry) by extension)

Everything else is additional to the use case.

So the RFC should only be about these 3 functions and mention the additional ones and trying to match the OGC standard.

RF

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20081105/d170d6f2/attachment-0001.html