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

Ideas about rendering #5

Open
kylebarron opened this issue Mar 11, 2020 · 0 comments
Open

Ideas about rendering #5

kylebarron opened this issue Mar 11, 2020 · 0 comments

Comments

@kylebarron
Copy link
Contributor

How should layers be created from the spec?

new DeckglStyleSpecLayer({...})

Props:

  • Style JSON
  • features (optional, because I can download them from the style json sources section. If provided, layer names must match.)

Then inside renderSubLayers I render individual layers.

How should the data process work?

  • Render individual deck.gl layer for every layer object in the Style JSON? I'm not sure what the overhead is on number of layers, but that seems like a lot, especially if rendered as a sublayer of a tile layer. You could have 20+, 50+ layers per tile. That seems like too much.
  • Then the other option is to combine Style JSON layers into a single Deck.gl layer per type of data. I.e. only ~3 layers would be rendered as sublayers of the style spec layer, one PathLayer, one SymbolLayer, one TextLayer (though start with the PathLayer).

I think the latter option makes more sense, so the following will pertain to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant