Timeline for GDAL Warp cutline invalid
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4, 2019 at 10:27 | vote | accept | Francis | ||
| Dec 3, 2019 at 18:08 | answer | added | user30184 | timeline score: 1 | |
| Dec 3, 2019 at 17:33 | comment | added | Francis | I've upgraded to 3.0.2 as well and I can confirm that has fixed it for me! If you want to add that as an answer I'd be happy to accept it. Unfortunately I have other issues with 3.0.2 and pyinstaller at the moment so I'll have to ask another question as well. | |
| Dec 3, 2019 at 17:18 | comment | added | user30184 |
I put your coordinates into WKT POLYGON, converted it into shapefile and used it as cutline for gdalwarp. gdalwarp test.tif out.tif -cutline cutline.shp. I did not get any errors. GDAL version is 3.0.2.
|
|
| Dec 3, 2019 at 16:25 | comment | added | Francis | It's a two step process, first the linestring is buffered into a polygon and saved to a shapefile, this shapefile is then passed directly to gdal warp. | |
| Dec 3, 2019 at 15:43 | comment | added | user30184 | The geometry is valid but it is quite large. How do you pass it to GDAL? Could it be possible that the input gets truncated because of too long string? | |
| Dec 3, 2019 at 15:01 | history | asked | Francis | CC BY-SA 4.0 |