[fdo-dev] [Proposal] FGF<->WKB converters as common utils

Gavin Cramer gavin.cramer at autodesk.com
Tue Aug 8 17:06:15 EDT 2006

Those functions are part of the FDO SDK.  Any provider can use them, as
well as any client.

Excluding the factory, FdoGeometry is a pure API too -- one can even
re-implement it to be a wrapper around any other geometry package, and
just call FdoGeometryFactoryAbstract::CreateGeometry(FdoIGeometry *
geometry) to do all conversions.  Note that FdoFgfGeometryFactory
extends the non-FGF-specific FdoGeometryFactoryAbstract, and that all
FGF-specific methods are in that one FdoFgfGeometryFactory class.


-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Tuesday, August 08, 2006 4:44 PM
To: dev at fdo.osgeo.org
Subject: Re: [fdo-dev] [Proposal] FGF<->WKB converters as common utils

Gavin Cramer wrote:
> If you follow the execution trail, you will find that
> GeometryFromWkb() and WkbFromGeometry() do indeed end up in the
> FgfGeometry code.  That's why the Geometry.c in the MySQL RDBI driver
> is so small -- it's just a wrapper around pre-existing, common code.


Yes, you're right.
Geometry.c functions are just a thin wrapper around the
FdoFgfGeometryFactory that makes it easier to operate on char-based
streams of WKB.

But why not to put those functions to a common place that all providers
will be able to use it ?
I don't see anything MySQL-specific there.

Best regards
Mateusz Loskot

To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org

More information about the Fdo-internals mailing list