[mapguide-users] using Feature Sources as flat file data stores.
tom.fukushima at autodesk.com
Fri Jan 19 11:29:04 EST 2007
Yes, this is the intended behavior of the API.
Since feature sources can be associated with any provider (for example,
an as yet unknown provider supplied written by xyz) we do not know
before hand what types of files a provider uses. So to support these
providers it is important to allow any file type to be added to the
feature source using SetResourceData.
Also note that we also need it to be possible to associate any data file
with the ODBC provider as the files required depends on which ODBC
driver is being used.
From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Thursday, January 18, 2007 11:11 PM
To: mapguide-users at lists.osgeo.org
Subject: [mapguide-users] using Feature Sources as flat file data
I've been testing SetResourceData in the Resource API (via mapagent) to
see what types of files I can put into the Feature source.
To my surprise (or non-knowledge) I can put just about any kind of file
in it, essentially allowing me to use a feature source as a flat-file
data store of sorts.
Was this functionality intended?
AEC Spatial Pty Ltd. / AEC Systems Pty Ltd.
SYDNEY - MELBOURNE - BRISBANE - PERTH - HOBART - AUCKLAND (NZ)
A.B.N: 32 075 809 451
Level 4, 37-41 Prospect St. Box Hill, Victoria, 3128
Phone: 1300 368 609
Fax: 1300 362 140
jackie.ng at aecsystems.com.au
<blocked::mailto:jackie.ng at aecsystems.com.au>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mapguide-users