[fdo-users] How does FDO handle invalid fgf geometries?
dan.stoica at autodesk.com
Thu Aug 21 10:16:18 EDT 2008
Just to make sure: is this Parcels.shp file located in \Providers\SHP\TestData\Sheboygan\ ?
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Thursday, August 21, 2008 8:39 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] How does FDO handle invalid fgf geometries?
How does FDO handle invalid FGF binary data?
Because I believe in the SHP test data, the 97th feature in Parcels.shp (FeatId = 97) contains an invalid geometry, as I cannot parse the byte array into FGF text, because it will throw an exception with the message: Memory allocation failed.
I even wrote my own FGF binary to text parser in managed code on the false belief that it was due to some memory leak in the FDO API, and tested it on this feature, and it too failed to correctly parse this geometry.
Does FDO have any safeguards in place to prevent insertion of invalid geometry values? (ie. Stop me from using a random binary BLOB as a geometry value)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fdo-users