• Tidak ada hasil yang ditemukan

WFS FES Default srsName for geometries in GetFeature response

N/A
N/A
Protected

Academic year: 2017

Membagikan "WFS FES Default srsName for geometries in GetFeature response"

Copied!
2
0
0

Teks penuh

(1)

All Fields marked with

*

are mandatory.

Name:

*

Clemens Portele

Organization:

*

interactive instruments

Email:

*

[email protected]

Document

Name/Version:

*

Web Feature Service 2.0 Interface Standard (also ISO 19142) / 2.0

OGC Project

Document:

*

09-025r1

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:

*

[WFS/FES SWG] Default srsName for geometries in GetFeature response

Source:

*

interactive instruments, OGC CITE tests

Work item code:

Category:

*

F (Critical correction)

Reason for

change:

*

It has been and is current practice that the srsName on the envelope of a feature collection is the default CRS of the geometries in a feature collection (e.g. the GetFeature response). This behaviour is normal GML behaviour, if the feature collection is a GML feature, but with WFS 2.0 this is no longer the case.

The CITE team insisted that the srsName in the gml:Envelope of the GetFeature response does not meet the criteria to be used as a default srsName for all feature geometries. Technically this reading is correct for the reason mentioned above and we need to explicitly clarify the intended mechanics in WFS 2.0.1.

Summary of

change:

*

Specify that a srsName on the envelope of a feature collection is the default srsName for all geometries in the feature collection

Consequences if

not approved:

Inconsistency with previous WFS versions and current practice as well as additional redundancy/overhead as srsName attributes must be attached to all geometries.

Clauses affected:

*

Include a statement similar to the one from GML 3.2.1, 9.10 in WFS 2.0.1, e.g. in a new sub-clause 11.3.6:

"For convenience in constructing feature collection instances, the value of the srsName attribute on the gml:Envelope which is the value of the gml:boundedBy property of a feature collection shall be

(2)

inherited by all directly expressed geometries in all properties of the members of the collection, unless overruled by the presence of a local srsName. Thus it is not necessary for a geometry to carry a srsName attribute, if it uses the same coordinate reference system as given on the gml:boundedBy property of the envelope. Inheritance of the coordinate reference system continues to any depth of nesting, but if overruled by a local srsName declaration, then the new coordinate reference system is inherited by all its children in turn."

Additional

Documents

affected:

Supporting

Documentation:

Comments:

See

https://portal.opengeospatial.org/?m=projects&a=view&project_id=85&tab=5&act=details&issue_id=862 for the related discussion in the CITE issues tracker.

Status:

Assigned

Assigned To:

WFS/FES SWG

Disposition:

Referred and Posted

Referensi

Dokumen terkait

A tatement like "If a spatial operator in a filter expression is testing a pair of geometries and one is null, the results should be FALSE (i.e. the two geometries

a) The service has indicated that it supports the Unit of measure conformance class as defined by the filter encoding specifications b) The properties of a feature type

Ease the restrictions in section 7.6.5.5 on page 26 and section 7.9.2.4.4 on page 35 and Table 11 on page 48 of OGC 09-025r1 (WFS 2.0.0) by permitting a service to encode

The WFS-G BP specifies that the top level container should be an iso19112:SI_Collection element but then gives an example that uses a wfs:FeatureCollection element. Summary

these examples gave origin to different interpretations and we now start see the usage of this nonexistent subtype parameter to express the notion of

It is proposed that the Filter specification should include a PropertyIsSemanticallyRelatedTo comparison operator that accepts a propertyname, resourceidentifier and zero or

In addition, GML data can be used, as described in this clause, for the encoding of coverage metadata, geographic features, annotations, annotation and feature styling, and supporting

Introduction 161 Constructing a proper attribute query syntax 162 Creating feature layers and table views 167 Selecting features and rows with the Select Layer by Attribute tool