• Tidak ada hasil yang ditemukan

Change Requests | OGC

N/A
N/A
Protected

Academic year: 2017

Membagikan "Change Requests | OGC"

Copied!
3
0
0

Teks penuh

(1)

All Fields marked with

*

are mandatory.

Change Request

#:

120

Assigned OGC

Document #:

10-197

Name:

*

Raj Singh

Organization:

*

OGC

Email:

*

[email protected]

Document

Name/Version:

*

Web Processing Service / 1.0.0

OGC Project

Document:

*

05-007r7

If this is a revision of a previous submission and you have a Change Request Number, then check here:

Enter the CR number here:

Enter the Revsion Number that you are revising here:

Title:

*

Axis order of input services to WPS

Source:

*

NGA, OWS-7 FDF thread

Work item code:

Category:

*

(2)

Reason for

change:

*

clarity, tighter specification

Summary of

change:

*

Is there anything we should/could look at adding to WPS to

check/correct axis order of input services before trying to execute a process?

Consequences if

not approved:

Many processes will return incorrect results if they treat axis order incorrectly. Right now, vendors are trying to figure axis order out on their own in-process.

Clauses affected:

*

No clauses currently discuss this.

Additional

Documents

affected:

Supporting

Documentation:

Comments:

Status:

Assigned To:

Disposition:

(3)

3 of

Referensi

Dokumen terkait

These difficulties typically require local edits to approved XML Schema Documents, stored at http://schemas.opengis.net/ , when two or more used together reference two or more

In addition, service requests and responses now allow additional parameters via extension elements (see SWE Service Model specification, work in progress and foreseen to be ready at

This conformance class is an extension of the Core conformance class, supporting registration of quality conformanceadditional metadata elements. Test case

This principle extends the CityGML topological structure for LandUse (page 94 of CityGML specifications) to other classes at surface level which as per this proposal would be

a) GetCapabilities (mandatory) – This operation allows a client to request and receive service metadata (or Capabilities) documents that describe the abilities of the specific

Summary of change:  Edit NOTE 2 following Table 3 to be clearer about the meaning of “Character String Type, not empty”. Consequences if

Comments/justifications for changes: A new conceptual model and encoding for temporal concepts is developed as part of SWE Common instead of importing ISO 19108.. The reasons for

Section 11.3 contains an excerpt of the schema definition of InlineFeature.. Additional Documents affected: