You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Our search API sometimes returns cities as separate polygons and streets as separate polylines because these areas and streets are not always connected with each other. However they should still be displayed and treated like one object.
Would something like #1729 effectively cover this? We've targeted it previously just in terms of polygons, but the same concept could apply to polylines, though MapKit (which we are modeled after here) doesn't have that concept.
@incanus Not entirely I'm afraid. While interior polygons would be useful it doesn't cover the entire use case. It was very easy to add this to legacy MapBox but i haven't hade a look at gl yet since I've never worked with c++ nor OpenGL.
Our search API sometimes returns cities as separate polygons and streets as separate polylines because these areas and streets are not always connected with each other. However they should still be displayed and treated like one object.
I added support for this in legacy MapBox mapbox/DEPRECATED-mapbox-ios-sdk#663
Is there any chance we can get this in
gl
please?cc @Zakay
The text was updated successfully, but these errors were encountered: