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.

Sign up for GitHub

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

Jump to bottom

Be aware of Endian differences in spatial data. #14

Open

Aeryka opened this issue Dec 2, 2010 · 1 comment

Labels

10.1.0 Geospatial

Aeryka commented Dec 2, 2010

The internal spatial data will have to be Endian aware once differing platforms are supported.

Author

Aeryka commented Dec 2, 2010

Potentially this could be solved by storing spatial data in network byte order all the time and translating to host when extracting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment