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()
21 lines
1.2 KiB
Plaintext
21 lines
1.2 KiB
Plaintext
0|GEOMETRYCOLLECTION EMPTY
|
|
1|LINESTRING(0 0,1 1,2 2)
|
|
2|LINESTRING(0 0,1 1,2 2,3 3)
|
|
3|MULTILINESTRING((0 0,1 1,2 2,3 3),(5 5,4 4,2 2))
|
|
4|POLYGON((0 0,10 0,10 10,0 10,0 0),(5 5,5 8,8 8,8 5,5 5))
|
|
5|MULTIPOLYGON(((0 0,10 0,10 10,0 10,0 0),(5 5,5 8,8 8,8 5,5 5)),((50 50,50 60,60 60,60 50,50 50),(55 55,55 58,58 58,58 55,55 55)))
|
|
6|MULTIPOINT((60 60),(60 50),(58 58),(58 55),(55 58),(55 55),(50 60),(50 50),(10 10),(10 0),(8 8),(8 5),(5 8),(5 5),(0 10),(0 0))
|
|
7|GEOMETRYCOLLECTION(MULTIPOLYGON(((50 50,50 60,60 60,60 50,50 50),(55 55,58 55,58 58,55 58,55 55)),((0 0,0 10,10 10,10 0,0 0),(5 5,8 5,8 8,5 8,5 5))),MULTIPOINT((60 60),(60 50),(58 58),(58 55),(55 58),(55 55),(50 60),(50 50),(10 10),(10 0),(8 8),(8 5),(5 8),(5 5),(0 10),(0 0)))
|
|
8|POINT(0 0)
|
|
9|CURVEPOLYGON ZM (CIRCULARSTRING ZM (-2 0 0 0,-1 -1 1 2,0 0 2 4,1 -1 3 6,2 0 4 8,0 2 2 4,-2 0 0 0),(-1 0 1 2,0 0.5 2 4,1 0 3 6,0 1 3 4,-1 0 1 2))
|
|
10|LINESTRING(0 0,0 0)
|
|
11|LINESTRING(0 0,0 0)
|
|
12|3
|
|
13|LINESTRING(0 0,2 0,4 0)
|
|
14|LINESTRING(10 0,10 10)
|
|
15|MULTIPOINT((0 0),(1 1),(2 2))
|
|
16|MULTIPOINT((0 0),(1 1),(2 2))
|
|
17|MULTIPOINT((0 0),(4 4))
|
|
18|POLYGON((-215922 5325694,-218693 5322119,-216112 5325812,-215922 5325694))
|
|
19|POLYGON((0 0,10 0,10 10,0 10,0 0))|BOX(0 0,10 10)
|