You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output contains an excessive number of decimal points (e.g., 170.86789491627363), which is unnecessary and increases the file size of both GeoJSON and SVG. Should we limit the precision to 1-4 decimal points?
@nihalzp is this something viable? I remember you mentioning that there is some sort of rounding that we do that has been helpful in removing intersections, and we need some degree of precision to not have intersections, but could we reduce the number of decimal places in the output without any problems?
The output contains an excessive number of decimal points (e.g., 170.86789491627363), which is unnecessary and increases the file size of both GeoJSON and SVG. Should we limit the precision to 1-4 decimal points?
Related article: https://css-tricks.com/understanding-and-manually-improving-svg-optimization/
The text was updated successfully, but these errors were encountered: