alonisser
commented
10 years ago +1
Twitter:@alonisser https://twitter.com/alonisser LinkedIn Profile http://www.linkedin.com/in/alonisser Facebook https://www.facebook.com/alonisser _Tech blog:_4p-tech.co.il/blog _Personal Blog:_degeladom.wordpress.com Tel:972-54-6734469
On Thu, Nov 21, 2013 at 3:34 PM, Nir Yariv notifications@github.com wrote:
Right now our geoJSON data stores coordinates within 15 digits after the decimal point. This makes for fairly large files.
Google Maps API works with up to 6 decimals' accuracy.
Interestinghttps://groups.google.com/d/msg/google-maps-api/uSi1-8U1GCE/X8fTe5g96lwJ: "At the equator, 1 degree is 111320m, which means that 0.000001deg is around 11cm. Seven decimal places allows you to place a marker to an accuracy of around a centimetre, which can't be shown on a map. At higher latitudes, six decimals will be an accuracy of less than 10cm."
I reckon we could suffice with 6 digits after the decimal point as well..
— Reply to this email directly or view it on GitHubhttps://github.com/niryariv/opentaba-client/issues/41 .
florpor
Right now our geoJSON data stores coordinates within 15 digits after the decimal point. This makes for fairly large files.
Google Maps API works with up to 6 decimals' accuracy.
Interesting: "At the equator, 1 degree is 111320m, which means that 0.000001deg is around 11cm. Seven decimal places allows you to place a marker to an accuracy of around a centimetre, which can't be shown on a map. At higher latitudes, six decimals will be an accuracy of less than 10cm."
I reckon we could suffice with 6 digits after the decimal point as well..