[fdo-internals] Motion: vote RFC 39 - Spatial operator combinations support

[Greg Boone]

What about applications other than MapGuide?

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Dan Stoica
Sent: Tuesday, July 28, 2009 5:24 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Motion: vote RFC 39 - Spatial operator combinations support

Thanks, Traian, you saved me an email :)

Dan.

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian Stanev
Sent: Tuesday, July 28, 2009 5:20 PM
To: 'FDO Internals Mail List'
Subject: RE: [fdo-internals] Motion: vote RFC 39 - Spatial operator combinations support


Well, I checked the MG codebase, and there is already such conversion function between the Mapguide and the FDO enumeration (see s_FdoSpatialOperation map), so it should not be a problem for MapGuide either.

Traian


From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian Stanev
Sent: Tuesday, July 28, 2009 5:04 PM
To: 'FDO Internals Mail List'
Subject: RE: [fdo-internals] Motion: vote RFC 39 - Spatial operator combinations support


I guess since FDO API compatibility is already broken for 3.5 versus 3.4, it's ok to make the change, with the knowledge that people will have to recompile their programs anyway.

However, I remember that MapGuide has a mirror of this enumeration that it uses in its API and then casts to FDO enumerated values directly. So I assume that there will need to be at least a change in MapGuide to add a function that does the conversion now, since the values no longer match. Might be worth searching the MapGuide API code for MgFeatureSpatialOperations.

Traian


From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Tuesday, July 28, 2009 4:45 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Motion: vote RFC 39 - Spatial operator combinations support

What about API functional compatibility?

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Dan Stoica
Sent: Tuesday, July 28, 2009 4:35 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Motion: vote RFC 39 - Spatial operator combinations support

The backward compatibility is already broken...

Thanks,
Dan.

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian Stanev
Sent: Tuesday, July 28, 2009 4:15 PM
To: 'FDO Internals Mail List'
Subject: RE: [fdo-internals] Motion: vote RFC 39 - Spatial operator combinations support

+1 Traian

I assume that renumbering the existing FdoSpatialOperations enumeration was considered OK in terms of backward compatibility?


From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Orest Halustchak
Sent: Tuesday, July 28, 2009 4:03 PM
To: FDO Internals Mail List
Subject: [fdo-internals] Motion: vote RFC 39 - Spatial operator combinations support

Hi,

There haven't been any more comments on FDO RFC 39 - Spatial operator combinations support.

http://trac.osgeo.org/fdo/wiki/FDORfc39

I would like to motion for a vote on this RFC.

+1 from me.

Thanks,
Orest.

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