Custom tile renderers #219
Labels
discussion: capability
a specific capability or feature: should it be included? what details? should it be a requirement?
status: suggestion
this issue discusses a suggested addition to the report, that is not yet in the draft
I didn't know where to put this, so for discussion, and potential relocation if necessary.
Many (all?) of the commercial content providers you use in the examples for this document deploy custom content rendering, using WebGL and custom server formats e.g. MVT, Google geobuffers and who knows what else.
Assuming that these providers won't be changing those renderer any time soon, a map solution for Web maps will, if it wants to incorporate these custom formats without asking the platform itself to support them directly, will have to be able to allow script or WASM to render content, perhaps in a "tile" event or something along those lines. In other words, the map solution will have to work with libraries to support custom client side rendering.
The text was updated successfully, but these errors were encountered: