Your assumption of:
FeatureClass
Table
FeatureDataset\FeatureClass
RelationshipClass
FeatureDataset\RelationshipClass
is correct.
As far as metadata goes, you can add Domains ("Coded Value Domains" and
"Range Domains") as well as Subtypes.
Here is an explanations of what they are
http://webhelp.esri.com/arcgisdesktop/9.3/datainterop/mergedProjects/FME_Workbench/editing_geodatabase_domains_and_subtypes.htm
The way that LoadLayers is setup, it is currently asking the GDB for every
single type supported. If you only want to open certain things, you can just
hardcode the strings that you want to support instead of calling
GetDatasetTypes().
Also, I coded LoadLayers it was right after their beta 1 launch... they have
since added more schema reading functions that would allow the loading of
schema to be more selective and efficient.
Hope that helps,
- Ragi
On Fri, May 6, 2011 at 9:09 PM, <[email protected]> wrote:
> Date: Fri, 6 May 2011 16:46:47 -0700
> From: Paul Ramsey <[email protected]>
> Subject: [gdal-dev] Metadata (FGDB)
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> So, the end goal of my wanking around with OGR and FGDB is to write a
> utility that will convert FGDB into PostGIS and then back again with
> as much fidelity as possible. So ideally the output would look much
> like the input. FGDB has some fun stuff that doesn't fit into the OGR
> model very well.
>
> FGDB Fields can have an Alias. Presumably to provide a more human
> readable form. I could map these to PostgreSQL comments on the
> columns, but there is no slot for them in OGR to pass them through.
> FGDB Tables can have Metadata. There seems to be an OGR slot for this
> (GetInfo) but it's deprecated and highly freeform.
> FGDB Tables can have Indexes. I see in trunk there's some index stuff
> (GetIndex, InitializeIndexSupport) but not sure how far along it is.
> It would be nice to be able to tell OGR to create an index and have it
> magically happen.
>
> Actually, going over this, it's not bad, better than I thought when I
> started looking. I am assuming that, if/when I get past the basics
> I'll have to push my utility forward by adding some special methods on
> the Pg and FileGDB drivers to do things like set relationships and so
> on.
>
> P.
>
>
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
