GML CR Compact Encoding of Circle, Arc, Rectangle, Triangle

(1)

Open Geospatial Consortium

OGC Doc 08-138

CR-Form-v3

CHANGE REQUEST



_{GML CR ?}

_08-138

 rev -  Current version: 3.2.1 

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:  GML CR Compact Encoding for Circle, Arc, Rectangle, Triangle

Source:  GMLJP2 V1.1 SWG

Work item code:  Date:  2008-08-27

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:  Conclusions from OGC Land Information Initiative project—GML geometry encodings are too verbose

Summary of change:  Create compact GML implementation of Geometry objects corresponsing to Circle, Arc, Rectangle, Triangle similar to compact encoding of LineString vs Curve/segments/LineStringSegment encoding.

Consequences if 

not approved: Excessive verbosity of GML, some LandGML features were _{20x larger than corresponding LandXML features.}

Clauses affected:  Additional subclauses of 10.4 and additional schema definitions in geometryPrimitives.xsd

Other specs  Other core specifications 

Affected: Abstract specifications

(2)

07-092r1 Change Request: Add URN values for URN definitions OGC Doc 08-039

The CircleGeometry is equivalent to the following GML Curve:

</segments> </Curve>

Similarly compact encodings for Arc, Rectangle, and Triangle should be created.

Last Revision Date: 2 December 2017