Publication Date: 2020-07-08
Approval Date: 2020-06-26
Submission Date: 2020-05-01
Reference number of this document: OGC 19-082r1
Reference URL for this document: http://www.opengis.net/doc/PER/vtp2-D001
Category: OGC Public Engineering Report
Editor: Sergio Taleisnik
Title: OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report
COPYRIGHT
Copyright © 2020 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/
WARNING
This document is not an OGC Standard. This document is an OGC Public Engineering Report created as a deliverable in an OGC Interoperability Initiative and is not an official position of the OGC membership. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard. Further, any OGC Public Engineering Report should not be referenced as required or mandatory technology in procurements. However, the discussions in this document could very well lead to the definition of an OGC Standard.
LICENSE AGREEMENT
Permission is hereby granted by the Open Geospatial Consortium, ("Licensor"), free of charge and subject to the terms set forth below, to any person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual Property without restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify, merge, publish, distribute, and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual Property is furnished to do so, provided that all copyright notices on the intellectual property are retained intact and that each person to whom the Intellectual Property is furnished agrees to the terms of this Agreement.
If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above copyright notice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by LICENSOR.
THIS LICENSE IS A COPYRIGHT LICENSE ONLY, AND DOES NOT CONVEY ANY RIGHTS UNDER ANY PATENTS THAT MAY BE IN FORCE ANYWHERE IN THE WORLD. THE INTELLECTUAL PROPERTY IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE INTELLECTUAL PROPERTY WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE INTELLECTUAL PROPERTY WILL BE UNINTERRUPTED OR ERROR FREE. ANY USE OF THE INTELLECTUAL PROPERTY SHALL BE MADE ENTIRELY AT THE USER’S OWN RISK. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR ANY CONTRIBUTOR OF INTELLECTUAL PROPERTY RIGHTS TO THE INTELLECTUAL PROPERTY BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM ANY ALLEGED INFRINGEMENT OR ANY LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR UNDER ANY OTHER LEGAL THEORY, ARISING OUT OF OR IN CONNECTION WITH THE IMPLEMENTATION, USE, COMMERCIALIZATION OR PERFORMANCE OF THIS INTELLECTUAL PROPERTY.
This license is effective until terminated. You may terminate it at any time by destroying the Intellectual Property together with all copies in any form. The license will also terminate if you fail to comply with any term or condition of this Agreement. Except as provided in the following sentence, no such termination of this license shall require the termination of any third party end-user sublicense to the Intellectual Property which is in force as of the date of notice of such termination. In addition, should the Intellectual Property, or the operation of the Intellectual Property, infringe, or in LICENSOR’s sole opinion be likely to infringe, any patent, copyright, trademark or other right of a third party, you agree that LICENSOR, in its sole discretion, may terminate this license without any compensation or liability to you, your licensees or any other party. You agree upon termination of any kind to destroy or cause to be destroyed the Intellectual Property together with all copies in any form, whether held by you or by any third party.
Except as contained in this notice, the name of LICENSOR or of any other holder of a copyright in all or part of the Intellectual Property shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Intellectual Property without prior written authorization of LICENSOR or such copyright holder. LICENSOR is and shall at all times be the sole entity that may authorize you or any third party to use certification marks, trademarks or other special designations to indicate compliance with any LICENSOR standards or specifications.
This Agreement is governed by the laws of the Commonwealth of Massachusetts. The application to this Agreement of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded. In the event any provision of this Agreement shall be deemed unenforceable, void or invalid, such provision shall be modified so as to make it valid and enforceable, and as so modified the entire Agreement shall remain in full force and effect. No decision, action or inaction by LICENSOR shall be construed to be a waiver of any rights or remedies available to it.
None of the Intellectual Property or underlying information or technology may be downloaded or otherwise exported or reexported in violation of U.S. export laws and regulations. In addition, you are responsible for complying with any local laws in your jurisdiction which may impact your right to import, export or use the Intellectual Property, and you represent that you have complied with any regulations or registration procedures required by applicable law to make this license enforceable.
- 1. Subject
- 2. Executive Summary
- 3. References
- 4. Terms and Definitions
- 5. Overview
- 6. Background
- 7. Tile Set Metadata Model
- 8. Implementations
- 9. Discussion
- 10. Results
- 11. Findings
- 12. Lessons Learned
- 13. Conclusions
- Annex A: Tile Set Metadata JSON Encoding
- Annex B: Revision History
- Annex C: Bibliography
1. Subject
The OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report (ER) describes a conceptual model for Tile Set Metadata that provides information about the intended usage of a Tile Set as well as the origin, security level, tiling scheme, layers and feature properties contained within. In this ER, a tile set is a series of tiles containing data and following a common tiling scheme.
The metadata is intended to facilitate retrieval of tile sets and describes the major characteristics of tile sets without actually accessing the tiles nor the content contained in a tile. Such a process could be time consuming when there are a large number of tiles in a tile set.
Additionally, this ER summarizes the discussions about Tile Set Metadata among the VTP2 participants, and draws up conclusions and recommendations for future work on the subject.
Finally, this ER describes the Technology Integration Experiments (TIEs) performed to test the prototype implementation of the proposed Tile Set Metadata Model on API endpoints, client applications, and GeoPackages.
2. Executive Summary
Tile sets are a well-established method for structuring, storing, and accessing manageable packages of tiled data, both offline and online. As the use of tile sets increases and the need for seamless transitions between online and offline environments increases, the need for efficient access to the tile set metadata becomes more critical.
The objective of VTP2 was to deliver a consistent, interoperable online/offline architecture for vector tiles based on feature servers, tile servers and GeoPackage.
The metadata activities of VTP2 can be grouped into three major components:
-
Designing the Tile Set Metadata Model.
-
Capturing and summarizing discussions and recommendations.
-
Describing TIEs implementing the Tile Set Metadata Model.
The Tile Set Metadata Model built in VTP2 is based on requirements established in the Call For Participation (CFP) and then further refined through the course of the Pilot. The initial metadata requirements specified in the CFP were to:
-
Develop a metadata model for vector tiles and stored tile caches.
-
Extend the National System for Geospatial Intelligence (NSG) Metadata Foundation (NMF).
-
Design the metadata to describe fundamental aspects of the tiles, such as date, creator, source, etc.
-
Specify metadata elements that describe the tiling scheme (tile matrix set).
-
Define how space is partitioned into individual tiles, substitution variables to identify tiles using a three-part identifier such as {level} (zoom), {row} (vertical) and {col} (column: horizontal).
-
Provide elements for Style names or identifiers and metadata to describe multi-layer vector tiles.
-
Provide other elements required to support the Vector Tiles Filter language [1].
-
Provide a standard resource path structure to consistently present simple metadata for vector tiles as an extension to tile and feature servers, standalone tile caches and GeoPackage tables.
Note
|
The term tile cache was used in the VTP2 CFP as a synonym for tile set repositories. The use of this term was subject to discussion throughout the Pilot and reflected by this ER. |
Since the CFP was defined a year before its release, many requirements evolved in order to cope with the developments carried out since then. Additionally, conversations throughout the Pilot further refined these requirements: The requirement to extend the NMF was changed to limiting the NMF elements implemented to only those considered of value to the tile set use cases presented in this Pilot, and the requirement for describing tile and tile set metadata was changed to exclusively describing tile set metadata.
The metadata model defined in this Pilot can be divided into three main groups:
-
Describing fundamental aspects of the TileSet (representation of a tile set) such as names, identifiers, dates, owners, origin, security levels, etc.
-
Describing the tiling scheme by storing the Tile Matrix Set information of the TileSet. This helps identify the geographic extent, the level of detail and the tiling scheme.
-
Describing the layers and feature properties stored within, in order to understand the use and application domain of the TileSet.
A novel approach to store and access Tile Set Metadata was implemented. The creation of an additional resource to an OGC Application Programming Interface (API) was discarded for many technical reasons. This led to consensus that all the Tile Set Metadata should be stored in a stand-alone file that would be located in the root folder of the offline repository.
2.1. Business Value
The main benefit of transitioning from raster tiles to vector tiles has been the possibility of flexible map styling and the reduction of storage space required for maps, the latter allowing for maps being stored on devices with lower storage capacity as well as requiring lower bandwidth communications for transmission. In some cases, depending on the file format, maps structured using tiled vector/feature data can be 20 to 30 times smaller than the same maps represented by raster tiles for a similar level of detail. This reduction enables the possibility of storing a large number of maps (i.e.,tile sets) into secure and lightweight removable media devices.
The VTP2 initiative implemented a scenario (Figure 1) in which a tile set repository (such as GeoPackage) is being used by a humanitarian relief convoy in the middle of the desert. The convoy has limited to no connectivity and is only supported by a group of interconnected systems working and communicating with each other. The repositories are generated in Command Post Computing Environments (CPCE) and comprise tile sets, styles, maps and routes served by National-level Services and Enterprise-level Services, which communicate with each other through implementations of OGC APIs for styles, tiles, images and routes.