• Tidak ada hasil yang ditemukan

Change Requests | OGC

N/A
N/A
Protected

Academic year: 2017

Membagikan "Change Requests | OGC"

Copied!
2
0
0

Teks penuh

(1)

All Fields marked with

*

are mandatory.

Change Request

#:

113

Assigned OGC

Document #:

10-162

Name:

*

Panagiotis (Peter) A. Vretanos

Organization:

*

CubeWerx Inc.

Email:

*

[email protected]

Document

Name/Version:

*

CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW / 1.0.1

OGC Project

Document:

*

07-110r4

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:

*

Define a "where" slot.

Source:

*

Panagiotis (Peter) A. Vretanos

Work item code:

Category:

*

B (Addition of feature)

Reason for

change:

*

(2)

Summary of

change:

*

1) Define a standard geometry-valued slot named "where" that may be used to characterize the geographic extent of a registry object.

2) A "where" slot shall contain a point, line, polygon or envelope value.

3) If a registry object has other geometry-valued slots it is recommended that the value of the "where" slot have some

relation to the value of one of those other slots (e.g. centroid, generalization, etc.)

Consequences if

not approved:

Makes it very difficult for CSW-ebRIM clients to formulate spatial predicates with operators other than BBOX.

Clauses affected:

*

7.8

Additional

Documents

affected:

Supporting

Documentation:

Comments:

Additional changes that might be considered with this change proposal is to define additional discovery methods (e.g. extension to GetDomain or define a stored query) that returns a list of slot/slotTypes.

Status:

Assigned

Assigned To:

ebRIM AP of CSW

Referensi

Dokumen terkait

a) GetCapabilities – This request allows a client to retrieve a resource that describes the essential capabilities and non-computational characteristics of the service.

a) Test Purpose: Verify that a basic CSW server interface satisfies all requirements of the GetDomain operation. b) Test Method: Make several GetDomain requests using a variety

Reason for change:  Three standard elements or attributes are available to hold object identifiers in GML applications: @gml:id, gml:name and gml:identifier.. There is need for

There is an overlap between some themes in CityGML and the data themes identified by Inspire annexes, such as transportation networks, land use, terrain models or buildings.

XML representation of spatial observation data requires that it satisfies the core requirements class for observation data, and adds the requirement that the observation shall

While this could just be handled internally within the implementation, there is a question as to whether allowable roles should be disclosed in the Capabilities. Consequences if

In clause 7.1.2 Spatial reference system information, either add a uri column to the spatial_ref_sys table definition, or add text noting that a URI/URN spatial reference

Interestingly the gml:Grid object is defined to support both: It allows for a single gml:axisLabels element which is of type gml:NCNameList but also for an unlimited number