tangrams / cartography-docs Goto Github PK

On https://github.com/tangrams/cartography-docs/blob/master/themes.md we talk about themes generally and then dive right into what themes each Map Style supports.

Let's add a pre-amble explaining the color, label, and detail axis and the rational for each and a small discussion of what each label or detail "step" offers.

/cc @tallytalwar

Most the styles must be updated to allow this, though.

Question: /cc @bcamper

• Should Mapzen house styles styles continue to ship with Mapzen's API keys set or leave that blank?

If we remove it, then our product pages would need to set them on map init, and the Github repo index pages would also need to set them on init.

Blocked by the following issues:

• tangrams/refill-style#35
• tangrams/walkabout-style#101
• tangrams/tron-style#136
• https://github.com/tangrams/zinc-style/issues/12
• tangrams/cinnabar-style#13

• Remove Zinc from Basemap styles page (fine to add note under Cinnabar for redirection). Copy what Refill did, with single URL instead of all the label variants.
• In Themes page add new Cinnabar section, with a Color section and a labels section. This is a little heavy handed, but until all styles have each of these options it's probably better to be explicate.
• In the Icons big table remove the duplicate Zinc column (it's off screen, didn't you know!) @nvkelso

• Supported in all styles
• sdk_building_extrude (default true except for Zinc when it's false)
• sdk_road_shields (default true)

Blocked by the following issues:

• tangrams/walkabout-style#100
• https://github.com/tangrams/zinc-style/issues/13
• tangrams/cinnabar-style#14

It's confusing to new users (saw this in person!) to see references made to Bubble Wrap, Zinc without a picture that clicks into a full page view of a basemap.

v2.1 of Walkabout (all label variants) now supports basic SDK/UI styles:

• Data visualization
• Default draw styles
• Basic user experience styles
• Transit user experience styles

But still not:

• Language
• Transit overlay

The table of all the icons should still be good... but we're publishing an update for official support for mapzen_icon_library imports and the following sections need updating:

• Using built-in sprites
• Using Mapzen icons independently (move above the table of icons). Most of this content can be deleted, it's only the import that is unique over the Using built-in sprites example.
• Update version numbers (increment major number – if it was 5 then it's 6 now)
• At the bottom of the Icons page in the Versions section add "and later":
  • example: Bubble Wrap: 6.0.0 and later

Both should reference mapzen_icon_library as the style name (not icons).

When we need a new version of Tangram, that should require a major version bump in the styles. Right now that is minor version of Tangram, in the future that may be major.

In the setting an API key example we show an older version of a updating the Tangram scene after import to override a global value. New Tangram ES have different syntax, and allow chaining modifications together.

This is a better example for newer Tangram ES:

map->loadScene(
    "https://mapzen.com/carto/refill-style/6/refill-style.yaml",
    false,
    { SceneUpdate("global.sdk_mapzen_api_key", "mapzen-xxxxxx"),
      SceneUpdate("global.sdk_building_extrude:", "false") }
);

While previously we stated:

map->loadScene(
    "https://mapzen.com/carto/refill-style/6/refill-style.yaml",
    false,
    { "global.sdk_mapzen_api_key", "mapzen-xxxxxx" }
);

Which wasn't wrong, but the updated syntax allows chaining the globals.

The assets need to be scaled down or be told to be smaller in markdown / CSS.