Opened 3 months ago
Last modified 2 months ago
#5776 new defect
ST_LineSubstring 3D support
Reported by: | vla123 | Owned by: | pramsey |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.4.4 |
Component: | postgis | Version: | 3.4.x |
Keywords: | Cc: |
Description
It seems that ST_LineSubstring function return wrong results for 3D linestrings.
select st_3dlength(geometry) as full_line , st_3dlength(st_linesubstring(geometry, 0.0, 0.50)) as half_line from ( select st_makeline(ARRAY[ st_setsrid(st_pointz(0,0,0), 3857), st_setsrid(st_pointz(0,2,5), 3857), st_setsrid(st_pointz(0,10,10), 3857) ]) as geometry ) line Output : "full_line" "half_line" 14.819145939191106 8.92290773165573
This should be explicitly stated on documentation.
Change History (3)
comment:1 by , 3 months ago
Milestone: | PostGIS 3.4.3 → PostGIS 3.4.4 |
---|
comment:2 by , 2 months ago
comment:3 by , 2 months ago
Hm. Implication is the need for an ST_3DLineSubstring
because silently processing the 3D coordinates in ST_LineSubstring will have the same problem in reverse.
Note:
See TracTickets
for help on using tickets.
For those who want to split 3D LINESTRING, here is a plpgsql function :