ST_LocateBetweenElevations failing on typed collections

[komzpa]

I observe the following inconsistency:

[local] gis@gis=# select ST_AsText(ST_LocateBetweenElevations('MULTILINESTRING Z((0 0 0, 10 10 10))'::geometry, 11, 11));
ERROR:  XX000: lwgeom_clip_to_ordinate_range clipping routine returned NULL
LOCATION:  pg_error, lwgeom_pg.c:164
Time: 0,408 ms
[local] gis@gis=# select ST_AsText(ST_LocateBetweenElevations('LINESTRING Z(0 0 0, 10 10 10)'::geometry, 11, 11));
┌─────────────────────────┐
│        st_astext        │
├─────────────────────────┤
│ MULTILINESTRING Z EMPTY │
└─────────────────────────┘
(1 row)

Time: 0,393 ms

[zarthur]

Hello,

I send pull request ​https://github.com/postgis/postgis/pull/112. After this fix the query give the following result:

=> SELECT ST_AsText(ST_LocateBetweenElevations('MULTILINESTRING Z((0 0 0, 10 10 10))'::geometry, 11, 11));
        st_astext        
-------------------------
 MULTILINESTRING Z EMPTY
(1 row)

I suppose ST_LocateBetweenElevations() becomes consistent after it. After viewing code I don't see any drawbacks.

[strk]

Could you please also add a testcase in regress_lrs{.sql,expected} ? You can reference this ticket by number in the test description (first value returned by query) see examples in tickets.sql

[strk]

In 15036:

Fix inconsistency with multilinestring in ST_LocateBetweenElevations()

Fixes #3607.
Includes testcase.

Patch by Artur Zakirov <a.zakirov@…>

[zarthur]

Ofcourse. I fixed tests.

[strk]

In 15037:

Fix inconsistency with multilinestring in ST_LocateBetweenElevations()

Closes #3607
Includes testcase

Patch by Artur Zakirov <a.zakirov@…>

[strk]

For the record: commit for trunk is r15035 r15036 is for 2.2 branch and r15035 for 2.1 branch