Hello list, We are using GeoServer for impact calculations and noticed that the GeoServer WCS module is not able to report the origin attribute with sufficient precision (for our application) We expected (105.29857, -5.56523) but got (105.30417, -5.570833).
Has anyone experienced a similar issue? What's a good way to start debugging this? Ariel. More details and a script to reproduce it (including sample data) below: https://gist.github.com/825323 Using the following version of GeoServer version = 2.2-SNAPSHOT svn revision = 15968 build date = 01-Jun-2011 03:32 geotools version = 8-SNAPSHOT geotools revision = 37354 hudson build = 725 Origin obtained using gdalinfo in the original file: Origin = (105.298569999999998,-5.565233000000000) Origin obtained using WCS DescribeCoverage in the original file: <gml:pos>105.30417 -5.570833</gml:pos> ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
