Skip to content
This repository has been archived by the owner on Dec 8, 2017. It is now read-only.

Have two words for "Layer" #13

Closed
lucaswoj opened this issue Mar 22, 2016 · 5 comments
Closed

Have two words for "Layer" #13

lucaswoj opened this issue Mar 22, 2016 · 5 comments

Comments

@lucaswoj
Copy link

  • Layers are things you define in a style
  • Layers are also things in a datasource

Two concepts deserve two words

originally posted by @tmcw as mapbox/mapbox-gl-js#1237

cc @peterqliu @anandthakker @nickidlugash @jfirebaugh @mourner @ansis @springmeyer @yhahn @bhousel

@lucaswoj
Copy link
Author

This is a complex issue.

Studio and the APIs currently use subset to refer to a "things in a datasource"

mapbox-gl-js, mapbox-gl-native, mapbox-gl-style-spec, exiting mapbox styles, and the vector tile spec use source-layer to "things in a datasource"

In my opinion, studio and the APIs should change to match the convention of calling "things in a datasource" source-layer. The "source" modifier is an acceptable differentiator between types of things.

@jfirebaugh
Copy link
Contributor

Both things are called "layers" in their respective specifications.

It's unlikely that we're going to rename either of these at the specification level, and I believe that introducing terms different than the underlying specification confuses, rather than clarifies, the issue. Let's use "source layer" and "style layer" where explicit disambiguation is necessary.

@tmcw
Copy link

tmcw commented Mar 22, 2016

cc @mapbox/appbox is this okay from a studio perspective, could we do a studio-wide rename?

@lyzidiamond
Copy link

I'm okay with source layer and style layer, so long as we are consistent.

@scothis
Copy link

scothis commented Mar 22, 2016

is this okay from a studio perspective, could we do a studio-wide rename?

Doable. There are a couple tight places where we'll need to manually nudge the UI.

I'm okay with source layer and style layer, so long as we are consistent.

agreed

@lucaswoj lucaswoj closed this as completed Jun 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants