46e17651a8
Because this is what is mandated by the spec. As put in a code comment, we should in theory also do that for SFSQL since this is what SFA 1.2.1 BNF mandates, but it looks like SFSQL means "old way", so I didn't touch that. I see SFA 1.2.1 BNF is consistent with this old draft of the SQL/MM Part 3 spec (https://web.archive.org/web/20071212154300/http://jtc1sc32.org/doc/N1101-1150/32N1107-WD13249-3--spatial.pdf) I discovered this issue when realizing that GDAL rejected strings like 'MULTIPOINT Z (1 2 4,4 5 6)' that current PostGIS exports with ST_AsText()
13 lines
547 B
Plaintext
13 lines
547 B
Plaintext
1|POINT(0 0)
|
|
2|MULTIPOINT((0 0))
|
|
3|COMPOUNDCURVE((0 0,10 0))
|
|
4|MULTICURVE((0 0,10 0),(30 0,30 2))
|
|
5|CURVEPOLYGON((0 0,10 0,10 10,0 10,0 0))
|
|
6|MULTISURFACE(((0 0,10 0,10 10,0 10,0 0)))
|
|
7|GEOMETRYCOLLECTION(MULTIPOLYGON(((0 0,10 0,10 10,0 10,0 0))))
|
|
8|CIRCULARSTRING(0 0,10 1,20 0)
|
|
9|COMPOUNDCURVE(CIRCULARSTRING(0 0,10 1,20 0))
|
|
10|MULTICURVE(COMPOUNDCURVE(CIRCULARSTRING(0 0,10 1,20 0)))
|
|
11|CURVEPOLYGON(COMPOUNDCURVE(CIRCULARSTRING(0 0,10 1,20 0),(20 0,0 0)))
|
|
12|MULTISURFACE(CURVEPOLYGON(COMPOUNDCURVE(CIRCULARSTRING(0 0,10 1,20 0),(20 0,0 0))))
|