3 4-D Wx Data Cube WCS 1.1 Extensions - UCAR Wiki

squabbletownmushySoftware and s/w Development

Dec 14, 2013 (3 years and 10 months ago)

160 views



4
-
Dimensional Weather Data Cube

Web Coverage Service (WCS) 1.1.2 Interface Extensions


Version
2
.
1

2
/
15
/
20
11







National Center for Atmospheric Research

MIT Lincoln Laboratory

National Oceanic and Atmospheric Administration/Global Systems Division




DO
CUMENT REVISION REGISTER

Version

Date

Content Changes

Editors

Contributors

1.0

5/7/2010

Preliminary draft

Aaron Braeckel


2.0

12/21/2010

Updates to reflect NWS
review

Aaron Braeckel


2.1

2/15/2011

Updates to align with
WFS Interface
Document v2.0
.
Diag
ram/clarity
improvements

Aaron Braeckel





Please direct comments or questions to:

Aaron Braeckel

National Center for Atmospheric Research



3450 Mitchell Ln



Boulder, CO 80301



braeckel@ucar.edu








Terms of Use

The following Terms of Use applies to
the NNEW Documentation.

1.

Use.

The User may use NNEW Documentation for any lawful purpose without any fee or cost.
Any modification, reproduction and redistribution may take place without further permission so
long as proper copyright notices and acknowle
dgements are retained.

2.

Acknowledgement.

The NNEW Documentation was developed through the sponsorship of the
Federal Aviation Administration.

3.

Copyright.

Any copyright notice contained in this Terms of Use, the NNEW Documentation,
any software code, or

any part of the website shall remain intact and unaltered and shall be
affixed to any use, distribution or copy. Except as specifically permitted herein, the user is not
granted any express or implied right under any patents, copyrights, trademarks, or o
ther
intellectual property rights with respect to the NNEW Documentation.

4.

No Endorsements.

The names, MIT, Lincoln Labs, UCAR and NCAR, may not be used in any
advertising or publicity to endorse or promote any program, project, product or commercial
enti
ty.

5.

Limitation of Liability.

The NNEW Documentation, including all content and materials, is
provided "as is." There are no warranties of use, fitness for any purpose, service or goods,
implied or direct, associated with the NNEW Documentation and MIT a
nd UCAR expressly
disclaim any warranties. In no event shall MIT or UCAR be liable for any damages of any nature
suffered by any user, or any third party resulting in whole or in part from use of the NNEW
Documentation.





Table of Contents


1

Introduction

................................
................................
................................
................................
..........

6

2

Purpose

................................
................................
................................
................................
..................

7

3

4
-
D Wx Data Cube WCS 1.1 Extensions
................................
................................
..............................

8

3.1

SOAP

................................
................................
................................
................................
..............

8

3.2

NetCDF 4/CF Output Format Support

................................
................................
...........................

9

3.3

GRIB2 Output Format Su
pport

................................
................................
................................
......

9

3.4

SOAP with Attachments (SWA)

................................
................................
................................
.....

9

3.5

Trajectory Support

................................
................................
................................
........................

9

3.6

Publish/Subscribe Support

................................
................................
................................
..........

10

3.7

Model Run Time/Valid Time Support

................................
................................
.........................

10

3.8

Units of Measure

................................
................................
................................
.........................

10

3.9

GetCoverage Callbacks (store=true)

................................
................................
...........................

10

3.10

GetMetadata operation and ISO 19139 Metadata

................................
................................
.....

10

3.11

Request Reconstruction

................................
................................
................................
..............

11

4

Examples

................................
................................
................................
................................
.............

12

4.1

GetCapabilities Examples

................................
................................
................................
............

12

4.2

DescribeCoverage Examples

................................
................................
................................
.......

12

4.3

GetCoverage Examples

................................
................................
................................
...............

12

4.4

GetCoverage Corridor/Trajectory Examples

................................
................................
...............

14

APPENDIX A
-

Acronyms

................................
................................
................................
.........................

16

APPENDIX B


Definitions and Terms

................................
................................
................................
.....

18

APPEN
DIX C
-

References

................................
................................
................................
........................

19





1

Introduction

The NextGen Network Enabled Weather (NNEW) Program is tasked with creating an infrastructure that
will allow users of the United States’ national airspace system (NAS) to access a single
, nationwide
picture of the weather

for decision
-
making purposes
. This infrastructure, the 4
-
D Wx Data Cube, serves
as a virtual, distributed data store, disseminating up
-
to
-
the
-
minute weather information synthesized from
tens of thousands of data sources.

It provides its users with a single, authoritative source of weather
observation and forecasting data.

The 4
-
D Wx Data Cube is a standards
-
based system, designed to be compatible with a number of
standardized interfaces and geospatial formats. Among these

formats is the Web
Coverage

Service [
i
],
developed by the Open Geospatial Consortium (OGC) as a method of interfacing with web
-
based
databases for the purpose of providing filtered access to
coverage data

in turn used by the 4
-
D Wx Data
Cube to store grid
ded geospatial data. For the purposes of this document, gridded and
coverage

data types
may be considered synonymous.

The primary means of data retrieval for the W
C
S is through a flexible filtering mechanism built in a
standards
-
based, on
-
the
-
wire form.



2

P
urpose

The OCG Web
Coverage

Service
1.1

spec
is

an international standard for geospatial data storage and
retrieval.
This service has
been implemented by the NNEW program for use in the 4
-
D Wx Data Cube.
NNEW’s
requirements for the dissemination of aviatio
n weather data have
, however, required a series of
extensions to the core WCS 1.1 interface. This document provides an overview of the extensions

and
specializations

made by the NNEW program to the
OGC
WCS 1.1 specification.


Hereafter, specific terminolog
y is used relating to the term “W
C
S”:


WCS



The OGC/ISO Web Coverage Service Specification draft 1.1. This is a general
-
purpose
geospatial data access specification, and includes no weather
-
specific elements.


WCS
-
Wx



The extended W
C
S specification as im
plemented and specialized for the 4
-
D Wx Data
Cube. This is the set of standards (including 4
-
D Wx Data Cube
-
specific specializations) that are
used throughout the 4
-
D Wx Data Cube. Note that this term may be used to reference all
implementations of the
WC
S
-
Wx

specification.


WCSRI
-

A
WCS
-
Wx

reference implementation. This is an open source,
WCS
-
Wx

compliant
implementation developed primarily in Java by the FAA for use in the 4
-
D Wx Data Cube. It is
the default implementation used within the 4
-
D Wx Data Cub
e for gridded data exchange.



3

4
-
D Wx Data Cube WCS 1.1 Extensions

Extensions to the OGC Web Coverage Service 1.1 specification are shown below. Note that

the extension
descriptions below should not be considered final. It is anticipated that implementation

of the WCSRI
and data consumer libraries
will affect these extensions

based on security and performance impacts
.


T
hese des
criptions
should
currently
be considered

informative

rather than normative.


Figure
1

-

Overview of WCS
-
Wx

Components

3.1

SOAP

The WCS uses a SOAP binding, rather than a Key
-
Value
-
Pair (KVP)
or Plain
-
Old XML (POX)
binding.
OGC services
are often used with

a KVP binding, but
SOAP
is necessary
to
support
securit
y, policy, and
other enterprise
-
class
features.


Note
:
it is hoped that REST bindings develop to a sufficient level of
maturity

and standardization that
they
may

b
e supported in future versions.
REST bindings

are

not
sufficiently developed
, either in OGC
or more broadly in the REST communit
y, to support an
enterprise class

solution.



3.2

NetCDF 4/CF Output Format Support

A
WCS
-
Wx

must return

data in NetCDF version 4 that follows the Climate and Forecast (CF) version 1.3
convention. Data consumers may request NetCDF 4 formatted data by asking for an output format

of
“application/netcdf4”.

3.3

GRIB2 Output Format Support

GRIB 2 is a commonly used
weather
gridded file format defined by the WMO.
Work is underway to
identify whether GRIB 2 offers significant compactness advantages over NetCDF 4, and therefore
whether GR
IB 2 support is required for
WCS
-
Wx
s. If this analysis concludes that GRIB 2 is necessary
for the 4
-
D Wx Data Cube, the functionality described following paragraphs of this section will be
required for
WCS
-
Wx
s.



