[mapguide-users] MGOS 2.0.1 as a WFS Server

[BenoitBegin]

I'm trying to setup my MGOS 2.0.1 server as a WFS server. Basically, I have
very mixed results using various software to attempt to consume the WFS
provided by MGOS.

1) FDO Provider for WFS in Mapguide / Studio
I create a connection with the WFS FDO Provider. I put the url as
"http://localhost/mapguide/mapagent/mapagent.fcgi" and the connection tests
properly. I then create  a layer that uses this FeatureSource and it is able
to list all of the available FeatureSources I flagged as WFS serviceable.

However, if I try and build filters and use the "Get Values" feature, it
returns no alphanumeric data. If I do a preview in the LayerDefinition, it
returns no data whatsoever. I know my <Bounds /> is properly set and I even
converted all my data to EPSG:4326 to make sure that it's not some funky
data conversion problem MGOS seems to have with WFS/WMS.

2) FDO Provider for WFS in AutoCAD MAP 2009
I create a data connection with the WFS FDO Provider. It properly connects,
but lists no available layers. So there is something wrong with either the
getCapabilities or the describeFeatureType call done to MGOS. Which is odd,
because the same FDO Provider seems to have two entirely different results.

3) WFS Connection inside of gvSIG
I downloaded gvSIG off of the OSGEO website to get an "outside of Autodesk"
product. It can connect properly to the WFS server and even lists the
layers. However, it seems as if it cannot resolve the layer type and some
data type. So my guess is that, as before, there is something wrong with the
getCapabilities or the describeFeatureType calls to the WFS in MGOS.

My next step was to check the XML returned by those two functions. In the
describeFeatureType, I see a lot of tags with fdo: attributes. I also see
that fdo:int32 is used for the FeatId property. I'm guessing that this value
simply cannot be processed by a WFS client, as it's something only FDO-aware
applications would understand.

Why is there so much fdo specific information returned in the
describeFeatureType call? Is this information making the WFS publishing
capabilities of MGOS unusable by any WFS aware applications? Did anyone
every manage to get their MGOS to publish WFS succesfully?
-- 
View this message in context: http://www.nabble.com/MGOS-2.0.1-as-a-WFS-Server-tp20740258p20740258.html
Sent from the MapGuide Users mailing list archive at Nabble.com.