[fdo-users] How does FDO handle invalid fgf geometries?

[Jackie Ng]

Hi All,

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)

- Jackie

-- 
Blog: http://themapguyde.blogspot.com
Facebook: http://www.facebook.com/profile.php?id=599261907
LinkedIn: http://www.linkedin.com/in/jackieng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-users/attachments/20080821/95e6cd0b/attachment.html