Creating Interoperable Tiled Maps
Formal Metadata
| Title | Creating Interoperable Tiled Maps |
|
| Title of Series | |
| Number of Parts | 156 |
| Author | |
| Contributors | |
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Tiled maps are the backbone of most web applications that show geospatial information. Before OGC API - Tiles was approved, last year, there was not really an interoperable way of creating these maps using a resource oriented architecture and JSON encodings.
OGC API - Tiles puts some formality to what people have been doing for years, with 'xyz' tilesets, but it also enables the clients to create a better user experience, by providing metadata, such as title, description or available zoom levels.
In this talk we'll provide an overview of this standard, and discuss its advantages, when compared to other standards/specifications, like WMTS or TileJSON. We'll illustrate the benefits of interoperability, with an example that uses FOSS4G software implementing OGC API - Tiles.
Finally, we'll point out some resources, available to anyone who wishes to develop and validate an OGC API - Tiles implementation. |
|
| Keywords | |