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

OGC Doc 08-138

Open Geospatial Consortium

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

Title:

 GML CR Compact Encoding for Circle, Arc, Rectangle, Triangle


Source:

 GMLJP2 V1.1 SWG

Work item code: 
Category:

Other

Date:  2008-08-27

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

Excessive verbosity of GML, some LandGML features were
20x larger than corresponding LandXML features.

Consequences if
not approved:




Clauses affected:

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

Other specs



Affected:

Other core specifications



Abstract specifications
Best Practices Document

Supporting Doc.




Other comments:
Status
Disposition






Suggest the addition of 4 new compact encodings of geometry types
corresponding to a circle, arc, rectangle, and triangle. For example:

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


1 0
0 1
-1 0



The CircleGeometry is equivalent to the following GML Curve:



1 0
0 1
-1 0



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

Last Revision Date: 2 December 2017
Page

2