I think the example of the Polygon domain type is wrong. It has the same dimensionality as the MultiPolygon. I think we need to reduce the dimensionality of the array by one, to make it consistent with a GeoJSON Polygon.
It looks like this:
{
"type": "Domain",
"domainType": "Polygon",
"axes": {
"composite": {
"dataType": "polygon",
"coordinates": ["x","y"],
"values": [
[ [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ] ]
]
},
"z": { "values": [2] },
"t": { "values": ["2008-01-01T04:00:00Z"] }
},
"referencing": [...]
}
I think it should look like this:
{
"type": "Domain",
"domainType": "Polygon",
"axes": {
"composite": {
"dataType": "polygon",
"coordinates": ["x","y"],
"values": [
[ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ]
]
},
"z": { "values": [2] },
"t": { "values": ["2008-01-01T04:00:00Z"] }
},
"referencing": [...]
}
(A Polygon is an array of LinearRings, each of which is an array of coordinate value pairs.)
The Playground does not seem to support Polygons anyway. But the schema will probably need correcting.
I think the example of the Polygon domain type is wrong. It has the same dimensionality as the MultiPolygon. I think we need to reduce the dimensionality of the array by one, to make it consistent with a GeoJSON Polygon.
It looks like this:
I think it should look like this:
(A Polygon is an array of LinearRings, each of which is an array of coordinate value pairs.)
The Playground does not seem to support Polygons anyway. But the schema will probably need correcting.