Opened 15 years ago
Closed 14 years ago
#283 closed defect (fixed)
Patch: ported linearref from JTS
| Reported by: | novalis | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | 3.2.0 |
| Component: | Default | Version: | main |
| Severity: | Unassigned | Keywords: | |
| Cc: |
Description
I have ported the linearref code from JTS to GEOS.
Attachments (1)
Change History (6)
by , 15 years ago
| Attachment: | linearref.patch added |
|---|
comment:2 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
FYI: the code applied contains memory errors and leaks. I'll spend some hours on that, but dunno if I've enough funding to complete it.
comment:3 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
alright, memory error is gone as of r2697. I'll close this and open a new one for the leaks.
comment:4 by , 14 years ago
| Priority: | major → blocker |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
GEOSInterpolate, like GEOSProject, segfaults. I fixed GEOSProject, but don't have time/funding to fix GEOSInterpolate.
When new code is added, it should come with unit testing. It would have been easy to catch such situations.
Also in this case the segfault is triggered by calling the function against a POINT, so the root cause might be the same (not checking that input is a LINESTRING)
comment:5 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Filed another ticket for the segfault: #353
patch to add linearref support