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
Hi.
If you take a look at the example of GeoJSON file, you can see that the coordinate may have up to 16 decimals.
When I deserialize the data from such file using FeatureCollection - I loose 2 decimals in coordinates...
I think you should store coordinates as a Decimal type instead.
The text was updated successfully, but these errors were encountered:
Hi @alexandis. Why would you need so much precision ? Are those coordinates expressed in Lat/Lon ? If so, please read this : https://gis.stackexchange.com/a/8674.
Changing to decimal is a big breaking change, and should be considered only if it is really helpful.
Hi.
If you take a look at the example of GeoJSON file, you can see that the coordinate may have up to 16 decimals.
When I deserialize the data from such file using
FeatureCollection
- I loose 2 decimals in coordinates...I think you should store coordinates as a
Decimal
type instead.The text was updated successfully, but these errors were encountered: