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

Store slim coordinates in unprojected units #542

Closed
pnorman opened this issue Feb 27, 2016 · 2 comments · Fixed by #668
Closed

Store slim coordinates in unprojected units #542

pnorman opened this issue Feb 27, 2016 · 2 comments · Fixed by #668

Comments

@pnorman
Copy link
Collaborator

pnorman commented Feb 27, 2016

Storing coordinates as scaled projected units means that it is necessary to scale differently for different projection, leading to bugs like #121 and untested code in #357

Instead, we should store unprojected WGS84 units as they are in the OSM file.

@pnorman pnorman added this to the 0.92.0 milestone Feb 27, 2016
@Komzpa
Copy link
Contributor

Komzpa commented Dec 22, 2016

Please also don't limit them to fixed point, as most reprojections will require floating point math.

@pnorman
Copy link
Collaborator Author

pnorman commented Dec 22, 2016

The plan is to use libosmium. iirc, this is fixed precision and internally uses 64 bits to store the location. This says nothing about if it can do floating point math, which shouldn't be a problem.

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

Successfully merging a pull request may close this issue.

2 participants