<html>
<head>
</head>
<body><br />
>It's not in order to store lat/long, but in order to get a better<br />
>resolution than 360x180, right ? It's a matter of choosing a resolution,<br />
>more than a number of digits.
<div><br />
<div>Ok, I think I get what you mean</div>
<div><br />
><br />
>GEOJson uses the concept of "quantization" as the number of distinct<br />
>values each ordinate can take.</div>
<div><br />
</div>
<div>But the "percision" value in geojson, isn't that also number of decimals? ST_AsGeoJSON(geom,1) seems to give a result with 1 decimal.</div>
<div><br />
</div>
<div> The format encodes the scale and offset,<br />
>right ?</div>
<div><br />
</div>
<div>yes, you are right. in the header it stores "precision" in 4 bits, like 2 for instance.</div>
<div>That means it multiplicates the offset from last coordinate with 100, and vice verse at client side.</div>
<div><br />
</div>
<div>But it is not intended to be used at different scales. Isn't one of the big pros with vektor data that it can be used all over the range as long as it keeps "enough" details.</div>
<div><br />
</div>
<div>Leaflet for instance have a functionality called <span style="">smoothFactor, that, if I understand it right, simplifies the geometries at render time.</span></div>
<div><span style=""><br />
</span></div>
<div><br />
</div>
<div><br />
</div>
<div>I will try to read more about it to understand pros and cons by different concepts.</div>
<div><br />
</div>
<div><br />
</div>
<div>Thanks</div>
<div><br />
</div>
<div>Nicklas</div>
<div><br />
><br />
><br />
>--strk; <br />
>_______________________________________________<br />
>postgis-devel mailing list<br />
>postgis-devel@lists.osgeo.org<br />
>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel<br />
><br />
>
</div></div>
</body>
</html>