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()
18 lines
835 B
Plaintext
18 lines
835 B
Plaintext
1|LINESTRING(0 0,0 51,50 20,30 20,7 32)
|
|
2|LINESTRING Z (0 0 3,0 51 1,50 20 6,30 20 9,7 32 10)
|
|
3|LINESTRING M (0 0 3,0 51 1,50 20 6,30 20 9,7 32 10)
|
|
4|LINESTRING ZM (0 0 3 2,0 51 1 6,50 20 6 7,30 20 9 9,7 32 10 5)
|
|
5|MULTIPOINT ZM ((0 0 3 2),(0 10 6 1),(0 51 1 6),(50 20 6 7),(30 20 9 9),(7 32 10 5))
|
|
6|MULTILINESTRING ZM ((0 0 3 2,0 51 1 6,50 20 6 7,7 32 10 5),(0 0 4 3,20 20 5 30))
|
|
7|POLYGON ZM ((0 0 3 2,0 51 1 6,50 20 6 7,7 32 10 5,0 0 3 2))
|
|
8|POLYGON ZM ((0 0 3 2,0 51 1 6,50 20 6 7,30 20 9 9,7 32 10 5,0 0 3 2),(1 1 4 3,1 3 2 3,18 18 5 30,1 1 4 3))
|
|
9|
|
|
10|LINESTRING(0 0,0 10)
|
|
11|MULTIPOLYGON(((100 100,100 130,130 130,130 100,100 100)))
|
|
12|MULTIPOLYGON(((100 100,100 130,130 130,130 100,100 100)))
|
|
13|
|
|
14|POLYGON((0 0,10 0,10 10,0 0))
|
|
15|POLYGON((0 0,10 0,10.5 10.5,0 10,0 0))|BOX(0 0,10.5 10.5)
|
|
16|TRIANGLE((0 0,0 9,9 0,0 0))
|
|
17|
|