-
Notifications
You must be signed in to change notification settings - Fork 919
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
Support 3D geometries #2534
Comments
Thanks for raising this @kevinschaich. To what extent are you requesting support? Let's say the spectrum runs from "let people provide z coords but ignore them for calculations" all the way up to "fully incorporate altitude variations in to all functionality". Do you have a particular use case? Or are you getting errors when supplying a z coord? |
E.g. bezierSpline ignores the z coordinate and returns two-dimensional coordinates. Other 2D functions could project points onto a plane and work inside it. |
Ignore z coordinate would be a great first step. I imagine things get much more complicated if you're doing the actual operations – the GeoJSON spec says:
so that would mean the three coordinates are not in the same units ( Do all the functions share a common parser step at the beginning? If so, would be easy to just strip off the third coordinate and then pass that in. |
Is it possible to support 3D geometries with an optional
z
/altitude
/elevation
coordinate?This is now supported by the GeoJSON spec.
The text was updated successfully, but these errors were encountered: