Decouple layout and populating paint attribute buffers

[anandthakker]

Currently, the following two processes are always done together:

• layout - i.e., parsing vector tile feature geometries into a "layout vertex array" for each layer. This includes, e.g., symbol placement (and collision detection), triangulating polygons with earcut, etc.
• populating paint attribute buffers - when a layer has data-driven paint properties (i.e. feature-property-dependent), we populate a "paint vertex array" (or more than one, in GL Native), parallel to the layout array, containing paint attribute data for each vertex.

The principal reason for building these arrays in tandem is that it prevents us from having to keep track of which vertices belong to each vector tile feature. We could track this, though, and it would allow us to update paint buffers without redoing layout, which might significantly improve runtime styling performance in the case where a user sets a paint property to a data-driven value. (E.g. #4575)

[anandthakker]

I forgot to add: this decoupling would also largely clear the path towards updateable feature property data -- i.e., updating feature properties without wasting time reparsing geometries.

[ReevesSher]

I am in the same situation with #4575, i wonder that if i set stops[ [ 'uuid', '#fff'] ] , does it mean that compare this uuid with all other features of the layer?
if so, is it possible to do this just in the current viewport or some other limitation?

[ryanbaumann]

@anandthakker This would also be an enabler for transitions for DDS property style updates #3170

cc @averas

[keyofj]

I may have two paint properties to update such as line-color, line-width in some cases.

It seems like calling setPaintProperty for each redraws on each call which is visually slowing user performance.
_mapCanvas.setPaintProperty("nmap-boundary-layer", "line-color", _layerPaintProperties[0]); _mapCanvas.setPaintProperty("nmap-boundary-layer", "line-width", _layerPaintProperties[1]);

Is there a way to set both properties and result in only one redraw?

[anandthakker]

@keyofj style updates are batched per animation frame, so two consecutive calls shouldn't result in duplicate work. If you are, in fact, seeing this, then it's a bug--in which case, please do open a new issue (with an example if possible 🙏 )!

[keyofj]

Thanks. Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: Anand Thakker <notifications@github.com> Sent: Friday, June 2, 2017 5:08:02 PM To: mapbox/mapbox-gl-js Cc: Michael Clark; Mention Subject: Re: [mapbox/mapbox-gl-js] Decouple layout and populating paint attribute buffers (#4576) @keyofj<https://github.com/keyofj> style updates are batched per animation frame, so two consecutive calls shouldn't result in duplicate work. If you are, in fact, seeing this, then it's a bug--in which case, please do open a new issue (with an example if possible 🙏 )! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#4576 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHoyQDTjl4Y70rYkPXno-AWrWIlGgajNks5sAHmygaJpZM4M6uMB>.

[asheemmamoowala]

#6263 Keeps track of paint buffers per feature and may help with this. I suspect that this would only be useful in a narrow range where a layer already uses data-driven styling and wants to change the expression for a paint property.