A
WCS
-
Wx

must return data in GRIB version

2 format. Data consumers may request GRIB 2 formatted
data by asking for an output format of “application/grib2”.

WCS
-
Wx
s shall fully support retrieval of one or more streamed GRIB 2 response files to satisfy ad
-
hoc
data requests. Therefore,
WCS
-
Wx
s mus
t be capable of creating GRIB 2 files based on filtering its data
(files in the backing store, for example).

3.4

SOAP with Attachments (SWA)

To
support

the request/response pattern
to return

data
using SOAP, data must be wrapped in SOAP
headers. To support SO
AP
-
based responses, data (such as NetCDF 4 response files)
is
provided as a
SOAP attachment (SWA).


3.5

Trajector
y

Support

To support many aviation use cases, it is often useful to be able to retrieve weather data relative to a
trajectory. In many cases this
trajectory represents the flight trajectory of an aircraft. In this section, the
term “trajectory” is used as a general term to refer to a number of concepts:



Cross section
s


A grid representing a vertical cross section of data along a trajectory. Cross

sections typically represent a single data time



3
-
D trajectories


A grid representing data within a fixed distance of a trajectory



4
-
D trajectories


A grid representing data within a fixed distance of a trajectory

over time

The WCS specification allows
for data consumers to specify the desired Coordinate Reference System.
WCS
-
Wx
s shall support a trajectory CRS

for this purpose that allows data consumers to retrieve data
along a trajectory

via the GetCoverage operation
.



3.6

Publish/Subscribe Support

The OGC
WCS specification only specifies a request/reply approach to data exchange. For continuous
data streams, the WCS specification has been extended to support the publish/subscribe model.
W
hen
data consumers contact
a

WCS
-
Wx

for
data, they pass filtering in
formation as part of a GetCoverage
request. This same filtering information may also be used as a parameter when
making

a subscription.

The OGC PubSub Standards Working Group (SWG) will provide standardized mechanisms for the
publish/subscribe model. As
this SWG completes its work, further detail will be added to this document
on making use of this specification in a WCS.

The WCSRI currently implements a non
-
standard
mechanism for delivering notifications, in contrast to the WFSRI which currently impleme
nts a similar
but non
-
standard approach for pushing data contents

themselves
.

3.7

Model Run Time
/Valid Time Support

The meteorological and oceanographic communities frequently work with data generated by numerical
model runs. In many cases different runs
of t
he same model
will generate two different forecasts for the
same valid time. Therefore, a request to a WCS for a particular valid time can have more than one
matching data time.
WCS
-
Wx
s support mechanisms to uniquely identify and request data with a
vali
d/
model run time

time pair.

The WCS specification has generic mechanisms to deal with dimensions
and axes, but lacks a domain
-
specific mechanism to describe and request these times.


3.8

Units of Measure

The WCS specification implicitly deals with units of me
asure as a portion of CRS support, but in the
weather domain there are additional requirements. As
stated in

the WCSRI requirements document,
WCS
-
Wx
s are expected to support conversions among different altitude units (flight levels, feet above
ground leve
l, meters above mean sea level, pressure, etc.)

As the technical details are developed, they
will be documented in this section.

3.9


GetCoverage Callbacks (store=true)

The WCS specification allows for WCS server implementations to return a URL
to a filtered
data file
(instead of the data files themselves)
for data clients. Therefore WCS clients may not be returned an
actual data response from a GetCoverage request, but instead a
download
URL.
WCS
-
Wx
s
must
implement direct data responses as described in Sect
ion
0
, and
may
optionally
implement
the store=true
callback mechanism as well
.

3.10


GetMetadata operation and
ISO 19139 Metadata

The retrieval of metadata in the WCS is split between a GetCapabilities operation and a
DescribeCove
rage operation. GetCapabilities returns “service” metadata, while DescribeCoverage
returns “coverage” metadata. As defined in the 4
-
D Wx Data Cube Metadata Guidelines, metadata is
conveniently dealt with as a single large group rather than as two distinc
t bodies of metadata. To match
this model, and to ensure consistency with the 4
-
D Wx Data Cube Registry/Repository,
WCS
-
Wx
s shall
support an additional GetMetadata operation that returns filtered ISO 19139 metadata following the 4
-
D
Wx Data Cube Metadata
Guidelines
.

This operation is a direct extension of the WCS.



3.11

Request Reconstruction

In the operational aviation weather domain, it can be necessary to reconstruct the data that was returned to
a data consumer at a particular point in time. This is partic
ularly useful in accident reconstruction.
Therefore,
WCS
-
Wx
s shall support a mechanism to return the data contents that were returned to a
particular data consumer at a particular time, within the time bounds over which the
WCS
-
Wx

is
configured to
keep re
quest

history.

The specifics of this mechanism have not yet been defined.



4

Examples

4.1

GetCapabilities Examples

Example
1:

The following XML shows an example of
a GetCapabilities request against a
WCS
-
Wx
:

<?xml version="1.0" encoding
="UTF
-
8"?>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap
-
envelope" xmlns:ns="http://www.opengis.net/wcs/1.1"
xmlns:ns1="http://www.opengis.net/ows/1.1">


<soap:Header/>


<soap:Body>


<ns:GetCapabilities service="WCS">


<!
--
Opti
onal:
--
>


<ns1:AcceptVersions>


<!
--
1 or more repetitions:
--
>


<ns1:Version>1.1.2</ns1:Version>


</ns1:AcceptVersions>


</ns:GetCapabilities>


</soap:Body>

</soap:Envelope>

4.2

DescribeCoverage Examples

Example
2:

The following XML shows an example of
a DescribeCoverage request against a RUC
temperature coverage
:

<?xml version="1.0" encoding="UTF
-
8"?>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap
-
envelope" xmlns:ns="http://www.ope
ngis.net/wcs/1.1">


<soap:Header/>


<soap:Body>


<ns:DescribeCoverage service="WCS" version="1.1.2">


<!
--
1 or more repetitions:
--
>


<ns:Identifier>urn:fdc:ncar.ucar.edu:Dataset:RUC20
-
GRB</ns:Identifier>


</ns:DescribeCoverage
>


</soap:Body>

</soap:Envelope>

4.3

GetCoverage Examples

Example
3:

The following XML shows an example of
a GetCoverage request

for a single time
and spatial
subset
against a coverage with x, y, z, and time axes (RUC

temperature
)
:

<
?xml version="1.0" encoding="UTF
-
8"?>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap
-
envelope" xmlns:ns="http://www.opengis.net/wcs/1.1"
xmlns:ns1="http://www.opengis.net/ows/1.1"

xmlns:gml="http://www.opengis.net/gml">


<soap:Header/>


<soa
p:Body>


<ns:GetCoverage service="WCS" version="1.1.2">


<
!

-

The coverage identifier
--
>


<ns1:Identifier>urn:fdc:ncar.ucar.edu:Dataset:RUC20
-
GRB</ns1:Identifier>


<ns:DomainSubset>


<
!

-

Three spatial dimensions
--
>


<ns1:BoundingBox crs="urn:ogc:def:crs:OGC:2:84" dimensions="3">


<ns1:LowerCorner>
-
120.0 38.6 3.893606</ns1:LowerCorner>


<ns1:UpperCorner>
-
106.6 42.5 3.893606</ns1:UpperCorner>


</ns1:BoundingBox>



<ns:TemporalSubset>


<!
--
You have a CHOICE of the next 2 items at this level
--
>


<ns:TimePeriod>


<ns:BeginPosition>2009
-
06
-
17T21:00:00.000Z</ns:BeginPosition>


<ns:EndPosition>2009
-
06
-
17
T21:00:00.000Z</ns:EndPosition>


<!
--
Optional:
--
>


<!
--
ns:TimeResolution>?</ns:TimeResolution
--
>


</ns:TimePeriod>


</ns:TemporalSubset>


</ns:DomainSubset>


<ns:Output format="appl
ication/netcdf4" store="false"></ns:Output>


</ns:GetCoverage>


</soap:Body>

