Open Geospatial Consortium

Submission Date: 2021-07-06

Approval Date:   2021-xx-xx

Publication Date:   2021-xx-xx

External identifier of this OGC® document: http://www.opengis.net/doc/NOTE/GPKG-notes/1.1

Internal reference number of this OGC® document:    21-047

Version: 1.1

Category: OGC® Release Notes

Editor:  Carl Reed, PhD

OGC GeoPackage Tiled Gridded Coverage Version 1.1 Release Notes

Copyright notice

Copyright © 2021 Open Geospatial Consortium

To obtain additional rights of use, visit http://www.ogc.org/legal/

Warning

This document is not an OGC Standard. This document is distributed for review and comment. This document is subject to change without notice and may not be referred to as an OGC Standard.

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

Document type:    OGC® Release notes

Document subtype:   

Document stage:    Approved

Document language:  English

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.

Preface

This document provides the set of revision notes for the GeoPackage Tiled Gridded Coverage Extension Standard, version 1.1 [OGC <document number>]> and does not modify that standard.

This document provides the details of edits, deficiency corrections, and enhancements of the above-referenced standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

Keywords

ogcdoc, geopackage, tiled gridded coverage, tiles, coverage, release notes

1. Introduction

1.1. Scope

This Release Notes document provides information on changes to version 1.0 of the GeoPackage Tiled Gridded Coverage Extension.

1.2. Document contributor contact points

All questions regarding this document should be directed to the contacts provided below or the referenced standard editor(s).

Table 1. Contacts
Name Organization

Jeff Yutzler

Image Matters

Carl Reed

Carl Reed & Associates

2. References

The following normative documents are new or updated references in the standard to which these Release Notes apply.

Note
Need to update link to document!!

3. Terms and definitions

This document uses the terms defined in Sub-clause 5.3 of [OGC 06-121r8], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

For the purposes of this document, the following additional terms and definitions apply.

3.1. administrative change

An administrative change is a change that does not alter the conformance abstract tests for any requirements. It includes typographical errors, changes in wording to improve clarity or consistency, and perfunctory changes such as changes in version numbers.

3.2. critical Change

A critical change is a change that alters requirements in a way that is known to cause reverse compatibility issues.

3.3. substantive change

A substantive change is a change that alters requirements or schemas in a way that is not deemed to have a high risk for causing reverse compatibility issues.

3.4. Abbreviated terms

4. Change Log

4.1. KEY

  • Source:

    • CR - Formal Change Request

    • Issue - GitHub Issue

    • Editor - The GeoPackage document Editor

    • OGC-NA - OGC Naming Authority review

    • Public - Public Comment period

    • SWG - Approved decision by the Standards Working group (SWG)

    • User - The GeoPackage User Community

    • Other

  • Identifier: Change Request number or issue number and pull request/commit in GitHub

  • Type:

    • A=Administrative

    • S=Substantive

    • C=Critical

See Description of Critical Changes for more information on critical changes and Description of Substantive Changes for more information on substantive changes.

  • Section: Section number in the updated document

  • Description: Brief text describing the change

  • Purpose: the reason for the change:

    • Clarity

    • Consistency

    • Interoperability

    • Perfunctory

    • Readability

    • Usability

    • Change Request

Note
The following are examples and need to be replaced with changes for this revision!!!

4.2. Change Table

Table 2. Change Log
Source Identifier Type Section Description Purpose

Editors

NA

A

Various

Change all cover page to reflect Version 1.1 revision

Consistency

Editors

NA

A

Various

Move source code etc from stand alone Git repo into GPKG repo

Consistency

Issue

552

S

Clause 7

Request supporting additional data types in GeoPackage coverages

Resolve Issue 552, Usability

Issue

553

S

Clause 7 - Tiff

Request supporting multiple channels in a GeoPackage Coverage

Resolve Issue 553, Usability

Editors

NA

S

Requirement 10

Modify Requirement 10 to make more generic in data type reference

Clarity

Issue

553

S

Clause 7, Requirement 14

Modify Requirement 14 in support of TIFF changes. Move this requirement into the TIFF requirements class

Resolve Issue 553 and 576

Editors

NA

S

Requirement 14

Modify Requirement 14 for clarity

Clarity

Editors

NA

S

Requirement 15

Modify Requirement 15 to reference correct CIS class

Clarity

Issue

