• Tidak ada hasil yang ditemukan

OWS Common Add nilValue Element Change Request

N/A
N/A
Protected

Academic year: 2017

Membagikan "OWS Common Add nilValue Element Change Request"

Copied!
5
0
0

Teks penuh

(1)

Open Geospatial Consortium

OGC Doc 08-012r2

CR-Form-v3

CHANGE REQUEST

OWS

Common 1.1.0

CR ?

 rev

2

 Current version: 1.2.0 

For

HELP

on using this form, see bottom of this page or look at the pop-up text over the symbols.

Proposed change affects:  AS Imp Spec X Best Practices Paper Other

Title:  OWS Common Change Request: Add nilValue Element

Source:  GMLJP2 V1.1 SWG

Work item code:Date:  2008-03-05

Category:B

Use one of the following categories:

F (Critical correction)

A (corresponds to a correction in an earlier release)

B (Addition of feature),

C (Functional modification of feature)

D (Editorial modification)

Detailed explanations of the above categories can be found in the TC Policies and Procedures.

Reason for change:  Consistency of nil value element definitions among OGC Implementation Specifications (in particular GMLJP2 V1.1 in progress and WCS 1.1)

Summary of change:  Add XML Schema definition of nilValue element to describe allowable nil/special values of coverage range parameters

Consequences if

not approved: Different OGC specifications will encode same information in different ways, reducing interoperability

Clauses affected:  Annex B, Clause 13

Other specsX Other core specifications  Modification of wcsDescribeCoverage.xsd which accompanies 06-083r8 Web Coverage Service (WCS) Implementation

Specification.

Affected: Abstract specifications Best Practices Document

Supporting Doc.

Other comments:  The requirement for the nilValue element arose from OGC 07-125r2, GMLJP2 V1.1 SWG Charter and subsequent decisions made in the GMLJP2 V1.1 SWG..

Status

(2)

GMLJP2 V1.1 SWG suggests adding the following text to clause 13

(Other Data Types)

Start of suggested text addition to Clause 13

---13.6 nilValue

13.6.1 Introduction

The intent of the nilValue element is to encode a value which represents a nil value (e.g. -251) or other missing information. The nil value should be encoded along with an accompanying reason (e.g. withheld) for the nil value, which is encoded in the optional nilReason attribute. The codeSpace attribute may also be used to encode authority for the nil value. If the codeSpace attribute is present, its value shall reference a dictionary, thesaurus, or authority for the nil value, such as the organization who assigned the value, or the dictionary from which it is taken.

13.6.2 XML Encoding

An example of the intended usage for the nilValue element in the context of a Coverage range parameter encoding is provided in the following instance fragment:

<gml:RectifiedGridCoverage> …

<gml:rangeParameters> <RangeParameter1>

<nilValue nilReason=”urn:ogc:def:nil:OGC:1.0:inapplicable”>-250</nillValue>

<nilValue nilReason=”urn:ogc:def:nil:OGC:1.0:withheld”>-251</nillValue>

<nilValue

nilReason=”urn:ogc:def:nil:OGC:1.0:instrument:LowInstSat”>-252</nillValue>

<nilValue

nilReason=”urn:ogc:def:nil:OGC:1.0:instrument:HighInstSat”>-253</nillValue>

<nilValue

nilReason=”urn:ogc:def:nil:OGC:1.0:instrument:LowReprSat”>-254</nillValue>

<nilValue

nilReason=”urn:ogc:def:nil:OGC:1.0:instrument:HighReprSat”>-255</nillValue>

<gml:rangeParameters> …

</gml:RectifiedGridCoverage>

Note that the nilReason values in the instance above are defined in OGC 08-039 (Change Proposal for 07-092r1)

An example of the intended usage of the nilValue element in the context of a WCS Coverage Description Field element is provided in the following instance fragment:

<CoverageDescription> ...

<Range> <Field>

<ows:Title>Sensor Wavelength</ows:Title>

(3)

<Identifier>Wavelength</Identifier> <Definition>

<owcs:AnyValue/> </Definition> <ows:nilValue

nilReason=”urn:ogc:def:nil:OGC::inapplicable”>0.0</ows:nilValue> ...

</CoverageDescription>

The schema definition for nilValue can be found in the schema file owsAdditions.xsd, which accompanies this document.

End of suggested text addition to Clause 13

---The GMLJP2 V1.1 SWG also suggests appending the following schema definitions to an appropriate OWS Common schema file (e.g. owsAdditions.xsd).

<!--============================================== ========== -->

<element name="nilValue" type="ows:NilValueType"/>

<!--============================================== ========== -->

<complexType name="NilValueType"> <annotation>

<documentation>The value used (e.g. -255) to represent a nil value with optional nilReason and codeSpace attributes.</documentation>

</annotation> <simpleContent>

<extension base="ows:CodeType">

<attribute name="nilReason" type="anyURI" use="optional"> <annotation>

<documentation>An anyURI value which refers to a resource that describes the reason for the nil value</documentation>

</annotation> </attribute> </extension> </simpleContent>

For backwards compatibility considerations with WCS 1.1, the GMLJP2 V1.1 SWG suggests that the WCS 1.2 SWG consider modifying the FieldType schema definition as follows (in bold) and add the global wcs:NullValue element which substitutes for the ows:nilValue in wcsDescribeCoverage.xsd:

<complexType name="FieldType"> <annotation>

<documentation>Description of an individual field in a coverage range record. </documentation>

</annotation> <complexContent>

<extension base="owcs:DescriptionType">

(4)

<sequence>

<element name="Definition" type="owcs:UnNamedDomainType"> <annotation>

<!-- ===== GMLJP2 V1.1 SWG Recommends Changing the Local Element Declaration of NullValue to ows:nilValue for harmonization with other OGC Specifications (GMLJP2 V1.1, GML V3.1-V3.2, 07-092r1) === -->

<element ref="ows:nilValue" minOccurs="0" maxOccurs="unbounded"/>

<element ref="owcs:InterpolationMethods"> <annotation>

<element name="Axis" type="wcs:AxisType" minOccurs="0" maxOccurs="unbounded"> </complexContent> </complexType>

(5)

<element name="NullValue" type="ows:NilValueType" substitutionGroup="ows:nilValue">

<annotation>

<documentation>Unordered list of the values used when valid Field values are not

available for whatever reason. The coverage encoding itself may specify a fixed

value for null (e.g. “–99999” or “N/A”), but often the choice is up to the provider

and must be communicated to the client outside the coverage itself. Each null value

shall be encoded as a string. The optional nilReason attribute can reference a

definition of the reason why this value is null.</documentation> </annotation>

</element>

Referensi

Dokumen terkait

CC_ConcatenatedOperation (instead of grid points) to specify the relationship between grid coverage positions and positions in another CRS, as suggested in Clause 8.10.1.1 of Topic

The Filter Encoding Implementation Specification (v1.1) defines the filterCapabilities.xsd schema that provides elements that advertise supported OGC filter components in a

To access the dependant parameters a server simply needs to extract the value of the fixed parameter, URL Decode the value, then parse the value using the

In the event that an OWS server encounters an error servicing an operation request, it shall return an exception report message as specified in Clause 8. The allowed exception

(The presented order of REQUEST and ACCEPT_VERSIONS in the GetCapabilities operation request is correct, since ACCEPT_VERSIONS is logically a parameter that is to

Summary of change:  Rename the element “sml:mathml” located in the algorithm definition of a process method to “sml:externalDefinition”. Consequences if

Other comments:  Of course, the Application Profiles which a server implements could be identified in a non-machine-readable manner in text within the Abstract element in the

The document named Edited OWS Common incorporating change request to Define URN to identify ServiceType.doc contains all of the edits to OWS Common 1.1. The modified XSD files are: