Skip to content
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

Custom tile renderers #219

Open
prushforth opened this issue Jul 9, 2020 · 0 comments
Open

Custom tile renderers #219

prushforth opened this issue Jul 9, 2020 · 0 comments
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

Comments

@prushforth
Copy link
Member

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.

@Malvoz Malvoz added 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 labels Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants