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

Altitude, Elevation or LocationCoordinate3D #179

Open
paulsUsername opened this issue Jan 30, 2022 · 3 comments
Open

Altitude, Elevation or LocationCoordinate3D #179

paulsUsername opened this issue Jan 30, 2022 · 3 comments
Labels
backwards incompatible changes that break backwards compatibility of public API feature New feature request. Java parity jira-sync-complete JS parity
Milestone

Comments

@paulsUsername
Copy link

paulsUsername commented Jan 30, 2022

Is there any roadmap for the addition of altitude data (by convention the 3 Double in the array of Coords in a Geometry LineString Object is an optional altitude value).

Or is there any know branch or fork with this functionality?

@paulsUsername paulsUsername changed the title Altitude, Elevation of LocationCoordinate3d Altitude, Elevation or LocationCoordinate3D Jan 30, 2022
@1ec5 1ec5 added backwards incompatible changes that break backwards compatibility of public API feature New feature request. labels Feb 2, 2022
@1ec5
Copy link
Contributor

1ec5 commented Feb 2, 2022

This library has always used CLLocationCoordinate2D in order to better integrate with frameworks in the Apple ecosystem such as Core Location. We could define our own Position struct with an altitude property, but it would require us to provide conversions to and from CLLocationCoordinate2D. We’d need to make sure relying so heavily on these conversions wouldn’t significantly affect performance for the very common use cases that require CLLocationCoordinate2D.

@1ec5
Copy link
Contributor

1ec5 commented Feb 2, 2022

If we move off CLLocationCoordinate2D as the principle data type, we should consider depending on an SPM package that conditionally includes Core Location on Apple platforms, as a more seamless way to support Core Location and Linux simultaneously.

Edit: wrong link, wrong library.

@1ec5 1ec5 added this to the v3.0 milestone Feb 2, 2022
@1ec5
Copy link
Contributor

1ec5 commented Feb 2, 2022

In the meantime, GeoJSON and GEOSwift both support representing altitudes as part of positions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backwards incompatible changes that break backwards compatibility of public API feature New feature request. Java parity jira-sync-complete JS parity
Projects
None yet
Development

No branches or pull requests

3 participants