[OSGeo-Discuss] Re: idea for an OSGeo project -- a new, open data format
traian.stanev at autodesk.com
Thu Nov 22 19:23:00 PST 2007
I think many people have it backwards. SDF is basically a reference implementation of the FDO API (or a significant subset thereof). It's not an independent file format that happens to have an FDO driver. Any C++ API for SDF would likely have to use FDO data structures and types underneath to get SDF data out of the file. This is because FDO data structures are directly serialized into SDF binary tables.
From: discuss-bounces at lists.osgeo.org [discuss-bounces at lists.osgeo.org] On Behalf Of Christopher Schmidt [crschmidt at crschmidt.net]
Sent: Thursday, November 22, 2007 9:23 PM
To: OSGeo Discussions
Subject: Re: [OSGeo-Discuss] Re: idea for an OSGeo project -- a new, open data format
On Thu, Nov 22, 2007 at 05:17:46PM -0800, Traian Stanev wrote:
> How about an OGR driver for SDF? No need to invent a new API when one already exists.
I think that was exactly Bob's point: There is already an FDO driver for
SDF. If OGR is sufficient, I'm not entirely sure why FDO wouldn't be by
the same argument.
I'm with Mat, in feeling that it's not the path to the widest usage in
only FDO *or* OGR, and that a reference implementation outside of either
of those would result in possibly higher OEM-style integration into non
OGR/FDO products, and that a single shared implementation is the best
way for all developers to share a single effort when moving forward.
Discuss mailing list
Discuss at lists.osgeo.org
More information about the Discuss