Opened 10 years ago
Closed 4 months ago
#682 closed defect (fixed)
ST_OffsetCurve fails for some geometries
| Reported by: | jventin | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 3.6.6 |
| Component: | Default | Version: | 3.4.2 |
| Severity: | Unassigned | Keywords: | |
| Cc: |
Description (last modified by )
Please refer to discussion:
http://osgeo-org.1560.x6.nabble.com/Problems-with-ST-OffsetCurve-td5101491.html
Here is another geometry for which ST_OffsetCurve gives same error with offset parameter value -16
01020000A0FB0B00002600000023DBF9FEA6901A41666666A6246F5A410000000000000000B07268911C911A418D976EEA286F5A4100000000000000000AD7A3F0F7981A415A643BD7716F5A4100000000000000003108AC9CC8991A41C74B3791576F5A4100000000000000004E6210584D9A1A41AC1C5A2C456F5A410000000000000000BA490C827B9A1A411058392C3A6F5A4100000000000000002DB29DEF899A1A4114AE4799326F5A4100000000000000008195438B619A1A418195431B2C6F5A4100000000000000004C3789C1109A1A414C3789A1236F5A4100000000000000006891EDFC9C991A41986E124B1D6F5A410000000000000000643BDFCF2C991A41DF4F8DCF186F5A410000000000000000F6285C0FC2981A41F2D24D620A6F5A410000000000000000448B6C67B9981A41A69BC498066F5A410000000000000000A01A2F5DAB981A416ABC74CB026F5A4100000000000000001B2FDDA47B981A41295C8F2A016F5A410000000000000000B6F3FDD47A961A41022B8796EF6E5A410000000000000000E17A14AE83961A4114AE47A9F16E5A410000000000000000105839B4F1961A418B6CE7BB0B6F5A41000000000000000048E17A94A1981A41F4FDD498246F5A410000000000000000E7FBA971EE981A4117D9CE67356F5A410000000000000000B29DEF27F0981A4191ED7CC7356F5A41000000000000000060E5D0A290981A41B07268093D6F5A4100000000000000008FC2F5A838981A415A643B473C6F5A410000000000000000D578E9A62A971A412731080C5A6F5A410000000000000000022B871644961A41105839B4516F5A4100000000000000006210583950961A4119045696416F5A4100000000000000007D3F35DE7B951A41FA7E6A742A6F5A4100000000000000003108AC9C36961A41EE7C3F6D0B6F5A4100000000000000008716D94EEB951A41E5D022ABEA6E5A4100000000000000004E62105825951A41DBF97EE2E36E5A4100000000000000003BDF4F0DCF931A41643BDF27D86E5A4100000000000000002FDD2406CA921A41CFF753DBEC6E5A4100000000000000005A643BDFD7911A41560E2DE2016F5A4100000000000000008B6CE77B1F911A41F0A7C683096F5A410000000000000000A4703D8A5E901A41B29DEF9F186F5A410000000000000000BC7493980E901A41A8C64B1F1F6F5A4100000000000000001283C0CA2B901A41E17A142E206F5A41000000000000000023DBF9FEA6901A41666666A6246F5A410000000000000000
Change History (11)
comment:1 by , 10 years ago
comment:5 by , 6 years ago
| Milestone: | 3.6.3 → 3.6.4 |
|---|
comment:7 by , 5 years ago
| Description: | modified (diff) |
|---|
comment:8 by , 3 years ago
A cross-reference to what I think is another example of this error using parallel_offset on a LineString in Shapely.
comment:10 by , 4 months ago
This appears to be fixed now. The provided test case works and gives a reasonable result.
comment:11 by , 4 months ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
It should be added that I have encountered this problem only with polygons. When switching start and end point for the geometries causing errors, it seems that the offset function will give a result (not error).