Timeline for GDAL only reads one hole from Polygon in KML depending on wrapping of innerBoundaryIs
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2023 at 13:56 | answer | added | Andy Harfoot | timeline score: 0 | |
| May 8, 2018 at 18:22 | vote | accept | Cameron Bieganek | ||
| May 8, 2018 at 9:39 | answer | added | Spacedman | timeline score: 5 | |
| May 7, 2018 at 22:22 | history | tweeted | twitter.com/StackGIS/status/993616993579421703 | ||
| May 7, 2018 at 21:48 | comment | added | user30184 | Contact your ESRI support and ask if they have a bug in their product. Or the bug can be in GDAL and LIBKML even the latter is the reference implementation by Google gdal.org/drv_libkml.html. | |
| May 7, 2018 at 21:05 | comment | added | Cameron Bieganek | Perhaps I should elaborate. Many parts of the process are automated, but I think the source of the KML is typically a shapefile converted to KML within ArcGIS. Please don't ask me why we convert shapefiles to KML... :) | |
| May 7, 2018 at 21:02 | comment | added | user30184 | See also stackoverflow.com/questions/12037297/… | |
| May 7, 2018 at 20:54 | comment | added | user30184 |
I believe that you should fix the automatic process. From developers.google.com/kml/documentation/… I can read <innerBoundaryIs> Contains a <LinearRing> element. A Polygon can contain multiple <innerBoundaryIs> elements, which create multiple cut-outs inside the Polygon. Unfortunately the specification is not very exact about inner boundaries and linearrings.
|
|
| May 7, 2018 at 20:37 | review | First posts | |||
| May 7, 2018 at 20:41 | |||||
| May 7, 2018 at 20:37 | history | asked | Cameron Bieganek | CC BY-SA 4.0 |