Timeline for Simplification by constrained anti-aliasing in PostGIS
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 26, 2022 at 17:23 | comment | added | dr_jts | The JTS algorithm is doing a fair bit more work to prevent invalidity occurring (but it's more general-purpose as well). My guess is that it is too complex to consider porting it to SQL - but feel free to try! | |
| Apr 26, 2022 at 15:12 | comment | added | geozelot | @dr_jts yeah I mentioned that it will only work with simple Polygons - as in valid. I'll go through your JTS algorithm later, see how you handle some of the ambiguities. | |
| Apr 26, 2022 at 14:48 | comment | added | dr_jts |
Clever! There might be an issue if the "raster" polygon boundary loops back on itself and touches, but that can probably be taken care of by ST_MakeValid.
|
|
| Apr 26, 2022 at 14:02 | history | edited | geozelot | CC BY-SA 4.0 |
added 26 characters in body
|
| Apr 26, 2022 at 13:48 | history | edited | geozelot | CC BY-SA 4.0 |
deleted 27 characters in body
|
| Apr 26, 2022 at 13:24 | history | edited | geozelot | CC BY-SA 4.0 |
added 235 characters in body
|
| Apr 26, 2022 at 13:12 | comment | added | geozelot | OP let me know how well this does on real data. @dr_jts since I have not tested for robustness - any immediate issues you can see? | |
| Apr 26, 2022 at 13:08 | history | answered | geozelot | CC BY-SA 4.0 |