[fdo-users] RE: Which GML version is supported by FDO 3.5.0

Brent Robinson brent.robinson at autodesk.com
Mon Jan 17 09:34:38 EST 2011

If you use the xmlFeatureSerializer then the null properties will be absent in the output file, which would be a bug. This is done to be consistent with how FDO serializes feature schemas; a nullable property is represented by an <element> with minoccurs="0". I don't remember why this was done, rather than set the nillable attribute, probably an oversight. For reading schemas, the situation is a bit better; the nillable attribute is handled if present.


-----Original Message-----
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Crispin_at_1Spatial
Sent: Friday, January 14, 2011 3:40 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] RE: Which GML version is supported by FDO 3.5.0

The provider is SHP.

I have the same code in two .NET projects referencing FDO 3.5 and 3.6 so I
end up with a 3.5 exe and a 3.6 exe so I know the application is the same
and I am referencing the same SHP file.

A query to get spatial context returns "Default" on the SHP file in 3.5 and
3.6 (there is no .PRJ file with the SHP)

So it looks like the previous 3.5 XML provider is setting the srs to
EPSG:4326 - through some rule?
The 3.6 provider is preserving the default name.

I am no GML expert so I couldn't say which is a better interpretation where
there is no spatial context found.

I'd be more interested in a clarification if NULL properties should be
absent or with empty XML tags.

 Thanks for updating the thread - Crispin
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Which-GML-version-is-supported-by-FDO-3-5-0-tp5906711p5921022.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 mailing list