Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current Coordinate type - Double - does not have enough precision #23

Open
alexandis opened this issue Feb 14, 2024 · 1 comment
Open

Comments

@alexandis
Copy link

alexandis commented Feb 14, 2024

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.

@xfischer
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants