<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hello list,<o:p></o:p></p><p class=MsoNormal>Does anyone know of a way to set the numeric precision on a Geometry.ExportToWKT() call ? For the SRS, we are using EPSG:4326 (WGS-84) so the multipolygon coordinates are in latitude/longitude, and most of the coordinate strings seem to carry 15 digits past the decimal point !! For our needs, 7 or 8 digits would be sufficient, so this seems wasteful, especially when the string is stored in a database. I examined the OGR documentation but I don’t see any variation of ExportToWKT nor any other means of setting the numeric precision. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I estimate using 7 digits of precision instead of 15 could reduce total storage by about 40%. I realize I could post-process the string produced by ExportToWKT() to reduce all coordinates to the desired precision. But did I miss anything in OGR capabilities ?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>BTW we are using GDAL/OGR 1.8.0 with C# bindings.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in'><b><span lang=EN-GB style='font-size:10.0pt;color:#004080'>Jay Jennings</span></b><b><span style='font-size:10.0pt;color:#004080'><o:p></o:p></span></b></p><p class=MsoNormal style='mso-margin-top-alt:3.0pt;margin-right:0in;margin-bottom:3.0pt;margin-left:0in'><span lang=EN-GB style='font-size:10.0pt;color:#004080'>GeoEye, Inc.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>