</soap:Envelope>



Example
4:

The following XML shows an example of
a GetCoverage request for a
time series

of two
times

(
and spatial subset
)

against

a coverage with x, y, z, and time axes (RUC temperature)
:

<?xml version="1.0" encoding="UTF
-
8"?>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap
-
envelope" xmlns:ns="http://www.opengis.net/wcs/1.1"
xmlns:ns1="http://www.opengis.net/ows/1.1"

xmlns
:gml="http://www.opengis.net/gml">


<soap:Header/>


<soap:Body>


<ns:GetCoverage service="WCS" version="1.1.2">


<
!

-

The coverage identifier
--
>


<ns1:Identifier>urn:fdc:ncar.ucar.edu:Dataset:RUC20
-
GRB</ns1:Identifier>


<n
s:DomainSubset>


<
!

-

Three spatial dimensions
--
>


<ns1:BoundingBox crs="urn:ogc:def:crs:OGC:2:84" dimensions="3">


<ns1:LowerCorner>
-
120.0 38.6 3.893606</ns1:LowerCorner>


<ns1:UpperCorner>
-
106.6 42.5 3.8
93606</ns1:UpperCorner>


</ns1:BoundingBox>


<ns:TemporalSubset>


<!
--
You have a CHOICE of the next 2 items at this level
--
>


<ns:TimePeriod>


<ns:BeginPosition>2009
-
06
-
17T2
0
:00:00.000Z</ns
:BeginPosition>


<ns:EndPosition>2009
-
06
-
17T2
3
:00:00.000Z</ns:EndPosition>


<!
--
Optional:
--
>


<!
--
ns:TimeR
esolution>?</ns:TimeResolution
>


</ns:TimePeriod>


</ns:TemporalSubset>



</ns:DomainSubset>


<ns:Output format="application/netcdf4" store="false"></ns:Output>


</ns:GetCoverage>


</soap:Body>

</soap:Envelope>



4.4

GetCoverage Corridor/Trajectory Examples

Example
5:
The following XML sho
ws an example of
a simple GetCoverage corridor request against a
coverage with x, y, z, and time axes (RUC temperature) with two 4
-
D waypoints
:

<?xml version="1.0" encoding="UTF
-
8"?>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap
-
envelope" xmlns
:ns="http://www.opengis.net/wcs/1.1"
xmlns:ns1="http://www.opengis.net/ows/1.1"

xmlns:gml="http://www.opengis.net/gml">


<soap:Header/>


<soap:Body>


<ns:GetCoverage service="WCS" version="1.1.2">


<ns1:Identifier>urn:fdc:ncar.ucar.edu:Dat
aset:RUC20
-
GRB</ns1:Identifier>


<ns:DomainSubset>


<ns1:BoundingBox crs="temporaryCorridorCRS" dimensions="4">


<ns1:LowerCorner>0
-
5.0
-
0.5 0</ns1:LowerCorner>


<ns1:UpperCorner>499 5.0 0.5 499</ns1:UpperCor
ner>


</ns1:BoundingBox>


<!
--
Optional:
--
>


<ns:TemporalSubset>


<!
--
You have a CHOICE of the next 2 items at this level
--
>


<gml:timePosition>2009
-
06
-
17T13:00:00.000Z</gml:timePosition>



</ns:TemporalSubset>


</ns:DomainSubset>


<!
--
Optional:
--
>


<ns:RangeSubset>


<!
--
1 or more repetitions:
--
>


<ns:FieldSubset>


<ns1:Identifier
>Temperature</ns1:Identifier>


</ns:Fie
ldSubset>


</ns:RangeSubset>


<ns:Output format="application/netcdf4" store="false">


<!
--
Optional:
--
>


<ns:GridCRS gml:id="iDontKnow">


<!
--
Optional:
--
>


<gml:srsName>temporaryCorridorCRS</
gml:srsName>


<ns:GridBaseCRS>urn:ncar:def:crs:NCAR_Corridor_CRS:500:39.863:
-
104.684:1.609:1245380400000:40.795:
-
111.98:1.288:1245380400000</ns:GridBaseCRS>


<!
--
Optional:
--
>


