Concept
Alternate Profiles
Different views and formats:
Alternate Profiles ?Profiles (alternative information views) encoded in various Media Types (HTML, text, RDF, JSON etc.) are available for this resource.
- Preferred Labelskos:prefLabel
OGC Testbed-15: Styles API Engineering Report
- URI
- http://www.opengis.net/def/docs/19-010r2 ↗Go to the persistent identifier link
- Within Vocab
- OGC Documents
| Definitionskos:definition | This document is a proof of concept of a draft specification of the OGC Styles Application Programming Interface (API) that defines a Web API that enables map servers and clients as well as visual style editors to manage and fetch styles. Web APIs are software interfaces that use an architectural style that is founded on the technologies of the Web. Styles consist of symbolizing instructions that are applied by a rendering engine on features and/or coverages. The Styles API supports several types of consumers, mainly: Visual style editors that create, update and delete styles for datasets that are shared by other Web APIs implementing the OGC API - Features - Part 1: Core standard or the draft OGC API - Coverages or draft OGC API - Tiles specifications; Web APIs implementing the draft OGC API - Maps specification fetch styles and render spatial data (features or coverages) on the server; Map clients that fetch styles and render spatial data (features or coverages) on the client. Feature data is either accessed directly or organized into spatial partitions such as a tiled data store (aka vector tiles). The Styles API is consistent with the emerging OGC API family of standards. The Styles API implements the conceptual model for style encodings and style metadata as documented in chapter 6 of the OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report. The model defines three main concepts: The style is the main resource. Each style is available in one or more stylesheets - the representation of a style in an encoding like OGC SLD 1.0 or Mapbox Style. Clients will use the stylesheet of a style that fits best based on the capabilities of available tools and their preferences. For each style there is style metadata available, with general descriptive information about the style, structural information (e.g., layers and attributes), and so forth to allow users to discover and select existing styles for their data. |
|---|---|
| Broaderbroader | Public Engineering Report |
| http://purl.org/dc/terms/createdcreated | 2019-12-12 |
| Creatorcreator | Clemens Portele |
| seeAlsoseeAlso | https://docs.ogc.org/per/19-010r2.html |
| Statusstatus | valid |
| Notationnotation | 19-010r2 |
| Alternative LabelaltLabel | OGC Testbed-15: Styles API Engineering Report |
| 19-010r2 | |
| OGC document typedoctype | Public Engineering Report |