TranslatedStyleLayer¶
Namespace: ThinkGeo.Core.Styling
One GPU style layer a classic style became: what it draws, when, and which classic style it came from - so a translation can be read before it is added, and a layer that looks wrong on the map can be traced to its origin.
public sealed class TranslatedStyleLayer
Inheritance object → TranslatedStyleLayer
Properties¶
Id¶
The id the layer carries in the style - SetLayerVisibility addresses it by this. It starts with the source id, so two translations of the same data added to one style keep ids of their own.
public string Id { get; }
Property Value¶
Type¶
Fill, line, circle or symbol.
public StyleLayerType Type { get; }
Property Value¶
MinZoom¶
The zoom range the classic zoom level covered, in the map's zoom; null at either end for unbounded.
public Nullable<double> MinZoom { get; }
Property Value¶
MaxZoom¶
public Nullable<double> MaxZoom { get; }
Property Value¶
Origin¶
The classic style this layer draws - an AreaStyle, a ValueStyle's item style, and so on.
public Style Origin { get; }
Property Value¶
Methods¶
A(int)¶
internal StyleLayer A(int )
Parameters¶
`` int
Returns¶
ToJson()¶
The layer as a style.json layer, for what reads the document rather than the compiled layers - the Blazor overlay, a file the style is saved to. Its id carries the source layer's name when several layers share one source, so two layers over different data never take the same id. Null when what it draws has no style.json form - a RegexStyle's match, for one - and only the code path draws it; the translation's FeatureLayerTranslation.JsonWarnings say which.
public JsonObject ToJson()