Hi Gorgon, I believe FDO in general has some quirks with floating point precision. This might be related to an issue I reported here: https://trac.osgeo.org/fdo/ticket/929
I remember having similar issues back in my C++ days. Going from a floating type to a string type would have quirky decimal values under certain circumstances. I can confirm, however, that we haven't encountered this issue using the C# API for both FDO and Mapguide to display values. So the display issue is likely located somewhere within the MapAgent code itself. Ben -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
