• 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.

Name:

*

Luc Van Linden Van Linden

Organization:

*

HL Consulting

Email:

*

[email protected]

Document

Name/Version:

*

Requirements and Space-Event Modeling for Indoor Navigation / 0.1.0

OGC Project

Document:

*

10-191r1

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:

*

elaboration on \

Source:

*

Luc Van Linden

Work item

code:

Category:

*

D (Editorial modification)

Reason for

change:

*

I apologise if this seems obvious, although I had some difficulties on understanding it directly. I believe this sentence might require more elaboration to help the reader understanding the example quicker.

Summary of

change:

*

\"now contains this information\". It seems to me that this

information is not contained by the dual graph itself, but represented by the dual graph. This means that \"this information\" (the

single step in the middle of the floor) can be derived/interpreted explicitly from the combination of the dual graph and the topographic space. In other words, the dual graph contains the information on what cell(s) is(are) connected to others and it is only when the

Inter-space connections are taken into account that \"this information\" can be derived.

(2)

To me it read as if the dual-graph contained this information implicitly.

Consequences if

not approved:

Clauses

affected:

*

page 32 line 6 = > \"The dual graph denoting cell adjacency within the subspace layer (see dotted edges between the nodes of the subspace) now contains the information.\"

Additional

Documents

affected:

Supporting

Documentation:

Comments:

Status:

Assigned

Assigned To:

3DIM WG

Referensi

Dokumen terkait

The descriptive information includes such information as the name of the operation, operation description, and number of source grid coverages required for the operation.

RapidEye's standard products (metadata) contain masks which mask not only clouds but as well other type of "unusable" data, e.g. missing lines, no

"A bounding rectangle, encoded as specified in OGC 06-131r3, indicating that all resources which intersect that BBOX shall be retrieved from some data

The GMLCOV schema has a definition for a type called "AbstractDiscreteCoverageType" which is not specified as abstract=true. Furthermore, this type is used unchanged as

where an attribute or role is intended to redefine one originally defined on a parent class, this should be indicated in the model using a tagged value "ownedBy" that

This is in particular true of the binary encodings, variable array size, local and reference frames and semantics concepts4. Summary of change:  Add clear examples and

"City wall" should be broadly defined to not only comprise ancient fortifications, but also smaller walls such as garden walls or fences.. As for CityGML 1.0, the

If a GetCoverage request contains a format parameter then this parameter shall contain a MIME type identifier occurring in some wcs:formatSupported element of the response to