[fdo-users] Writing managed provider - HowTo

Maksim Sestic max at geoinova.com
Thu Oct 18 11:16:08 EDT 2007


Hi Orest,

That's true, Geospatial API is a tricky thing. I'm also aware of Autodesk's
policy on implementing something geospatial on something not ment to be
geospatial (e.g. deploying FDO provider for vanilla AutoCAD) :-) Besides
that, I was planning to run my custom implementation on Map OEM since I'm on
Autodesk's Build! programme.

On the other hand, Map treats imported FDO feature classes as some kind of
"proxies". It bothers me. I was thinking of full meta-data persistance
within generic DBObjects. This is certainly doable. It would allow full set
of off-line operations over ACAD geometries and data, without any need for
them to ever go "on-line". Present solution treats DWG as a simple
passthrough to, say, RDBMS.

Regards,
Maksim Sestic



Orest Halustchak wrote:
> 
> Hi Maksim,
> 
> In this case, you'll also run into problems from Map and MapGuide access
> because they both include unmanaged references to the FDO api.
> 
> Yes, Map currently does not support all capabilities from FDO - these
> are works in progress.
> 
> Thanks,
> Orest.
> 
> -----Original Message-----
> From: fdo-users-bounces at lists.osgeo.org
> [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Maksim Sestic
> Sent: Wednesday, October 17, 2007 10:29 AM
> To: fdo-users at lists.osgeo.org
> Subject: RE: [fdo-users] Writing managed provider - HowTo
> 
> 
> Hi Orest,
> 
> I was thinking of using .NET. I'll explain my intentions a bit more in
> detail... it's actually about writing FDO provider for Autodesk DWG. I
> already did something similar using my own meta-model, but "porting" it
> to
> FDO would be, I guess, interesting thing to see. Autodesk Map 3D
> currently
> lacks support for certain FDO types (e.g. associations, object data
> properties) which is truly pitty since DWG, as it is, makes the whole
> thing
> doable.
> 
> It's also very challenging at the same time, since I cannot rely on DWG
> only
> as a container to entities. Mechanism should be able to support Cloning
> and
> DeepCloning opreations, even to and from different databases (DWGs),
> just as
> AutoCAD originally does.
> 
> Regards,
> Maksim Sestic
> 
> 
> 
> Orest Halustchak wrote:
>> 
>> Hi Maksim,
>> 
>> This is something that's not quite supported yet by FDO, all providers
>> so far are unmanaged. We had discussed support of managed providers
>> initially, but haven't built in complete support for this yet.
>> 
>> Are you thinking of using .Net or Java?
>> 
>> Thanks,
>> Orest.
>> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/Writing-managed-provider---HowTo-tf4640210s18162.h
> tml#a13254821
> Sent from the fdo-users mailing list archive at Nabble.com.
> 
> _______________________________________________
> fdo-users mailing list
> fdo-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users
> 
> _______________________________________________
> fdo-users mailing list
> fdo-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users
> 
> 

-- 
View this message in context: http://www.nabble.com/Writing-managed-provider---HowTo-tf4640210s18162.html#a13276871
Sent from the fdo-users mailing list archive at Nabble.com.



More information about the fdo-users mailing list