WCS Application Profile for JPIP Coverage Encoding146
TITLE: AUTHORS:
Peter Giacovelli, ITT peter.giacovelliitt.com
Michael P. Gerlek, LizardTech mpglizardtech.com
DATE: 28 November 2007
CATEGORY: Draft Proposal
This is a draft document. Editorial comments, unresolved issues, etc, are noted with italics andor highlighting. Send comments to the authors listed above.
1. Overview
This document provides an application profile to enable WCS 1.x clients and servers to support coverages expressed as JPIP streams of JPEG 2000 JP2 data. This document is specific to JPIP coverage formats.
This document is based on work done in 2006 for the OWS-4 project, as described in “OWS-4 IPR for WCS Support for JPEG 2000” 06-128.
Note that this document does not address support for “static” non-streaming JPEG 2000 data; that is covered in a separate document, “WCS Application Profile for JPEG 2000 Coverage Encoding” 07-145.
The present 07-146 document can be viewed at some level as an extension to the 07-145 document.
1.1 JPIP for WCS
[mpg will complete this section] WCS Application Profile for JPIP Coverage Encoding
Page 1
Short blurb on the basic properties of JPIP, emphasizing why is requires special handling. Point to the potential complexity of handling arbitrary coverages on the backend. Emphasize that philosophically we
want to preserve the WCS model, while still allowing a smart client to take advantage of all that JPIPpy goodness.
1.2 Summary of Changes
This application profile makes the following sets of changes to WCS:
A new MIME type is added
DescribeCoverage has one new parameter: o
SupportedGMLJP2Formats
GetCoverage has one new parameter:
GMLJP2Format
1.3 The Application Profile
As implied by Section 9.3.2.2 of the WCS 1.1 specification 07-067r2, an application profile must consist of several specific components. This document addresses these issues, as follows:
“MIME types and brief description” – see Sections 3, 4, 5, and 6
“Pointers to documentation” – see Section 2
“Data model mapping” – see Section 7
“Examples” – see Section 8
“Pointers to implementing software” – see Section 9
“Compliance testing” – see Section 10
1.4 Use Cases