<ns:GridType>urn:ogc:def:method:WCS:1.
1:2dSimpleGrid</ns:GridType>


<!
--
Optional:
--
>


<ns:GridOrigin>0 0 0 0</ns:GridOrigin>


<ns:GridOffsets>1 0 0 0 0 0.1 0 0 0 0 0.05 0 0 0 0 1</ns:GridOffsets>


<!
--
Optional:
--
>


<ns:GridC
S>urn:ogc:def:cs:OGC:0.0:Grid2dSquareCS</ns:GridCS>


</ns:GridCRS>


</ns:Output>


</ns:GetCoverage>



<!
--

Picture of this test case
-

TIME



Data valid times: 6/17 13:00



Eternity <=====x====> Eternity


Data applicable ranges: Eternity Eternity



Corridor x (2 waypts at 2009
-
06
-
19T03:00:00.000Z


--
>



<!
--

Picture of this test ca
se
-

ALTITUDE (horiz though)


Data altitudes Corridor



10000 pa ____________________________________________


|


|


|


|


|


|


|


| 2.
109
-


| 1.609 x
-

1.788


| x 1.288


| 1.109
-

-

0.788


|


|


|


|


1000000 pa


--
>



</so
ap:Body>



</soap:Envelope>


Example
6:
The following XML shows an example of
a simple GetCoverage corridor request against a
coverage with x, y, and time axes (National Ceiling and Visibility


Ceiling field)
:

<?xml version="1.0" enc
oding="UTF
-
8"?>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap
-
envelope" xmlns:ns1="http://www.opengis.net/ows/1.1"
xmlns:ns2="http://www.opengis.net/wcs/1.1">


<soap:Header/>


<soap:Body>

<ns2:GetCoverage xmlns:ns1="http://www.opengis.net/ows
/1.1" xmlns:ns2="http://www.opengis.net/wcs/1.1"
xmlns:ns3="http://www.w3.org/1999/xlink" xmlns:ns4="http://www.opengis.net/gml"
xmlns:ns6="http://www.w3.org/2001/SMIL20/" xmlns:ns7="http://www.w3.org/2001/SMIL20/Language" version="1.1.2"
service="WCS">



<ns1:Identifier>urn:fdc:ncar.ucar.edu:Dataset:CEIL</ns1:Identifier>


<ns2:DomainSubset>


<ns1:BoundingBox dimensions="4" crs="temporaryCorridorCRS">


<ns1:LowerCorner>0.0
-
10.0
-
2.0 0.0</ns1:LowerCorner>


<ns1:UpperCorner>199.0

10.0 2.0 199.0</ns1:UpperCorner>


</ns1:BoundingBox>


<ns2:TemporalSubset>


<ns2:TimePeriod>


<ns2:BeginPosition>2009
-
07
-
22T02:00:00.000Z</ns2:BeginPosition>


<ns2:EndPosition>2009
-
07
-
22T03:20:00.000Z</ns2
:EndPosition>


<ns2:TimeResolution>PT10M</ns2:TimeResolution>


</ns2:TimePeriod>


</ns2:TemporalSubset>


</ns2:DomainSubset>


<ns2:RangeSubset>


<ns2:FieldSubset>


<ns1:Identifier>Geometric_height</ns1:Iden
tifier>


</ns2:FieldSubset>


</ns2:RangeSubset>


<ns2:Output store="false" format="application/netcdf4">


<ns2:GridCRS>


<ns4:srsName>temporaryCorridorCRS</ns4:srsName>


<ns2:GridBaseCRS>urn:ncar:def:crs:NCAR_Corridor_CR
S:200:39.832:
-
104.657:0:1248228000000:39.934:
-
105.133:3.048:1248228600000:40.125:
-
106.403:3.048:1248229200000:40.263:
-
107.389:3.048:1248229800000:40.322:
-
107.835:3.048:1248230400000:40.521:
-
109.443:3.048:1248231000000:40.583:
-
109.985:3.048:1248231600000:40
.778:
-
111.969:0.2:1248232200000</ns2:GridBaseCRS>


<ns2:GridType>urn:ogc:def:method:WCS:1.1:2dSimpleGrid</ns2:GridType>


<ns2:GridOrigin>0.0 0.0 0.0 0.0</ns2:GridOrigin>


<ns2:GridOffsets>1.0 0.0 0.0 0.0 0.0 0.2 0.0 0.0 0.0 0.
0 0.1 0.0 0.0 0.0 0.0 1.0</ns2:GridOffsets>


<ns2:GridCS>urn:ogc:def:cs:OGC:0.0:Grid2dSquareCS</ns2:GridCS>


</ns2:GridCRS>


</ns2:Output>


</ns2:GetCoverage>


</soap:Body>

</soap:Envelope>




APPENDIX
A

-

Acronyms


API


application progr
amming interface

CITE


Compliance & Interoperability Testing & Evaluation

CONOPS

Concept of Operations

CF


Climate and Forecast

CRS


coordinate reference system

DOD


Department of Defense

ESB


Enterprise Service Bus

FAA


Federal Aviation Administration

FTI


Federal Telecommunications Infrastructure

FUSE


File System in Userspace

GSD


Global Systems Division

HTTP


Hypertext Transfer Protocol

IOC


Initial Operating Capability

ISO


International Organization for Standardization

IT


information technology

JMBL


Joint METOC Broker Language

JPDO


Joint Program Development Office

METOC

Meteorological and Oceanographic Data

MIME


Multipurpose Internet Mail Extensions

MIT


Massachusetts Institute of Technology

NAS


National Airspace System

NextGen

Next Generation Air

Transportation System

NCAR


National Center for Atmospheric Research

NNEW


NextGen Network Enabled Weather

NOAA


National Oceanic and Atmospheric Administration

OGC


Open GeoSpatial Consortium

OPeNDAP

Network Data Access Protocol

POX


plain
-
old
-
XML

RAL


R
esearch Applications Laboratory

RegRep


Registry and Repository

RUC


Rapid Update Cycle

SAS


Single Authoritative Source

SOAP


Simple Object Access Protocol

SWIM


System Wide Information Management

TAF


Terminal Aerodrome Forecasts

UOM


Unit(s) of measure

URI


Uniform Resource Identifiers

URL


Uniform Resource Locators

URN


Uniform Resource Names

WCS


Web Coverage Service



WCPS


Web Coverage Processing Service

WCSRI


Web Coverage Service Reference Implementation

WGS84


World Geodetic System 1984

XML


Extensi
ble Markup Language



APPENDIX
B



Definitions and Terms


4
-
Dimentional Weather Data Cube



A
virtual
entity comprised of a federation of distributed weather
data sources, which provides a common source of weather information to all users of the NAS.

Coverag
e



A conceptual dataset representing a single gridded data product, which may be composed of
several different data files and fields, and may pertain to a general time range. A dataset.

Dataset



May be composed of several files or a time series of data,
that comprise a single logical
product. Examples include RUC, Icing/CIP, GOES satellite imagery, etc. This is equivalent to the ISO
19115 “Dataset series” terminology.

Initial Operating Capability



The 4
-
D

Wx

Data

Cube Initial Operating Capability. This
includes an
initial (not CONUS
-
wide) operational demonstration of capability. Subsequently a full CONUS
-
wide
deployment will take place.

Offered Coverage



A high level dataset/coverage offered by a particular WCSRI installation.

Open Geospatial Consortium



A standards organization that is leading the development of standards
for geospatial and location based services.

Registry/Repository



The registry/repository reference implementation for the 4
-
D

Wx

Data

Cube.

Service Provider



An entity (a person or
organization) that hosts an installation of the WCSRI, and is
the original provider of zero or more datasets.

United States National Airspace System



The national aviation system of the United States of
America. It is a large operational system, and as
such includes strict operational requirements relating to
security, quality of service, and related critical infrastructure.

Web
Coverage

Service



A service standard developed by the Open Geospatial Consortium that
encompasses a standard protocol for acce
ssing
coverage
-
based (typically gridded) data.



APPENDIX
C

-

R
eferences





[
i
] Open Geospatial Consortium,
“Web Coverage Service”
, http://opengeospatial.org/standards/wcs/