553

S

Requirement 17

Modify Requirement 17 to allow SampleFormat tag to be 1 (unsigned integer), 2 (signed integer), or 3 (IEEE floating point)

Resolve Issue 553 and 576

Issue

572

A

Requirement 21

Requirement 21 still mentions Elevation

Resolve Issue 572, Consistency

Issue

576

S

Clause 7

Clarify existing requirements classes. Added additional informative wording and moved content to reflect requirements classes reorganization

Resolve Issue 576, Usability

Editors

NA

S

Requirement 19

Modify Requirement 19 to make more generic in data type reference

Clarity

Editors

NA

S

Requirement 20

Modify Requirement 20 to make more generic in data type reference

Clarity

Issue

576

S

TGCE Requirements 1 and 2

Moved into new Core Requirements Class

Resolve Issue 576

Issue

576

S

Requirements Class : Table Values removed

Requirements placed into Core.

Resolve Issue 576

Issue

576

S

Requirements Class : 2d Gridded Coverage Ancillary removed

Requirements placed into Core.

Resolve Issue 576

Issue

576

S

Requirements Class : 2d Gridded Tile Ancillary removed

Requirements placed into Core.

Resolve Issue 576

Issue

576

S

Requirement 13

Moved into the Core requirements class

Resolve Issue 576, Usability

Issue

553

S

Pyramid Requirements Class

The requirements_class_Tile_Pyramid_User_Data_Tables was removed and the two requirements moved into the Core Requirements Class and the TIFF Requirements Calss

Resolve Issue 553 and 576.

5. Description of Critical Changes

5.1. <short name for the change>

<details of the change>

There are no critical changes in this release.

6. Description of Substantive Changes

There are two substantive changes incorporated into the GeoPackage Tiled Gridded Coverage Version 1.1 extension. These changes do not impact backwards compatibility.

6.1. Issue 552: Request ability to support additional data types in GeoPackage coverages.

A synopsis of the issue and related suggested changes is:

The CDB SWG is considering the use of GeoPackage to store coverage data as component of CDB 2.0. CDB currently uses a variety of data element types (in GeoTiff) to store coverage data. Therefore, the CDB SWG is requesting being able to use these data types in a GeoPackage coverage tile:

8/16/32 bit signed integers
8 bit unsigned integer (16-bit integer is currently supported, but only for PNG)
32-bit floating point (already supported in GeoPackage coverages)
1 bit (will be used in CDB 1.2 when adopted, as a binary mask)

Therefore there is benefit to allowing the use of GeoPackage coverages beyond a few narrow use cases that the existing formats allow.

6.2. Issue 553: Request enabling the use of multiple channels in a GeoPackage Coverage

A synopsis of the issue and related suggested changes is:

Using a single channel coverage can cover many data types and use cases, but not all. In particular, there are data coverages that are comprised of multiple data values per grid cell, and designed such that all the data elements to make use of this type of data are needed. For example, a layer that describes current wind conditions would be defined by both wind cardinal direction and velocity. In this example, using either coverage without the other would be very difficult.

In the CDB Standard, there are coverages that represent the physical material of a grid on the ground or on a model. These coverages consist of the material index and a percentage of that material. Another use case is encoding elevation data based on a point elevation (not an average), where at lower resolutions we want to adjust the point’s position (in latitude/longitude) as offsets from the grid cell corner.

If coverages were more flexible in this manner, then imagery could just become another coverage, and possibly also contain non-visual bands (like Near Infrared (NIR) or Short-Wave Infrared (SWIR) data).

6.3. Issue 576: Clarify existing requirements classes

A synopsis of the issue is and related changes are:

Right now there is a lack of precision in some of the TGCE requirements classes. Also there are currently too many requirements classes. The current set of requirements classes can be consolidated into two requirements classes and related conformance classes: Core (Requirements 1-13 / Section 7) TIFF Encoding (Requirements 14-21 / Section 8)

Therefore Requirement 14 needs to get moved into the TIFF Encoding Requirements Class and rewritten in such a way that it can be supplanted by a more flexible (but harder to implement) Requirements Class as described in issues #552 and #553 (See above).

The SWG discussed and approved the changes necessary to resolve this issue.

7. Future Work

Annex A: Revision History

Date Release Editor Primary clauses modified Description

2021-03-09

1.1

C. Reed

all

initial version