[fdo-users] MapInfo provider
traian.stanev at autodesk.com
Wed Mar 25 10:45:41 EDT 2009
What MapInfo features that can be provided by FDO are hidden by OGR? How important are they?
Seems like the answers to those questions would help determine whether it's worth writing a dedicated provider.
I know that Autodesk has successfully used the OGR provider with Map3D for certain customers (also in Australia).
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Wednesday, March 25, 2009 10:11 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] MapInfo provider
Something that's been brewing in the back of my mind is whether it is feasible to write an FDO provider for MapInfo.
Now the reason I say feasible is because:
a) The OGR provider already supports MapInfo files. I could be duplicating effort here, but then again this could be a SHP or PostGIS situation where OGR can support it, but there is already a specialized provider for it.
b) The only libraries I know of that can read/write MapInfo file are MITAB and OGR, but reading more about MITAB I find that its is based on the OGR library, so this is going back to point a)
We have a lot of potential clients (MapInfo users) here in Australia, where a dedicated MapInfo FDO provider could really sway them over. Having to work with the lowest common denominator behaviour of the OGR provider is kind of cumbersome though.
I guess my question is: Is it worth writing a MapInfo-only FDO provider when the OGR provider already exists that can adequately serve this purpose?
View this message in context: http://n2.nabble.com/MapInfo-provider-tp2532574p2532574.html
Sent from the FDO Users mailing list archive at Nabble.com.
fdo-users mailing list
fdo-users at lists.osgeo.org
More information about the fdo-users