Add standard icons and glyphs to all Mapbox styles

[lucaswoj]

We get so many support requests like mapbox/mapbox-gl-js#1999 that it would make sense to to add a standard set of icons (Maki) and glyphs to all Mapbox-provided styles.

Thoughts @lyzidiamond @danswick @jfirebaugh @samanpwbb @xrwang @peterqliu?

[jfirebaugh]

👍

Icons and glyphs.

[lyzidiamond]

Yes. All maki icons available in all template styles is a great idea. Also all glyphs. Yes.

[peckjon]

+1 this would be incredibly helpful

[samanpwbb]

I think it'd be wrong to give users the impression that maki was somehow built into Mapbox styles. There is a problem here, and it's that sprites are just inherently complicated to understand, not that styles don't come with default sprites. If we did have default sprites, the icons in them wouldn't be modifiable (unless we added SDF support or https://github.com/mapbox/maki-chef/ support to the style api) and it's not possible to find an icon style that would work for any map style.

Eventually, it'd be nice to soften this problem by making it easy to add a variety of pre-made icon sets to styles while leaving default sprites as-is through a UI in studio. Sprites should only contain the images that the map style uses.

[nickidlugash]

Agree with @samanpwbb. We have several different designs of maki icons across our different templates, and it doesn't make sense to replace them all with a default set. Maki is a customizable system, and our templates wouldn't demonstrate this.

Also, I don't think it makes sense for all customer styles made from our templates to have hundreds of potentially unused sprites. We've been working hard to minimize sprint bloat, and this goes against that.

What does it mean to add all glyphs? Are we talking about including all the fontstacks used across all the styles in every style?

[jfirebaugh]

We are continuing to get issues filed about this. It's something that commonly trips people up and is easily addressable by adding a default icon set to styles that don't already have one. We should just do it.

If we did have default sprites, the icons in them wouldn't be modifiable

Users who run into the issue don't usually care about modifiability; they just want some icon to be available. If they do care about modifiability, we point them to Studio. Adding defaults doesn't make the situation any worse, and it helps a significant number of users.

it doesn't make sense to replace them all with a default set

We're not suggesting replacing them all with a default set, we're suggesting adding defaults to styles that don't have any icons.

[jfirebaugh]

Concretely, here's what I suggest we do:

• Symlink sprites/satellite-v8 to sprites/satellite-hybrid-v8 and check in the symlink

• Add to satellite-v8.json:

  "sprite": "mapbox://sprites/mapbox/satellite-v8",
  "glyphs": "mapbox://fonts/mapbox/{fontstack}/{range}.pbf",
  

• Put out a point release, update the Styles API

[samanpwbb]

I'm on board with that. We're planning to do a big release as part of streets-v7 soon, so we can probably fit this in, cc: @amyleew @nickidlugash.

[nickidlugash]

👍

[lyzidiamond]

Hmm. What about light-v8 and dark-v8?

[amyleew]

@jfirebaugh @samanpwbb - satellite-v8.json updated for Studio merge #256

/cc @lucaswoj