[
https://issues.apache.org/jira/browse/SEDONA-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620436#comment-17620436
]
Martin Andersson commented on SEDONA-179:
-----------------------------------------
There are some conformance classes defined in "A.4.1 Types of conformance
classes". Hopefully Sedona can claim compliance with some, even without support
for M.
The different geometry types are a bit confusing to me. They are not supported
in Postgis and i can't see any tests for them in the test suite. They could be
interpreted as "logical" types for the type hierarchy. For instance: LinearRing
_is a_ Curve so it has a length like all curves. LinearRing _has a_ Surface and
hence an area like all surfaces.
Curves are not instantiable. From section 7.2.10.2:
{{CREATE TYPE ST_Curve}}
{{ UNDER ST_Geometry}}
{{ NOT INSTANTIABLE}}
{{ NOT FINAL}}
!image-2022-10-19-18-04-11-734.png!
> Claim Open Geospatial Consortium compliance
> -------------------------------------------
>
> Key: SEDONA-179
> URL: https://issues.apache.org/jira/browse/SEDONA-179
> Project: Apache Sedona
> Issue Type: Improvement
> Reporter: Martin Andersson
> Priority: Major
> Attachments: image-2022-10-19-18-04-11-734.png
>
>
> Sedona is mature enough now that it should be able to claim compliance with
> OGC sql standards. OGC has a test suite (see annex A-C in the linked
> document). If Sedona would implement those tests as unit tests and make them
> pass, Sedona should be able to claim compliance.
> Adding those tests would be a good way to catch defects and regressions.
> Claiming compliance would hopefully increase trust in Sedona and increase
> adoption.
> There is a license on the first page. I looks very liberal to me. But I don't
> speak legal. Would this have to be cleared be Apache legal first?
> https://www.ogc.org/standards/sfs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)