You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 8bbe8a1 version, "CompoundCurve", "MultiCompoundCurve", "CurvePolygon", "MultiCurvePolygon" use a "coordinates" member that holds an array of sub geometries. This is awkward. "geometries" would be a better naming, and consistent with "GeometryCollection" and "CurveGeometryCollection"
do we need Circle ? A 5 points closed Arc does the same job. No strong opinion though
MultiCompoundCurve could be renamed to MultiCurve for consistency with OGC/ISO specs. It could also potentially accept as items any one Arc, (Circle if kept), LineString and CompoundCurve, to be consistent with the OGC/ISO specs too.
MultiCurvePolygon could be renamed to MultiSurface for consistency with OGC/ISO specs. And it could accept both Polygon and CurvePolygon as items.
CurveGeometryCollection could be perhaps renamed to "GeneralizedGeometryCollection" ? and accept any classic GeoJSON geometry as well as extended ones of ogc-feat-geo-json
The text was updated successfully, but these errors were encountered:
The text was updated successfully, but these errors were encountered: