shape annotations#1655
Conversation
- track ordered shapes in AnnotationManager - add shape source at style parse time - add shape layers & buckets at annotation tile invalidation time - expose Annotation to MapContext for style querying
There was a problem hiding this comment.
Remember to pull these changes out before merging.
This should actually be pretty easily fixed. In shape adds, I'm just overflowing the tile extent and assuming all shapes belong in only one tile, as a naive extension of the point add. That's why this happens: Fixing that up now as a staged approach, so that we don't necessarily need the GeoJSONVT simplification stuff in the first cut. This is a ~2,500 point polyline and it performs well now. |
|
Taking a break from feature clipping, which is a bit of going in circles. I may just punt and bring in the GeoJSONVT work which takes care of this now instead of later, bringing along simplification for the ride. My reluctance to do so there is a bottleneck around the In the break I am going to rough out the Cocoa adding/removing/styling API since that part won't change and we are successfully using the direct C++ one right now. |
There was a problem hiding this comment.
prints to the console in Release mode?
There was a problem hiding this comment.
|
Split GeoJSONVT out to https://github.com/mapbox/geojson-vt-cpp. Currently just dupe-copied here still; no formal build or dep process. |
There was a problem hiding this comment.
This is kind of a sneaky way of getting access to these methods. The declarations should go in a private header in platform/ios/.
…e into shape-annotations
|






Runtime shape annotations.
StylePropertieset al. toMapusersProblems/checkpoints:
MapContext::updateAnnotationTiles()returns early. This doesn't affect points as their styling is all wrapped up in the style parsing step (since the variable parts are covered in the runtime{sprite}property), the conclusion of which performs a render. Worked around right now with a hack to add after a delay upon startup.